fix(cli): correct the shipped provenance claim, and record the two new declarations in the CI filter-parity pin

Two review findings from PR #15974.

1. The head reddened `check-ci-filter-parity --self-test`: the pre-#10015
   rollback now uncovers 21 globs, not 19. Measured, the delta is exactly the
   two `content/docs` pages this branch declared for `@objectstack/cli`
   (troubleshooting.mdx, getting-started/index.mdx) — an origin/main control
   yields 19 with an empty symmetric difference otherwise. Both are recorded by
   name, the way the pin's own comment prescribes for #14824's three, rather
   than the count merely being bumped.

2. The shipped history claim was wrong. `dbb54e12f0c` (2026-05-25) added the
   bundled template at `^5.3.0`, not `^6.0.0`; `eaff01425b7` (#2907,
   2026-07-14) moved it to `^6.0.0` and recorded no reasoning about TypeScript
   — in that same one-file diff the five `@objectstack/*` ranges move
   `^6.0.0` to `^14.0.0` while the `typescript` line moves onto the `^6.0.0`
   they are vacating. So the three-value split is 53 days old, not 102, and
   the two-value split is 210 (the changeset said 211). Corrected in init.ts,
   create.ts, the pin's header and the changeset, which now agree.

A dated provenance claim written into source comments is exactly the restated
fact nothing checks that this card exists to close; shipping a wrong one inside
the fix would have been self-refuting.

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

Author: os-litant

.changeset/scaffold-emission-policy-one-definition.md

@@ -4,7 +4,7 @@
 
 `objectstack init` and `objectstack create` now read one emission policy instead of each restating it.
 
-Both commands write a `tsconfig.json` and a set of third-party dependency ranges into a new project. Each had written those in its own words, and the words had come apart. Measured on the tree: the TypeScript range — the value that decides whether a scaffolded project type-checks at all — was written in six places across three scaffolders and had split into three values (`^5.3.0`, `^5.8.0`, `^6.0.0`); the vitest range into two. The two CLI values were written in the same commit and stayed apart for 211 days.
+Both commands write a `tsconfig.json` and a set of third-party dependency ranges into a new project. Each had written those in its own words, and the words had come apart. Measured on the tree: the TypeScript range — the value that decides whether a scaffolded project type-checks at all — was written in six places across three scaffolders and had split into three values (`^5.3.0`, `^5.8.0`, `^6.0.0`); the vitest range into two. Dated off `git log -G` as of 2026-09-05: the two CLI values were written in the same commit and stayed apart for 210 days, and the third value is 53 days old — the bundled template landed at `^5.3.0` like the others and was moved to `^6.0.0` later, in a commit that records no reasoning about TypeScript.
 
 The control for that reading was already in the same file: `SCAFFOLD_PNPM_RANGE` and `renderPnpmWorkspaceYaml()` are imported by the second scaffolder rather than restated, and across the same five emissions, the same window and the same authors, they had not drifted at all. So the policy moved to where those already live — `renderScaffoldTsconfig()` and one `SCAFFOLD_*_RANGE` constant per dependency, in `init.ts`, imported by `create.ts`.
 

packages/cli/src/commands/create.ts

@@ -65,8 +65,9 @@
  * already been paid for twice in this repo: the build-approval block landed in
  * one scaffold path and not the other, and one of them shipped the pre-fix shape
  * for months; and the TypeScript range a scaffold installs was written in six
- * places and split into three values, the split surviving 102 days on the value
- * that decides whether the scaffold type-checks at all. The emission policy has
+ * places and split into three values — the two CLI values 210 days apart, the
+ * third 53 and recorded nowhere — on the value that decides whether the
+ * scaffold type-checks at all. The emission policy has
  * one home now — see the block above `renderScaffoldPackageJson` in `init.ts`
  * for the measurement and for which values survived.
  *

packages/cli/src/commands/init.ts

@@ -234,12 +234,24 @@ export const SCAFFOLD_PNPM_RANGE = '>=10.15';
 //   os create           `^5.8.0`   (two write points in create.ts)
 //   create-objectstack  `^6.0.0`   (its bundled template's package.json)
 //
-// The split is not recent and nobody caused it deliberately: `^5.3.0` and
-// `^5.8.0` were written in the same commit (2026-02-07), and the third value
-// arrived with the bundled template on 2026-05-25 — 102 days of three
-// scaffolders answering "which TypeScript does a new ObjectStack project
-// install?" three different ways, on the value that decides whether the
-// scaffold type-checks at all.
+// The split is not recent and nobody caused it deliberately. Read off `git
+// log -G` over the three files, as of 2026-09-05:
+//
+//   338e68d2564  2026-02-07  `^5.3.0` and `^5.8.0` written in the SAME commit
+//                            — 210 days apart and counting
+//   dbb54e12f0c  2026-05-25  the bundled template lands, also at `^5.3.0`
+//                            — so this is still a TWO-value tree
+//   eaff01425b7  2026-07-14  that template's line moves `^5.3.0` → `^6.0.0`
+//                            — the third value, 53 days old
+//
+// ⚠️ And the move that made the third value recorded no reasoning about
+// TypeScript at all. #2907's commit message documents the `@objectstack/*`
+// version sync and nothing else, and in that same one-file diff the five
+// `@objectstack/*` ranges move `^6.0.0` → `^14.0.0` while the `typescript`
+// line moves ONTO the `^6.0.0` those lines are vacating. Whatever the intent
+// was, no statement of it exists — which is the point: an unrecorded value is
+// what a restatement decays into, and it decayed on the value that decides
+// whether a new project type-checks at all.
 //
 // The control for that reading is in this same file: `SCAFFOLD_PNPM_RANGE`
 // and `renderPnpmWorkspaceYaml()` are IMPORTED by the other scaffolder rather

packages/cli/test/scaffold-emission-policy.e2e.test.ts

@@ -11,9 +11,12 @@
  * whether a scaffolded project type-checks at all — was written in SIX places
  * across three scaffolders and had split into THREE values (`^5.3.0` in
  * `init.ts`, `^5.8.0` in `create.ts`, `^6.0.0` in the bundled
- * `create-objectstack` template). vitest had split into two. The two CLI values
- * were written in the SAME commit and stayed apart for 211 days; the third
- * arrived 102 days before the measurement.
+ * `create-objectstack` template). vitest had split into two. Dated off `git
+ * log -G` as of 2026-09-05: the two CLI values were written in the SAME commit
+ * (338e68d2564, 2026-02-07) and stayed apart for 210 days; the bundled template
+ * landed at `^5.3.0` too (dbb54e12f0c, 2026-05-25) and only became the third
+ * value 53 days ago, when eaff01425b7 moved it to `^6.0.0` without recording
+ * any reasoning about TypeScript.
  *
  * The control for that reading sits in the same file as the defect:
  * `SCAFFOLD_PNPM_RANGE` and `renderPnpmWorkspaceYaml()` are IMPORTED by the

scripts/check-ci-filter-parity.mjs

@@ -680,14 +680,20 @@ export async function selfTest() {
   // @objectstack/cli: `os create`'s emitted plugin shape is stated nowhere but
   // its documentation, so the pin holding the template to it reads all three
   // pages, each covered only through the `content/**` root #10015 added.
-  // Ten plus one plus two plus one plus one plus one plus three: the rollback
-  // now uncovers nineteen. This pin is judged over the LIVE declaration table on
-  // purpose: a declaration added under a root the rollback keeps leaves the
-  // count alone, one under a new root moves it and is recorded here by name.
+  // Plus, since #15818, the two doc pages THAT card declared for the same
+  // package: the TypeScript floor both scaffolders emit was chosen because those
+  // two pages already promise it, so the pin holding the emitted range to that
+  // promise reads both -- and each is covered only through the same `content/**`
+  // root, exactly like #14824's three.
+  // Ten plus one plus two plus one plus one plus one plus three plus two: the
+  // rollback now uncovers twenty-one. This pin is judged over the LIVE
+  // declaration table on purpose: a declaration added under a root the rollback
+  // keeps leaves the count alone, one under a new root moves it and is recorded
+  // here by name.
   const preFix = judge(fixtureWorkflow({ core: real.filters?.core, crosspkg: ['scripts/**'] }), CROSS_PACKAGE_TEST_INPUTS);
   assert(
-    new Set(uncoveredGlobs(preFix)).size === 19,
-    `rolling \`crosspkg\` back to its pre-#10015 list uncovers the ten it fixed plus #10848's one plus #10178's two plus #12201's one plus #12924's one plus #14561's one plus #14824's three -- got ${new Set(uncoveredGlobs(preFix)).size}`,
+    new Set(uncoveredGlobs(preFix)).size === 21,
+    `rolling \`crosspkg\` back to its pre-#10015 list uncovers the ten it fixed plus #10848's one plus #10178's two plus #12201's one plus #12924's one plus #14561's one plus #14824's three plus #15818's two -- got ${new Set(uncoveredGlobs(preFix)).size}`,
   );
   assert(
     uncoveredGlobs(preFix).includes('skills/**'),
@@ -723,6 +729,15 @@ export async function selfTest() {
       `-- and #14824 added the \`os create plugin\` scaffold-listing page ${page}, by name`,
     );
   }
+  for (const page of [
+    'content/docs/deployment/troubleshooting.mdx',
+    'content/docs/getting-started/index.mdx',
+  ]) {
+    assert(
+      uncoveredGlobs(preFix).includes(page),
+      `-- and #15818 added the TypeScript-floor page ${page}, by name`,
+    );
+  }
 
   // ── (7) WIRING: the gate and its self-test really run in CI ──────────────
   battery('(7) WIRING: the gate and its self-test really run in CI');
@@ -794,7 +809,7 @@ export async function selfTest() {
       `same-root-different-file case observed failing and then covered by naming the file, a glob covered by ` +
       `\`core\`, one covered only by \`crosspkg\` and one covered by neither judged separately in one table, the ` +
       `stale-entry direction, seven refusals over subjects that could not be read, the checked-in ci.yml, the ` +
-      `pre-#10015 rollback uncovering the ten it fixed plus #10848's one plus #10178's two plus #12201's one plus #12924's one plus #14561's one plus #14824's three, ` +
+      `pre-#10015 rollback uncovering the ten it fixed plus #10848's one plus #10178's two plus #12201's one plus #12924's one plus #14561's one plus #14824's three plus #15818's two, ` +
       `and the CI wiring read out of lint.yml.`,
   );
   selfTestReachedVerdict = true;