Alright, let's kick off the Q2 planning. I've pulled the velocity numbers from last sprint — we averaged about 34 points. Given the API migration is still in flight, I want to be conservative with what we commit to.

Yeah agreed. The auth service blocker is the big unknown. Sarah's looking into it but I don't want to promise Friday until we know the scope. I'd say we treat it as a stretch goal for the first sprint and lock it in once we have more clarity, maybe Wednesday?

That works. Let's plan around the assumption that it's resolved by Wednesday and flag it in the risk register. What are your three epics for Q2?

API migration is obviously the big one — that's mine. Then the mobile performance work we pushed from Q1, specifically the list rendering bottleneck. And I'd like to get proper error boundary coverage in place. We keep patching individual screens but we need a real system.

On the design side I'm taking the design system epic — we've been accruing a lot of inconsistency, especially in the settings area. I need a design review session before end of this week to get sign-off before I start generating the component specs. Can we schedule that?

Yes, let's lock in Thursday afternoon. I'll send a calendar invite after this. What's the status on the mobile release? QA was pending on two tickets last I checked.

Tickets 412 and 415 — both need QA sign-off before we can cut the release branch. The mobile release is targeting Tuesday. If those two aren't cleared by Friday we'll need to slip to the following week.

I'll handle QA sign-off on those two today. Last thing — Jake, can you update the migration runbook with the rollback steps before the Friday deploy? I want that documented in case things go sideways over the weekend.

On it. I'll have a draft in the shared doc by Thursday morning. I'll ping you both when it's ready for review.

One more thing — the settings page redesign I mentioned. I'll need engineering estimates for the navigation refactor before I finalize the designs. Can someone look at that in the next sprint?

Put it in the backlog with a design-ready label and I'll assign it at the next sprint kickoff. Alright, I think we've covered everything — good session everyone.