Skip to content

chore(release): enforce documentation surface parity - #218

Merged
kevintseng merged 5 commits into
mainfrom
chore/pre-release-surface-parity
Aug 28, 2026
Merged

chore(release): enforce documentation surface parity#218
kevintseng merged 5 commits into
mainfrom
chore/pre-release-surface-parity

Conversation

@kevintseng

@kevintseng kevintseng commented Aug 28, 2026

Copy link
Copy Markdown
Contributor

Summary

  • make CODEMAP version, package bins, hook commands, and local messaging anchors fail the release gate when stale
  • bind the canonical MCP tool contract to the three READMEs, AGENTS.md, the MeMesh skill, API reference, and architecture overview
  • correct v4.8.1 documentation drift found by an independent audit: all 11 skill tools, 11 MCP handlers, 8 hooks, required merge_strategy, and experimental Gemini ACP status
  • keep the release path small: one focused CODEMAP checker plus the existing MCP documentation checker

Verification

  • npm run test:surface-parity
  • npm run verify:release
  • exact-head CI matrix on Linux, macOS, and Windows
  • packaged artifact and upgrade smoke tests
  • focused negative paths for stale version, missing bin/hook/messaging anchors, missing tool rows/API sections, architecture inventory drift, and canonical MCP contract drift

This is a post-v4.8.1 follow-up. It does not rewrite the published v4.8.1 tag or npm tarball.

@kevintseng
kevintseng force-pushed the chore/pre-release-surface-parity branch 2 times, most recently from ec1b41e to d6a50af Compare August 28, 2026 10:09
@kevintseng
kevintseng force-pushed the chore/pre-release-surface-parity branch from d6a50af to c7ae99e Compare August 28, 2026 10:20
@kevintseng
kevintseng merged commit e7316ab into main Aug 28, 2026
13 checks passed
@kevintseng
kevintseng deleted the chore/pre-release-surface-parity branch August 28, 2026 11:45
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.

1 participant