Skip to content

docs: document release, consensus CLI and extension layout in CLAUDE.md - #122

Open
savvides wants to merge 1 commit into
mainfrom
claude/claude-md-improvements-43a068
Open

savvides wants to merge 1 commit into
mainfrom
claude/claude-md-improvements-43a068

Conversation

@savvides

Copy link
Copy Markdown
Owner

What

Adds 17 lines to CLAUDE.md. No existing wording changes.

  • Commands: bin/idstack-consensus status (also: configure, query, verify, sync).
  • Releasing: the four-part version must agree across VERSION, .claude-plugin/plugin.json, CHANGELOG.md, README.md and docs/index.html; what a v* tag push does in release.yml. The extension version and the manifest schema version (1.4) are bumped separately.
  • Chrome extension: what each folder holds; no package.json, no build step, native ES modules.
  • Evidence standards: a note that test/test-evidence-labels.mjs parses the tier table, so the table and TIER_METADATA must change together.
  • Evidence verification (Consensus API): how the review skills verify staged findings, the order the API key is looked up in, and where responses are cached (IDSTACK_CONSENSUS_CACHE_DIR).

Why

An audit of CLAUDE.md found every count, path and flag still current. The gaps were the release gate (spread across three checkers and a workflow), the Consensus CLI that three skills and the preamble call, the extension layout, and an unmarked test dependency on the tier table.

For reviewers

  • The hard-coded test counts are unchanged. They match a live run, and smoke-test's comment relies on CLAUDE.md listing them.
  • Checks run locally: check-doc-accuracy.py exits 0, smoke-test 405/405, test-extension.sh passes, mutation-test 142 guarded / 0 not guarded.

🤖 Generated with Claude Code

Add the release version-agreement rules and tag flow, the Consensus
evidence-verification path, a short Chrome extension layout note, and a
warning that test-evidence-labels.mjs parses the tier table.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

This branch has not been deployed

No deployments
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