v1.12.1

A documentation release. No command contracts, agents or shipped code changed; every path a new reader follows was checked against the command files and corrected.

The demo is every path's input

The demo was documented as step B1 of the step-by-step recipe, which read as though only that path needed one. Every path converts a demo: /wp-init reads it to learn the project, /wp-yolo converts it page by page, /wp-section --transcribe copies its declared values, and /wp-seed turns its files into WP Pages. There is no path that begins at WordPress.

That framing also hid an ordering trap. /wp-init has a demo-first flow: hand it a mockup and it copies the file into demo/, polishes it if it has no section delimiters, and reads the project name, industry, colours and fonts out of the file instead of interviewing you. Both docs put a bare /wp-init in setup before any mention of a demo, so a reader following the old order guaranteed that flow never triggered and answered by hand what the mockup already knew.

README.md and docs/workflows.md now carry a required demo stage between setup and build, with the three ways in:

• Have a mockup → /wp-init path/to/mockup.html (reads it, skips the interview)
• Have files in demo/ → /wp-polish demo/index.html
• Have nothing yet → /wp-init, then /wp-demo or /wp-cinematic-demo

The one real ordering rule is stated once: /wp-demo needs .claude/CLAUDE.md, so it runs after /wp-init.

A full pass for a new reader (#39)

• The README's opening How It Works diagram, the first thing a new user reads, still had the demo buried inside path B and contradicted the corrected section further down the same file. Rewritten.
• Three docs named a basic template that no longer exists; /wp-init keeps it only as a legacy alias for tailwind, and only two starters ship. Removed, and tailwind is stated as the default.
• Path A never said its prerequisite. Both build paths now open with a Needs: line pointing at the demo stage.
• /wp-demo-verify is the name shown everywhere, with /wp-responsive-check noted once as its alias, and docs/commands.md gains the demo section and the /wp-demo-verify table row it was missing.
• /wp-init's three questions state their defaults so a reader knows Enter takes all three.

Also on main after this tag

tests/checks/tailwind-docs.sh asserted that the newest CHANGELOG entry mentioned the Tailwind migrator, which only the release that shipped it could satisfy; it failed on this docs-only patch and would have failed on every release after. It now anchors on the [1.8.0] entry that shipped the pipeline and is verified against every tag from v1.8.0 onward. That fix is in 1cfe5b7, one commit after this tag, and changes no shipped behaviour.

Verification

49 check scripts pass and bin/doc-sync-check.sh passes. Every behaviour documented here was read out of the command files first.