Repository navigation
feat(ready): the content category's contracts; wordpress-cli in shared-roots - #664
Merged
Merged
Conversation
…d-roots cli-dev ready asked a content CLI's DESIGN.md category and found no entry, so its contracts row was never verified. It now asks for contentSourceContract, contentSyncContract and contentWriteContract by the category's value or new's label. wordpress-cli joins the shared-roots parity group and holds 03:17 UTC in WC-CI-9's table. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- the fragment puts wordpress-cli's join under Added - audit.ts says wordpress-cli shares only the roots, not the crm group - TOOLING.md lists every shared-roots and crm member - a test that a content CLI without contentSyncContract is not verified Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…erified Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
leemour
added a commit
that referenced
this pull request
Nov 19, 2026
bin/release raised the published 0.123.0 section to 0.124.0 and dropped the fragment of #664. Put 0.123.0 back and give 0.124.0 the fragment's entries. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Merged
leemour
added a commit
that referenced
this pull request
Nov 19, 2026
Releases 0.124.0: `cli-dev ready` knows the content category, and wordpress-cli joins `shared-roots` (#664). bin/release first renamed the published 0.123.0 section to 0.124.0 and dropped #664's fragment. The second commit puts 0.123.0 back and makes the fragment 0.124.0's section. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
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.
Why
cli-dev readyon a content CLI (cli-template 0.32.0new --from-configwithcategory: "content") said the DESIGN.md category "blog or site content (posts, pages, tags)" is no category new writes, so its contracts row could never be verified. Found while building wordpress-cli, the first content CLI.What
CATEGORY_CONTRACTS:contentand new's label ask forcontentSourceContract,contentSyncContractandcontentWriteContract(cli-core 0.707.0 exports all three from@wirecat/cli-core/content/testing; the sync contract runs over any store).shared-rootsand holds 03:17 UTC in WC-CI-9's table. It is not in the family packages, soaudit --familyinstalls nothing for it until it is on npm, as with attio and hubspot.shared-rootsandcrm.Testing
src/dev/ready.test.ts: a content CLI with the three contracts is verified, by value and by label; one withoutcontentSyncContractis not.pnpm vitest run src/dev/ready.test.ts src/dev/audit.test.ts src/standards,pnpm docs:check,changelog fragments.🤖 Generated with Claude Code