From 4b7d344303af184e79624ac7828554fff4ca9343 Mon Sep 17 00:00:00 2001 From: Claude Date: Sat, 29 Aug 2026 00:44:26 +0000 Subject: [PATCH] docs(cli): drop stale family counts from json-stdout-purity docblock The docblock said "there are ten of them / the other nine / the eleventh" while the discovered FAMILY table now holds twelve. The prose is reader-facing only: the family is DISCOVERED from the source tree and reconciled against FAMILY, so no assertion, exit code or criterion reads these words. Removes the magnitude ("one implementation face per command", "the others", "a new one") rather than resetting it to twelve, so the drift construct is deleted instead of re-armed. The same stale "nine" in the beforeAll comment goes with it. The sharp measurements next to it (the ~60 INFO lines, the #4873 extractor, the two independent pollution sources) are untouched -- not being doubted because of an adjacent stale count is the whole point. Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_01UjujZN219uFzBhSYfMykCd --- .../cli/test/json-stdout-purity.e2e.test.ts | 22 +++++++++---------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/packages/cli/test/json-stdout-purity.e2e.test.ts b/packages/cli/test/json-stdout-purity.e2e.test.ts index 82aed8ccfd..af39210b78 100644 --- a/packages/cli/test/json-stdout-purity.e2e.test.ts +++ b/packages/cli/test/json-stdout-purity.e2e.test.ts @@ -15,16 +15,16 @@ * * ## Why the whole family, from one expectation * - * The contract has one implementation face per command, and there are ten of - * them. A file that pinned `migrate recorded-by` alone would go green while the - * other nine stayed broken, and would say nothing at all about the eleventh. So - * the family is DISCOVERED from the source tree — every command that calls - * `bootSchemaStack` and declares a `--json` flag — and the discovered set is - * reconciled against {@link FAMILY} below. Add a member and this file goes red - * until it is listed here and passes; drop one and it goes red until it is - * removed. The seam itself (`bootSchemaStack`'s required `jsonOutput` option) - * makes the mistake a compile error first; this is the runtime proof that the - * seam actually delivers the invariant. + * The contract has one implementation face per command. A file that pinned + * `migrate recorded-by` alone would go green while the others stayed broken, + * and would say nothing at all about a new one. So the family is DISCOVERED + * from the source tree — every command that calls `bootSchemaStack` and + * declares a `--json` flag — and the discovered set is reconciled against + * {@link FAMILY} below. Add a member and this file goes red until it is listed + * here and passes; drop one and it goes red until it is removed. The seam + * itself (`bootSchemaStack`'s required `jsonOutput` option) makes the mistake a + * compile error first; this is the runtime proof that the seam actually + * delivers the invariant. * * ## Deliberately an UNCOMPILED fixture * @@ -186,7 +186,7 @@ beforeAll(async () => { // Sequential, each on its own database file: several members create tables, // and a shared SQLite file would make one member's run depend on the order // the others happened to run in. Sequential also keeps peak memory at one - // booted kernel rather than nine. + // booted kernel rather than one per member. runs = []; for (const [id, extra] of Object.entries(FAMILY)) { const slug = id.replace(/[^a-z0-9]+/gi, '-');