test(scripts): give sync-template-versions a --self-test wired into Lint & Repo Gates (#9880)

* test(scripts): give sync-template-versions a --self-test covering the red paths and the CLEAN control

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XqDQYVU5smx29ts9pAErja

* fix(scripts): make the self-test's stamp-coverage control report before it can crash

Control G asserts every TEXT_STAMPS row has a fixture body, but it ran INSIDE
the fixture block. `buildFixture` indexes SELF_TEST_BODIES by key, so an
uncovered row threw `TypeError: SELF_TEST_BODIES[stamp.key] is not a function`
out of Control A and killed the process before the failure list was printed.
Measured by adding a fourth TEXT_STAMPS row with no body: exit 1 either way —
the gate held — but the one message written for this exact case never reached
the log in the exact case it was written for.

Ordering is the whole fix: the control moves ahead of the scratch dir (it needs
no fixture) and reports through a shared reportFailures(), which also replaces
the duplicated tail block. No case is added, removed or reworded.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XqDQYVU5smx29ts9pAErja

---------

Co-authored-by: Claude <noreply@anthropic.com>

Author: os-steve

.github/workflows/lint.yml

@@ -501,6 +501,42 @@ jobs:
       - name: Docs image-tag version-time rewriter self-test
         run: pnpm check:docs-image-tag-sync
 
+      # #9348 — the same treatment for the OTHER version-time rewriter, and the
+      # scheduling gap that made it necessary after #9648 already added a vitest
+      # file which runs the CLI. `create-objectstack#test` is reachable only from
+      # ci.yml's `test` job, which is gated on the `core` paths-filter; `core` is
+      # `packages/**`, `examples/**`, `apps/!(docs)/**`, `package.json`,
+      # `pnpm-lock.yaml`, `tsconfig.json`, `.github/workflows/ci.yml` and matches
+      # no path under `scripts/`. Measured with picomatch 4.0.5 (the matcher
+      # dorny/paths-filter uses): a diff confined to
+      # scripts/sync-template-versions.mjs yields core=false, so Test Core is
+      # skipped ENTIRELY on the PR that changes the rewriter, and with it the
+      # vitest. The two layers that look like they cover it do not: `turbo ls
+      # --affected` returns ZERO packages for that diff (a package-local edit
+      # returns 1, so the probe is live) — turbo.json's `$TURBO_ROOT$` entry
+      # moves the task HASH, which is what stops a cached green on the merge
+      # queue, not what schedules the job — and the `--union-into` step that DOES
+      # pull create-objectstack back in is a step inside the skipped job. The
+      # queue build catches it, one merge late, as batch collateral; that is the
+      # failure shape check-cross-package-test-inputs.mjs's own ledger records
+      # twice.
+      #
+      # This workflow carries no paths filter and no filter job, so this step
+      # runs on every pull request, push and merge-queue build. That is the whole
+      # reason the flag exists rather than more cases in the vitest file.
+      #
+      # Only the --self-test runs here, for the same reason as the step above:
+      # the rewriter has nothing to do on a green corpus. The cases are scoped to
+      # what the vitest does NOT assert — a CLEAN corpus left byte-identical and
+      # UNWRITTEN, and every red path (missing stamp, missing file, unparseable
+      # package.json, a template with no @objectstack/* dependency, the empty
+      # templates directory) observed exiting 1 and naming the file. The STALE ->
+      # rewritten direction and the discovery walk stay in
+      # packages/create-objectstack/src/template-version-stamps.test.ts; two
+      # harnesses asserting the same thing would be worse than one.
+      - name: Template version-time rewriter self-test
+        run: pnpm check:template-version-sync
+
       # #4851: the docs-accuracy-audit workflow carries its default scope inline
       # (a workflow script runs in a vm with no filesystem, so it cannot enumerate
       # content/docs/ itself). Hand-kept, that list rotted in BOTH directions —

package.json

@@ -41,6 +41,7 @@
     "check:docs-redirects": "node scripts/check-docs-redirects.mjs --self-test && node scripts/check-docs-redirects.mjs",
     "check:docs-image-tag": "node scripts/check-docs-image-tag.mjs --self-test && node scripts/check-docs-image-tag.mjs",
     "check:docs-image-tag-sync": "node scripts/sync-docs-image-tags.mjs --self-test",
+    "check:template-version-sync": "node scripts/sync-template-versions.mjs --self-test",
     "check:role-word": "node scripts/check-role-word.mjs --self-test && node scripts/check-role-word.mjs",
     "check:quick-reference-counts": "node scripts/check-quick-reference-counts.mjs --self-test && node scripts/check-quick-reference-counts.mjs",
     "check:runtime-services-index": "node scripts/check-runtime-services-index.mjs --self-test && node scripts/check-runtime-services-index.mjs",