refactor(agents): render the template pane unconditionally and remove the standalone Agent Templates page

[xuejinT]

Problem / Motivation

The dashboard had two places for an agent's template. The standalone Agent Templates page (a Capabilities tab) showed a template's definition, and #8307 added the same definition inside each agent's Template pane — but behind the agent_template_pane flag, which defaulted off. So for most users the in-agent pane never rendered, and the standalone page was still the only template UI.

Why it matters

Two doors to the same thing is a navigation tax, and the page carries ~1,100 lines that must be kept in sync with the pane that mirrors it. But the page can't simply be deleted while its replacement is dark — that would strand template viewing/editing (exactly what the first review round on this branch caught). And flipping the flag's default is not enough either: older builds materialized agent_template_pane: false into every saved config.json, so a new default never reaches an existing install (the second round's design blocker).

What changed (motivation → approach → change)

Delete the flag entirely, render the pane unconditionally, then remove the page — one coherent change so there is never a window with no template UI, on fresh installs and upgrades alike.

• Flag deleted end-to-end, pane unconditional. agent_template_pane is removed from the config dataclass, the parse, to_dict(), config-baseline.json (regenerated for only this diff's entries), and the frontend (useAgentTemplatePane.ts deleted; KiroCrewAgentsPage.tsx imports AgentTemplateDetail statically and renders it whenever the Template pane is open — no lazy chunk, so no chunk-load failure path). The pane sits inside a retryOnly ErrorBoundary: a render crash shows a contained Try Again in the pane — no dashboard blank-out, and no /chat hand-off that would discard the sheet's unsaved edits. A stale materialized false in an existing config is a retired key: ignored at load, dropped on the next save, never warned about (CONFIG_RESERVED_TOP_KEYS), pinned by test_retired_key_is_ignored_dropped_and_never_warned. No migration needed — nothing reads the key anymore.
• Page removed. Deletes AgentsPage.tsx and its 7 suites, the Capabilities templates tab, the pinnable-surface entry, and repoints the two chat "Manage agents" footers at ?tab=crews. /agents already redirects. The page's default-template picker goes with it — the same control survives in the create form and the chat agent dropdown.
• Ghost pins pruned. A user who had pinned the Templates tab to the nav rail would keep a pin with no row and no way to unpin it, silently consuming one of the 5 pin slots. readNavPinned now drops retired surface ids before the cap applies (navPinned.retiredIds.test.ts).
• Extra surfaces retired end-to-end (design owner's call): the page uniquely hosted per-session context-window meters, "clear completed" subagents, and template delete. Their client methods AND their server halves are removed — GET /api/sessions/context (plus the now-consumerless context_info()), DELETE /api/spawn, and the DELETE /api/agents/detail/{name} branch with its reference-guard test. Template delete is done by removing the JSON file on disk.
• Cleanup. Prunes 65 dead pages.agentsPage.* i18n keys plus their pluralKeys.json / en.context.json leftovers, drops the stale destructive-confirm exemption, deletes the two capture harnesses that targeted the removed tab (capture-agent-templates.mjs, capture-agent-skills.mjs — the pane harness covers their subjects), and updates agents.md, the feature map, and the dashboard spec.

flowchart LR
  subgraph Before
    A1[open agent]:::ctx --> F1{agent_template_pane?}:::removed
    F1 -->|off, the default| P1[picker only]:::removed
    F1 -->|on| P2[full definition]:::ctx
    A2[Agent Templates page]:::removed --> D1[full definition]:::ctx
  end
  subgraph After
    A3[open agent]:::ctx --> P3[Template pane: full definition, always]:::added
  end
  classDef added fill:#DCFCE7,stroke:#16A34A,color:#14532D,stroke-width:2px
  classDef removed fill:#FEE2E2,stroke:#DC2626,color:#7F1D1D,stroke-dasharray:4 3
  classDef ctx fill:#E0F2FE,stroke:#0284C7,color:#0C4A6E
  linkStyle 0,1,2,3 stroke:#DC2626,stroke-dasharray:4 3
  linkStyle 4 stroke:#16A34A,stroke-width:2px

Loading

🟩 added · 🟥 removed · 🟦 unchanged

The flag and the standalone page are both gone; every agent's Template pane shows the full definition, for existing installs too.

Tests

test_retired_key_is_ignored_dropped_and_never_warned pins the upgrade path: a config carrying a stale agent_template_pane: false loads with no field, no round-trip, and no unrecognized-key warning. navPinned.retiredIds.test.ts pins the ghost-pin prune: a retired pin is dropped before the 5-slot cap so remaining pin controls stay usable. test_config_baseline.py parity passes with the row removed. The page's 7 frontend suites and the DELETE-route guard test are deleted with their subjects; test_api_server, owner-auth, messaging-coverage, and the session suites are updated for the removed routes and pass (798 Python tests green across the touched suites; 191 affected vitest tests green).

Manual verification

npx tsc -b clean; i18n-check + check-i18n-keys clean; flake8 / isort clean on the changed Python. The capture harness (capture-agent-template-pane.mjs) runs the real built SPA with no flag stub and its self-checks pass — the pane renders unconditionally.

Screenshots / video

The in-agent Template pane, now always on — it renders the full definition (model, skills, tools, auto-approved, MCP servers, system prompt, guardrails) inline, which is what makes the standalone page redundant.

Built-in template (kirocrew, the default agent):

A custom template (atlas):

The two frames are committed under temp-screenshots/agent-template-pane/ (the repo’s screenshot convention; cleanup-temp-screenshots.yml prunes them on schedule). Captured with the repo's capture-agent-template-pane.mjs harness (real built SPA, fixture-stubbed API, no flag stub). The removed standalone tab's "after" is its absence from the Capabilities rail; the pane above is the replacement users get instead.

Related Issues

no linked issue: completes the #8307 in-agent template pane by making it unconditional, then removing the page it replaces.

Checklist

• At most two commits (one), Conventional Commits title
• Existing tests pass and tests updated for the changed behavior
• Self-review completed; code follows project style guidelines
• Documentation updated (agents.md, feature map, dashboard spec)
• No secrets, credentials, or internal references in the diff

[xuejinT]

Intent: Remove the standalone Agent Templates page now that #8307 put template editing inside each agent's editor, leaving one place to manage a template.
Not a goal: Changing the in-agent template pane itself, the pages.agentsPage.* strings it still uses, or any agent/template data model — this is a pure UI/route removal.

[github-actions]

Design Review (Fable 5) — 🟡 CONCERNS

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

Design-Verdict: CONCERNS

Sound consolidation with a real upgrade story, but retiring the only guarded template-delete path leaves reference integrity unenforced.

Watch

• Template delete now happens only by "removing the JSON file on disk", yet the deleted route carried the sole authoritative guard — the lock-held check that a template is not the default agent or bound to a crew (the removed agents.py hunk calls itself "the authority and the UI is now just the early, friendlier signal"). Cause → mechanism → consequence: no guarded delete surface remains → a user unlinks a bound template's file → cfg.agents[*].kiro_agent or default_agent dangles, and the failure the 409s ("still used by …", "Change the default first") existed to prevent now surfaces later, at session start, with no early signal. The invariant was judged worth a race-free lock design; the PR retires the surface but not the invariant.
  Clears when: a remaining path (load-time validation warning on a dangling binding, or a CLI/MCP guarded delete) owns the invariant, or the owner explicitly accepts dangling bindings as tolerable and documents the failure mode.

Suggestions

• RETIRED_NAV_PINS and the retired-keys arm of CONFIG_RESERVED_TOP_KEYS are the same "retired id" pattern born in one PR; a one-line pointer between them would keep the next retirement from doing only half.

[DESIGN-REVIEWED] 4b3a6c6

[github-actions]

GPT 5.6 Review — ✅ no blocking findings

GPT 5.6 completed its review of 4b3a6c698359b1e2b72b5e16d169247c63369919 and found no blocking issues.

This comment is updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] 4b3a6c6

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

[github-actions]

UX Review (Fable 5) — 🟡 CONCERNS

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

UX-Verdict: CONCERNS

The now-always-on Template pane ships with its source chip stranded over the explainer copy in both committed screenshots — first-time readers see it as broken.

Watch

• Stranded Built-in/Custom chip. The chip belongs in the sticky TEMPLATE header row (AgentTemplateDetail.tsx:446-490), yet both committed screenshots show it floating ~60px below, overlapping the "…reset to the original anytime" note — the exact regression the code comment says was fixed ("stranded the chip ~60px below its header slot, over the explainer copy"). Blind reader: "looks broken or misplaced — it half covers a sentence and I can't tell what it labels." Every open of what is now the only template UI × comprehension loss × every time. Fix: verify chip placement at HEAD; if the bug is live, fix the transform; if the captures are stale, re-capture — the committed evidence currently shows a defect.
• "used by 2 agents" vs own-copy note pull apart. Reader: "I can't tell whether editing here could ever touch the other agent" — the header count and the reassurance sit in tension for anyone on a shared template. Smallest fix: append to the used-by text something like "edits here never change them."

Evidence gaps

• The new retryOnly crash fallback in the template pane (Try Again with no "Ask the agent") appears in no screenshot.
• The Capabilities tab bar after the Templates tab's removal (and the repointed "Manage agents" landing on Crews) is shown nowhere.

[UX-REVIEWED] 4b3a6c6

[github-actions]

Opus 4.8 Review — ✅ no blocking findings

Reviewed 4b3a6c698359b1e2b72b5e16d169247c63369919 — this comment is updated in place on each push.

Review details

No findings.

[OPUS-REVIEWED] 4b3a6c6

Verdict parsed from the review's SHA-scoped output markers for commit 4b3a6c698359b1e2b72b5e16d169247c63369919.

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

[github-actions]

First Principles Review (Fable 5) — 🟡 CONCERNS

Premise-level review of 4b3a6c698359b1e2b72b5e16d169247c63369919 — why this exists and whether the shipped surface is the smallest honest version. Updated in place on each push. A BLOCK verdict blocks PR readiness; PASS/CONCERNS are advisory.

All verification done. Producing the review.

First-Principles-Verdict: CONCERNS

Template delete now rests on an unverified kiro-cli claim: that a missing spec "falls back to the default agent spec" instead of failing session start.

What this change ships

Inventory (10 items) — 10 justified

Intent: make the in-agent Template pane the only template UI — on upgrades too — and delete the duplicate standalone page. FIX (of a two-doors duplication left half-finished by #8307).

1. Every agent's Template pane shows the full definition, always (was flag-off for nearly everyone) — justified
2. agent_template_pane config key retired: ignored at load, dropped on save, never warned — justified
3. Standalone Agent Templates tab removed from Capabilities — justified
4. Two chat "Manage agents" footers now open the Crews tab — justified
5. Ghost "Agent Templates" nav pins pruned so the pin slot is reclaimed — justified
6. Per-session context-window meters and GET /api/sessions/context removed — justified
7. "Clear completed" subagents and DELETE /api/spawn removed; per-id delete remains — justified
8. In-app template delete (and its locked 409 reference guard) removed; deletion is now manual file removal — justified
9. Pane crash shows a contained Try Again with no /chat hand-off (retryOnly, 1 consumer: KiroCrewAgentsPage.tsx:2244) — justified
10. Template detail code ships in the main chunk (no lazy load, no chunk-failure path) — justified

More items exist below the cap (65 i18n keys pruned across 13 locales, two capture harnesses deleted, baselines regenerated, screenshots committed per the cleanup-temp-screenshots.yml convention) — all declared, all harm-free cleanup.

Counts run: agent_template_pane, context_info|sessionsContext|/api/sessions/context, spawnClear|api_spawn_clear|agentDelete, tab=templates|capabilities-templates → zero remaining consumers for every removed surface; the "older builds materialized false" premise is confirmed by the deleted unconditional to_dict() line.

Watch

• Item 8 replaces a race-free, lock-held 409 reference guard with a doc procedure whose safety story is one sentence: "kiro-cli cannot resolve the missing spec and falls back to the default agent spec" (src/kiro_crew/docs/agents.md, feature map). That vendored-tool behavior is asserted, not evidenced — no test, no linked observation — and if wrong, a user following the new documented deletion procedure breaks a bound crew at session start. Clears when: the fallback is confirmed on kiro-cli with a crew bound to a deleted spec (or a linked issue/test records it).

[FIRST-PRINCIPLES-REVIEWED] 4b3a6c6

[xuejinT]

span=4659357888e5

• Flag flip inert for already-saved configs (BLOCKER)
  self-added: yes
  mechanism: retired-key tombstone — agent_template_pane added to CONFIG_RESERVED_TOP_KEYS (ignored at load, dropped on save, never warned)

Disposition: fixed in cea9b1b.

Correct, and fixed by SUBTRACTION rather than a migration: the flag is deleted end-to-end (loader field + parse + to_dict, resolution.py, config-baseline.json regenerated, useAgentTemplatePane.ts deleted) and the Template pane renders unconditionally. A config with a materialized agent_template_pane: false now renders the pane after upgrade because NOTHING reads the key anymore; the stale key is a retired key — ignored at load, dropped on the next save, never warned about.
Pinned by test_retired_key_is_ignored_dropped_and_never_warned (test_config_extra_sections.py). This ruling covers every finding that requires a migration or superseded-default entry for this key: with the flag gone there is no default left to drift.

[xuejinT]

span=48bcd838f698

• Two PNGs land permanently in the repo under temp-screenshots/
  Disposition: rebutted — this is the repository's own screenshot convention, not an accident.

The required Screenshot Evidence gate (screenshot-evidence.yml) demands visual evidence in the body for user-visible frontend changes, and the repo's documented convention is committing frames under temp-screenshots/<feature>/ with commit-SHA-pinned raw URLs (external hosts are camo-blocked; PR attachments cannot be captured by a CLI workflow).
They are not permanent: cleanup-temp-screenshots.yml runs weekly and prunes temp-screenshots/ files past the retention window — the directory exists precisely so evidence images never ship in the wheel/DMG and get reaped on schedule. The body's "What changed" needn't list evidence files; the Screenshots section names how they were captured.

[xuejinT]

span=b028d969143a

• Scope contradiction: 'used by 2 agents' vs 'other agents are not affected'
  Disposition: accepted-and-deferred to Agent Template pane: copy + badge polish (deferred from PR #9936 UX review) #9961 (label deferred-finding, assigned to the design owner, Due 2026-09-24).

Legitimate: the intro copy should read as one story (fork-on-edit gives THIS agent a private copy; the count names who shares the original).
Deferred, not fixed here, because the copy and badge live in AgentTemplateDetail.tsx from #8307 — this PR does not touch that component, and its wording is a design-owner call. #9936's scope is making the pane the only template surface and removing the page; the pane's copy polish is tracked in the issue above with the concrete rewording proposals.

[xuejinT]

span=c58c60f99e9e

• Custom/Built-in badge floats between intro and MODEL and can overlap
  Disposition: accepted-and-deferred to Agent Template pane: copy + badge polish (deferred from PR #9936 UX review) #9961 (label deferred-finding, assigned to the design owner, Due 2026-09-24).

Legitimate: the badge should be anchored beside the template name with the overlap cleared.
Deferred, not fixed here, because the copy and badge live in AgentTemplateDetail.tsx from #8307 — this PR does not touch that component, and its wording is a design-owner call. #9936's scope is making the pane the only template surface and removing the page; the pane's copy polish is tracked in the issue above with the concrete rewording proposals.

[xuejinT]

span=0fca2def5eb3

• 'this agent can override it under Model' does not name the winner
  Disposition: accepted-and-deferred to Agent Template pane: copy + badge polish (deferred from PR #9936 UX review) #9961 (label deferred-finding, assigned to the design owner, Due 2026-09-24).

Legitimate: the note should say explicitly that the agent's Model page wins when set.
Deferred, not fixed here, because the copy and badge live in AgentTemplateDetail.tsx from #8307 — this PR does not touch that component, and its wording is a design-owner call. #9936's scope is making the pane the only template surface and removing the page; the pane's copy polish is tracked in the issue above with the concrete rewording proposals.

[xuejinT]

span=ea1ae43ec34b

• Undeclared: the page's default-template picker is also removed
  Disposition: fixed in cea9b1b (PR body).

Declared now: the body's "Page removed" bullet states the default-template picker goes with the page and that the same control survives in the create form and the chat agent dropdown — matching your own harm-free assessment.

[xuejinT]

span=25d648f6b07f

• Item 9 — the kept opt-out has zero consumers
  Disposition: fixed in cea9b1b.

The opt-out is gone: agent_template_pane is deleted end-to-end (loader field/parse/to_dict, resolution.py, config-baseline.json, useAgentTemplatePane.ts, its flag test) and the pane renders unconditionally. See the Subtractions disposition for the file list.

[xuejinT]

span=85ab384fdef7

• The retired surfaces kept their server halves
  self-added: no
  Disposition: fixed in cea9b1b.

All three routes and their handlers are deleted: GET /api/sessions/context (routes/system.py + api_sessions_context), DELETE /api/spawn (server.py + api_spawn_clear), and the DELETE /api/agents/detail/{name} registration plus the whole DELETE branch of api_agent_detail; test_agent_delete_reference_guard.py goes with it. Also removed one layer down: SessionManager.context_info() and its allocation-boundary producer, whose only non-test consumer was the deleted route. Route-list/owner-auth/coverage tests updated.

[xuejinT]

span=2f6082500a24

• Crews maps an unrelated endpoint (BLOCKING)
  self-added: yes

Disposition: fixed in c53c1f2.

GET /api/agent/config is removed from the Crews endpoint cell in docs/feature-map/README.md. Verified by grep: the endpoint's only frontend caller is api.agentConfig used by pages/overview/AgentCfgTab.tsx; KiroCrewAgentsPage.tsx never calls it. The round-6 retrospective ran this round: it kept all four surviving mechanisms (retired-key tombstone, RETIRED_NAV_PINS prune, the pane ErrorBoundary, retryOnly) and confirmed the lazy-loader subtraction as the close of the 6e26220b5826 arc — nothing further was removed.

[xuejinT]

span=063a9298bf87

• Template lifecycle has no sanctioned in-product delete (WATCH)
  self-added: yes
  Disposition: rebutted — the finding's first Clears-when branch is met: the design owner's decision to drop guarded delete is confirmed on this PR.

The design owner (xuejinT) has confirmed ON THIS PR — in the round-3 owner-acceptance comment and the round-5 disposition on span 7af72fab1749 — that dropping the guarded DELETE route in favour of documented on-disk deletion is the accepted design. What a crew bound to a deleted template does at session start is documented in src/kiro_crew/docs/agents.md and pinned by test_resolve_agent_model_cache_miss_returns_auto; repair_agent_configs() reconciles configs at gateway startup. 6th round of the guarded-delete class; this owner confirmation covers the class, including future instances that cite the deleted handler's comments as authority.

[xuejinT]

span=e002a7fcabdc

• If delete returns, resurrect the removed handler verbatim (SUGGESTIONS)
  Disposition: rebutted — no code change is required now; the guidance is preserved where it can be found.

The suggestion is conditional on a future in-product delete, which this PR deliberately does not build (owner-confirmed). Keeping the handler API-only was already declined on span ee23f6e492c1: an unreferenced route is dead code with a live maintenance surface. The review-hardened handler (lock discipline, alias set, 409 codes) remains verbatim in this PR's git history, which the suggestion itself names as the spec — nothing further is needed to preserve it.

[xuejinT]

span=abc80c2c9464

• Direct deletion bypasses the removed reference guard (BLOCKING)
  self-added: yes

Disposition: rebutted (not a defect) — the finding's failure chain does not occur; the doc is corrected in 4b3a6c6 to state the real behavior.

The chain "documented deletion -> ACP rejects the missing agent mode -> breaking subsequent crew turns" does not hold: when a crew names an agent spec kiro-cli cannot resolve, kiro-cli SILENTLY FALLS BACK to the default agent spec and the session runs (documented in this codebase at src/kiro_crew/agent.py:2853 and :3241, and in resolve_agent_bindings' docstring in src/kiro_crew/config/loader.py — the "silent substitution" behavior). Nothing rejects, no crew turn breaks; the crew runs with default prompt/tools until repointed, and the model resolves via the auto fallback (test_resolve_agent_model_cache_miss_returns_auto). agents.md is corrected in 4b3a6c6 to state exactly this degradation, and the retirement rationale plus the fallback behavior are recorded in docs/system-specs/modules/learn-cron-dashboard.md. This ruling covers the guard-removal class for on-disk template deletion: the failure mode is silent-default-fallback, never a rejected session. 7th round of this class; owner (xuejinT) has confirmed retiring the guarded route on this PR.

For a human override if this recurs: /ai-review override gpt 4b3a6c6: on-disk deletion of a bound template cannot break sessions — kiro-cli silently falls back to the default agent spec; degradation is documented in agents.md and the dashboard spec, and the design owner accepted retiring the guarded route.

[xuejinT]

span=76a4e6fdfdbe

• Template deletion loses both its surface and its safety (WATCH)
  self-added: yes

Disposition: fixed in 4b3a6c6 — the second Clears-when branch is now satisfied in full.

The design owner's rationale for retiring guarded delete is recorded in the dashboard spec (docs/system-specs/modules/learn-cron-dashboard.md, "Template deletion" section) alongside exactly what a dangling binding does at session start: kiro-cli falls back to the default agent spec and the session runs with default behavior until repointed (agent.py:2853/:3241). src/kiro_crew/docs/agents.md now states the same degradation instead of the vaguer "keeps working". 7th round of this class — the clears-when condition is met by a durable spec record, not only by PR comments.

[xuejinT]

span=76f35a762ba7

• Rehome the guarded-delete handler rather than re-derive it later (SUGGESTIONS)
  Disposition: fixed in 4b3a6c6 — the preservation pointer is now durable.

The dashboard spec's new "Template deletion" section instructs any future in-product delete to reuse the removed handler from this repo's history (lock discipline, alias set, 409 reference guard) rather than re-deriving it. The suggestion's substance — do not lose the hard-won invariants — is satisfied without keeping a caller-less route alive (declined on ee23f6e492c1).

[xuejinT]

span=ea808e6d2ee8

• Template pane copy/affordance polish
  Disposition: accepted-and-deferred to Agent Template pane: copy + badge polish (deferred from PR #9936 UX review) #9961 (item 1 (shared-template copy contradiction); label deferred-finding, assignee xuejinT, Due 2026-09-24).

Real pane polish, but the strings and layout live in AgentTemplateDetail.tsx from #8307, outside this PR's removal diff; wording and interaction are the design owner's call and are tracked as item 1 (shared-template copy contradiction) on the existing deferral issue. This ruling covers the #8307 pane-polish class for this PR.

[xuejinT]

span=a2d25b627c3d

• Template pane copy/affordance polish
  Disposition: accepted-and-deferred to Agent Template pane: copy + badge polish (deferred from PR #9936 UX review) #9961 (item 2 (provenance chip overlapping the explainer); label deferred-finding, assignee xuejinT, Due 2026-09-24).

Real pane polish, but the strings and layout live in AgentTemplateDetail.tsx from #8307, outside this PR's removal diff; wording and interaction are the design owner's call and are tracked as item 2 (provenance chip overlapping the explainer) on the existing deferral issue. This ruling covers the #8307 pane-polish class for this PR.

[xuejinT]

span=ecdbdbb9a664

• Template pane copy/affordance polish
  Disposition: accepted-and-deferred to Agent Template pane: copy + badge polish (deferred from PR #9936 UX review) #9961 (item 8 (destructive chips need a Removed/Undo acknowledgment); label deferred-finding, assignee xuejinT, Due 2026-09-24).

Real pane polish, but the strings and layout live in AgentTemplateDetail.tsx from #8307, outside this PR's removal diff; wording and interaction are the design owner's call and are tracked as item 8 (destructive chips need a Removed/Undo acknowledgment) on the existing deferral issue. This ruling covers the #8307 pane-polish class for this PR.

[xuejinT]

span=d2b3475bf17b

• Template pane copy/affordance polish
  Disposition: accepted-and-deferred to Agent Template pane: copy + badge polish (deferred from PR #9936 UX review) #9961 (item 3 (name which Model setting wins); label deferred-finding, assignee xuejinT, Due 2026-09-24).

Real pane polish, but the strings and layout live in AgentTemplateDetail.tsx from #8307, outside this PR's removal diff; wording and interaction are the design owner's call and are tracked as item 3 (name which Model setting wins) on the existing deferral issue. This ruling covers the #8307 pane-polish class for this PR.

[xuejinT]

span=e2683a38363f

• Drop the dead pages/AgentsPage.tsx i18n baseline entry (SUBTRACTIONS)
  self-added: no

Disposition: fixed in 4b3a6c6.

The pages/AgentsPage.tsx ceiling entry is deleted from website/src/i18n/untranslated-baseline.json — the file it capped was deleted by this PR. i18n-check passes with the entry gone.

[xuejinT]

span=92c862fa3095

• Delete the stale lazy-load comment in CrewRoster.test.tsx (SUBTRACTIONS)
  self-added: yes

Disposition: fixed in 4b3a6c6.

The comment now says the header selector is awaited via findByRole for the pane render; the lazy-load claim is gone — this PR made the import static.

[xuejinT]

span=a5a12402e0cd

• The kiro-cli fallback claim is asserted, not confirmed (WATCH)
  self-added: yes

Disposition: rebutted (confirmed by direct test) — the finding's Clears-when is met: the fallback was exercised on kiro-cli itself.

Ran kiro-cli chat --agent kc-missing-spec-probe-xyz --no-interactive (a name with no spec on disk) on this machine. kiro-cli printed verbatim: "Error: no agent with name kc-missing-spec-probe-xyz found. Falling back to user specified default" — and the session continued to start. The behavior the docs describe is the vendored tool's actual, observed behavior, not an inference from this repo's comments. This confirmation covers the fallback-verification class for on-disk template deletion.

[xuejinT]

span=c7911bd9b25a

• On-disk delete leaves the binding invariant unowned (WATCH)
  self-added: yes

Disposition: rebutted — the finding's second Clears-when branch is met: the owner explicitly accepts dangling bindings as tolerable, and the failure mode is documented.

The design owner (xuejinT) accepted retiring the guarded route on this PR (round-3 owner acceptance, round-5 and round-6 dispositions on spans 7af72fab1749 and 063a9298bf87). The failure mode is documented twice — src/kiro_crew/docs/agents.md and the dashboard spec's "Template deletion" section — and is now empirically confirmed on kiro-cli: a session naming a missing spec prints "Falling back to user specified default" and keeps running. 8th round of the guarded-delete class; this owner ruling plus the recorded failure mode covers it, including restatements that relocate to new files.

[xuejinT]

span=9cd4ef2b49cf

• Cross-point RETIRED_NAV_PINS and the retired-keys reserved set (SUGGESTIONS)
  Disposition: rebutted — disproportional for this diff; the linkage is already durably recorded.

The two retirement mechanisms are already named together in the dashboard spec's retired-surfaces sections and in this PR's thread, and a grep for either constant lands on this PR, which shows both halves. Adding cross-reference comments to guard a hypothetical future half-retirement is speculative hardening beyond this PR's purpose; the durable record already does that job.

[xuejinT]

span=03bfe4b1b1a4

• Template pane copy/affordance polish
  Disposition: accepted-and-deferred to Agent Template pane: copy + badge polish (deferred from PR #9936 UX review) #9961 (item 2 (Built-in/Custom chip stranded below its header slot); label deferred-finding, assignee xuejinT, Due 2026-09-24).

Recurring #8307 pane polish: the chip layout and header copy live in AgentTemplateDetail.tsx, outside this PR's removal diff, and their design is the owner's call — tracked as item 2 (Built-in/Custom chip stranded below its header slot). This ruling covers the #8307 pane-polish class for this PR.

[xuejinT]

span=8271f286c82e

• Template pane copy/affordance polish
  Disposition: accepted-and-deferred to Agent Template pane: copy + badge polish (deferred from PR #9936 UX review) #9961 (item 1 (used-by count vs own-copy reassurance pull apart); label deferred-finding, assignee xuejinT, Due 2026-09-24).

Recurring #8307 pane polish: the chip layout and header copy live in AgentTemplateDetail.tsx, outside this PR's removal diff, and their design is the owner's call — tracked as item 1 (used-by count vs own-copy reassurance pull apart). This ruling covers the #8307 pane-polish class for this PR.