Skip to content

docs(rfc): move solo-spawn gate RFC to in-progress while its removal is in flight - #13705

Merged
iamwhatever merged 1 commit into
mainfrom
docs/rfc-solo-spawn-gate-in-progress
Sep 25, 2026
Merged

iamwhatever merged 1 commit into
mainfrom
docs/rfc-solo-spawn-gate-in-progress

Conversation

@iamwhatever

Copy link
Copy Markdown
Contributor

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, reads superseded on main (from #13511), and the lane's closed set of decision statuses is accepted, in-progress, partial, implemented. superseded is 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-progress means "Implementation is live in an open PR or an active branch." That is exactly where the removal is.

File Change
docs/request-for-change/rfc-solo-spawn-gate.md status: in-progress; implementation-prs adds 13458; audited-at moves to 2fbd88d07a; the status line says the removal is live in #13458 and the doc moves to superseded once it merges
docs/request-for-change/README.md The index row reads in-progress with the same wording, and the audit paragraph records the move

Docs only. No code, prompt or test changes.

Backwards compatibility

Compatible: documentation status change only.

Tests

None. scripts/docs_lint.py --test and scripts/docs-lint.sh pass; the comment-history and changelog-history gates pass on the diff.

Manual verification

  • git ls-tree 2fbd88d07a src/kiro_crew/solo_spawn.py shows the gate file still on main at the audited SHA.
  • README row, RFC front matter and RFC status line all read 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

  • Docs-only change; lint gates pass locally

@iamwhatever
iamwhatever requested review from a team and chenmingwei23 September 25, 2026 06:02
@github-actions github-actions Bot added the readiness: checking Automated validation is still running label Sep 25, 2026
@github-actions

github-actions Bot commented Sep 25, 2026 •

Copy link
Copy Markdown
Contributor

GPT 5.6 Review — ✅ no blocking findings

GPT 5.6 completed its review of 482c309cc02e5df899b37b2e9f112801bc1d0d48 and found no blocking issues.

This comment is updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] 482c309

False positive or not applicable? A repository writer can comment:
/ai-review override gpt 482c309cc02e5df899b37b2e9f112801bc1d0d48: <one-sentence reason>

@github-actions

github-actions Bot commented Sep 25, 2026 •

Copy link
Copy Markdown
Contributor

Design Review (Fable 5) — ✅ PASS

Design-level review of 482c309cc02e5df899b37b2e9f112801bc1d0d48 — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS/CONCERNS are advisory.

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

@github-actions

github-actions Bot commented Sep 25, 2026 •

Copy link
Copy Markdown
Contributor

Opus 5 Review — ✅ no blocking findings

Reviewed 482c309cc02e5df899b37b2e9f112801bc1d0d48 — this comment is updated in place on each push.

Review details

No findings.

[OPUS-REVIEWED] 482c309

Verdict parsed from the review's SHA-scoped output markers for commit 482c309cc02e5df899b37b2e9f112801bc1d0d48.

False positive or not applicable? A repository writer can comment:
/ai-review override fable 482c309cc02e5df899b37b2e9f112801bc1d0d48: <one-sentence reason>

@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention readiness: checking Automated validation is still running and removed readiness: checking Automated validation is still running readiness: action required A blocking check or review needs attention labels Sep 25, 2026
@github-actions github-actions Bot added the merge conflict Branch has merge conflicts with its base — author must resolve before merge label Sep 25, 2026
@iamwhatever
iamwhatever force-pushed the docs/rfc-solo-spawn-gate-in-progress branch from 9e411a2 to 482c309 Compare September 25, 2026 17:19
@iamwhatever

Copy link
Copy Markdown
Contributor Author

Rebased onto fresh main (new head 482c309cc0) to resolve a conflict in docs/request-for-change/README.md's index paragraph, where main independently added later RFC audit sentences to the same paragraph this PR's sentence appends to. Kept both additions, in order. Doc gates (docs-lint, comment-history, changelog) pass; CI re-running.

@github-actions github-actions Bot added readiness: checking Automated validation is still running readiness: action required A blocking check or review needs attention and removed readiness: action required A blocking check or review needs attention merge conflict Branch has merge conflicts with its base — author must resolve before merge readiness: checking Automated validation is still running labels Sep 25, 2026
@iamwhatever

Copy link
Copy Markdown
Contributor Author

RFC doc only, merge

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant