docs: align suite framing with cross-CLI INTEROP (template-vault-cli v0.4.8)#24
Merged
Conversation
…v0.4.8) The README's suite blockquote listed the four-stage draft → review → convert → sign chain but didn't reference template-vault-cli (the storage layer that feeds draft-cli via `template-vault get <ref>`) or compare-cli (the auxiliary drift detector). Both are referenced elsewhere in the README's body — only the top-of-file framing was out of date. This matches the cross-CLI convention now codified in template-vault-cli v0.4.8's docs/INTEROP.md and SIBLING-ISSUES.md §1.
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
1 participant
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
The README's "Part of the contract-operations CLI suite" blockquote listed
draft → review → convert → signbut didn't reference template-vault-cli (the storage layer that feedsdraft-cliviatemplate-vault get <ref>) or compare-cli (the auxiliary drift detector).template-vault-cli landed in v0.4.x with full
info --jsonoutput that draft-cli could consume to know what placeholders to expect. This PR brings the top-of-README framing into line with the convention codified in template-vault-cli v0.4.8'sdocs/INTEROP.mdanddocs/SIBLING-ISSUES.md§1.What changed
One line edited in
README.md— the existing suite blockquote now ends withStorage layer: template-vault-cli. Drift detection: compare-cli.before the "Showcase site" link. Style and tone match the existing one-line blockquote convention this repo uses (rather than the multi-line example in SIBLING-ISSUES.md).Out of scope (per the brief)
--from-vault <ref>flag, no JSON Schema consumption, no INTEROP-target conventions (--demo,--why, color helpers, etc.). The brief explicitly parks these as separate work.template-vault getandtemplate-vault-clicorrectly — left untouched.Test plan
npm test→ 288/288 pass, 0 fail🤖 Generated with Claude Code