fix: deliver the handoff brief to the slash commands

[d6veteran]

Session handoff briefing was listed as aspirational. It was already built. Planning this turned it inside out.

175 tests (was 170). shellcheck clean.

What was actually there

	Before
Profiles defining a ### Handoff Brief	17 / 17
Generated subagents carrying it	17 / 17
Generated /name slash commands carrying it	0 / 17
Coordinator profiles instructing the persona to produce one	2 / 2

Byte-identical opening and closing stems across all seventeen. Three DEVLOG entries treat "3 behaviors + handoff" as a structural invariant. The ROADMAP entry was written by paraphrasing the already-shipped robin.md text.

The defect, and why it landed on the worst possible surface

### Handoff Brief sat inside ## Required Interactive Behaviors, which strip_interactive_behaviors excises from every slash command.

profiles/coordinator.md:126 tells the user, at the exact moment of a handoff:

"We're moving into [domain] territory — want to switch to [Name]? Run /[name] right here to switch for this session, no restart needed."

and :128 then instructs the coordinator to ask that persona for a Handoff Brief.

The asker had the instruction. The answerer, on the path the coordinator itself recommends, had never been told what a Handoff Brief is. It would have to improvise from the coordinator's one-line description.

The fix

### Handoff Brief becomes ## Handoff Brief. This codifies what the structure already implied — the section was deliberately left unnumbered while its siblings are ### 1., ### 2., ### 3.

The stripper's end marker moves from ## Signature Question to ## Handoff Brief, so the excised range ends one section earlier. Position in the profile is unchanged.

Generator guard added. The generator now aborts on a profile with no ## Handoff Brief, matching the existing ## Greeting guard. Not ceremony: the stripper resets skip on that marker, so a profile without it would silently drop every later section from the slash command. The same latent failure mode exists today with ## Signature Question and goes unnoticed only because all seventeen happen to have one.

The drift test asserted the gap as correct, since its awk mirrors the stripper. Both moved in lockstep.

Parallel sessions had the same shape of gap

A session prompt carried Persona, Task, File scope and nothing about what had already been decided, so each session re-derived context it was never given. The /parallel template also seeds sessions with /akira — the same stripped surface.

Both coordinator profiles and commands/parallel.md gain a fourth Context field. A finished session with dependents writes a Handoff Brief that becomes the downstream session's Context.

Prompt-only, per your call: no new files, no stored state, no CLI surface. That also keeps it clear of the shared-state locking the branch index needed.

Verification

• All five new tests fail on the previous tree. One removes the section from a profile in a throwaway copy and requires the generator to refuse, so the guard is proven rather than assumed.
• Agents changed by exactly one heading level per file and nothing else — verified by reducing the whole 17-file diff to its unique change shapes, which are ### Handoff Brief → ## Handoff Brief and nothing more.
• All four delivery surfaces confirmed end to end: profiles 17/17, agents 17/17, commands 17/17, and cmd_use carrying it into the global pin.

Roadmap

Moved from aspirational to shipped. That empties the aspirational list, since the other two items were retired in #23, so it now reads as an invitation to open an issue rather than an empty heading. Existing dated revision rows unchanged.

---

Generated by Claude Code