Write a weekly status update people actually read.

It's Friday afternoon. Slack pings you for the weekly update. Your options are (a) skip it, (b) write a two-line 'still working on the same stuff', or (c) write the update your manager can forward without editing. This is option (c).

Write me a weekly status update for my manager. I'll paste bullets of what I did this week below. Structure the update in exactly this format, in Markdown:

**Shipped**
- One bullet per thing that reached completion. Keep it factual — no "I'm proud to say".

**In flight**
- One bullet per thing that's mid-progress. Include the specific next step and when it lands.

**Blocked or at risk**
- One bullet per thing that is stuck or slipping. Name what would unblock it. If nothing is blocked, write "Nothing." — do not manufacture drama.

**What I need from you**
- Zero to three specific asks of the manager. Each one is a decision, a signoff, or a piece of context, not a status question I could look up myself.

No opening greeting. No closing pleasantry. Under 250 words total. If a section has nothing in it, write "Nothing." — do not skip the section.

Here's the raw material:

[PASTE BULLETS HERE]

• Turn a difficult thread into one calmer reply.
• Turn meeting notes into a decision log.
• Turn a messy Slack thread into a one-pager.