Skip to content

docs: align suite framing with cross-CLI INTEROP (template-vault-cli v0.4.8)#187

Merged
DrBaher merged 2 commits into
mainfrom
docs/suite-framing-interop
May 19, 2026
Merged

docs: align suite framing with cross-CLI INTEROP (template-vault-cli v0.4.8)#187
DrBaher merged 2 commits into
mainfrom
docs/suite-framing-interop

Conversation

@DrBaher
Copy link
Copy Markdown
Owner

@DrBaher DrBaher commented May 19, 2026

Summary

Aligns the README's suite-header framing with the cross-CLI interop contract published in template-vault-cli's docs/INTEROP.md and the corresponding sibling-issue (§5 sign-cli) in docs/SIBLING-ISSUES.md. template-vault-cli v0.4.8 is now shipped, so the framing it specifies is no longer forthcoming.

  • Adds template-vault-cli as the storage layer feeding the pre-execution pipeline
  • Adds draft-cli at the start of the chain (previously missing — sign-cli's README started at nda-review-cli)
  • Adds compare-cli as the cross-version drift detector (sibling, not in the linear chain)
  • Replaces ""three-CLI contract suite"" → ""contract-operations CLI suite""

Change

One line — the suite-header blockquote at the top of README.md.

Before:

Part of the three-CLI contract suite. nda-review-cli (draft, review, negotiate) → docx2pdf-cli (DOCX → PDF) → sign-cli (signing + audit). Showcase site.

After:

Part of the contract-operations CLI suite. template-vault-cli (storage) feeds the pipeline: draft-cli (fill placeholders) → nda-review-cli (review, redline, negotiate) → docx2pdf-cli (DOCX → PDF) → sign-cli (signing + audit). Drift detection via compare-cli. Showcase site.

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)

  • No version bump, CHANGELOG entry, or tag — this is a docs nudge, not a release
  • No new flags (--why, -V, etc.) — those conventions are target-state for a separate PR
  • No new dev tooling

Test plan

  • npm run lint:legal-claims — clean (31 files scanned)
  • npm run typecheck — clean
  • npm test — 766 / 767 pass, 1 skipped, 0 failures (~14s)

Push only — please review and merge.

🤖 Generated with Claude Code

DrBaher and others added 2 commits May 19, 2026 20:35
…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>
@DrBaher DrBaher merged commit 1999528 into main May 19, 2026
@DrBaher DrBaher deleted the docs/suite-framing-interop branch May 19, 2026 18:41
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