Commands and verification
The block below is compared character by character with the accepted lifecycle decision. If they drift apart, the documentation build fails.
Status: accepted0.2.0 has no release-verification script. What you rely on instead is simple and boring: exact versions and a frozen lockfile.
The lifecycle decision still lists the command below as planned work. Quoting it here is not an invitation to run it: it does not work today, it is not part of the currently verified workshop path and must not be presented as runnable until its release gate is green.
pnpm workshop:verify -- --root "$RELEASE_ROOT"Run the starter’s typecheck and workflow test commands in a clean copy of the project. Confirm the tests really hit PostgreSQL, keep the output, and record the commit and the dependency versions that were actually resolved.
For the documentation project, G14 additionally requires format lint, JS lint,
the plain build, the CHECK_LINKS=true build, the documentation contract, and
the typecheck. The facilitator route table is valid only after all 27 curriculum
targets resolve to built pages. The lightweight #46 documentation test also
checks the external consumer’s byte-locked blocks without starting its
PostgreSQL runtime. The same G14 command also runs the Slidev build.
Start a second copy on the same machine, with its own state, and repeat the same checks.
Remote delivery, staging, production, signing, and promotion are not available. A command someone plans to build is not a command you can demonstrate.
For every run, record: the target, the revision, the package versions, the PostgreSQL image, the command, its exit status, and its output.
Redact credentials, tokens, full provider payloads, and personal data before you save any of it. Do it as you go — a bundle you have to sanitise afterwards usually doesn’t get sanitised.