Repository navigation
docs(rfc): screen 02 records the returning-visit landing on the MRU crewmate - #13169
Conversation
…recently-used crewmate
GPT 5.6 Review — ✅ no blocking findingsGPT 5.6 completed its review of This comment is updated in place on each push. Review detailsNo findings. False positive or not applicable? A repository writer can comment: |
Design Review (Fable 5) — ✅ PASSDesign-level review of Design-Verdict: PASS Verify the added tiebreaker specifics (browser-remembered first, activity fallback, sub-medium roster landing) match the product owner's call, not #12924's implementation. [DESIGN-REVIEWED] 20c819e |
Opus 5 Review — ✅ no blocking findingsReviewed Review detailsNo findings that block the merge. FINDING — docs/request-for-change/rfc-crewmates-launch.md:340 — the [OPUS-REVIEWED] 20c819e Verdict parsed from the review's SHA-scoped output markers for commit False positive or not applicable? A repository writer can comment: |
…recently-used crewmate (kirodotdev#13169)
Problem / Motivation
docs/request-for-change/rfc-crewmates-launch.md(accepted) decides screen 02 as the empty state, the New crewmate dialog and the post-create open, and says nothing about what the Crewmates tab shows to a returning person who already has crewmates. That default was the product owner's explicit call for the launch — with crewmates present, open the most-recently-used chat — and it was recorded in the original screen 03 text, which #13032 replaced with the startup prune. The First Principles lane reads product shape off the base branch, so the RFC on main must carry the decision the implementing PR (#12924) ships.Why it matters
Until the RFC records the landing rule, #12924 is blocked as a product-shape change without an RFC, and the launch's decision record is silent on the screen every returning user sees first.
What changed (motivation → approach → change)
Docs only, one file. Screen 02 gains one decided bullet and one paragraph of reasoning:
The reasoning paragraph says why: the tab is a place to talk to a teammate, not a menu of them; a returning person wants the conversation they left; the roster stays one column away; this replaces the earlier "the user picks" default (#11763), which predated crewmates having conversations worth returning to; a wrong guess costs one click and loses nothing.
Two references are updated so the RFC agrees with itself:
implementation-prsin the front matter gains 12924, and the § 8 branch entry forfeat/crewmates-page-empty-createbecomes the #12924 link naming the landing. Every other line of the RFC is byte-identical.Backwards compatibility
Compatible: a documentation change.
Tests
N/A — docs only;
scripts/docs-lint.shpasses.Manual verification
N/A — docs only.
Related Issues
no linked issue: amends the accepted launch RFC for #12924.
Checklist
feat|fix|docs|refactor|perf|test|chore|ci|build|revert: ...)