After two bless walks and a bunch of research, here's the status. What you've already locked, what's still open, and what happens next.
These came back from the v2 walk with a clear bless. They're now treated as decided, won't show up in v3 with toggles. Final.
standing: true in their handoff frontmatter. No special prefix.# SL-0.6: Title, not the long dash.AL-1.3 as a tag, handoff-AL-1.3-naming-research.md as a filename.These will show up in the v3 walk for you to bless or redirect. Each gets its own card with the latest thinking.
AL1-0.2 shape across all workshops?AL1-..., or do they stay as AL-... forever? (My lean: stay forever; new ones use the new shape.)RL (rules lab) need a mission number even if it only ever has one mission? (My lean: opt-in. Small workshops skip it.)0a.X, named suffix 0.orch.X, frontmatter role: only, or use a different major. (My current lean: named suffix.)~/.claude/rules/chat-naming.md so it applies to every workshop, not just AL. (Almost-locked; you said this in v2.)chat_name: to chat-name: for full consistency? (My lean: keep underscores; YAML/tooling expect them.)You don't have to know your answer to any of these right now. Bless walk v3 will give each one a button + a text box. You read each card, hit bless or redirect, leave a note if you want to change something, hit submit.
Partially yes. Investigation came back with the full picture:
From the CLI: when you spawn a Claude chat from the terminal, pass -n "your-name":
claude -n "AL2-1.5 naming-research"
This sets the name from day 1. /resume picker shows it correctly. ✓
Inside an active chat: run /rename AL2-1.5 naming-research. Claude Code writes the new name into the session's internal storage. ✓
The VS Code sidebar tab title is auto-generated from your first message. It doesn't refresh when you /rename — you have to close the tab and reopen it to see the new title. There are open GitHub issues asking for this fix; not implemented yet.
When the handoff-creator skill writes a new handoff file with chat_name: AL2-1.5 in the frontmatter, it can also output the exact command at the bottom: claude -n "AL2-1.5 naming-research". You copy-paste, the chat opens pre-named. Tiny enhancement, big win.
Four clear steps left, in order:
You and I chat through the 8 open items above. Pick the easy ones; surface the hard ones; leave anything genuinely unclear for v3.
I generate a new HTML walkthrough — fresh shape, drops the "Beginner" header, uses all three buttons consistently. Roughly 22 cards covering everything still open.
A fresh chat reads the whole updated proposal cold and tries to break it. Surfaces edge cases, future failure modes, anything we missed. You get a written report.
A new chat takes the final proposal and writes it to ~/.claude/rules/chat-naming.md (global). Done. The rule auto-loads in every future session.
Two enhancements queue up: (1) the handoff-creator skill outputs claude -n commands; (2) the bless-walk format itself becomes a documented pattern in a ~/lab/reports/retros/bless-walks/ folder, so the design improvements compound across walks.
The pattern works. The drifts are identified. The new ideas (mission + multi-seat) have proposals. The chat-rename mechanism is mapped. All the research is done.
What's left is one bless walk + one red-team + one install. A few hours of work spread across three small dispatches. Then the rule is live and you stop reinventing this stuff every time you start a chat.
Drop a message that answers the 8 open items above (even quick partial answers — "lean toward your pick" works). I'll bake them into bless walk v3 and ship it.
AL1-0.2) adds a big-initiative number to the prefix. Multi-seat handling needs a way to disambiguate when two seat types share a major.claude -n at the CLI, or /rename inside a chat. The VS Code tab title is the only stale piece.