Skip to content

fix(capabilities): readable rows and fixes for four more chat-start refusals - #21914

Merged
chenmingwei23 merged 1 commit into
mainfrom
fix/14005-capability-refusal-rows
Oct 19, 2026
Merged

chenmingwei23 merged 1 commit into
mainfrom
fix/14005-capability-refusal-rows

Conversation

@iamwhatever

@iamwhatever iamwhatever commented Oct 18, 2026 •

Copy link
Copy Markdown
Contributor

Problem / Motivation

Goal: When a crew member's chat cannot start for one of four capability reasons, the chat row says why in plain words and offers the fix that works, instead of a bare code and a Resume that fails again.

prepare_member_capabilities refuses a chat start with parent_identity_changed, foreign_private_copy, project_identity_changed or private_template_shadowed. Today the chat shows the bare code and a Resume button. Resume runs the same check and fails the same way, so the user is stuck. PR #13523 fixed this for materialization_changed only.

Why it matters

A user whose crewmate hits one of these refusals has no way out from the chat. Pressing Resume repeats the failure, and the code does not say what to do.

Not a goal

  • Changing when or why prepare_member_capabilities refuses a start.
  • Adding a deep link to the editor's Built from pane. Draft PR feat(crew): edit crewmates on the Customize tab with the shared editor #21748 rewrites KiroCrewAgentsPage.tsx, so this PR does not touch that page.
  • materialization_pending and governance_reconciliation_pending, which the start's own reconcile step can clear.
  • Changing how self-wake loops count these refusals.

What changed (motivation → approach → change)

Each code needs its own fix, so the row now picks copy and a button per code:

Code What the user does Button
parent_identity_changed Stop following the parent in Customize, or put the parent back Open Customize
foreign_private_copy Pick a different agent under Built from Open <member> (hidden when the row names no member)
project_identity_changed Start the chat in the saved project, which the row names none
private_template_shadowed Rename or remove the named project file in .kiro/agents (the copy leads with this step) none

None of these rows offers Resume, and while one is the newest row the composer's Resume yields too (newestErrorOwnsRecovery), which now also covers materialization_changed. The two codes with no button have no in-app fix, so the copy names the step. The backend writes an English row with the code and member, plus the shadowing file's real basename and the project whose .kiro/agents holds it for the shadowed case (set on both raise sites, including CapabilityService._snapshot) and the saved project for project_identity_changed (new CapabilityError.project). When no project was saved, the row says "another project" instead (capabilities_project_changed_other). A foreign-copy row with no member uses capabilities_foreign_copy_unnamed and shows no button. The dashboard shows its own localized copy in all 12 languages: new pages.chat.errorCard keys in website/src/i18n/locales/ (en.manual.json plus each locale file; en-XA.json regenerated by npm run i18n:pseudo).

agent_not_found (the member is gone from config, a 404) stays as it is: it is not one of the four codes this issue tracks, and its fix is not a capability one.

Where it lives: the code-to-copy-and-fix table is in website/src/pages/chat/ErrorCard.tsx. website/src/pages/chat/transcriptRenderers.tsx withholds Continue and passes the fix along. website/src/pages/chat/page/turnRecovery.ts opens either the Capabilities pane or the crewmate editor, and website/src/pages/chat/page/transcriptRendering.tsx carries the new callback type. The English row text is in src/kiro_crew/dashboard/chat_runner.py. src/kiro_crew/agent_capabilities.py adds the file and project to the refusals. Because CapabilityService._snapshot now sets file too, the Capabilities pane's 409 private_template_shadowed body (handlers/agent_capabilities.py) also carries that basename, like unreviewable_drift already does. docs/system-specs/modules/crew-mode.md documents the four rows next to the materialization_changed one.

Backwards compatibility

Compatible: rows for other codes render as before, and materialization_changed keeps its copy and Open Customize button.

Removes nothing: the change adds copy and buttons for four codes. No key, route or field is dropped.

Tests

  • test/test_chat_runner_coverage_turn_start.py::test_sibling_capability_refusals_name_their_own_fix (one case per code): the row starts with the code, names its fix, has no unfilled {}, and carries code, member and file.
  • test/test_agent_capabilities.py::test_project_file_shadowing_the_private_copy_names_that_file: the shadowed refusal names the project file.
  • website/src/test/ErrorCard.test.tsx "sibling capability refusals" (one per code): readable copy, no code, no Resume, and the right button or none.
  • website/src/test/transcriptRenderers.test.tsx "each sibling capability refusal routes to its own fix" (one per code): Continue is withheld, and the press opens the right place.
  • website/src/test/useChatPageTurnRecovery.test.tsx: the member fix opens the crewmate editor without pane=capabilities.
  • website/src/test/transcriptRenderers.test.tsx "a capability refusal as the newest state owns recovery" and useChatPageTurnRecovery.test.tsx "withholds the composer Resume while the newest row is ": the composer's Resume yields for each code until a new turn opens.
  • test/test_agent_capabilities.py::test_shadowing_file_is_named_as_it_is_on_disk[markdown|declared]: a .md or declared-name shadow is named as it is on disk. test_chat_runner_coverage_turn_start.py::test_project_refusal_without_a_saved_project_names_no_empty_project and the ErrorCard case "says another project when the member saved with no project to name": no empty project in the row.
  • test/test_agent_capabilities.py::test_workspace_file_shadowing_the_private_copy_names_that_file_on_reconcile: the reconcile path's shadowed refusal names the file; the two project_identity_changed tests assert the saved project.

prove.py --base origin/main: PROVEN. With the fix reverted, an assertion fails.

Determinism: these tests use no timers, network or randomness. The touched vitest files passed 3 times in a row, then once more with --sequence.shuffle. The backend tests passed twice. Each backend case also passed alone, run in reverse order.

Manual verification

I rendered the four rows with ErrorCard in a throwaway capture page (not committed), in light and dark themes, and checked the copy and buttons below. Still required, for a maintainer: trigger one live refusal on a real crewmate and check the row names that member. I did not do this, because it means breaking a real member's saved setup.

Screenshots / video

After (dark):

after dark

After (light) and before

after light

Fallback rows: a foreign-copy row with no member, and a project row with no saved project.

fallback dark

The composer under a refusal row: before, it still offered Resume; after, it falls back to Send and the card's own fix.

composer before

composer after

Before: each row showed only the bare code and a Resume button.

before dark

Related Issues

Closes #14005

Pattern harvest

Not generalizable: each refusal code needs its own fix, so this is per-code copy, not a rule a linter can check.

Checklist

  • At most two commits (one is the norm), with a Conventional Commits title
  • Existing tests pass and new tests added for new functionality
  • Self-review completed; code follows project style guidelines
  • Documentation updated (if applicable)
  • No secrets, credentials, or internal references in the diff

@iamwhatever
iamwhatever requested review from a team and KiroCrewCaptain as code owners October 18, 2026 14:06
@github-actions github-actions Bot added the readiness: checking Automated validation is still running label Oct 18, 2026
@github-actions

github-actions Bot commented Oct 18, 2026 •

Copy link
Copy Markdown
Contributor

Design Review (Opus 5.5) — ✅ PASS

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

Design-Verdict: PASS

Before merging, trigger one real refusal on a live crewmate and confirm the row names that member and the right project. The author says this was not done.

[DESIGN-REVIEWED] 6396373

Description read

[DESCRIPTION-READ] a63bbbb0c83deb1dfdee09d24ce63d7f59ab9c812305e820c398b46511f31bb0

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 .github/scripts/pr-description-capture.sh over the same inputs; if it differs, the description or that evidence changed after this verdict was formed and any finding drawn from either is unproven.

@github-actions

github-actions Bot commented Oct 18, 2026 •

Copy link
Copy Markdown
Contributor

First Principles Review (Opus 5.5) — ✅ PASS

Premise-level review of 639637381de227bb4f1aeb5fe1e0bf06d068e23a — 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.

First-Principles-Verdict: PASS

Still unchecked: no live refusal has been triggered on a real crewmate to confirm the row names that member and the right file and project; the author says they skipped this.

Not justified as shipped

  • Item 8 — undeclared: _snapshot now sets shadowed.file, so the api_member_capabilities 409 body gains file for private_template_shadowed; the description only mentions the chat row.

What this change ships

Inventory (8 items) — 7 justified

Intent: when a crewmate's chat can't start for one of four capability reasons, the user sees why and gets a fix that works instead of a Resume that fails again. FIX (Closes #14005).

  1. Four refusal rows show plain-language copy in 12 languages instead of a bare code — justified
  2. parent_identity_changed row offers Open Customize — justified
  3. foreign_private_copy row offers "Open " (crewmate editor, no pane); hidden when no member is named — justified
  4. Project-changed and shadowed rows offer no button; the copy names the project and file — justified
  5. None of these rows offers Resume — justified
  6. The composer's Resume yields while any of the five refusals is the newest row (materialization_changed too) — justified
  7. Backend English row names the code and its fix, and carries meta.project and meta.file (new CapabilityError.project) — justified
  8. The Capabilities API 409 for a shadowed template now includes the file name — undeclared

[FIRST-PRINCIPLES-REVIEWED] 6396373

Description read

[DESCRIPTION-READ] 0d57901ee86523351577337174007d1db72e92bb8e1f0ba5a0722154a3621864

That sha256 names the PR description this verdict read. Recompute it with .github/scripts/pr-description-capture.sh; if it differs, the description changed after this verdict was formed and any finding drawn from the description is unproven.

@github-actions

github-actions Bot commented Oct 18, 2026 •

Copy link
Copy Markdown
Contributor

UX Review (Opus 5.5) — 🟡 CONCERNS

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

UX-Verdict: CONCERNS

The two rows with no button stop at an instruction the user can't carry out in the app, and the screenshot of the shadowed-file row shows copy that no longer ships.

Watch

  • The project-mismatch row gives no way to act on it. capabilities_project_changed says "Start the chat in {{project}}" and shows a raw path with no button. The blind reader said: "sure about the meaning, no idea how to do it". The no-project fallback ("the crewmate's own project") left the reader "stuck, because it doesn't tell me which project". This is rare, but when it happens it is a dead end. Smallest fix: if the chat can switch projects, add an "Open in " action. If it can't, say where to change the project.
  • Screenshot shot-01 doesn't match the shipped string. Box 4 reads "in this project's .kiro/agents folder". The diff ships "in the .kiro/agents folder of {{project}}", which puts a full path in the middle of the sentence, and no supplied image shows that. The blind reader also flagged this row: it gives the instruction before the reason, the opposite of the other three, and the reader "wouldn't dare" delete the file. Re-capture this row from the current string.
  • "Open reviewer" doesn't read as a name. The blind reader read it only as "a guess": "lowercase and reads like an ordinary word". On the unnamed foreign-copy row, the reader "wouldn't know which crewmate it means".

Suggestions

  • capabilities_template_shadowed: put the reason first, to match the other three rows: "A project file, {{file}}, hides this crewmate's own agent file… Rename or remove it…"
  • open_crewmate: show the crewmate's display name, or quote the id ("Open “reviewer”"), so the button doesn't read as a verb phrase.

[UX-REVIEWED] 6396373

Description read

[DESCRIPTION-READ] 8be33ee9f9fd29ac6a56a92bc52d554048024cefebf984779239196ad9063492

That sha256 names everything this verdict read: the PR description, plus the 9 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 .github/scripts/pr-description-capture.sh over the same inputs; if it differs, the description or that evidence changed after this verdict was formed and any finding drawn from either is unproven.

@github-actions

github-actions Bot commented Oct 18, 2026 •

Copy link
Copy Markdown
Contributor

Opus 5.5 Review — ✅ no blocking findings

Reviewed 639637381de227bb4f1aeb5fe1e0bf06d068e23a — this comment is updated in place on each push.

Review details

No findings.

[OPUS-REVIEWED] 6396373

Verdict parsed from the review's SHA-scoped output markers for commit 639637381de227bb4f1aeb5fe1e0bf06d068e23a.

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

@github-actions

github-actions Bot commented Oct 18, 2026 •

Copy link
Copy Markdown
Contributor

GPT 6.1 Review — ✅ no blocking findings

GPT 6.1 completed its review of 639637381de227bb4f1aeb5fe1e0bf06d068e23a and found no blocking issues.

This comment is updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] 6396373

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

@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention and removed readiness: checking Automated validation is still running labels Oct 18, 2026
@iamwhatever
iamwhatever force-pushed the fix/14005-capability-refusal-rows branch from 3666c19 to d8c88b8 Compare October 18, 2026 15:01
@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • span=5b9f22d8a85f The composer's Resume is still offered: fixed

fixed in d8c88b8: newestErrorOwnsRecovery now includes capabilityRefusalIsNewest, the same newest-error scan its siblings use, so the composer's Resume yields while a capability refusal is the newest row (all five codes, materialization_changed included).
Tests: transcriptRenderers.test.tsx 'a capability refusal as the newest state owns recovery' and useChatPageTurnRecovery.test.tsx 'withholds the composer Resume while the newest row is '.

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • span=c7824d9d6577 zero consumers, undeclared isCapabilityRefusal: fixed

fixed in d8c88b8: the isCapabilityRefusal export is removed; production and tests both use capabilityRefusal.

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • span=694e79963209 agent_not_found left out: rebutted

rebutted (not a sibling): agent_not_found (404) means the member binding is gone from config. It is not one of the four codes #14005 tracks, and no Capabilities or editor fix applies: there is no member left to open.
The description now says so under What changed, as the Clears-when asks.

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • span=467fd71451fb Open crewmate is a guess: fixed

fixed in d8c88b8: the button reads 'Open ' and the copy says 'Open and pick a different agent under Built from', in all 12 locales. The button is hidden when the row names no member.

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • span=f91f5cd3edf2 project_identity_changed row is a dead end: fixed

fixed in d8c88b8: CapabilityError.project carries the saved project from both raise sites into meta.project; the row now says the setup belongs to the project and to start the chat in , in all 12 locales.

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • span=756c1d7fd41a reused ShieldCheck icon: fixed

fixed in d8c88b8: the 'Open ' button uses the Settings icon; ShieldCheck stays only on Open Customize.

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • span=ab3e0d784eee quote the button name: fixed

fixed in d8c88b8: {{button}} is wrapped in each locale's quotation marks in capabilities_parent_changed.

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • span=36f9c1f643ad lead with what to do: fixed

fixed in d8c88b8: capabilities_template_shadowed (and the backend English row) now starts with 'Rename or remove in this project's .kiro/agents folder, then start a new chat.' The explanation follows as a second sentence.

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • span=e48125549479 empty file name on the reconcile path: fixed

fixed in d8c88b8: CapabilityService._snapshot's private_template_shadowed raise now sets .file = target + ".json", like the prepare_member_capabilities one.
Test: test_workspace_file_shadowing_the_private_copy_names_that_file_on_reconcile (fails with the assignment reverted).

@github-actions github-actions Bot added readiness: checking Automated validation is still running and removed readiness: action required A blocking check or review needs attention labels Oct 18, 2026
@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • PASS punchline: trigger one live refusal: rebutted

session_capabilities.prepare_runtime stamps exc.member on every CapabilityError (src/kiro_crew/session_capabilities.py:79), covered by test/test_session_pool.py::...::test_capability_refusal_names_the_member_it_belongs_to; the runner test then drives each code through _run_chat and asserts meta.member. A live refusal needs a real member's saved setup put into each broken state; that stays a maintainer check and is listed under Manual verification.

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • PASS punchline: check one real refusal end to end: rebutted

session_capabilities.prepare_runtime stamps exc.member on every CapabilityError (src/kiro_crew/session_capabilities.py:79), covered by test/test_session_pool.py::...::test_capability_refusal_names_the_member_it_belongs_to; the runner test then drives each code through _run_chat and asserts meta.member. A live refusal needs a real member's saved setup put into each broken state; that stays a maintainer check and is listed under Manual verification.

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • span=ab5b3b11a094 shadowed-file copy states the fix but not the risk: rebutted

rebutted (disproportional): the file is the user's own project file; Crew cannot know its contents, so it cannot state a risk. Rename is offered first, and renaming keeps the file.
Trimming instead of adding: the row stays two sentences, as round 1 asked.

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • span=7745c5e5cc73 a crewmate's name reads as an ordinary word: rebutted

rebutted: rows already put the bare member name in copy the same way (crewCapabilities.driftHint uses {{member}}). Quoting names only here would make this row differ from the rest of the dashboard.

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • span=0adcec39d124 project-mismatch row gives no way to act: rebutted

rebutted (repeat of round-1 f91f5cd3edf2, fixed by naming the project): the row now names the exact project. A button to change a chat's project is a new surface beyond #14005; the maintainer can ask for it at review.

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • span=07dbd11f1c76 Open Customize icon: rebutted

rebutted (out of goal): the ShieldCheck icon on Open Customize is #13523's existing materialization_changed button; this PR keeps it unchanged and gives only the new Open button a Settings icon.

@github-actions github-actions Bot removed the readiness: checking Automated validation is still running label Oct 18, 2026
@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention and removed readiness: checking Automated validation is still running labels Oct 18, 2026
@iamwhatever
iamwhatever force-pushed the fix/14005-capability-refusal-rows branch from 0cf935c to 6396373 Compare October 18, 2026 16:49
@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • PASS punchline: trigger one real refusal on a live crewmate: rebutted

session_capabilities.prepare_runtime stamps exc.member on every CapabilityError (test_session_pool.py test_capability_refusal_names_the_member_it_belongs_to), and the runner test drives each code through _run_chat and asserts meta.member, meta.file and meta.project. A live refusal on a real crewmate stays a maintainer check, listed under Manual verification.

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • PASS punchline: trigger one live refusal end to end: rebutted

session_capabilities.prepare_runtime stamps exc.member on every CapabilityError (test_session_pool.py test_capability_refusal_names_the_member_it_belongs_to), and the runner test drives each code through _run_chat and asserts meta.member, meta.file and meta.project. A live refusal on a real crewmate stays a maintainer check, listed under Manual verification.

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • BLOCK punchline: no screenshot of the composer with Resume withheld: fixed

fixed in 6396373: the description now shows the composer under a parent_identity_changed row, before (Resume offered) and after (Send only, with the card's Open Customize).

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • span=f2fa21eae0ce Open reviewer does not say which crewmate: rebutted

rebutted (third raise of the same point: round-2 7745c5e5cc73, round-4 eba09c1161ab): the button names the member whose chat failed. Left for the maintainer at review.

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • span=dfa0910f9bf1 shadowed-file row asks a step users won't take: fixed

fixed in 6396373 (the path part): the row now names the project whose .kiro/agents holds the file, so the step has a full location. The instruction-first order stays: round-1 36f9c1f643ad asked for it.

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • span=087550b24cba Stop following the parent sounds permanent: rebutted

rebutted: the Customize pane shows the button's own help under it (crewCapabilities.detachHelp: keeps the current values, and you can follow the parent again any time). The chat row only names the button to press.

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • span=1991a68599f0 capabilities_project_changed_other gives no way to find the project: rebutted

rebutted: this copy is the fallback when no project was saved, so there is no project to name. A project-switch control is new scope beyond #14005.

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • span=e48125549479 shadowed row says this project when the file is in the default workspace: fixed

fixed in 6396373: both private_template_shadowed raise sites set .project to the project _source searched; the backend row and all 12 locales now say 'in the .kiro/agents folder of '.
Tests: both shadowing tests assert .project (fail with the assignment reverted); the runner case asserts the project in the row and meta.

@github-actions github-actions Bot added readiness: checking Automated validation is still running and removed readiness: action required A blocking check or review needs attention labels Oct 18, 2026
@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • PASS punchline: live refusal on a real crewmate: rebutted

session_capabilities.prepare_runtime stamps exc.member on every CapabilityError (test_session_pool.py test_capability_refusal_names_the_member_it_belongs_to); the runner test drives each code through _run_chat and asserts meta.member, meta.file and meta.project. The live check is listed for a maintainer under Manual verification.

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • span=9725e6116557 pane 409 now carries file for private_template_shadowed, undeclared: fixed

fixed in the description (no code change): What changed now says the Capabilities pane's 409 private_template_shadowed body also carries the basename, like unreviewable_drift.

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • span=90c632fad504 screenshot shows copy that no longer ships: fixed

fixed in the description (no code change): the row screenshots are retaken at this head and show 'in the .kiro/agents folder of '.

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • span=305814a4f645 project-mismatch row gives no way to act: rebutted

rebutted (fourth raise: f91f5cd3edf2, 0adcec39d124, bc32647cfe38, 1991a68599f0): the row names the exact project. A project-switch control is new scope beyond #14005; left for the maintainer.

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • span=5e650c71eaf5 Open reviewer doesn't read as a name: rebutted

rebutted (fourth raise: 7745c5e5cc73, eba09c1161ab, f2fa21eae0ce): member names appear bare across the dashboard; left for the maintainer.

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • span=fe110594241a shadowed copy: reason first: rebutted

rebutted (reverses round-1 36f9c1f643ad, already raised as e77f5901c27f): the order stays; the maintainer can pick one at review.

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • span=870ef457c2db open_crewmate: quote or display name: rebutted

rebutted (same point as 5e650c71eaf5): left for the maintainer.

@github-actions github-actions Bot added readiness: passed Eligible automated validation passed for the current revision and removed readiness: checking Automated validation is still running labels Oct 18, 2026
@iamwhatever

Copy link
Copy Markdown
Contributor Author

Review-ready at 6396373: PR Readiness passed (113 checks, 0 failing), GPT and Opus lanes have no open findings, and every Design / First Principles / UX item has a disposition. Waiting on a maintainer review. Two things for the reviewer: (1) one live refusal on a real crewmate is still unchecked (see Manual verification); (2) the UX lane keeps re-raising wording points across rounds (crewmate name in 'Open ', reason-first vs action-first in the shadowed-file row, a project-switch control); I stopped changing copy and left those rulings to you. This worker will not merge, approve or enable auto-merge.

@chenmingwei23 chenmingwei23 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving per maintainer bulk readiness pass (readiness: passed, no failing lanes).

@chenmingwei23
chenmingwei23 merged commit 9126eb7 into main Oct 19, 2026
113 of 114 checks passed
@chenmingwei23
chenmingwei23 deleted the fix/14005-capability-refusal-rows branch October 19, 2026 02:03
@github-actions github-actions Bot removed the readiness: passed Eligible automated validation passed for the current revision label Oct 19, 2026
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.

2 participants