Skip to content

fix(dashboard): say when a saved MCP change did not reach the agent spec - #19213

Merged
bolichen97 merged 1 commit into
mainfrom
fix/mcp-rebuild-verdict-18679
Oct 12, 2026
Merged

bolichen97 merged 1 commit into
mainfrom
fix/mcp-rebuild-verdict-18679

Conversation

@bolichen97

@bolichen97 bolichen97 commented Oct 12, 2026 •

Copy link
Copy Markdown
Contributor

Problem / Motivation

Goal: When a dashboard MCP or computer-use change is saved but the agent spec is not rewritten, the dashboard says so instead of reporting plain success.

Adding or editing a custom MCP server, installing one from Discover, importing MCP servers in onboarding, applying the MCP tab, toggling computer use, or changing a connection's OAuth client all end with a call to the plain rebuild_agent_config(). That rebuild can finish without writing the agent spec: the shared-home guard declines when this instance may not own ~/.kiro/agents. The handlers ignored that and answered success, so the user saw "saved" while new sessions still loaded the old servers.

Why it matters

Anyone on a non-default data home (a pod, a worktree instance) who edits MCP servers from the dashboard is told the change landed when it did not. They then debug a "missing" server that was saved but never reached the spec.

Not a goal

  • Changing when the shared-home guard declines, or making it write.
  • The capability-provider install path, which syncs through _sync_mcp_to_agent, not this rebuild.
  • Retrying a declined rebuild.

What changed (motivation → approach → change)

Surface Endpoint Saved but spec not rewritten
Custom server modal POST/PUT /api/mcp/custom agent_spec_rewritten: false; modal stays open with the notice and only Close
Discover install POST /api/mcp/discover/install agent_spec_rewritten: false; notice in the detail pane
Onboarding import POST /api/onboarding/import/apply agent_spec_rewritten: false; notice on the result page, without the "ready" line
MCP tab apply POST /api/mcp/apply rebuild: {ok: false, error}; the notice replaces the green Applied line, and it and the tab's Add Custom / Discover modals drop the hand-off while changes are staged
Computer use PUT /api/computer-use/config agent_spec_rewritten: false; notice in the panel without the agent hand-off, kept until an enable change rebuilds again; the restart line drops "so this takes effect"
OAuth app (Settings) PUT/DELETE /api/connections/oauth-clients/{slug} 200, audited, agent_spec_rewritten: false; notice on the card (a raised rebuild keeps the existing projection_refresh_failed 500)
Connection Disconnect POST /api/connections/disconnect agentSpecRewritten: false; the feedback becomes an alert

The rebuild already reports whether it wrote, through rebuild_agent_config_reporting(). The handlers now use it through one helper, rebuild_agent_spec() in dashboard/handlers/_shared.py. The helper returns True only when the write is confirmed. A declined write and a raised rebuild both return False, and the config write that already landed stays saved. The MCP tab apply, the OAuth client refresh and the Disconnect transaction in connections/ownership.py call rebuild_agent_config_reporting() directly; apply fills its existing rebuild field, and the OAuth client refresh tells a decline (answered and audited) from a failure (500).

On the dashboard, one AgentSpecNotRewrittenNotice component renders through ErrorNotice with the agent hand-off. It says the change was saved, that this copy of Kiro Crew could not update the agent config so new chats keep the old setup, and to open the Logs page to see why. The hand-off is off on the Computer Use panel, where it would navigate away from unsaved drafts. The response types in website/src/api and website/src/types/index.ts carry the optional field. The string is translated in every website/src/i18n/locales catalog, and en-XA is regenerated.

The capability install and uninstall handlers in dashboard/agent_admin/capabilities.py (skill and agent packages, not MCP edits) keep their current answer; they are a known deferral, tracked in #19306.

Backwards compatibility

Compatible: every response gains a field (or reuses rebuild.ok), and no input main accepts is rejected. DisconnectScope gains a required agent_spec_rewritten field; its only constructor is remove_provider_entry. One answer changes: an onboarding MCP import whose rebuild raises returns 200 with agent_spec_rewritten: false instead of a 500, because the import itself landed. _refresh_client_projections returns None for a decline; both callers treat only False as the 500.

Removes nothing: no key, endpoint or capability is removed; the responses only add a field.

Tests

  • test/test_mcp_custom_api.py::TestSpecNotRewritten, test/test_mcp_discover_api.py::...test_install_reports_a_declined_rebuild, test/test_api_onboarding_import.py::test_apply_reports_whether_the_agent_spec_was_rewritten, test/test_computer_use_api.py::...test_the_save_reports_whether_the_spec_was_rewritten, test/test_connections_disconnect.py::test_disconnect_reports_a_spec_rebuild_that_did_not_write, test/test_connections_oauth_client_routes.py::test_the_projection_refresh_tells_a_decline_from_a_failure and ...test_a_declined_rebuild_answers_success_and_says_the_spec_did_not_follow, test/test_mcp_apply.py::...test_a_declined_rebuild_reports_rebuild_not_ok: a stub that behaves like the guard's refusal (returns the path, reports no write) gives false, and a writing stub gives true. The decline cases fail on origin/main (11 failed there) and pass here.
  • A raised rebuild reports false and keeps the save (custom add, onboarding import, computer use).
  • Existing rebuild stubs in test_mcp_apply.py, test_handlers_mcp_coverage.py and the fixtures report a write. test_computer_use_registration.py pins the rebuild call ahead of the session reset.
  • Frontend: McpCustomServerModal.test.tsx (new) checks that the modal closes on a confirmed write and stays open with Add disabled on a decline, and red on main's component. It also checks that only Close remains after the save. AgentImportFlow.test.tsx and ComputerUsePanel.test.tsx check that the notice renders only on false, ConnectionsPage.coverage.test.tsx checks the Disconnect alert, McpTab.integration.test.tsx checks that the notice replaces the green Applied line, and ConnectionsPanel.test.tsx checks the OAuth app card.

Manual verification

Each of the seven surfaces was rendered in Chromium against stubbed endpoints answering agent_spec_rewritten: false (or rebuild.ok: false, agentSpecRewritten: false), driven through its real flow, in dark and light themes. The notice appeared on each one.

Screenshots / video

Each surface after a save whose agent-spec rebuild did not confirm a write.

Custom server modal (dark)

MCP tab apply (dark)

Connection Disconnect (dark)

OAuth app card (dark)

All surfaces, dark and light

Discover install (dark)

Discover install (light)

Onboarding import (dark)

Onboarding import (light)

Computer use (dark)

Computer use (light)

Custom server modal (light)

MCP tab apply (light)

Connection Disconnect (light)

OAuth app card (light)

Related Issues

Closes #18679

Pattern harvest

Rule candidate: review-prompt
Pattern: a handler calls a step that can decline without raising, then reports success without reading that step's verdict.

Checklist

  • At most two commits (one is the norm), with a Conventional Commits title (feat|fix|docs|style|refactor|perf|test|chore|ci|build|revert: ...)
  • 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

@bolichen97
bolichen97 requested review from a team and KiroCrewCaptain as code owners October 12, 2026 00:04
@bolichen97
bolichen97 enabled auto-merge (squash) October 12, 2026 00:04
@github-actions github-actions Bot added the readiness: checking Automated validation is still running label Oct 12, 2026
@github-actions

github-actions Bot commented Oct 12, 2026 •

Copy link
Copy Markdown
Contributor

Design Review (Opus 5.5) — ✅ PASS

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

Design-Verdict: PASS

Check that tests stubbing rebuild_agent_config with no-kwarg lambdas (e.g. test_r7_s31_mcp_discover_owner_gate.py) still exercise the write path, not a swallowed TypeError.

[DESIGN-REVIEWED] 8baea42

Description read

[DESCRIPTION-READ] 7e77e5f9efeaa7bc3039022f145055b7b46d07edc28a6e9112d2eaeae12568a1

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 12, 2026 •

Copy link
Copy Markdown
Contributor

First Principles Review (Opus 5.5) — ✅ PASS

Premise-level review of 8baea429dffbcdd6b983f0822aea6125d42ea422 — 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

Check one changed answer: an onboarding MCP import whose rebuild raises used to return 500 and now returns 200 with agent_spec_rewritten: false.

What this change ships

Inventory (10 items) — 10 justified

Intent: when a dashboard MCP, computer-use or OAuth-client change is saved but the agent spec is not rewritten, the dashboard says so instead of reporting plain success. This is a FIX (#18679; the decline tests fail on base).

  1. When the spec is not rewritten, the custom-server modal stays open with the notice, and Close is its only button — justified
  2. Discover install shows the notice in the detail pane when the spec is not rewritten — justified
  3. The onboarding import result shows the notice and drops the "ready" line — justified
  4. MCP tab Apply reports rebuild.ok: false on a decline; the notice replaces the green "Applied" line — justified
  5. The Computer Use panel shows the notice; the restart line drops "so this takes effect" — justified
  6. The OAuth client card shows the notice on a decline (still 200 and audited); a raised rebuild stays 500 — justified
  7. Connection Disconnect feedback turns into an error alert when the spec is not rewritten — justified
  8. A raised onboarding-import rebuild now answers 200 instead of 500 — justified
  9. The agent hand-off is hidden in the MCP tab's modals while changes are staged, and on the Computer Use and OAuth panels — justified
  10. New agent_spec_rewritten / agentSpecRewritten response field on seven endpoints, plus a DisconnectScope field, a rebuild_agent_spec helper (4 callers) and one shared notice component — justified

[FIRST-PRINCIPLES-REVIEWED] 8baea42

Description read

[DESCRIPTION-READ] 42123f7aa648907060dd35170014fe1c4e9de73d9fc934768b4a2aca218e4dfc

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 12, 2026 •

Copy link
Copy Markdown
Contributor

UX Review (Opus 5.5) — 🟡 CONCERNS

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

UX-Verdict: CONCERNS

The new notice sends users to a "Logs page" it never links to, and "this copy of Kiro Crew… agent config" is jargon the blind reader couldn't follow.

Watch

  • No way to reach the Logs page. The notice ends with "Open the Logs page to see why", but it renders through ErrorNotice with no link. The blind reader said: "I don't know where the 'Logs page' is, because nothing here is a link to it." The notice's only next step leads nowhere, on all seven surfaces, every time the save is declined. Fix: make "Logs page" a link to /logs that opens in a new tab, as EmbeddingModelCard.tsx:387 already does. A new tab also avoids the risk of losing unsaved Computer Use edits.
  • The wording uses terms users don't know. The reader understood "sure that something went wrong" but had "no idea what 'agent config' or 'this copy' means". The notice says what happened but not how to fix it. Fix: say it in the user's words, e.g. "Saved, but new chats will still use the old servers. This Kiro Crew instance doesn't manage the agent setup." (Note the reader also stumbled on "Kiro" vs "Kiro Crew".)
  • The Disconnect feedback contradicts itself on the Notion card (shot-03). The card shows a "Connected" badge and a live Disconnect button, and the alert says both "Disconnected locally" and "new chats still load this connection". The reader called these "three different answers." This shows up on every declined disconnect. Fix: start disconnect_spec_not_rewritten with what is still true, e.g. "New chats still load Notion until…", or make the card's badge reflect the partial state.
  • Two Computer Use lines appear to clash (shot-09). The reader read "new chats keep the old setup" next to "Your chat sessions were restarted" as a contradiction. Fix: change the restart line next to the notice to "Chat sessions restarted, but still on the old setup."

Suggestions

  • McpCustomServerModal: once notApplied is set, disable or hide the "Enable immediately" checkbox. The reader couldn't tell whether ticking it after "Saved" did anything.
  • McpBrowserModal (shot-05): when the notice is showing, change "Installs disabled — you review and enable it…" so it no longer sits next to "✓ Installed" as if both were true.

[UX-REVIEWED] 8baea42

Description read

[DESCRIPTION-READ] b62b1b04716001a34ada4997cb87cb23b94e33a27fc3174566adc3cd8133b711

That sha256 names everything this verdict read: the PR description, plus the 17 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 12, 2026 •

Copy link
Copy Markdown
Contributor

Opus 5.5 Review — ✅ no blocking findings

Reviewed 8baea429dffbcdd6b983f0822aea6125d42ea422 — this comment is updated in place on each push.

Review details

No findings.

[OPUS-REVIEWED] 8baea42

Verdict parsed from the review's SHA-scoped output markers for commit 8baea429dffbcdd6b983f0822aea6125d42ea422.

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

@github-actions

github-actions Bot commented Oct 12, 2026 •

Copy link
Copy Markdown
Contributor

GPT 6.1 Review — ✅ no blocking findings

GPT 6.1 completed its review of 8baea429dffbcdd6b983f0822aea6125d42ea422 and found no blocking issues.

This comment is updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] 8baea42

False positive or not applicable? A repository writer can comment:
/ai-review override gpt 8baea429dffbcdd6b983f0822aea6125d42ea422: <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 12, 2026
@bolichen97
bolichen97 force-pushed the fix/mcp-rebuild-verdict-18679 branch from 6a89d9a to c3da398 Compare October 12, 2026 01:03
@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 12, 2026
@bolichen97
bolichen97 force-pushed the fix/mcp-rebuild-verdict-18679 branch from c3da398 to dafba0c Compare October 12, 2026 01:17
@bolichen97

bolichen97 commented Oct 12, 2026 •

Copy link
Copy Markdown
Contributor Author
  • ux finding span=0b2e36982caa

fixed in dafba0c: The notice now states the verdict plainly: "Saved, but the agent config was not updated, so new sessions will use the previous setup."

@bolichen97

bolichen97 commented Oct 12, 2026 •

Copy link
Copy Markdown
Contributor Author
  • ux finding span=c2b5d52fe317

fixed in dafba0c: Same change: the system's verdict is no longer worded as a doubt on any of the six surfaces.

@bolichen97

bolichen97 commented Oct 12, 2026 •

Copy link
Copy Markdown
Contributor Author
  • ux finding span=ef9678041e77

fixed in dafba0c: MCP tab drops the green Applied line when the rebuild did not write; the import result keeps its counts, which are true, under the plain notice.

@bolichen97

bolichen97 commented Oct 12, 2026 •

Copy link
Copy Markdown
Contributor Author
  • ux finding span=67b3c7be9369

fixed in dafba0c: The wording fix applies to the one shared string, so it reaches every surface and every non-default-home user at once.

@bolichen97

bolichen97 commented Oct 12, 2026 •

Copy link
Copy Markdown
Contributor Author
  • ux finding span=74347f819115

fixed in dafba0c: Took the suggested wording for the shared notice, and the Disconnect clause now says new sessions will still load the connection.

@bolichen97

bolichen97 commented Oct 12, 2026 •

Copy link
Copy Markdown
Contributor Author
  • ux finding span=1fba676d5aec

fixed in dafba0c: The shared string now says "the previous setup", which fits Computer Use as well as the MCP surfaces.

@bolichen97

bolichen97 commented Oct 12, 2026 •

Copy link
Copy Markdown
Contributor Author
  • ux finding span=9fc030442440

fixed in dafba0c: Add is hidden once the save landed; Close is the only action left.

@bolichen97

bolichen97 commented Oct 12, 2026 •

Copy link
Copy Markdown
Contributor Author
  • ux finding span=b559070675fd

fixed in dafba0c: When rebuild.ok is false the green Applied line is not set; McpTab.integration.test.tsx pins it.

@bolichen97

bolichen97 commented Oct 12, 2026 •

Copy link
Copy Markdown
Contributor Author
  • opus finding span=bcb19f814792

fixed in dafba0c: AgentSpecNotRewrittenNotice takes askAgent; ComputerUsePanel passes askAgent={false} because its numeric fields hold drafts the hand-off would discard. ComputerUsePanel.test.tsx asserts no button.

@bolichen97

bolichen97 commented Oct 12, 2026 •

Copy link
Copy Markdown
Contributor Author
  • opus finding span=1b989084b3c0

fixed in dafba0c: onMutate no longer clears the notice, and onSuccess only updates it when the response carries agent_spec_rewritten; a test saves Attach screenshots after a declined enable and the notice stays.

@bolichen97

Copy link
Copy Markdown
Contributor Author

rebutted: the Disconnect alert keeps the error style on purpose. The grant was revoked, but the agent spec still mounts the connection, so new sessions keep loading it; that is a failed step, reported the same way as a surviving grant artifact on the same card.

@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 12, 2026
@bolichen97
bolichen97 force-pushed the fix/mcp-rebuild-verdict-18679 branch from dafba0c to 28afa4e Compare October 12, 2026 01:52
@bolichen97

Copy link
Copy Markdown
Contributor Author
  • Logs link and wording span=1fe4f88dbfc9

rebutted: ErrorNotice owns the error surface and has no link slot; the notice names the page by its nav label, and the copy has been revised across rounds to state cause, effect and where to look.

@bolichen97

Copy link
Copy Markdown
Contributor Author
  • drop "this copy of" span=cb3c7387ad55

rebutted: the phrase is what tells a non-default-home user that this instance, not the product, could not write the shared config; keeping it.

@bolichen97

Copy link
Copy Markdown
Contributor Author
  • capabilities.py install sites span=fdb3a965a91d

accepted-and-deferred: the three capability install and uninstall sites install skill and agent packages, not MCP or computer-use edits, so they are outside this PR's goal; the work is tracked in #19306 (deferred-finding, assigned, Due 2026-10-25) and the description now names them as a known deferral.

@bolichen97

Copy link
Copy Markdown
Contributor Author
  • Logs page link span=b5be5812125f

rebutted: ErrorNotice owns the error surface and has no link slot; the notice names the page by its nav label.

@bolichen97

Copy link
Copy Markdown
Contributor Author
  • agent config wording span=8533b183724b

rebutted: the copy has been revised over several rounds and now states cause, effect and where to look; further wording is polish outside this fix.

@bolichen97

Copy link
Copy Markdown
Contributor Author
  • two Computer Use messages span=c54de33a97fb

rebutted: both are true and now say different things: the sessions were restarted, and the restarted chats keep the old setup; the restart line no longer claims the change took effect.

@bolichen97

Copy link
Copy Markdown
Contributor Author
  • Notion card badge span=7f0c23abbb39

rebutted: the badge comes from the gallery's status poll, which refetches after the Disconnect; changing its source is outside this fix.

@bolichen97

Copy link
Copy Markdown
Contributor Author
  • disable the checkbox after the save span=07bbbc9ae38a

rebutted: only Close remains, so the checkbox cannot change anything that is submitted; locking the fields is polish outside this fix.

@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 12, 2026
@bolichen97

Copy link
Copy Markdown
Contributor Author

Waiting on main: the cron manifest red is fixed on main by #19280, and the FilePathMenu.inApp.test.tsx red is being fixed in #19288 / #19298. This PR rebases once that lands.

@bolichen97

Copy link
Copy Markdown
Contributor Author

Rebased onto main now that #19280 and #19288 cleared the two main-side reds (cron manifest, FilePathMenu); both pass locally on this head. CI re-running.

@bolichen97
bolichen97 force-pushed the fix/mcp-rebuild-verdict-18679 branch from 1c0bc77 to 8baea42 Compare October 12, 2026 07:58
@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 12, 2026
@bolichen97

Copy link
Copy Markdown
Contributor Author

The earlier Backend Tests shard 1 failures here (Windows and Linux) in test/test_app_cron_timeout_manifest.py came from main, not this PR: #19231 started requiring permissions.cron when a manifest declares crons, and that test's fixtures did not grant it. #19280 fixed the fixtures on main. The new CI run builds on the fixed main, so those failures should clear.

@bolichen97

Copy link
Copy Markdown
Contributor Author
  • Logs page link span=036ee74fab6f

rebutted: ErrorNotice owns the error surface and has no link slot; the notice names the page by its nav label.

@bolichen97

Copy link
Copy Markdown
Contributor Author
  • wording span=d0eb035c2641

rebutted: the copy has been revised over several rounds and states cause, effect and where to look; further wording is polish outside this fix.

@bolichen97

Copy link
Copy Markdown
Contributor Author
  • Notion card badge span=6df9ab98913a

rebutted: the badge comes from the gallery's status poll, which refetches after the Disconnect; changing its source is outside this fix.

@bolichen97

Copy link
Copy Markdown
Contributor Author
  • two Computer Use lines span=26b196278b35

rebutted: both are true and say different things: the sessions were restarted, and the restarted chats keep the old setup; the restart line no longer claims the change took effect.

@bolichen97

Copy link
Copy Markdown
Contributor Author
  • checkbox after the save span=1b84da763a7d

rebutted: only Close remains, so the checkbox cannot change anything submitted; locking the fields is polish outside this fix.

@bolichen97

Copy link
Copy Markdown
Contributor Author
  • install hint beside the notice span=f79e7f626d84

rebutted: that hint is the existing Discover copy for an install that landed disabled and stays true; rewording it is outside this fix.

@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 12, 2026

@iamwhatever iamwhatever 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.

Dashboard MCP, Discover, onboarding import, computer-use and OAuth-client saves used to ignore whether rebuild_agent_config() wrote the spec. A shared-home decline therefore showed as plain success. This PR fixes that at the root by switching every caller to rebuild_agent_config_reporting(), through one helper (rebuild_agent_spec in handlers/_shared.py) and the direct calls in connections/ownership.py, connections.py and mcp.py. I read every backend hunk. A decline or a raised rebuild returns False, and the config write that already landed is kept. The OAuth client route tells a decline (None: 200, audited, agent_spec_rewritten: false) from a failure (False: the existing 500). Computer use still rebuilds under the config lock and reports only when a rebuild ran. The one changed answer, an onboarding import whose rebuild raises now returns 200 instead of 500, is declared and correct because the import landed. Responses only gain a field. The UX CONCERNS on 8baea42 each have a posted disposition, and checks are green. — crew-pr-reviewer (deep re-check)

@bolichen97
bolichen97 merged commit 3f046cb into main Oct 12, 2026
137 of 149 checks passed
@bolichen97
bolichen97 deleted the fix/mcp-rebuild-verdict-18679 branch October 12, 2026 17:07
@github-actions github-actions Bot removed the readiness: passed Eligible automated validation passed for the current revision label Oct 12, 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.

Dashboard MCP edits report success when the spec rebuild skips

2 participants