docs: align suite framing with cross-CLI INTEROP (template-vault-cli v0.4.8)#187
Merged
Conversation
…v0.4.8) Per template-vault-cli's docs/SIBLING-ISSUES.md §5 and docs/INTEROP.md, update the suite header to (a) add template-vault-cli as the storage layer, (b) add draft-cli at the start of the pre-execution pipeline, and (c) add compare-cli as the cross-version drift detector. Keeps the existing bold-linked-name + short-parens tone. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…terop # Conflicts: # README.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Aligns the README's suite-header framing with the cross-CLI interop contract published in template-vault-cli's
docs/INTEROP.mdand the corresponding sibling-issue (§5 sign-cli) indocs/SIBLING-ISSUES.md. template-vault-cli v0.4.8 is now shipped, so the framing it specifies is no longer forthcoming.Change
One line — the suite-header blockquote at the top of
README.md.Before:
After:
Divergence from the SIBLING-ISSUES §5 sketch
§5's example uses bare
[name]-style placeholders. I instead matched the INTEROP.md authoritative example shape (linked-bold names + short parenthetical descriptors) because that preserves this README's existing voice — the current header already uses[**name-cli**](url)+ short parens for every tool. Functionally identical, stylistically aligned with what's already on the page.Out of scope (per the issue)
--why,-V, etc.) — those conventions are target-state for a separate PRTest plan
npm run lint:legal-claims— clean (31 files scanned)npm run typecheck— cleannpm test— 766 / 767 pass, 1 skipped, 0 failures (~14s)Push only — please review and merge.
🤖 Generated with Claude Code