diff --git a/changes/feat-wordpress-content-ready.md b/changes/feat-wordpress-content-ready.md new file mode 100644 index 0000000..b1015c9 --- /dev/null +++ b/changes/feat-wordpress-content-ready.md @@ -0,0 +1,6 @@ +### Added + +- **`cli-dev ready` knows the content category.** A CLI whose `docs/dev/DESIGN.md` names `content` (or `new`'s label, + "blog or site content (posts, pages, tags)") is asked for cli-core's `contentSourceContract`, `contentSyncContract` + and `contentWriteContract`. Before, its contracts row said the category was unknown. +- **wordpress-cli joins the `shared-roots` parity group**, and its monthly run holds 03:17 UTC in WC-CI-9's table. diff --git a/docs/TOOLING.md b/docs/TOOLING.md index b5f7b10..9e939fb 100644 --- a/docs/TOOLING.md +++ b/docs/TOOLING.md @@ -113,8 +113,8 @@ a group covering the whole tree has the same paths), `same-flag-meaning`, `same- =`) and `same-error-reason` (from `--reasons =`, a JSON list of `defineReasons` entries). The two last rules print `n/a` for a CLI that gave no such file. `PARITY_GROUPS` names who is compared where — `messengers` (tg, max) over the whole tree, `all` over the shared roots, `mail-shared` and `gcal-shared` over the roots mail and -gcal already share, `shared-roots` over `commands`, `doctor`, `skill`, `mcp` and `upgrade` for b24, beeline, pbx, notion, amo and hubspot, `crm` (b24, -amo, hubspot) over the CRM roots they share — and each group's declared `differences`, each with a reason, at most 10. `--groups ` +gcal already share, `shared-roots` over `commands`, `doctor`, `skill`, `mcp` and `upgrade` for b24, beeline, pbx, notion, amo, hubspot, attio, ydisk and wordpress, `crm` (b24, +amo, hubspot, attio) over the CRM roots they share — and each group's declared `differences`, each with a reason, at most 10. `--groups ` replaces `PARITY_GROUPS` with the JSON list of groups in that file, in the same shape and checked the same way, so a CLI outside WireCatLabs keeps its own groups in its repository and lists itself next to ours; `--differences ` (entries of `group`, `rule`, `target`, `expected`, `reason`) then adds to whichever groups diff --git a/docs/standards/ci.md b/docs/standards/ci.md index 4b69c78..942d77c 100644 --- a/docs/standards/ci.md +++ b/docs/standards/ci.md @@ -189,6 +189,7 @@ its prompt in cli-template says so from cli-template 0.8.0. A CLI on an older te | 03:09 | beeline-cli | | 03:11 | hubspot-cli | | 03:13 | zoom-cli | + | 03:17 | wordpress-cli | | 03:20 | cli-docs | - **Exceptions:** cli-core also builds and probes its native packages in their own workflows, after the window: diff --git a/src/dev/ready.test.ts b/src/dev/ready.test.ts index 8fb9160..ec76c52 100644 --- a/src/dev/ready.test.ts +++ b/src/dev/ready.test.ts @@ -247,6 +247,26 @@ describe("cli-dev ready", () => { } }) + it("asks a content CLI for cli-core's content contracts, by the category's value or its label", () => { + for (const category of ["content", "blog or site content (posts, pages, tags)"]) { + const cwd = cli({ + "docs/dev/DESIGN.md": `- **Category:** ${category}\n`, + "src/content.test.ts": "contentSourceContract(make)\ncontentSyncContract(make)\ncontentWriteContract(make)\n", + }) + expect(row(cwd, shell(cwd, { "src/content.test.ts": ["passed"] }).run, "contracts")?.status).toBe("verified") + } + const noSync = cli({ + "docs/dev/DESIGN.md": "- **Category:** content\n", + "src/content.test.ts": "contentSourceContract(make)\ncontentWriteContract(make)\n", + }) + expect(row(noSync, shell(noSync, { "src/content.test.ts": ["passed"] }).run, "contracts")).toMatchObject({ + status: "partially", + fix: + "run cli-core's contentSyncContract in a test (testing.md), or except it in lint/contract-exceptions.json " + + "with its reason, then run cli-dev ready again", + }) + }) + it("does not verify the live check from another version's record or from code changed since", () => { const other = cli({ "docs/dev/live-checks.txt": "0.2.0 abc123 2026-11-10 bin/acme-live\n" }) expect(row(other, shell(other).run, "live")).toMatchObject({ diff --git a/src/dev/ready.ts b/src/dev/ready.ts index 01888c1..0fc6fa1 100644 --- a/src/dev/ready.ts +++ b/src/dev/ready.ts @@ -59,6 +59,10 @@ const CATEGORY_CONTRACTS: { names: string[]; contracts: string[] }[] = [ ], }, { names: ["tracker", "issue tracker (issues, projects, teams)"], contracts: ["trackerSourceContract"] }, + { + names: ["content", "blog or site content (posts, pages, tags)"], + contracts: ["contentSourceContract", "contentSyncContract", "contentWriteContract"], + }, { names: ["messenger", "notes"], contracts: [] }, ] diff --git a/src/standards/audit.ts b/src/standards/audit.ts index 3a3d3a1..f2caad4 100644 --- a/src/standards/audit.ts +++ b/src/standards/audit.ts @@ -201,6 +201,7 @@ export const PARITY_GROUPS: ParityGroup[] = defineParityGroups([ // bitrix24-cli's search is cli-core's CRM `search all`, and beeline-cli's and asterisk-cli's meetings take call // recordings, not zoom-cli's: they are compared on the root commands every CLI shares, the way gcal and mail are. // amo-cli, hubspot-cli and attio-cli share them too, and their CRM commands are compared with b24 in `crm` below. + // wordpress-cli shares only these roots: it is the first content CLI, so its posts commands have no group yet. // notion-cli joins here until its documents commands ship; then it moves next to drive. ydisk joins here too: in "all" // its search and notes differ from the messengers' and memo's as drive's do, and a documents group of drive, notion // and ydisk differs in 39 paths (session, folders browse, summaries; measured on the published CLIs 2026-11-17). @@ -221,6 +222,7 @@ export const PARITY_GROUPS: ParityGroup[] = defineParityGroups([ "hubspot", "attio", "ydisk", + "wordpress", ], covers: ["commands", "doctor", "skill", "mcp", "upgrade"], differences: [...MEMO_HAS_NO_PROFILES, ...MEMO_MCP_SUMMARIES, MEMO_DOCTOR_DEEP],