Skip to content

feat(ready): the content category's contracts; wordpress-cli in shared-roots - #664

Merged
leemour merged 3 commits into
mainfrom
feat/wordpress-content-ready
Nov 19, 2026
Merged

leemour merged 3 commits into
mainfrom
feat/wordpress-content-ready

Conversation

@leemour

@leemour leemour commented Nov 19, 2026

Copy link
Copy Markdown
Member

Why

cli-dev ready on a content CLI (cli-template 0.32.0 new --from-config with category: "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: content and new's label ask for contentSourceContract, contentSyncContract and contentWriteContract (cli-core 0.707.0 exports all three from @wirecat/cli-core/content/testing; the sync contract runs over any store).
  • wordpress-cli joins shared-roots and holds 03:17 UTC in WC-CI-9's table. It is not in the family packages, so audit --family installs nothing for it until it is on npm, as with attio and hubspot.
  • TOOLING.md lists every member of shared-roots and crm.

Testing

  • src/dev/ready.test.ts: a content CLI with the three contracts is verified, by value and by label; one without contentSyncContract is not.
  • pnpm vitest run src/dev/ready.test.ts src/dev/audit.test.ts src/standards, pnpm docs:check, changelog fragments.
  • Reviewed by a fresh agent: fragment heading, a wrong comment and the TOOLING.md list fixed. The template's content seed still lacks the sync contract: a cli-template PR follows.

🤖 Generated with Claude Code

leemour and others added 3 commits November 19, 2026 07:21
…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
leemour merged commit 15d0c22 into main Nov 19, 2026
10 checks passed
@leemour
leemour deleted the feat/wordpress-content-ready branch November 19, 2026 06:31
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>
@leemour leemour mentioned this pull request Nov 19, 2026
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>
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