Repository navigation
docs(rfc): re-audit kas, jev and early-l RFC status - #39830
Conversation
First Principles Review (Opus 5.5) — ⏭️ skippedRevision |
UX Review (Opus 5.5) — ⏭️ skippedRevision |
Design Review (Opus 5.5) — ✅ PASSDesign-level review of Design-Verdict: PASS This is a docs-only status sweep, so nothing blocks. Both status changes match the tree: [DESIGN-REVIEWED] a7e693a Description read[DESCRIPTION-READ] 048b05b0d0b91304e94c8fb8d5caea807afc9be384e59015852db86cb4ec3728 That sha256 names everything this verdict read: the PR description, plus the 1 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with |
GPT 6.1 Review — ✅ no blocking findingsGPT 6.1 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: |
Opus 5.5 Review — 🔴 changes requested (blocking)Reviewed The RFC index in BLOCKING — docs/request-for-change/README.md:45 [BLOCK-MERGE] a7e693a Verdict parsed from the review's SHA-scoped output markers for commit False positive or not applicable? A repository writer can comment: |
Problem / Motivation
Goal: RFC status fields match what main implements.
Why it matters
The First Principles review lane and readers trust each RFC's
status; a status behind main misleads both.Not a goal
docs/request-for-change/README.md(handled by a separate finisher PR).What changed (motivation → approach → change)
Re-audited each RFC's
status,last-auditedandaudited-atagainst main.rfc-kas-session-head-in-agent-prompt:accepted->implemented. perf(kas): send a new chat's session-stable blocks as the agent prompt #37108 shippedsession_head.py, read byacp/harness/kas.pyandcontext_assembly/turn_message.py.rfc-jev-task-executor:accepted->partial. Rollout step 2 is on main (NoulandScoreindecisions/types.py, feat(decisions): add noul and score question types #16014);jev_executor/,jev_computer_taskanddispatch_structuredare not.rfc-issue-radar-dispatch,rfc-kas-own-engine-route,rfc-kiro-sign-in-card-extension,rfc-large-session-bounded-restore,rfc-leaked-runtime-reclaim,rfc-living-ui,rfc-local-notification-bus,rfc-main-spec-start-recovery: status still matches main; audit keys bumped.Backwards compatibility
Compatible: documentation front matter and status prose only.
Removes nothing: no RFC body, key or file is removed.
Tests
Proof: not provable -- docs or config only.
./scripts/docs-lint.shexits 0.Manual verification
Each status was checked by grepping the named deliverables (definition and caller) on main and reading the listed PRs with
gh pr view.Real-machine verification
N/A -- docs only, the diff runs nothing.
Related Issues
N/A -- periodic docs sweep.
Checklist
feat|fix|docs|style|refactor|perf|test|chore|ci|build|revert: ...); PR Hygiene does not count commitsContribution License Agreement