<!--
Session-wrap template (FLY-990). This is the body posted as the project
update at session end — a standup for the team, read by people who did NOT
do the work. Fill each section, then pass the filled text as the `body` of
`session_wrap`, alongside `health: onTrack|atRisk|offTrack`. Runner fallback:
`flydocs run session.wrap --health <onTrack|atRisk|offTrack> --file <a filled
copy under .flydocs/scratch/>`.

RULES (enforced by the wrap — it will refuse to post otherwise):
- Accomplished, Next up, Blockers & open questions, and Progress are REQUIRED.
- Blockers: write "None" if there are none — never leave it empty.
- Notes is OPTIONAL: delete the whole section (header included) if empty.
- Health is passed as its own argument and rendered as the opening label.

WRITING FOR THE READER (a non-technical teammate/stakeholder):
- Lead with outcomes in plain language. What changed and why it matters.
- No issue codes in prose. They belong ONLY in Progress.
- Keep Accomplished to ~6 bullets; group related work rather than listing every commit.
-->

## Accomplished

- [What shipped, outcome first — e.g. "Moved the GitHub integration to read-only access so enterprise clients no longer dead-end on approvals."]

## Next up

- [What the next session picks up.]

## Blockers & open questions

- [Anything waiting on a person or decision, and who — or "None".]

## Notes

- [Optional context worth surfacing. Delete this whole section if empty.]

## Progress

[N] issues closed ([FLY-refs]). [One line on overall project status.]
