Skip to content

docs(spec): stop claiming install targets register MCP servers - #1223

Merged
Fmarzochi merged 1 commit into
mainfrom
docs/spec-truth
Aug 6, 2026
Merged

docs(spec): stop claiming install targets register MCP servers#1223
Fmarzochi merged 1 commit into
mainfrom
docs/spec-truth

Conversation

@Fmarzochi

@Fmarzochi Fmarzochi commented Aug 6, 2026

Copy link
Copy Markdown
Owner

What was wrong

The executable spec under docs/spec/ had drifted from the code in two ways:

1. MCP registration attributed to install targets (three places). The Tier 1 row listed "MCP" among what the unified pipeline ships, and the per-tool table said the claude, zed and continue targets register MCP servers. Verified against the code: claude-home.js, zed-home.js and continue-home.js contain zero MCP registration; the whole registry lives in scripts/lib/mcp-register.js, driven by egc init and the shell installers. This is exactly the claim #1206 corrected in docs/installation.md ("--target <tool> only ever installs skills and rules"), which survived untouched in the spec.

2. A validator that no longer exists. The runtime-map row pointed at tests/test_orchestrator.py, deleted in #307. The schema's real consumers (scripts/runtime/discovery.js, scripts/orchestration/router.py) have no dedicated validator, so the row now sits with the other honest gaps the spec already tracks rather than claiming coverage it does not have.

What was checked and found correct

  • All 24 SUPPORTED_INSTALL_TARGETS identifiers in the compatibility commitments match install-manifests.js exactly.
  • Both Tier 2 entry points (.kiro/install.sh, .trae/install.sh) exist and are executable.
  • The legacy plugin identifiers still resolve through resolve-egc-root.js.
  • Every other "Validated by" file in the table exists.
  • The four declared gaps (harness contract schema, per-harness smoke tests, ADRs, HARNESS-{target}.md) are all still genuinely missing, so those entries stay honest.

Documentation only, no contract change, so SPEC_VERSION stays at 0.1.0.

Verification

tests/spec/integration-tiers.test.js 5/5, tests/scripts/bootstrap-cognitive.test.js 50/50, tests/hooks/doc-file-warning.test.js 60/60, tests/ci/agent-yaml-surface.test.js 4/4.


Summary by cubic

Fixed the executable spec to stop claiming Tier 1 install targets register MCP servers and to reflect that the runtime map validator no longer exists. Targets install skills and rules only; MCP registration is handled by egc init and the shell installers.

  • Bug Fixes
    • Removed “MCP” from Tier 1 “What ships” and clarified claude, zed, and continue targets don’t register MCP servers.
    • Marked the runtime map validator as a gap and referenced its real consumers in scripts/runtime/discovery.js and scripts/orchestration/router.py.

Written for commit 7dc651d. Summary will update on new commits.

Review in cubic

The spec described MCP registration as part of the Tier 1 install
pipeline and, per target, as something the claude, zed and continue
targets do. None of them do: every '--target <tool>' installs skills
and rules only, and MCP registration belongs to 'egc init' and the
shell installers. This is the same false claim #1206 corrected in the
installation guide; it survived here.

The runtime map row also pointed at tests/test_orchestrator.py as its
validator, a file removed in #307. It is now listed among the honest
gaps the spec already tracks, alongside the schema's real consumers.

Signed-off-by: Felipe Marzochi <fmarzochi@gmail.com>
@sonarqubecloud

sonarqubecloud Bot commented Aug 6, 2026

Copy link
Copy Markdown

@cubic-dev-ai cubic-dev-ai Bot 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.

No issues found across 2 files

Re-trigger cubic

@Fmarzochi
Fmarzochi merged commit 6f07c65 into main Aug 6, 2026
41 checks passed
@Fmarzochi
Fmarzochi deleted the docs/spec-truth branch August 6, 2026 05:27
@Fmarzochi Fmarzochi moved this to Done in EGC Roadmap Aug 6, 2026
Fmarzochi added a commit that referenced this pull request Aug 6, 2026
The spec's own semver rule assigns PATCH to documentation and
non-contract changes. #1223 corrected what the spec said about MCP
registration and about a validator that no longer exists, without
touching any contract, so the spec version moves one patch.

Signed-off-by: Felipe Marzochi <fmarzochi@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

1 participant