Repository navigation
docs(rfc): move solo-spawn gate RFC to in-progress while its removal is in flight - #13705
Conversation
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 First Principles lane on #13458 actually goes green once this merges — the whole PR exists to clear that gate. [DESIGN-REVIEWED] 482c309 |
Opus 5 Review — ✅ no blocking findingsReviewed Verdict parsed from the review's SHA-scoped output markers for commit False positive or not applicable? A repository writer can comment: |
9e411a2 to
482c309
Compare
|
Rebased onto fresh main (new head |
|
RFC doc only, merge |
Problem / Motivation
The First Principles review lane blocks #13458, the PR that removes the solo-spawn gate. Its reason: the RFC that records the removal decision,
docs/request-for-change/rfc-solo-spawn-gate.md, readssupersededon main (from #13511), and the lane's closed set of decision statuses isaccepted,in-progress,partial,implemented.supersededis defined as "Replaced" and counts as no decision.Why it matters
Until the RFC status is in the closed set, #13458 cannot pass PR Readiness without a maintainer override, and the RFC index misstates the state of the gate: it is still live on main, not yet replaced.
What changed (motivation → approach → change)
The README's own status vocabulary has the right word:
in-progressmeans "Implementation is live in an open PR or an active branch." That is exactly where the removal is.docs/request-for-change/rfc-solo-spawn-gate.mdstatus: in-progress;implementation-prsadds13458;audited-atmoves to2fbd88d07a; the status line says the removal is live in #13458 and the doc moves tosupersededonce it mergesdocs/request-for-change/README.mdin-progresswith the same wording, and the audit paragraph records the moveDocs only. No code, prompt or test changes.
Backwards compatibility
Compatible: documentation status change only.
Tests
None.
scripts/docs_lint.py --testandscripts/docs-lint.shpass; the comment-history and changelog-history gates pass on the diff.Manual verification
git ls-tree 2fbd88d07a src/kiro_crew/solo_spawn.pyshows the gate file still on main at the audited SHA.in-progress.Screenshots / video
N/A: docs only.
Related Issues
no linked issue: unblocks #13458, which is a PR, not an issue.
Pattern harvest
N/A: docs-only status change, no fix pattern to record.
Checklist