docs(j5): record the Crews design sessions

[bryantderosier]

The worklog record for the Crews work: the move from a definition file to a proposed roster, the consolidation onto the shared handoff files, the review findings and the decisions that closed them, the stop and archive verbs, the review of the merged agents stack's feedback and what changed on the branch because of it, and the migration re-issue. Nothing but the record; the definitions it points at landed in the earlier PRs of this stack.

Built with Claude Fable 5.1 in Claude Code.

🤖 Generated with Claude Code

Closes #208.

[Jacksondr5]

The new decoupling record is accurate and supersedes the persona-launch story in the 2026-09-14 record. One request: the 2026-09-14 record's pre-push review section still presents the escalation guards as fixes that landed. A one-line pointer there to the 147 ruling (no parent-child ceiling, 2026-09-16) keeps a future reader from taking them as current. Nothing else.

Reviewed by Claude Fable 5.1 in Claude Code, with an independent pass by GPT-6-Astra in Codex.

[bryantderosier]

The pointer is in 144af7235, and the record also logs the three decisions from this round (the server guard, the boot sweep, the Crew record before seats) with what each was chosen over.

[Jacksondr5]

I think we should be able to create crew members that dont have personas. I think this makes it easier to spin up dynamic crews that don't fit a mold you've done before.

Also, idk what that input in the above screen was for.

---

When I asked an agent to spawn a crew, it just made subagents. Is the MCP tooling clear enough that it knows it has a crew tool? I recommend really scrutinizing the MCP tool descriptions if you aren't doing that already, the agents tend to write really bad ones.

---

Is there an icon we can use in place of the captain badge? We're running out of real estate in the card.
Same thing with the crew's names. It looks like their name includes the crew name, which takes up space. Also, idk if the badge and the second part of the name are literally the same piece of data or if I just hit an edge case, but that's also something to clean up. We may want to give guidance to the agents to give them very short names when they spawn them.
Also, did those 2 really settle immediately after completing? AFAIK, settling in Upstream only happens when a PR merges or the user manually settles it. Are we settling these too early? Settling doesn't really do much, I don't think. AFAIK, its purely an organizational thing for top-level agents. Since Crew members are already hidden in a collapsable section and have a 12 member limit, settling them doesn't really do much from a UI ordering perspective.
Lastly, can we see if we can mirror the parent agent's card layout, where the provider icon is on bottom and the time since active is on top?