Repository navigation
docs: re-audit request-for-change rfcs against main - #37153
Conversation
9089ecb to
7d61259
Compare
UX Review (Opus 5.5) — ⏭️ skippedRevision |
First Principles Review (Opus 5.5) — ⏭️ skippedRevision |
Design Review (Opus 5.5) — ✅ PASSDesign-level review of Design-Verdict: PASS Nothing blocks: this is a docs-only audit. Statuses only move forward, each backed by a merged PR, no RFC leaves Notes
[DESIGN-REVIEWED] 3689ff2 Description read[DESCRIPTION-READ] 550b1fcd92682411f5524e32b98b6b28c902ee8a66dee150e2d51f1b8a92a6ef 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 |
Opus 5.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: |
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: |
7d61259 to
2405973
Compare
Code change approver recommendation: A person should decideWhy: the decider estimates a 7% chance that this change introduces a defect, within the 12% limit for approving on its own, but it changes 912 lines, more than the 400 it may approve on its own. Docs-only audit of the request-for-change RFCs against main, approved. Every front-matter status change moves forward (accepted/in-progress to partial/implemented, three partial to implemented), and no RFC enters or leaves draft. The First Principles lane counts any status other than draft as a recorded decision (first-principles.md:466-485), so nothing it enforces gets looser. Spot-checks of the cited code all matched the repo: browser_harness/, _close_managed in conductor_close.py, followupStartSends.ts, crewFirst, spawn_impl in admission/gate.py, UNADVERTISED_AGENTS in spawn_allowlists.py:45, REMOVED_PROVIDERS, recall_pool_processes, _ask_question_blocking, mate_config.py and its migration, acp_failover.py, fold_delta.py, messaging/cards/*, pre_push_gate.py, WORK_CLOSED_WINDOW = 32, MATE_ROOT_FIELD, HEARTBEAT_INTERVALS, STEER_GRACE_SECONDS, worker_session_defaults, McpRedirect, isDiffCardItem, _install_team_lead_agent and others. DEFAULT_GOAL_ITEM_CAP and item_cap_notice are gone from src, as the PR says. Tests that read RFC text need exact strings that the PR leaves in place. The cli.md row matches the parsers in cli_parser_agent.py. An automated recommendation, not a review: a maintainer still decides. It approves on its own only when the estimated chance of a defect is at most 12% and the change has at most 400 changed lines. Decider v3c (217fe607) · commit |
2405973 to
3943dd4
Compare
|
3943dd4 to
200ff3a
Compare
5cdd1ad to
b0b52ec
Compare
KiroCrewCaptain
left a comment
There was a problem hiding this comment.
Thanks for the careful audit. One status in this PR does not match main and needs a fix before merge.
docs/request-for-change/rfc-remove-piper-tts.md:3(also line 17 anddocs/request-for-change/README.md:196). The PR marks this RFCimplemented. A reader of the index or the First Principles lane will conclude that Piper is fully removed. But the RFC's own Decision 3 (line 38) and rollout exit 3 (line 55, "the demo-recording skill and thedev-fleetspec no longer name Piper") are not met on main. The dev_fleetfeature-demo-recording/SKILL.md:92still offers--provider piperas whatautopicks. Line 144 says "--provider autoprefers piper", andreferences/deps.py:150-156still resolvesautoto piper. The PR body also lists this file under "Gaps for maintainers (files not changed for status)", which contradicts the diff. Smallest fix: setpartialin all three places. Say that Decisions 1, 2 and 4 shipped in #23189 and that Decision 3 (the dev_fleet demo-recording skill) is still open. Keepimplementation-prs: [23189].
Optional:
- The body's gap note for rfc-conversation-trust-follows-founder says no founder trust logic is on main. Main has it in
subagent_manager/turn_session.py(_founding_session,resolve_parent_policy), so the suggestion to withdraw that RFC rests on a wrong premise. - The kept rfc-browser-live-harness row (README.md:50) still opens with "no
browser_harnesspackage exists". The dated correction is attached without a sentence break. Consider adding the break, or putting the correction first. - The gap list heading says "files not changed for status", but rfc-crewmate-profile-settings.md is also moved to
implementedwhile its gap entry says the scope widened. Please confirm the widened part is built, or usepartial.
Bring every RFC's status and current-code references in line with main at 1d08e94, and fix the README index: one row per RFC, status text that matches each document, and notes where a status is a maintainer decision.
Decision 3 of rfc-remove-piper-tts is not on main: the dev_fleet feature-demo-recording skill and the dev-fleet spec still offer piper and have auto pick it. The RFC and its index row now read partial. The rfc-browser-live-harness row no longer opens with a claim that the browser_harness package is absent, and the rfc-conversation-trust-follows-founder row records that founder trust shipped in #30632.
b0b52ec to
3689ff2
Compare
|
Thanks. Fixed in 3689ff2 (rebased onto main first). Required: PR body. The piper entry is gone from the gap list, and the "Changed files" row for it now says Class swept: the gap-list heading said "files not changed for status", but Optional points.
Checks: |
KiroCrewCaptain
left a comment
There was a problem hiding this comment.
Thanks for the fixes. On this head the review checked these things. Every added implementation-prs number is a merged commit on main. Every status moves forward only. Each README index row matches its document's front matter. The new memory flags in the cli.md row match cli_parser_agent.py. The strings that the RFC-reading contract tests pin are unchanged.
Earlier review items:
rfc-remove-piper-ttsstatus: fixed. It readspartialin the front matter (line 3), the status line (line 17) and README.md:196, and it names Decision 3 as still open.- Founder trust gap note: fixed. The note and the README row now cite #30632 and
resolve_parent_policy. rfc-browser-live-harnessrow: fixed. It now opens with what main has.rfc-crewmate-profile-settings: rebutted with evidence that holds. The section 3 rules are built, soimplementedstands.
Done well: where the code shows only part of a design, the PR uses partial and names the open phase. Status calls that are out of scope go to a maintainer gap list and are not edited.
The design is signed off under the standing maintainer sign-off for changes by team members.
Optional:
- README.md:80 (rfc-remote-computer-use) still says the browser pull channel serves a local gateway. #26950 removed that channel. Also, rfc-crewmate-workers-under-the-crewmate.md:19 still calls rfc-mate-owned-agent-config
accepted. - Some rows still say "Nothing yet" or "Nothing on main" while main has the code. Examples: workflow-library-removal (#27528), acp-backend-failover and fold-delta-push. The dated "Built on main, status left for a maintainer" wording used at README.md:50 would fit them.
- This PR overlaps #30637 (fully) and #30675 (mostly) in README.md. A "Related:" line would help a maintainer close or trim those PRs after this one lands.
…tation PR The RFC index rows this PR first corrected were re-audited on main by kirodotdev#37153, and the piper and idle-compaction documents already list their implementation PRs. One gap is left: rfc-browser-live-harness.md still has an empty implementation-prs, though kirodotdev#26950 (merged 2026-11-04) built the harness. This lists it.
…k has landed The RFC index re-audit on main (kirodotdev#37153) fixed most rows this PR first touched. Two are left: rfc-remote-instance-on-microvm still says the MicroVM backend half (kirodotdev#17540, merged 2026-10-14) is open, and rfc-mate-sessions-folder-or-lineage still calls kirodotdev#26952 open. Both rows now say what merged. rfc-app-contribution-points.md lists kirodotdev#26878 and rfc-mate-sessions-folder-or-lineage.md lists kirodotdev#26952 in implementation-prs.
…k has landed The RFC index re-audit on main (kirodotdev#37153) fixed most rows this PR first touched. Two are left: rfc-remote-instance-on-microvm still says the MicroVM backend half (kirodotdev#17540, merged 2026-10-14) is open, and rfc-mate-sessions-folder-or-lineage still calls kirodotdev#26952 open. Both rows now say what merged. rfc-app-contribution-points.md lists kirodotdev#26878 and rfc-mate-sessions-folder-or-lineage.md lists kirodotdev#26952 in implementation-prs.
Problem / Motivation
Goal: Make every RFC under
docs/request-for-change/say what main does today, so a reader can trust its status and the names it cites.Many RFCs still said
accepted,in-progressor "Nothing built" for work that merged weeks ago. Others cited files, functions and tools that moved or were deleted. The README index had a duplicate row forrfc-browser-live-harness.md, and five rows whose status disagreed with the document's own front matter.Why it matters
The First Principles review lane reads an RFC's
statusfrom the base commit as the record of a product decision. A stale status misleads that lane and every person who reads the index. A path that no longer exists sends a reader to nothing.Not a goal
draft, or intoaccepted: those are maintainer decisions, listed below as gaps.rfc-app-agent-tools-third-party-grant.mdindex row, which docs: index third-party grant rfc and list missing tools and verbs #36750 is changing.What changed (motivation → approach → change)
Each RFC was checked against main at
1d08e941b3: definitions and callers by grep, merged and closed pull requests bygh. The code won every disagreement.partialorimplemented, backed by a merged PRA status moved only forward, with code on main:
accepted,in-progressorpartialtopartialorimplemented. Three moved frompartialtoimplemented(rfc-large-session-bounded-restore.md,rfc-conductor-default-patrol.md, and therfc-terminal-exit-closes-tab.mdindex row, whose document already saidimplemented). Each moved document carrieslast-audited: 2026-11-14,audited-at: 1d08e941b3, and the merged PR numbers inimplementation-prs. The full per-file table is under "Changed files" below.docs/system-specs/modules/cli.md: thekirocrew memoryexport/import/migrate row now names each verb with its flags fromcli_parser_agent.py(kirocrew memory import <file> [--store <name>]among them), so a search forkirocrew memory importfinds it, matchingsrc/kiro_crew/docs/memory-and-learning.md. The row's text is unchanged.Backwards compatibility
Compatible: docs only; no code, config or schema changes.
Removes nothing: the only deleted line is the second copy of a duplicate README index row; the document it points to keeps its other row.
Tests
Proof: not provable -- docs or config only
python3 scripts/docs_lint.py: exit 0 ("All documentation checks passed")../scripts/docs-lint.sh: exit 0.pytest test/test_docs*.py test/test_pr_quality_gates.py test/test_provider_mirrors.py test/test_cli_doctor.py test/test_crewmate_bundle_export.py: 1009 passed, 50 skipped.Manual verification
Every one of the 212
.mdfiles underdocs/request-for-change/(205 RFCs, the index,plans/andassets/) has a line in the audit log: file, verified, errors found, fixed. Each status change was checked withgh pr viewand a grep for the shipped symbol.Related Issues
N/A — routine docs audit.
Checklist
feat|fix|docs|style|refactor|perf|test|chore|ci|build|revert: ...)Gaps for maintainers
These need a person's decision; the README row for each says so where relevant. Some of these files were still moved forward on code evidence (the entry says so); the open decision is what remains.
rfc-browser-live-harness.md: draft whose code is on mainrfc-chat-backend-selection.md: draft, part of the idea may be on mainrfc-crew-log-telemetry-export.md: draft whose code is on mainrfc-crewmates-launch.md: status probably stale (accepted -> implemented?)rfc-dashboard-chrome-shell.md: accepted, sole implementation PR closed unmergedrfc-perpetual-agent.md: accepted, sole implementation PR closed unmergedrfc-app-contribution-points.md: draft with its proposals on mainrfc-python-rust-hybrid-backend.md: implementation PR closed unmergedrfc-session-tag-change-event.md: undefined statusin-reviewwith the code now on mainrfc-sandbox-ipc-capability.md: draft with Phase 1 "in flight"rfc-subagent-backend-selection.md: draft with Phase 1 on mainrfc-agent-temp-reclaim.md: draft whose Phase 1 is on main; status is a maintainer decisionrfc-dashboard-card-send.md: draft whose code is on main; status line "Nothing is on main" and implementation-prs [22379] (CLOSED) are stalerfc-remote-instance-on-microvm.md: draft whose code is on main; "Nothing built" banner and index row "Nothing of the design ... cloud/config.py reads a fargate block and no microvm one" are stale; front matter lacks last-audited/aud...rfc-rm-root-row-scratch-entries.md: draft whose code is on main (owner decision recorded in §1 but status not flipped); index row "Nothing built on main" contradicts its own "Built in fix(security): let the rm root row pass a plain rm of /tmp entries #36536"rfc-app-agent-routes.md: draft; its motivation (per-app hand-written tools) changed on main: feat(app-kit): let an app declare agent tools it serves itself #32660 (2026-11-08) added an app-declaredagentToolsseam (src/kiro_crew/apps/app_agent_tools.py) and refactor: serve ops_mission_control_api from the app's agentTools seam #33542 deleted `mcp_too...rfc-conductor-close-asks-first.md: draft; its Implementation line names feat(dashboard): ask before closing a conductor that has open workers #32788, which was CLOSED unmerged on 2026-11-12; nothing on main (no close-count preview). Maintainer: accept/withdraw or name a new implementation PR.rfc-conversation-trust-follows-founder.md:in-progressagainst fix: inherit per-chat trust to subagents at every spawn depth #13109, which was CLOSED unmerged on 2026-11-02. Founder trust is on main from fix: tighten tool approval for continued runs #30632 (merged 2026-11-06):resolve_parent_policyinsubagent_manager/turn_session.pykeeps a continuation's Trust only when_founding_sessionhas it too. Maintainer: decidepartialorimplementedagainst fix: tighten tool approval for continued runs #30632.rfc-crewmate-greeting-as-message.md: accepted; shipped in feat(crew): the crewmate greeting is a message in its chat, not a card #18651 (MateGreetingMessage), then undone by later owner decisions: feat: add return-triggered warm task briefs #20422 (warm task brief as a transcript row,components/chat/WarmBriefCard.tsx) and feat(crew): remove the cold Recap greeting; the warm brief is the only return greeting #23829 (deleted `MateW...rfc-fold-delta-push.md: draft whose code is partly on main: feat(crew-log): ship the work fold as deltas on a base revision, with every reader applying them #24749 (PR c+d, render-diff delta forwork) merged 2026-10-28,src/kiro_crew/crew_log/fold_delta.pyexists; line 17 still reads "Nothing built". Maintainer m...rfc-conductor-remote-dispatch.md: draft whose code is partly on main behind the default-offwork_ledger.remote_dispatchpreview:replyworker status (feat(work-ledger): add the reply worker status behind the remote-dispatch preview #25548, 2026-10-29) and theretire/destroyevent kinds (`src/kiro_crew/wo...rfc-acp-backend-failover.md: draft whose Phase 1 code is on main; status line still says "Nothing is on main"rfc-workflow-library-removal.md: in-progress listing only CLOSED PRs (feat(workflows): remove a saved workflow from the library #19040 impl, docs(rfc): record removing a saved workflow from the library as a tombstone #23393 doc), yet the design is on mainrfc-crew-lts-edition.md: moved accepted -> partial on code evidence (phases 1-3: edition.py build: add a build-time edition constant, default oss #23213, lts_gate/lts_boot/lts_signin_gateway feat: close the enterprise gate until a kiro login is seen #23697 fix: exit an enterprise boot that has no kiro login or no governance rules #23968 feat(enterprise): show a sign-in screen when an enterprise start has no sign-in #26818, enterprise_policy_fetch feat(enterprise): read the governance policy from the Kiro control plane #24661, LTS baseline in evaluator._quer...rfc-crew-owned-oauth.md: statusdraftand status line "Nothing is built", but Crew-owned OAuth is on main behind thecrew_oauthFeature Preview: feat(connections): bridge Crew-owned OAuth per session for claude #33597 (claude bridge), feat(connections): bridge Crew-owned OAuth for codex, copilot, pi and strands #33799, feat(connections): bridge Crew-owned OAuth for goose and deepseek #33882, feat(connections): TickTick on Crew-owned OAuth (DCR), served to expiry without refresh #34213 (TickTick DCR), feat(connections): owner-added MCP servers sign in through Crew-owned OAuth #35692, refactor: remove dead legacy compatibility shims #3...rfc-crewmate-greeting.md: statusaccepted, implementation-prs feat(crew): a crewmate greets you on open with where its work stands #17797/feat(crew): a crewmate opens a new or long-idle chat on a recap of its work #17822 merged, then feat(crew): remove the cold Recap greeting; the warm brief is the only return greeting #23829 removed the cold welcome andmateGreeting.ts; warm half was amended by rfc-delayed-task-brief.md. Maintainer: decide implem...rfc-crewmate-share.md: moved accepted -> partial: Import (feat(crewmates): import one crewmate from a .crewmate file #23424) and Export (feat(members): export one crewmate as a .crewmate file from the profile card #23223) both shipped, then the export format moved to.crewjam(feat(crewmate): export .crewjam files; import still takes .crewmate #26601) and.kirobot(feat: save a shared bot as a .kirobot file #29962). Maintainer: decide implemented, or supersed...rfc-notification-bridge.md: B2 listed WeCom;TRANSPORT_SINKShas discord/telegram/webex/feishu and no WeCom. Maintainer: drop WeCom from B2 or keep partial.Changed files
All 86 changed files and what was wrong
../system-specs/modules/cli.mdkirocrew memory import <file> [--store <name>]was folded into anexport/import <file>/migratelabel, so it did not read as its own CLI entryREADME.mdassets/autopilot-stage-timeout-evidence.mdplans/2026-08-27-agentcore-identity-gateway.mdrfc-achievement-feature-discovery.mdrfc-agent-config-mirror.mdrfc-agent-plugins-standard.mdrfc-agent-started-turns.mdacceptedwhile fmpartial; code has Phase 1+2 (on_agent_turn, dashboard/chat_turn/agent_started.py), label not builtrfc-app-agent-routes.mdmcp_tools/apps.py, deleted by #33542 (agentTools seam #32660)rfc-app-contribution-points.mdapps/link_preview_frame.py, renamed toapps/app_frame.pyby #26875 (frame_csp, CAPABILITY_HEADER, _CAPABILITY_TTL_SECS there); draft whose proposals are now on mainrfc-app-sandbox-isolation.mdpermissions.mcpTools/cronhave no gate; #22965 enforces mcpTools on app agent tools, #19231 checks cron at installrfc-app-sdk-durable-jobs-and-view-state.mdrfc-attended-turn-cap.mdrfc-autopilot-stage-budgets.mdrfc-brokered-delivery-confirmation.mdDeferredTool.on_answeredin mcp_shared_calls.py); proposedrelayedreason not builtrfc-channel-card-catalog.mdrfc-channel-plugin-architecture.mdChannelDescriptorfield list omittedrestart_credentials(messaging/registry.py); other claims verified (10 descriptors in channels.py, link.py parsers,_resolve_alias, slot stop route)rfc-chat-core-extraction.mdrfc-chat-steering-context.mdrfc-composable-layout-mechanism.mdrfc-conductor-chat-board-on-tab.mdrfc-conductor-close-closes-workers.mdrfc-conductor-context-cap.mdCONTEXT_CAP_HIGH_TOKENS = 400_000in dashboard/chat_turn/context_cap.py)rfc-conductor-default-patrol.mdscripts/patrol_budget.pyremoved by #33599rfc-conductor-drift-check.mdacceptedbut #36302 (701e45f) and the amendment's #36618 (551bb52) both merged; goal-conductor/SKILL.md step 5 carries drift check + "re-plan that item now"rfc-conductor-work-ledger.mdkirocrew-work; mcp_work.py now also carrieswork_ask_record(CONDUCTOR_TOOLS, #33805) andaccept_eval(CHECK_TOOLS, #31849).scripts/ledger.py= security-conduct...rfc-connections-mcp-layout.mdrfc-consolidation-fresh-conversation.mdin-progressbut #22207 merged 2026-10-19 andfresh_conversation=True/_start_fresh_conversation(llm_helpers_parts/background_turns.py) are on main, used by history_consolidation_pass.pyrfc-crew-log-wake.mdrfc-crew-lts-edition.mdrfc-crew-panel-default-tab.mdrfc-crewmate-dashboard-upkeep-skill.mdrfc-crewmate-dynamic-dashboard.mdrfc-crewmate-goals.mdrfc-crewmate-greeting.mdrfc-crewmate-guides-and-mate.mdrfc-crewmate-heartbeat.mdacceptedbut #21172 merged 2026-10-21 and the code is on main (member_goals.HEARTBEAT_INTERVALS = (30, 60, 120, 240),goal_reminder.heartbeat_prompt/milestones_card_waiting/gateway_stopping, CrewGoals.ts...rfc-crewmate-page-ambient-motion.mdrfc-crewmate-page-on-goal-wake.mdrfc-crewmate-profile-settings.mdacceptedbut #17836 (ce89f96) is on main:approval_modein config/sections_session.py:397, seed in dashboard/crewmate_approval.py, CrewProfileSettings.tsx, CrewComposer.tsx used by MembersPageThread.tsx. Every §3 rule is built: the profile card sets permission, model and effort, and CrewComposer drops the chips, meter and picker. Later PRs added harness and worker pickers on top; that is extra, not missing, soimplementedholdsrfc-crewmate-responsive-send.mdrfc-crewmate-share.mdrfc-crewmate-workers-under-the-crewmate.mdaccepted+ "Nothing built yet", but migration PRs 2/3/4/6 are on main (#26952 MATE_ROOT_FIELD in crew_mode.py:102, #28869, #28931, #30220 preview in crew_mode.py:585); PR 7 not (chat_folder_file_self still in...rfc-dashboard-chrome-shell.mdflushprop on OverlayDrawer.tsx). Pre-scan "missing" paths are files the plan proposesrfc-delayed-task-brief.mdrfc-deny-session-override.mdrfc-developer-tools-in-settings.mdacceptedthough #24810 merged 2026-10-28 and code is on main (DeveloperPage.tsx redirects to settings tabdevelopersubs, useDevMode.ts/developerMode.ts gone, app-menu.jsvisible: true); `electron/app-men...rfc-drop-goal-item-cap.mdaccepted, but #33601 (1c23741) is on main: noDEFAULT_GOAL_ITEM_CAP/MAX_GOAL_ITEM_CAP/item_cap_noticeleft in src;goal_items_usedkept (spec_prompts.py:399);item_cap_exceededstore code kept as...rfc-followup-start-sends.mdaccepted+ "Nothing ... built on main", but #25926 (11684ff) is on main: FOLLOWUP_START_SENDS_KEY in website/src/pages/chat/followupStartSends.ts, opt-in send + stay-in-place in useChatPageSlotSwitches.ts ...rfc-goal-loop-approval-hold.mdscripts/patrol_budget.pyas present; removed by #33599 (1665165, 2026-11-08)rfc-host-credential-vending.mdACP_BACKEND_ROUTINGinagent_sdk/backends.py; defined inagent_sdk/backends_routing.py:463since #21616 (d9b2e9d); other cited symbols (sandbox_tiers dirs, ENFORCED_ROUTINGS = 3 routings...rfc-i18n-measurement.mdi18nlane ofscripts/ci_e2e_parallel.py; #20638 moved it to ci.yml's owni18n-renderjob. §structural citesscripts/i18n-translate.mjs, real path `website/scri...rfc-idle-compaction-before-cache-expiry.mdin-progress, "nothing is on main"; Phase 1 merged in #24384 (2026-11-05):idle_compactionin config/loader_builders.py,idle_compaction_delay_secsin agent_sdk/backends_turns.py; Phase 2 Settings UI absen...rfc-issue-radar-crews.mdrfc-large-session-bounded-restore.mdpartial, but all four delivery parts are merged on main: 1.1 #36259 (8468181), 1.2 #36141 (88307c0), 1.3 #36035 (e618cbe), 1.4 #35960 (c12eb7b)rfc-mate-landing-once.mdrfc-mate-owned-agent-config.mdrfc-mcp-routed-server-working-dir.mdin-progress"implementation PR is open"; #36277 MERGED 2026-11-14 (538bad7); Proposal C still undecidedrfc-notification-bridge-actions.mdrfc-notification-bridge.mdrfc-overload-resilience.mdtimeline.py(#19942); other "shipped as" homes and not-built items verified; missing test_*.py names are design/plan recordsrfc-permanent-patrol.mdaccepted, but #33385 (57a1996) is on main:monitor_startarmsmax_cycles = 0for a gated loop and pins work-ledger patrols to PATROL_INTERVAL_SECS / no cap / runtime_ceiling_secs() (mcp_tools/control_p...rfc-perpetual-agent.mdrfc-pipeline-conductor.mdUNADVERTISED_AGENTSis insubagent_parts/agent_policy.py; it is defined insubagent_parts/spawn_allowlists.py:45(agent_policy.py only imports it under TYPE_CHECKING; moved by #35293). Five skill ...rfc-python-rust-hybrid-backend.mdnative/kc_nativeon main is the redaction gate (#19628), not this RFC's stubrfc-question-card-pager.mdacceptedwhile both parts shipped: #13196 pager and #15250 blocking ask_question (MERGED 2026-10-09,_ask_question_blockingin mcp_tools/control.py)rfc-recall-process-pool.mdmemory.recall_pool_processesin config/memory_sections.py)rfc-remote-computer-use.mdbrowser-agent-channel.js,command_bus.py,test_browser_command_handler_auth.py) as present; all removed by #26950 (6f13ecb)._computer_use_spec_gatecite...rfc-remove-piper-tts.mdaccepted, "Nothing is removed yet"; nowpartial: Decisions 1, 2 and 4 shipped in #23189 (piper_runtime.py/piper_worker.py deleted,REMOVED_PROVIDERS = {"piper"}in speech_providers.py); Decision 3 is open, since dev_fleetfeature-demo-recording(SKILL.md:92,144, references/deps.py:150-156, narrate.pyresolve_provider) and the dev-fleet spec still pick piper underautorfc-resumable-subagent-sessions.mdsubagent_manager/admission.pysplit intoadmission/package (#10521;spawn_implin admission/gate.py);sync_bridgeremoved by #10339rfc-review-loop-and-escaped-bug-reduction.mdaccepted+ "Nothing is built yet", but all eight decisions are on main: D1 #22698, D2 #22425, D3 #22957, D4 #22971, D5 #22961, D6 #22694, D7 #22973 (pre_push_gate.py), D8 #22702; nowimplementedrfc-security-conductor.mdis_deniedinsrc/kiro_crew/security.py(2 places); file split into a package by #9183 (09c54c7),is_deniednow insrc/kiro_crew/security/deny_gate.py:461. Other pre-scan misses are false: the scripts ...rfc-session-template-vs-crewmate.mdrfc-slack-code-channels.mdin-progress, status line says Phase 1 "is in the pull request that carries this document"; #21425 MERGED 2026-10-30, Phase 2 #21410/#22001 merged; the 2026-11-12 Stop-helper-agents amendment is unbuilt (`_sto...rfc-team-lead-default-agent.mdin-progressthough #18128 MERGED 2026-10-11:_install_team_lead_agentin agent_materialization/service_agents.py (called from agent_parts/spec_siblings.py), TEAM_LEAD_AGENT_FILENAME in agent_files.py owned ...rfc-tool-derived-diff-cards.mdrfc-ultra-mode-conductor-takes-defaults.mdacceptedbut its one implementation #31822 MERGED (0760ba5)rfc-wake-on-stop-signal.mddocs/work-ledger.mdis really src/kiro_crew/docs/work-ledger.mdrfc-work-dispatch.mdrfc-work-fold-forget-closed.mdforgottencounts in crew_log/projection_work.py; no item_store_full left i...rfc-work-ledger-concurrency-cap.mdDEFAULT_GOAL_CONCURRENCY_CAP = MAX_ITEMS_PER_CONDUCTOR), so status isimplemented(re-checked ate51c773a0c)rfc-work-report-wake-at.mdaccepted, "Nothing is built"; #33477 MERGED 2026-11-09 shipswake_aton work_report + storage + staleness deferral;wait_duewake, patrol text, board line not built (no hits in ledger_wake.py code, websit...rfc-worker-debate.mdaccepted+ "Nothing built on main yet", but Phase 1 skill change #33783 merged (live gh: MERGED, 92ee944; goal-conductor/references/worker-debate.md); Phase 2 measurement not donerfc-worker-model-inheritance.mdacceptedthough #19368 MERGED 2026-10-14:worker_session_defaults(config/sections_agent_fields.py:227) used by dashboard/session_control_parts/session_create.py:679rfc-workspace-config-evolution.mdversion-compliance-framework.md