Rebuild a weekly team meeting agenda so it's not just a status readout everyone tunes out of

This team's weekly sync has a specific problem, described below, and I need a redesigned agenda plus the actual facilitator language to make the new structure stick, not just a new template that quietly reverts to the old pattern within a month.

TEAM AND MEETING CONTEXT
8-person product team, weekly Monday sync, spans design, engineering, and product management.

CURRENT AGENDA AND WHAT'S WRONG WITH IT
Every person gives a 3-4 minute status update round-robin, eating 40 of the 45 minutes, leaving no real time for the cross-team blocker that's actually been stuck for two weeks.

WHAT ACTUALLY NEEDS TO HAPPEN IN THIS MEETING
Unblocking a decision on API contract ownership between two engineers who disagree, and deciding whether to cut a feature from this sprint.

MEETING LENGTH AND ATTENDEES
45 minutes, all 8 team members plus the EM, every Monday at 10am.

Redesign the agenda around the stated actual needs — typically real cross-team blockers, decisions that need a room full of the right people to make, and anything genuinely better discussed live than async — and explicitly move anything that's pure status (what did you do this week) out of the live meeting and into an async pre-read the team posts before the meeting starts, since status information doesn't need a synchronous meeting to transmit and the current-agenda-problem almost always traces back to exactly this kind of content eating live time it doesn't need. For each live agenda item, name who owns bringing it and what decision or output the meeting should produce by the end of that item, not just "discuss X," since an item with no defined output is what causes discussions to run long and go in circles. Give the facilitator two or three specific phrases to use in the room when the meeting starts drifting back into status-update mode ("let's take that to the async doc and come back to the blocker") — the redesign will not survive contact with an established meeting habit unless the facilitator has ready language for the moment it starts sliding back, not a rule that only exists on paper.

WHAT NOT TO DO
Do not simply relabel the same status-update items with new section headers — if an item genuinely doesn't need live discussion, cut it from the live meeting entirely rather than keeping it under a different name.

OUTPUT FORMAT
1. The async pre-read template (what goes there instead of live time).
2. The live meeting agenda (item, owner, intended output, rough time).
3. The facilitator's redirect phrases for when old habits resurface.