test(cli): drive migrate audit-metadata-bodies in the --json stdout-purity family

[objectstack-fleet]

Fixes #21347
Clause-②: no

What

packages/cli/test/json-stdout-purity.e2e.test.ts discovers its family from the source tree (every command whose comment-masked source calls bootSchemaStack( and declares a json: Flags.boolean( flag) and reconciles that set against FAMILY. os migrate audit-metadata-bodies (added by 336e191, PR #21144) joined the discovered set without joining FAMILY, so the nightly e2e tier went red on main on the reconciliation case.

This PR lists it in FAMILY with its bare argv ([]). The command's default is a read-only dry run, so the drive boots the stack with plugin-audit's objects registered, reads sys_audit_log / sys_activity, and writes nothing. The three per-member purity assertions now run against it: one JSON document on stdout through a bare JSON.parse, no kernel-logger record on stdout, and every boot diagnostic on stderr. discoverFamily is untouched, and the failing case keeps its name and body.

No command change was needed. Driven under --json, its stdout is exactly one document (measured below), so this PR does not touch packages/cli/src/commands/migrate/audit-metadata-bodies.ts, which has another change in flight.

Measurements

All readings are at this branch's single commit 105d266829, unless the table names another tree.

reading	tree	result
repro: OS_TEST_TIERS=nightly pnpm --filter @objectstack/cli exec vitest run --maxWorkers=2 test/json-stdout-purity.e2e.test.ts	43e928dd4c (origin/main, unmodified)	1 failed, 40 passed. AssertionError: expected [ 'meta resync', …(13) ] to deeply equal [ 'meta resync', …(12) ]; the extra member is migrate audit-metadata-bodies
the same command	105d266829	44 of 44 passed (41 plus this member's 3)
sibling test/config-miss-stdout-purity.e2e.test.ts, nightly tier	105d266829	174 of 174 passed
pnpm --filter @objectstack/cli typecheck (src plus the test layer)	105d266829	exit 0
pnpm --filter @objectstack/cli exec vitest run --project unit --maxWorkers=2	105d266829	244 files passed. Two published-subpath-*.pin files refused because packages/cli/dist was absent, which is a prerequisite refusal and not a measurement. After a cached full build, both re-ran green (29 of 29)

Direct drive of the member (a dry run against the uncompiled fixture and a fresh SQLite file): exit 0. Stdout is one JSON document: database, apply: false, a report with sys_audit_log and sys_activity each at 0 scanned / 0 rewritten, failures: 0, and duration. Stderr carries [StandaloneStack] no compiled artifact, Bootstrap complete, Graceful shutdown complete and the runner's own [stored-metadata-body-migration] would rewrite 0 of 0 … line.

Ablation

The fix was committed first (HEAD 105d266829). The mutation ran through node scripts/ablation-replace.mjs --anchor " 'migrate audit-metadata-bodies': []," --delete, wrapping the nightly command above:

• Mutation: it landed on disk. The anchor count went from 1 to 0, and the blob changed from 2b249b4b8c54 to 4389d5638a10. A grep in the child counted 0 before the suite started.
• Suite: 1 failed, 40 passed, with the original signature: expected [ 'meta resync', …(13) ] to deeply equal [ 'meta resync', …(12) ].
• Restore: the blob after restore, 2b249b4b8c54, equals the HEAD blob. git diff HEAD and git status --porcelain are both empty.

Gates

I ran node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack --commands with no paths. Its change set is this one file against merge base 43e928dd4. It derived 50 commands, which ran one after another at 105d266829, with each exit code recorded before any pipe.

• Exit 0: 49 commands.
• Exit 3: pnpm check:dual-build-cjs-loads (PREREQUISITE NOT MET, because 9 packages had no dist/). After a cached full build at the same HEAD, it re-ran with exit 0: 105 require entry points across 66 packages load.
• --ran reconciliation over the first sweep: 50 derived, 49 run, 1 NOT-MEASURED (the line above), 0 UNRUN.

The derivation also printed a stale-tree note. Local origin/main had moved past the base and changed .github/workflows/release.yml, scripts/release-pending-publish.mjs and scripts/release-verify-npm.mjs. The workflow change adds one invocation of a release script inside a release job. No PR gate places it on this path.

Lint was narrowed to the one changed file. eslint --no-inline-config --format json reported 1 file, 0 errors and 0 warnings. That file is the population eslint's own --print-config matches (5 rules). The config enables no type-aware linting (no parserOptions.project, no projectService), so this diff cannot move any untouched file's verdict. The repo-wide pnpm lint belongs to CI.

Changeset

None. The diff is test-only, and @objectstack/cli publishes only dist, README.md and CHANGELOG.md.

Acceptance notes

• The reconciliation case is pure source analysis, with no boot behind it. It still lives in a nightly-tier file, so the PR that added this member could not see it go red, and main found out only from the nightly. The pre-boot sibling (config-miss-stdout-purity.e2e.test.ts) has the same shape. Observation only, nothing filed. Carrier: none.

---

Generated by Claude Code

[github-actions]

📓 Docs Drift Check

Nothing in this diff resolved to a documentable surface (no symbol, route or SDK anchor derived from 0 changed package(s)), so this run has no opinion about the docs.

What this run could not see

• a page that states a rule by its inputs shares no identifier with the emitter that implements the rule, so an emitter-only diff cannot list it — not on this run and not on any run. Measured on fix(driver-sql): emit varchar(maxLength) for a text field a declared index keys on #11430: content/docs/protocol/objectql/types.mdx documents the text-family column mapping by the ObjectQL type names it maps FROM (text / textarea / html) while the diff changed createColumn; it went unlisted, and it was the page that diff falsified, in four places. No shared token exists to detect this on, so a rule your change carries has to be re-read by hand in the pages that restate it.
• a key NAME is not a key, so the hand re-read the line above prescribes can land on the wrong schema. The same spelling is authorable on one governed type and a [REMOVED] tombstone on another for each of active, aria, joins, objects, template, tools and version (censused on [finding] tools is a key on BOTH AgentSchema (tombstoned, dead) and SkillSchema (live, cloud-attested), so a name-based search attributes skill examples to the agent key — it produced a false stop-the-line alarm on PR #19059 #19093 over the liveness ledger's governed types, top-level keys); nothing in a search result distinguishes the two, so a grep hit on a LIVE example reads as evidence about the DEAD key. Measured on fix(spec): the agent.tools liveness row says dead — it claimed live on a key the schema tombstoned #19059: content/docs/ai/agents.mdx was reported as contradicting the agent.tools tombstone over its tools: example at :161, which is inside the defineSkill({ block opened at :155 — the page was already correct. Settle ownership by PARSING the value against both schemas, never by the name: that literal PASSES SkillSchema, and as an AgentSchema it FAILS at tools with the tombstone prescription. ⛔ These names are not the whole class — a key retired through a .strict() guidance map leaves no tombstone in the walked shape and none of them here (tool.category, live as AIToolDefinition.category).

Coarse fallback — 0 page(s) merely mention a changed package (the pre-#9192 predicate, kept for the deliberately-wide backstop): node scripts/docs-audit/affected-docs.mjs --json 51550933dbc5c7cbd89349a6beb5145363fc881d → packageMentionDocs.