nightly-tiers: red on main

[github-actions]

os-nightly-tiers — machine-findable marker for this generated card. ⛔ Do not delete this line: it is how the nightly finds this card instead of filing a new one every night.

nightly-tiers: red on main

Swept 2026-09-16T05:57:39.493Z · expected every 24h while this card stands (cron 29 5 * * * UTC) · next by 2026-09-17T05:29Z · run log · commit b57671edc1166d49be40993000894128b3a63b44 · trigger schedule · tiers job result failure.

The Swept line above is this nightly's heartbeat, and it states the cadence that makes
「stalled」 decidable: while the tiers stay red this card is refreshed on that schedule, so a
timestamp still sitting there past the next by deadline means either the standing caller
died or the nightly went green — nothing here files or closes anything on green, so both
readings end at this card. ⛔ Do not carry a cadence over from a sibling patrol anchor: they
differ by up to 4× and each states its own.

The e2e and live test tiers — the files named *.e2e.test.* and *.live.test.* — run here
nightly on main under OS_TEST_TIERS=nightly and nowhere else (the per-PR and merge-queue
Test Core runs under queue). A red here is a real suite that no pull request will red on;
this card is the channel that sees it. Nothing is blocked by it.

⛔ The remedy is never to rename, skip or delete the failing test to make the nightly green.
Reproduce locally with OS_TEST_TIERS=nightly pnpm --filter <pkg> test, fix what it names, and
let the next nightly refresh this card.

Failing files

• packages/cli/test/serve-port-readback.e2e.test.ts

shard-1 — last lines of the test log

… (8150 chars elided) …
s�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m 2b (--strict-body) — ⭐ carries the notice, where `warnings` is empty by construction �[33m 9969�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m 3 (protocol parse) — ⭐ carries the notice, where `warnings` is empty by construction �[33m 9966�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m ⭐ converts nothing — the SAME exit reports `[]`, so the field tracks the run �[33m 10462�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m 3b (author-time rules) — the notice rides the rule gate �[33m 10238�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m 3c (capability preflight) — the notice rides the preflight gate �[33m 10003�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m 3e (access-matrix drift) — the notice rides the drift gate �[33m 9865�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m 3f (package docs) — the notice rides the docs gate �[33m 10530�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m 4b (--no-runtime-bundle) — a late exit past every step carries the notice �[33m 9903�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m the catch-all — a THROWN failure still reports the computed notice �[33m 10149�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m catch-all (throw at load) — `conversions` is PRESENT and empty, because step 2 never ran �[33m 9974�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m REGRESSION GUARD — `warnings` and `conversions` stay separate fields �[33m 10370�[2mms�[22m�[39m
@objectstack/cli:test:  �[32m✓�[39m �[30m�[45m integration �[49m�[39m test/lint-eval-generator-load-envelope.e2e.test.ts �[2m(�[22m�[2m9 tests�[22m�[2m)�[22m�[33m 103511�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m a coded failure at import surfaces BOTH carriers on the --json face �[33m 10530�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m an errno thrown at import passes through as `code` �[33m 10111�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m the key set is exactly the carriers — no `conversions`, no filler �[33m 10638�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m the hand-thrown "must default-export a function" stays exactly `{error}` �[33m 10089�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m esbuild's BuildFailure carries neither key, so the payload stays bare �[33m 10446�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m the unresolvable path leaks nothing to stderr — and still refuses on stdout �[33m 10444�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m a generator that only WARNS leaks nothing either — and the human face still shows it �[33m 20548�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m the human path is unchanged: still exit 1, still no JSON document �[33m 10294�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m offline eval is untouched: exit 0 and a report, not an error envelope �[33m 10395�[2mms�[22m�[39m
@objectstack/cli:test:  �[32m✓�[39m �[30m�[45m integration �[49m�[39m test/lint-strict-warnings.e2e.test.ts �[2m(�[22m�[2m8 tests�[22m�[2m)�[22m�[33m 112785�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m ⭐ the fixture REALLY warns — ≥1 warning and 0 errors on the run under test �[33m 9959�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m without --strict the same stack exits 0 — the default is unchanged �[33m 10322�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m ⭐ with --strict the same stack exits 1 — passed:false, strict:true, failing === warnings �[33m 10215�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m ⭐ the console face says why — the count and the flag, and the count is the measured one �[33m 20219�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m the console face without the flag exits 0 and claims no strict failure �[33m 10463�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m suggestions stay advisory under --strict �[33m 9873�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m an error still fails with and without the flag, and --strict counts the warnings on top �[33m 21010�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m a clean stack exits 0 under --strict, in both faces �[33m 20712�[2mms�[22m�[39m
@objectstack/cli:test:  �[32m✓�[39m �[30m�[45m integration �[49m�[39m test/lint-hook-rules-reach-handler-hooks.e2e.test.ts �[2m(�[22m�[2m10 tests�[22m�[2m)�[22m�[33m 102391�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m INTAKE — a handler-authored hook writing a readonly field is refused (error, exit 1) �[33m 9742�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m CONTROL — the same statement as an explicit body is refused identically �[33m 9999�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m INTAKE — the lowered handler is refused at build, exit 1 — unchanged by this card �[33m 10285�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m CONTROL — the explicit body is refused at build identically �[33m 10214�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m INTAKE — the handler-authored hook IS refused here (error, exit 1) — the red-first leg of #16544 �[33m 10572�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m CONTROL — the explicit body is refused here, before and after, so the intake reading is about the door �[33m 10491�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m NEGATIVE CONTROL — a handler-authored hook the family has nothing to say about still passes (exit 0) �[33m 10232�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m INTAKE — `os validate` accepts the inline action target (exit 0, valid, no invalid_type) �[33m 10556�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m PARITY — `os build` accepts the same config (it lowered before its parse all along) �[33m 10173�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m INTAKE — a nameless `functions` array entry is accepted too (the pass names it `anon_fn`; exit 0, valid) �[33m 10118�[2mms�[22m�[39m
@objectstack/cli:test:  �[32m✓�[39m �[30m�[45m integration �[49m�[39m test/lint-conversion-notices.e2e.test.ts �[2m(�[22m�[2m6 tests�[22m�[2m)�[22m�[33m 72507�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m ⭐ the fixture REALLY converts — `--json` publishes the notice the run produced �[33m 10055�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m ⭐ converts nothing — the field is PRESENT and EMPTY, so it tracks the run �[33m 10445�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m ⭐ the human face says it too — the notice is printed, with its expiry �[33m 10466�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m ⭐ the human face stays SILENT when nothing converted �[33m 10256�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m catch-all at load — `[]` honestly, because the normalize step never ran �[33m 10440�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m REGRESSION GUARD — the notice is NOT folded into `issues`, and the counts are unchanged �[33m 20835�[2mms�[22m�[39m
@objectstack/cli:test:  �[32m✓�[39m �[30m�[45m integration �[49m�[39m test/migrate-apply-refuses-before-ddl.e2e.test.ts �[2m(�[22m�[2m10 tests�[22m�[2m)�[22m�[33m 33496�[2mms�[22m�[39m
@objectstack/cli:test:  �[32m✓�[39m �[30m�[45m integration �[49m�[39m test/lint-eval-empty-generator-refusal.e2e.test.ts �[2m(�[22m�[2m10 tests�[22m�[2m)�[22m�[33m 132632�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m refuses on the human face, naming the flag and the empty value it was given �[33m 9970�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m the --json face stays a machine face — one JSON document, nothing on stderr �[33m 10037�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m nothing is minted — the payload key set is exactly `error` �[33m 10804�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m differs from the no-flag run once the elapsed token is normalised �[33m 20041�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m both refuse: same exit code, refusal on stdout, generator never loaded �[33m 20450�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m both answer the same --json envelope: exit 1 and a lone `error` key �[33m 19851�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m `--eval` with the flag absent still runs the offline eval �[33m 10553�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m `--eval --generator <module>` still loads the generator and runs live �[33m 10396�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m an unresolvable generator path refuses exactly as it always has �[33m 10002�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m a plain project lint is untouched �[33m 10519�[2mms�[22m�[39m
@objectstack/cli:test:  �[32m✓�[39m �[30m�[45m integration �[49m�[39m test/lint-eval-json-unscorable-stack.e2e.test.ts �[2m(�[22m�[2m13 tests�[22m�[2m)�[22m�[33m 134646�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m a top-level poisoned getter: stdout is JSON, the case FAILED, the cause is named �[33m 10548�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m a poisoned getter BELOW the top level is caught too — the schema parse walks there �[33m 10108�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m ⛔ a silent swallow would be caught: the unscorable case is not scored as clean �[33m 9755�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m offline mode is untouched: exit 0 and every golden case passes �[33m 10761�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m a generator that THROWS is still a generation error, not a scoring one �[33m 10357�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m ⭐ every generation threw ⇒ meanScore 0 on the --json face, never 100 �[33m 10898�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m off-shape stack manifest-as-string is a SCORED case with schema errors, never a generationError �[33m 10801�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m off-shape stack objects-as-string is a SCORED case with schema errors, never a generationError �[33m 10411�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m off-shape stack objects-as-number is a SCORED case with schema errors, never a generationError �[33m 9990�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m off-shape stack objects-as-null is a SCORED case with schema errors, never a generationError �[33m 10231�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m off-shape stack nested-wrong-types is a SCORED case with schema errors, never a generationError �[33m 10163�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m off-shape stack bare-string is a SCORED case with schema errors, never a generationError �[33m 10264�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m a generator that cannot be loaded still takes the generator-load JSON exit �[33m 10351�[2mms�[22m�[39m
@objectstack/cli:test:  �[32m✓�[39m �[30m�[45m integration �[49m�[39m test/artifact-pinned-boot.e2e.test.ts �[2m(�[22m�[2m7 tests�[22m�[2m)�[22m�[33m 82541�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m boots an https:// artifact, overriding the image's OS_ARTIFACT_PATH default �[33m 14263�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m boots a file:// artifact — the volume-mount workflow �[33m 13446�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m boots unpinned, and says so rather than claiming verification �[33m 13686�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m refuses a hash mismatch, naming expected AND actual, and exits non-zero �[33m 10324�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m refuses an unreachable artifact instead of degrading to an empty kernel �[33m 10145�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m never prints the credential of a pre-signed URL — on the real refusal path �[33m 10330�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m refuses an artifact built for another protocol major (acceptance #4) �[33m 10328�[2mms�[22m�[39m
@objectstack/cli:test:  �[32m✓�[39m �[30m�[45m integration �[49m�[39m test/run-dev-cwd-tsconfig-redirect.e2e.test.ts �[2m(�[22m�[2m3 tests�[22m�[2m)�[22m�[33m 31202�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m loads its command set anyway, and says what it re-ran �[33m 12601�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m still explains itself when the pin is defeated, and refuses the rebuild remedy �[33m 8547�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m CONTROL — from the repo root nothing is redirected, so nothing is re-exec'd �[33m 10048�[2mms�[22m�[39m
@objectstack/cli:test:  �[32m✓�[39m �[30m�[45m integration �[49m�[39m test/build-json-undeclared-key-parity.e2e.test.ts �[2m(�[22m�[2m6 tests�[22m�[2m)�[22m�[33m 83627�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m reports the planted key in the payload, and the stack still builds (exit 0) �[33m 10477�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m carries the SAME undeclared-key set `os validate --json` reports on the same tree �[33m 21204�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m folds them in BESIDE the authoring-rule advisories, in the shape `os validate --json` uses �[33m 10189�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m adds NO new top-level key to the payload — this fills a declared key, it is not a new surface �[33m 9958�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m CONTROL — a clean stack reports no undeclared-key line on either face �[33m 21163�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m leaves the TEXT face saying what it always said �[33m 10626�[2mms�[22m�[39m
@objectstack/cli:test:  �[32m✓�[39m �[30m�[45m integration �[49m�[39m test/diff-usage-error-stream.e2e.test.ts �[2m(�[22m�[2m12 tests�[22m�[2m)�[22m�[33m 30863�[2mms�[22m�[39m
@objectstack/cli:test:  �[32m✓�[39m �[30m�[45m integration �[49m�[39m test/serve-ready-degraded-boot.e2e.test.ts �[2m(�[22m�[2m2 tests�[22m�[2m)�[22m�[33m 9867�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m prints ready AND the missing core service in the same output, with no unconditional tick �[33m 4614�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m leaves a healthy boot printing exactly the tick it always printed �[33m 5244�[2mms�[22m�[39m
@objectstack/cli:test:  �[32m✓�[39m �[30m�[45m integration �[49m�[39m test/json-stdout-purity.e2e.test.ts �[2m(�[22m�[2m41 tests�[22m�[2m)�[22m�[33m 147166�[2mms�[22m�[39m
@objectstack/cli:test:  �[32m✓�[39m �[30m�[45m integration �[49m�[39m test/init-created-files-summary.e2e.test.ts �[2m(�[22m�[2m4 tests�[22m�[2m)�[22m�[33m 20513�[2mms�[22m�[39m
@objectstack/cli:test:  �[32m✓�[39m �[30m�[45m integration �[49m�[39m test/create-refuses-invalid-project-name.e2e.test.ts �[2m(�[22m�[2m6 tests�[22m�[2m)�[22m�[33m 52514�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m refuses the card's input and writes NOTHING �[33m 10355�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m accepts a valid name — the positive control for the absence check above �[33m 10359�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m refuses a name only the COMPOSED length catches, which `os init` must keep accepting �[33m 31795�[2mms�[22m�[39m
@objectstack/cli:test:  �[32m✓�[39m �[30m�[45m integration �[49m�[39m test/compile-artifact-packages.e2e.test.ts �[2m(�[22m�[2m4 tests�[22m�[2m)�[22m�[33m 42925�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m writes `manifest` and NO `packages` key �[33m 11386�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m carries both package manifests through to the written artifact, in order �[33m 10596�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m keeps the singular `manifest` beside it — retained, not replaced �[33m 10347�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m exits non-zero rather than writing an artifact in the unreserved shape �[33m 10585�[2mms�[22m�[39m
@objectstack/cli:test:  �[32m✓�[39m �[30m�[45m integration �[49m�[39m test/migrate-plan-exits.e2e.test.ts �[2m(�[22m�[2m1 test�[22m�[2m)�[22m�[33m 6938�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m returns from a composed host stack that armed an unreleasable handle in init() �[33m 6934�[2mms�[22m�[39m
@objectstack/cli:test:  �[32m✓�[39m �[30m�[45m integration �[49m�[39m test/i18n-check-platform-bucket.e2e.test.ts �[2m(�[22m�[2m5 tests�[22m�[2m)�[22m�[33m 52606�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m reports 100% and exits 0 under --strict --threshold=100 �[33m 10799�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m is the SAME invocation that failed before — the control is --include-platform �[33m 9849�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m prints the hidden-bucket hint on the console face �[33m 10571�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m ⛔ still gates the package that SHIPS the baseline, with no flag at all �[33m 10367�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m accepts --no-include-platform, so the third state really is three states �[33m 11012�[2mms�[22m�[39m
@objectstack/cli:test:  �[32m✓�[39m �[30m�[45m integration �[49m�[39m test/generate-agent-retired.e2e.test.ts �[2m(�[22m�[2m9 tests�[22m�[2m)�[22m�[33m 31749�[2mms�[22m�[39m
@objectstack/cli:test:  �[32m✓�[39m �[30m�[45m integration �[49m�[39m test/serve-boot-diagnostics.e2e.test.ts �[2m(�[22m�[2m2 tests�[22m�[2m)�[22m�[33m 27093�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m prints the boot WARN a plugin logged while the banner was being assembled �[33m 13293�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m streams boot output live at --log-level debug instead of hiding it �[33m 13793�[2mms�[22m�[39m
@objectstack/cli:test:  �[32m✓�[39m �[30m�[42m unit �[49m�[39m test/vitest-resolution-base-collapse.e2e.test.ts �[2m(�[22m�[2m13 tests�[22m�[2m)�[22m�[32m 172�[2mms�[22m�[39m
@objectstack/cli:test:  �[32m✓�[39m �[30m�[45m integration �[49m�[39m test/serve-app-runtime-hooks.e2e.test.ts �[2m(�[22m�[2m1 test�[22m�[2m)�[22m�[33m 19784�[2mms�[22m�[39m
@objectstack/cli:test:      �[33m�[2m✓�[22m�[39m runs onEnable, so the declared script action has a handler �[33m 10116�[2mms�[22m�[39m
@objectstack/cli:test:  �[32m✓�[39m �[30m�[45m integration �[49m�[39m test/config-miss-stdout-purity.e2e.test.ts �[2m(�[22m�[2m174 tests�[22m�[2m)�[22m�[33m 321544�[2mms�[22m�[39m
@objectstack/cli:test: 
@objectstack/cli:test: �[2m Test Files �[22m �[1m�[32m34 passed�[39m�[22m�[90m (34)�[39m
@objectstack/cli:test: �[2m      Tests �[22m �[1m�[32m448 passed�[39m�[22m�[90m (448)�[39m
@objectstack/cli:test: �[2m   Start at �[22m 05:43:56
@objectstack/cli:test: �[2m   Duration �[22m 803.26s�[2m (transform 14.61s, setup 0ms, import 26.86s, tests 2157.44s, environment 5ms)�[22m
@objectstack/cli:test: 
@objectstack/cli:test: JSON report written to /home/runner/work/objectstack/objectstack/packages/cli/.nightly-tiers/vitest-report.json

  Tasks:    58 successful, 58 total
 Cached:    0 cached, 58 total
   Time:    19m36.654s 
Summary:    /home/runner/work/objectstack/objectstack/.turbo/runs/3JOhtqug8NCjhH3Nn9awnbOrBdy.json

shard-2 — last lines of the test log

@objectstack/cli:test: �[31m+     // Read the address by shape, not by which branch matches first. Every�[39m
@objectstack/cli:test: �[31m+     // driver here has a `config` property — SqlDriver's is knex-shaped,�[39m
@objectstack/cli:test: �[31m+     // MongoDBDriver's holds a top-level `url`, InMemoryDriver's is `{}` — so�[39m
@objectstack/cli:test: �[31m+     // returning early on "has a config" meant the mongo and in-memory arms�[39m
@objectstack/cli:test: �[31m+     // below never ran and every non-SqlDriver boot banner read `(unknown)`.�[39m
@objectstack/cli:test: �[31m+     // `driver.url` still covers a driver that keeps its DSN on the instance.�[39m
@objectstack/cli:test: �[31m+     const url = describeDriverConnection(cfg)�[39m
@objectstack/cli:test: �[31m+       ?? (typeof driver.url === 'string' && driver.url ? redactConnectionUrl(driver.url) : undefined);�[39m
@objectstack/cli:test: �[31m+�[39m
@objectstack/cli:test: �[31m+     // A memory driver has no address to show — say so, rather than�[39m
@objectstack/cli:test: �[31m+     // `(unknown)`, which reads as "we looked for one and failed".�[39m
@objectstack/cli:test: �[31m+     //�[39m
@objectstack/cli:test: �[31m+     // `sqliteFile` is the same config read a second time asking a DIFFERENT�[39m
@objectstack/cli:test: �[31m+     // question: not "what do I print" but "which file on this filesystem", so�[39m
@objectstack/cli:test: �[31m+     // a caller can `stat` it. Absent for every driver that serves no on-disk�[39m
@objectstack/cli:test: �[31m+     // SQLite file, which is the majority of them.�[39m
@objectstack/cli:test: �[31m+     return {�[39m
@objectstack/cli:test: �[31m+       label,�[39m
@objectstack/cli:test: �[31m+       url: url ?? (name.endsWith('.memory') ? '(in-memory)' : '(unknown)'),�[39m
@objectstack/cli:test: �[31m+       sqliteFile: describeDriverSqliteFile(cfg),�[39m
@objectstack/cli:test: �[31m+     };�[39m
@objectstack/cli:test: �[31m+   }�[39m
@objectstack/cli:test: �[31m+   return null;�[39m
@objectstack/cli:test: �[31m+ }�[39m
@objectstack/cli:test: �[31m+�[39m
@objectstack/cli:test: �[31m+ /**�[39m
@objectstack/cli:test: �[31m+  * Decide what the ready banner's `Config:`/`Artifact:` row should say�[39m
@objectstack/cli:test: �[31m+  * (#8978).�[39m
@objectstack/cli:test: �[31m+  *�[39m
@objectstack/cli:test: �[31m+  * `relativeConfig` is derived from `args.config` at the top of `run()`,�[39m
@objectstack/cli:test: �[31m+  * before the artifact-fallback branch is decided, and was being handed to�[39m
@objectstack/cli:test: �[31m+  * {@link printServerReady} unconditionally. On an `OS_ARTIFACT_URL` boot�[39m
@objectstack/cli:test: �[31m+  * the `objectstack.config.ts` in cwd is deliberately never executed — the�[39m
@objectstack/cli:test: �[31m+  * boot diagnostics say so plainly a few lines above the banner — yet the�[39m
@objectstack/cli:test: �[31m+  * banner still named it. On the plain artifact-fallback path (no config�[39m
@objectstack/cli:test: �[31m+  * authored, booting from `OS_ARTIFACT_PATH` or the `<cwd>/dist/objectstack.json`�[39m
@objectstack/cli:test: �[31m+  * convention) the row named a config file that does not exist on disk at�[39m
@objectstack/cli:test: �[31m+  * all. Both are the same defect: the row is the surface an operator reads�[39m
@objectstack/cli:test: �[31m+  * to answer "what is this container actually running", and naming what�[39m
@objectstack/cli:test: �[31m+  * did NOT boot points them at the wrong app (cloud#1292).�[39m
@objectstack/cli:test: �[31m+  *�[39m
@objectstack/cli:test: �[31m+  * - `pinnedArtifact` set (OS_ARTIFACT_URL, #8368) → report it. `.display`�[39m
@objectstack/cli:test: �[31m+  *   is already resolved and already redacted for a pre-signed URL by the�[39m
@objectstack/cli:test: �[31m+  *   resolver, so it is safe to print as-is.�[39m
@objectstack/cli:test: �[31m+  * - `useArtifactFallback` set with no `pinnedArtifact` (OS_ARTIFACT_PATH,�[39m
@objectstack/cli:test: �[31m+  *   the `dist/objectstack.json` convention, or an empty/quick-start boot)�[39m
@objectstack/cli:test: �[31m+  *   → no config was read and there is no safely-redacted display in hand�[39m
@objectstack/cli:test: �[31m+  *   here (OS_ARTIFACT_PATH may itself be a credentialed URL) — omit the�[39m
@objectstack/cli:test: �[31m+  *   row rather than name a nonexistent file or risk leaking a secret.�[39m
@objectstack/cli:test: �[31m+  * - Neither set → the ordinary config-boot path; report `relativeConfig`�[39m
@objectstack/cli:test: �[31m+  *   exactly as before.�[39m
@objectstack/cli:test: �[31m+  */�[39m
@objectstack/cli:test: �[31m+ export function resolveBannerConfigRow(opts: {�[39m
@objectstack/cli:test: �[31m+   relativeConfig: string;�[39m
@objectstack/cli:test: �[31m+   useArtifactFallback: boolean;�[39m
@objectstack/cli:test: �[31m+   pinnedArtifact?: { display: string };�[39m
@objectstack/cli:test: �[31m+ }): { configFile?: string; artifactSource?: string } {�[39m
@objectstack/cli:test: �[31m+   if (opts.pinnedArtifact) return { artifactSource: opts.pinnedArtifact.display };�[39m
@objectstack/cli:test: �[31m+   if (opts.useArtifactFallback) return {};�[39m
@objectstack/cli:test: �[31m+   return { configFile: opts.relativeConfig };�[39m
@objectstack/cli:test: �[31m+ }�[39m
@objectstack/cli:test: �[31m+�[39m
@objectstack/cli:test: �[31m+ /**�[39m
@objectstack/cli:test: �[31m+  * Collect the automation wiring facts for the startup banner (2026-07-17�[39m
@objectstack/cli:test: �[31m+  * third-party eval: a flow that failed to arm emits no log line to find, so the�[39m
@objectstack/cli:test: �[31m+  * banner reads the binding state off the engine instead).�[39m
@objectstack/cli:test: �[31m+  *�[39m
@objectstack/cli:test: �[31m+  * Every probe is feature-detected so an older `@objectstack/service-automation`�[39m
@objectstack/cli:test: �[31m+  * (without `getTriggerBindingAudit` / `getShadowedFlows` / extended runtime�[39m
@objectstack/cli:test: �[31m+  * states) degrades to the plain count line instead of crashing the banner.�[39m
@objectstack/cli:test: �[31m+  * Returns `undefined` when there is nothing automation-related to show at all.�[39m
@objectstack/cli:test: �[31m+  */�[39m
@objectstack/cli:test: �[31m+ export function collectAutomationSummary(�[39m
@objectstack/cli:test: �[31m+   kernel: any,�[39m
@objectstack/cli:test: �[31m+   declaredFlowCount: number,�[39m
@objectstack/cli:test: �[31m+ ): AutomationReadySummary | undefined {�[39m
@objectstack/cli:test: �[31m+   let automation: any;�[39m
@objectstack/cli:test: �[31m+   try { automation = kernel?.getService?.('automation'); } catch { /* not registered */ }�[39m
@objectstack/cli:test: �[31m+�[39m
@objectstack/cli:test: �[31m+   if (!automation) {�[39m
@objectstack/cli:test: �[31m+     return declaredFlowCount > 0�[39m
@objectstack/cli:test: �[31m+       ? {�[39m
@objectstack/cli:test: �[31m+           enabled: false,�[39m
@objectstack/cli:test: �[31m+           declaredFlowCount,�[39m
@objectstack/cli:test: �[31m+           flowCount: 0,�[39m
@objectstack/cli:test: �[31m+           boundCount: 0,�[39m
@objectstack/cli:test: �[31m+           triggerTypes: [],�[39m
@objectstack/cli:test: �[31m+           unbound: [],�[39m
@objectstack/cli:test: �[31m+           unknownObject: [],�[39m
@objectstack/cli:test: �[31m+           shadowed: [],�[39m
@objectstack/cli:test: �[31m+           draftCount: 0,�[39m
@objectstack/cli:test: �[31m+         }�[39m
@objectstack/cli:test: �[31m+       : undefined;�[39m
@objectstack/cli:test: �[31m+   }�[39m
@objectstack/cli:test: �[31m+�[39m
@objectstack/cli:test: �[31m+   /**�[39m
@objectstack/cli:test: �[31m+    * One flow body's provenance, as the engine spells it (`FlowContender` in�[39m
@objectstack/cli:test: �[31m+    * `@objectstack/service-automation`): a code-shipped artifact, or an�[39m
@objectstack/cli:test: �[31m+    * ADR-0005 runtime overlay row in `sys_metadata`.�[39m
@objectstack/cli:test: �[31m+    *�[39m
@objectstack/cli:test: �[31m+    * Declared structurally, like every other shape this function reads off the�[39m
@objectstack/cli:test: �[31m+    * engine. The probes below are feature-detected precisely so a host running�[39m
@objectstack/cli:test: �[31m+    * an OLDER automation package still boots its banner, and a nominal import�[39m
@objectstack/cli:test: �[31m+    * would type these reads against the CURRENT package while the runtime�[39m
@objectstack/cli:test: �[31m+    * deliberately tolerates a previous one.�[39m
@objectstack/cli:test: �[31m+    */�[39m
@objectstack/cli:test: �[31m+   type Contender = { source: 'package' | 'runtime'; packageId?: string };�[39m
@objectstack/cli:test: �[31m+�[39m
@objectstack/cli:test: �[31m+   let states: Array<{�[39m
@objectstack/cli:test: �[31m+     name: string;�[39m
@objectstack/cli:test: �[31m+     enabled: boolean;�[39m
@objectstack/cli:test: �[31m+     bound: boolean;�[39m
@objectstack/cli:test: �[31m+     status?: string;�[39m
@objectstack/cli:test: �[31m+     triggerType?: string;�[39m
@objectstack/cli:test: �[31m+     object?: string;�[39m
@objectstack/cli:test: �[31m+     // [#12028] `getFlowRuntimeStates()` has attached these two per row since�[39m
@objectstack/cli:test: �[31m+     // #11997 whenever a bare name had more than one contender. Named here so a�[39m
@objectstack/cli:test: �[31m+     // later read is type-checked against the row's real shape — casting past�[39m
@objectstack/cli:test: �[31m+     // this annotation is how the field goes back to being declared and unread,�[39m
@objectstack/cli:test: �[31m+     // which is the whole defect this banner line closes.�[39m
@objectstack/cli:test: �[31m+     armedFrom?: Contender;�[39m
@objectstack/cli:test: �[31m+     shadowed?: Contender[];�[39m
@objectstack/cli:test: �[31m+   }> = [];�[39m
@objectstack/cli:test: �[31m+   try { states = automation.getFlowRuntimeStates?.() ?? []; } catch { /* older engine */ }�[39m
@objectstack/cli:test: �[31m+   if (states.length === 0 && declaredFlowCount === 0) return undefined;�[39m
@objectstack/cli:test: �[31m+�[39m
@objectstack/cli:test: �[31m+   let triggerTypes: string[] = [];�[39m
@objectstack/cli:test: �[31m+   try { triggerTypes = automation.getRegisteredTriggerTypes?.() ?? []; } catch { /* older engine */ }�[39m
@objectstack/cli:test: �[31m+�[39m
@objectstack/cli:test: �[31m+   let unbound: Array<{ flowName: string; triggerType: string; reason: string }> = [];�[39m
@objectstack/cli:test: �[31m+   try { unbound = automation.getTriggerBindingAudit?.() ?? []; } catch { /* older engine */ }�[39m
@objectstack/cli:test: �[31m+�[39m
@objectstack/cli:test: �[31m+   // [#12028] Same-named definitions: which body armed, and which lost. Read�[39m
@objectstack/cli:test: �[31m+   // from the engine's dedicated receipt rather than from `states` above, for�[39m
@objectstack/cli:test: �[31m+   // one measured reason — `getFlowRuntimeStates()` can only attach the receipt�[39m
@objectstack/cli:test: �[31m+   // to a row it is already emitting, i.e. to a name still in the flow map,�[39m
@objectstack/cli:test: �[31m+   // whereas `getShadowedFlows()` returns every receipt the boot pull recorded.�[39m
@objectstack/cli:test: �[31m+   // A contested name is worth saying out loud either way.�[39m
@objectstack/cli:test: �[31m+   //�[39m
@objectstack/cli:test: �[31m+   // Feature-detected exactly like the `unbound` probe above and with nothing�[39m
@objectstack/cli:test: �[31m+   // more: optional call, `?? []`, `catch` for an older engine. No extra�[39m
@objectstack/cli:test: �[31m+   // tolerance — the neighbouring read is the standard here.�[39m
@objectstack/cli:test: �[31m+   let shadowing: Array<{ name: string; armed: Contender; shadowed: Contender[] }> = [];�[39m
@objectstack/cli:test: �[31m+   try { shadowing = automation.getShadowedFlows?.() ?? []; } catch { /* older engine */ }�[39m
@objectstack/cli:test: �[31m+�[39m
@objectstack/cli:test: �[31m+   // Dead bindings: a bound record-change flow whose target object nobody�[39m
@objectstack/cli:test: �[31m+   // registered — the hook is filtered to a name that never writes.�[39m
@objectstack/cli:test: �[31m+   const unknownObject: Array<{ flowName: string; object: string }> = [];�[39m
@objectstack/cli:test: �[31m+   let ql: any;�[39m
@objectstack/cli:test: �[31m+   try { ql = kernel?.getService?.('objectql'); } catch { /* absent */ }�[39m
@objectstack/cli:test: �[31m+   if (ql && typeof ql.getObject === 'function') {�[39m
@objectstack/cli:test: �[31m+     for (const s of states) {�[39m
@objectstack/cli:test: �[31m+       if (!s.bound || !s.object || s.triggerType !== 'record_change') continue;�[39m
@objectstack/cli:test: �[31m+       let known: unknown;�[39m
@objectstack/cli:test: �[31m+       try { known = ql.getObject(s.object); } catch { known = undefined; }�[39m
@objectstack/cli:test: �[31m+       if (!known) unknownObject.push({ flowName: s.name, object: s.object });�[39m
@objectstack/cli:test: �[31m+     }�[39m
@objectstack/cli:test: �[31m+   }�[39m
@objectstack/cli:test: �[31m+�[39m
@objectstack/cli:test: �[31m+   return {�[39m
@objectstack/cli:test: �[31m+     enabled: true,�[39m
@objectstack/cli:test: �[31m+     declaredFlowCount,�[39m
@objectstack/cli:test: �[31m+     flowCount: states.length,�[39m
@objectstack/cli:test: �[31m+     boundCount: states.filter((s) => s.bound).length,�[39m
@objectstack/cli:test: �[31m+     triggerTypes,�[39m
@objectstack/cli:test: �[31m+     unbound,�[39m
@objectstack/cli:test: �[31m+     unknownObject,�[39m
@objectstack/cli:test: �[31m+     // A receipt that displaced nothing is not a contested name. The engine�[39m
@objectstack/cli:test: �[31m+     // already refuses to record one, and the banner keeps its own end of that�[39m
@objectstack/cli:test: �[31m+     // guarantee here rather than inheriting it: a benign boot must print no�[39m
@objectstack/cli:test: �[31m+     // shadowing line at all, and this is where "benign" is decided.�[39m
@objectstack/cli:test: �[31m+     shadowed: shadowing�[39m
@objectstack/cli:test: �[31m+       .filter((r) => r.shadowed.length > 0)�[39m
@objectstack/cli:test: �[31m+       .map((r) => ({ flowName: r.name, armed: r.armed, shadowedCount: r.shadowed.length })),�[39m
@objectstack/cli:test: �[31m+     draftCount: states.filter((s) => s.enabled && (s.status ?? 'draft') === 'draft').length,�[39m
@objectstack/cli:test: �[31m+   };�[39m
@objectstack/cli:test: �[31m+ }�[39m
@objectstack/cli:test: �[31m+�[39m
@objectstack/cli:test: 
@objectstack/cli:test: �[36m �[2m❯�[22m test/serve-port-readback.e2e.test.ts:�[2m247:9�[22m�[39m
@objectstack/cli:test:     �[90m245|�[39m         'the ready banner no longer derives its API row from `resolveA…
@objectstack/cli:test:     �[90m246|�[39m         + 'if it now uses the REQUESTED port, the #12525 read-back is …
@objectstack/cli:test:     �[90m247|�[39m       ).toContain('externalBaseOrigin: resolveAuthBaseUrl(boundPort).b…
@objectstack/cli:test:     �[90m   |�[39m         �[31m^�[39m
@objectstack/cli:test:     �[90m248|�[39m       �[34mexpect�[39m(
@objectstack/cli:test:     �[90m249|�[39m         serveSource�[33m,�[39m
@objectstack/cli:test: 
@objectstack/cli:test: �[31m�[2m⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[2/2]⎯�[22m�[39m
@objectstack/cli:test: 
@objectstack/cli:test:  ELIFECYCLE  Test failed. See above for more details.
::error::command (/home/runner/work/objectstack/objectstack/packages/cli) /opt/hostedtoolcache/node/22.23.2/x64/bin/pnpm run test --shard=2/2 --reporter=default --reporter=json --outputFile.json=.nightly-tiers/vitest-report.json exited (1)
@objectstack/cli#test:  ERROR  command (/home/runner/work/objectstack/objectstack/packages/cli) /opt/hostedtoolcache/node/22.23.2/x64/bin/pnpm run test --shard=2/2 --reporter=default --reporter=json --outputFile.json=.nightly-tiers/vitest-report.json exited (1)

  Tasks:    57 successful, 58 total
 Cached:    0 cached, 58 total
   Time:    17m2.453s 
Summary:    /home/runner/work/objectstack/objectstack/.turbo/runs/3JOha9qvpAlJpAtb0pqUOBk2TR5.json
 Failed:    @objectstack/cli#test

 ERROR  run failed: command  exited (1)

Filed by .github/workflows/test-nightly-tiers.yml. Generated by Claude Code

[baozhoutao]

Claim: session_012GKcPZbMoGq7WPzKLfRBTU · claude/issue-17633-migrate-meta-semver-assertion

派发(本评论来自 domain:devx 执行 PM 席 · 座位贴 #6023)。assignee 与本条 claim 由本席代 dev 落;dev 继承二者,⛔ 不再发第二条 claim,⛔ 不写 assignee。

⚠️ 本卡由 .github/workflows/test-nightly-tiers.yml 生成,domain:devx + priority:p1 已在卡上但没有 pm:queue(分诊未定级)。main 上的红在本车道,本席按 p1 直接接。⛔ 卡顶那行 os-nightly-tiers 标记不许删 —— 卡面自己写明那是 nightly 用来找回本卡、而不是每晚新开一张的依据。

诊断 —— 本席已定位到根因,⛔ 但你要自己复量

origin/main 1f0b5659e4。失败的是 packages/cli/test/migrate-meta.e2e.test.ts:521:

it('prints no padded protocol semver in the human output, under any label', async () => {
  const stdout = await runMeta(['--from', String(PROTOCOL_MAJOR)], labelDir);
  expect(stdout).not.toContain(PROTOCOL_VERSION);          // ← 红在这一条
  expect(stdout).not.toMatch(/runtime \d+\.\d+\.\d+/);     // ← 这一条是绿的
}, 120_000);

packages/spec/src/kernel/protocol-version.ts:18 ⇒ PROTOCOL_VERSION = '17.0.0'。

弄红它的是迁移条目 why: 散文里的历史引文:

packages/spec/src/migrations/entries/semantic/18.ui-reference-rail-unknown-keys-refused.ts:21
    'through. Measured on 17.0.0 GA end to end: a planted entry `filter` passed tsc, '
packages/spec/src/migrations/entries/semantic/18.admin-export-wildcard-removed.ts:24
    'measured on 17.0.0 GA across 40 export probes: an org owner exported three objects on '
packages/spec/src/migrations/entries/semantic/18.stack-top-level-unknown-keys-refused.ts:19
    '17.0.0 GA (#8687): three injected bogus top-level keys added ZERO warnings to '
（registry.ts 里另有同文的四处副本:5118 / 5523 / 9856 / 10617）

os migrate meta 的人类输出把这些 why: 块逐字打出来(见卡面 shard-2 的日志尾巴)⇒ stdout 里出现了字面量 17.0.0 ⇒ 整篇 toContain 命中。

⭐ 对照,这一条最要紧:/runtime \d+\.\d+\.\d+/ 这个模式在整个 packages/spec/src/migrations/ 树里命中 0。⇒ 真正瞄准缺陷的那半仍然是绿的;红的是那条粗暴的整篇 toContain。

⭐ 这个测试防的到底是什么 —— 读它自己的 docblock,别读它的断言

:468-480:

PROTOCOL_VERSION is the protocol major padded to a semver ('17.0.0') and is never the installed package version. Printed here as a bare semver under the word "runtime", it read as one: on a 17.3.0 install the operator saw "runtime 17.0.0" beside the real package versions … Nothing about the VALUE was wrong; the LABEL and the semver FORM were.

⇒ 它防的是**「把 17.0.0 当成一个版本标签印在版本位置上」。而现在踩响它的是一句引用 17.0.0 GA 那次发布的历史陈述**。仪器分不清「标签」和「引文」。

⚠️ 这正是本车道反复遇到的那条线(#16664 / #15310 / #16277 都栽在同一处),这次它咬到的是测试自己。

判据

1. ⛔⛔ 绝不许改那三句(以及 registry 里的四处副本)散文去躲开仪器。 那是对一次真实历史测量的引用,把它改掉是为了让仪器闭嘴而损坏记录 —— 比原缺陷坏得多。卡面自己也写了:「⛔ The remedy is never to rename, skip or delete the failing test to make the nightly green.」同理也不许改被测数据。
2. ⛔ 不许删、不许 skip、不许改名这个测试,也不许把 not.toContain 整条删掉了事。
3. ✅ 让断言会分辨:它该断言的是版本标签那个面(Chain: 行 / runtime 位置),不是整篇 stdout。docblock 已经说清「两半都要断言,因为任一半单独都能被用错的方式满足」——⇒ 你的新写法必须仍然两半都在:
   • 「不以裸 semver 形式出现在版本位置上」;
   • 「不在 runtime 这个词后面出现 semver」(这半今天就是绿的,保持)。
4. ⭐ 红→绿两条腿都要:
   • 先在未改的树上复现这次红(至少把 runtime 那半与 toContain 那半分开跑,证明红的只是后者);
   • 改完之后,把 docblock 描述的那个原始缺陷重新植入(在版本位置上印一个裸 17.0.0),新断言必须红。⛔ 一个植回原缺陷仍然绿的断言,等于把这个测试废掉了 —— 那是比现在更坏的结果。
5. ⚠️ 本席的诊断你要自己复量(那三个文件 + registry 四处 + /runtime …/ 的 0 命中),⛔ 别引本评论当证据。

复现

卡面给了:OS_TEST_TIERS=nightly pnpm --filter @objectstack/cli test。⚠️ 这是 e2e 层、单条 120s、整包 ~18 分钟。⭐ 先只跑这一个文件再说,⛔ 不要一上来跑整包。

边界

• ⛔ 只动 packages/cli/test/migrate-meta.e2e.test.ts(以及,若确有必要,os migrate meta 的输出格式——但那属于扩面,动之前先报回来)。
• ⛔ 不动 packages/spec/src/migrations/**(那是被测数据,见判据 1)。
• ⛔ 不动 packages/spec/src/kernel/protocol-version.ts。
• ⛔ 不碰 content/docs/releases/、docs/adr/**、.claude/**、skills/**、AGENTS.md、CLAUDE.md。
• worktree-first;⛔ 不 git stash;⛔ 已推的分支不 rebase / amend / force-push。

交付纪律

• ⚠️ 关卡方式先查先例:本卡由 nightly 生成并自称「let the next nightly refresh this card」。⇒ 去查既往 nightly-tiers 卡是怎么收尾的(搜引用过 os-nightly-tiers 卡的已合并 PR),照先例写 PR 的卡片关系;查不到就在报告里说一声,由 PM 定。⛔ 别凭感觉写 Closes。
• changeset:packages/cli 是发布包,但 test/** 通常不在 files[] 里 —— ⛔ 先量再断言(packages/cli 的 files 是 ["dist","README.md","CHANGELOG.md"],自己复核)。判 skip 就给 PR 打 skip-changeset 标签(那是标签,不是 body 里的一句话)。
• **Clause-②**: no 写进 PR body 行首(只动测试断言,不动任何契约面);发前用 scripts/pm/check-clause2-carriers.mjs 的 readClause2Line() 自验。
• PR 开 draft。

---

Generated by Claude Code

[claude]

os-dev-report

{
"issue": 17633,
"status": "done",
"branch": "claude/issue-17633-migrate-meta-semver-assertion",
"pr": "#17654",
"premise_still_valid": true,
"summary": "Narrowed packages/cli/test/migrate-meta.e2e.test.ts's 'prints no padded protocol semver...' assertion to target the Chain: line specifically instead of whole stdout, so historical 17.0.0-GA citations in pre-registered protocol-18 migration why: prose no longer trip it, while the runtime-position half (already green) is unchanged. Re-measurement turned up a second, related red in the same describe block ('names this build's protocol major, in majors') caused by the same CHAIN_TERMINUS_MAJOR(18)-vs-PROTOCOL_MAJOR(17) drift; fixed by pinning --to explicitly. No production code or packages/spec/src/migrations/** touched.",
"tests": "Unmodified tree: OS_TEST_TIERS=nightly vitest run --project integration test/migrate-meta.e2e.test.ts -> 'Tests 2 failed | 17 passed (19)'. Leg 1 (assertions run separately via standalone script, not vitest's first-failure abort): not.toContain(PROTOCOL_VERSION) = FAIL(red); not.toMatch(/runtime d+.d+.d+/) = PASS(green) -- matches diagnosis. Fixed tree: same command -> 'Tests 19 passed (19)'. Leg 2 (ablation): re-planted the docblock's original defect in packages/cli/src/commands/migrate/meta.ts (Chain line printed PROTOCOL_VERSION instead of PROTOCOL_MAJOR under the words 'this runtime implements protocol'), ran the real edited test file -> target case goes RED ('prints no padded protocol semver...' fails, confirming the new chainLine-targeted assertion still catches the real defect). Reverted via git checkout HEAD; git hash-object before/after match (7af7441d...) and git diff HEAD is empty. pnpm --filter @objectstack/cli typecheck: exit 0. pnpm --filter '@objectstack/cli^...' build: exit 0. dispatch-gates: 48 families derived for this 1-file diff, all 48 run, reconciled 0 NOT-MEASURED/0 UNRUN; 47/48 exit 0, 1 (check:dual-build-cjs-loads) exit 3 PREREQUISITE NOT MET (needs dist/ for packages outside this diff's dependency closure -- studio, client-react, connectors, embedder-openai, knowledge-memory -- none built here; not a finding against this diff).",
"mcp_calls": "3 (2x search_pull_requests for nightly-tiers-card precedent, 1x create_pull_request)",
"open_questions": [],
"out_of_scope_findings": [
"noted, not filed: packages/cli/test/migrate-meta.e2e.test.ts's 'names this build's protocol major, in majors' case was ALSO red on the unmodified tree (not named by the card's diagnosis, which cited only the :521 assertion) -- same root cause (CHAIN_TERMINUS_MAJOR now exceeding PROTOCOL_MAJOR because protocol-18 migrations are pre-registered ahead of the runtime's own major bump); fixed in this same PR rather than filed separately since it lives in the exact file/describe-block this card names and is required for the file to go fully green. Carrier: this PR (#17654)."
]
}

---

Generated by Claude Code

[claude]

Premise check — the named failure is ALREADY REPAIRED on main; this card is waiting on the next nightly, not on a dev

domain:cli execution seat (#6024), 2026-09-12T04:40Z. This card reached this lane in the re-route at 5642269045 and sorts first in this lane's selection order (priority:p1). ⛔ It is not being dispatched, and the reason is a reading, not a judgement call.

1. What the card names, and what main says about it

The card names exactly one failing file — packages/cli/test/migrate-meta.e2e.test.ts — and the domain:devx seat dispatched it at 5631181204. That work landed:

reading	command	result
PR state	GET /pulls/17654	merged: true, merged_at 2026-09-11T09:23:09Z, 1 file, +19/−2
landing shape	git rev-list --parents -n 1 5ddd5d3f	2 fields ⇒ single-parent squash, not a merge commit
on the branch	git log --oneline -3 origin/main -- packages/cli/test/migrate-meta.e2e.test.ts	tip is 5ddd5d3f fix(cli): migrate-meta's semver-label assertion targets the Chain: line, not the whole stdout (#17654)

Reading 2, on the content rather than the commit — git show origin/main:packages/cli/test/migrate-meta.e2e.test.ts carries both repairs the dev reported:

• prints no padded protocol semver in the human output, under any label now selects the Chain: line and asserts expect(chainLine).not.toContain(PROTOCOL_VERSION), leaving the whole-transcript toContain behind. The already-green half (not.toMatch(/runtime \d+\.\d+\.\d+/)) is unchanged and still asserted against the whole stdout.
• names this build's protocol major, in majors now pins --to PROTOCOL_MAJOR explicitly, so it no longer rides the default that climbs to CHAIN_TERMINUS_MAJOR.

⭐ Both edits are in the test file. packages/spec/src/migrations/** is untouched, so the card's ⛔ line — never change the historical 17.0.0 GA citations to quiet the instrument — held.

2. Why the card still reads red: the run predates the fix

reading	result
GET /actions/workflows/test-nightly-tiers.yml/runs?branch=main	newest run is 34566550033, 2026-09-11T05:35:32Z, head 690f083f, failure — the one this body reports. No run since.
git merge-base --is-ancestor 690f083f 5ddd5d3f	exit 0 ⇒ the nightly's head precedes the fix
fabricated negative control (reverse direction)	exit 1 ⇒ the ancestry test can fail, so exit 0 above is a reading

⇒ the red on this body was measured ~3h45m before the repair merged. It is a stale transcript, ⛔ not a live failure. The triage premise check at 5642269045 was correct at its own reading (「no run has happened since」) and remains correct — what it did not reach is that the repair had already landed between the run and the check.

3. What happens next, and why nothing is dispatched

.github/workflows/test-nightly-tiers.yml is explicit about its own lifecycle (:46): 「On green this workflow files nothing, edits nothing and closes nothing.」 Its schedule is cron: '29 5 * * *' (:81) ⇒ the next run is due ~2026-09-12T05:29Z, and a green one will leave this card exactly as it is. The card is therefore closed by hand or not at all — and :54 says a closed card is never reopened, a later red is filed fresh, so closing it costs this channel nothing.

• ⛔ Not dispatched. Every work item this card names is already on main; a dev would open the file, find the repair, and stop with evidence. That is a correct outcome and still a wasted worktree.
• ⛔ Not closed yet. 判据取命令输出 — the close criterion is the next Nightly Tiers run reporting green on a head that contains 5ddd5d3f, ⛔ not my prediction that it will.
• The wait is written here because 「等待也是状态,写在卡上才存在」. This lane skips this card in the selection order until that run reports, and dispatches the next card by the same order instead.

Close criterion, for whoever gets here first: Nightly Tiers run newer than 34566550033 on main, conclusion: success, head containing 5ddd5d3f ⇒ close as completed, citing the run id. If it is red again on this same file, the body will have been rewritten in place by the report job and the card is live work again — re-read the new body before dispatching, ⛔ do not act on the transcript above. If it is red on a different file, that is a different defect wearing this card's title; grade it fresh.

---

Generated by Claude Code

[claude]

Claim: session_01TSf4DV7ziu4V5j73e46b7c
Branch: claude/issue-17633-json-stdout-family-account-issuer
Clause-②: no

Dispatch — domain:cli execution seat (#6024), round 22, 2026-09-12T06:06Z. The assignee and this Claim: line are written by the seat on the dev's behalf: the dev inherits both, ⛔ posts no second claim and ⛔ writes no assignee.

---

0. ⛔ The card body was REWRITTEN — the earlier transcript on this thread is spent

⚠️ Read the body above this comment, not comment 5643489339. That comment recorded that the previous failure (packages/cli/test/migrate-meta.e2e.test.ts) had already been repaired by #17654 and set a close criterion: a newer nightly reading success ⇒ close the card. That criterion is now spent, and it resolved the other way:

reading	result
GET /actions/workflows/test-nightly-tiers.yml/runs?branch=main	run 34675914967, started 2026-09-12T05:34:08Z, head 8fa3fe63d9, conclusion: failure
does that head carry the #17654 fix?	git merge-base --is-ancestor 5ddd5d3f 8fa3fe63 → exit 0 (control: the later 56103b73 is NOT in it ⇒ the test can return false)
the rewritten body's failing-files list	packages/cli/test/json-stdout-purity.e2e.test.ts — ⭐ migrate-meta.e2e.test.ts is gone from it

⇒ two facts, and they are separate. #17654's repair worked — that file is no longer failing, confirmed by its absence from a list that named it yesterday. And this is a different defect wearing the same card's title, filed in place by the report job because a card that is still open gets refreshed rather than replaced. Graded fresh below. ⛔ Nothing in the old transcript describes the work being dispatched here.

1. The failure, read out of the run log on the card

packages/cli/test/json-stdout-purity.e2e.test.ts:209, in describe('the family this contract has to hold across'):

FAIL  is exactly the set listed here — a new member goes red until it is driven too
AssertionError: expected [ 'meta resync', …(12) ] to deeply equal [ 'meta resync', …(11) ]

  [
      "meta resync",
  +   "migrate account-issuer",
      "migrate apply",
      …

expect(discoverFamily()).toEqual(Object.keys(FAMILY).sort()) — live discovery finds 12 --json members, the hand-listed FAMILY pin at :82 carries 11. The missing one is migrate account-issuer.

⭐ This is the tripwire firing exactly as designed, and the test's own name says so: "a new member goes red until it is driven too." describe.each(Object.keys(FAMILY)) at :248 is what drives each member, so FAMILY is not a list of names — it is the list of members that are actually driven, and its argv is the driving input.

Provenance, measured on origin/main: git log --oneline -3 -- packages/cli/src/commands/migrate/account-issuer.ts → 9bd4344e4 feat(auth)!: adopt better-auth's account-issuer rollback … (#17454). That PR added a new --json command and did not extend FAMILY. It merged green because per-PR CI runs the queue tier and this file is *.e2e.test.*, which runs only under OS_TEST_TIERS=nightly — precisely the class this card exists to see: 「a real suite that no pull request will red on」. ⛔ This is not a criticism of #17454's own work; it is the gap the nightly channel is for.

2. What to do, and the branch that decides the shape

The premise you must falsify first: that os migrate account-issuer --json actually satisfies the purity contract and all that is missing is its FAMILY row.

• If it does ⇒ add the member to FAMILY at :82 with argv that really drives it, and let describe.each do the rest. Test-only diff. That is the expected shape and the one this card's Clause-②: no is declared for.
• If it does NOT — the driven case goes red on the purity contract itself (stray output on stdout, a non-JSON line, something on the wrong stream) ⇒ ⛔ stop and report before writing a source fix. That is a defect in a published command's --json face, ⛔ not a list-maintenance chore, and it changes both the scope and the clause-② answer. Bring it back to this seat; ⛔ do not widen this card into it on your own.

⛔ Never add the member to FAMILY without driving it, and ⛔ never relax, skip or narrow discoverFamily() to make the counts agree. The card's own line is the governing one: 「The remedy is never to rename, skip or delete the failing test to make the nightly green.」 Making the discovery blind to a real member would be exactly that, wearing a tidier face.

Also check :227/:236: there is a second list, CONFIG_MISS_FAMILY, with an overlap assertion between them. Decide whether the new member belongs there too — and say which way you decided and why, ⛔ rather than leaving it to whichever answer happens to be green.

3. Premise readings taken at dispatch — re-measure them yourself

All at 2026-09-12T06:02Z against origin/main, fetched:

• Heavy-verify lock: lock is free, queue: empty ⇒ arrival depth 1, under LOCK_DEPTH_HOLD (2).
• Hot-file matrix over all 22 open PRs: no holder of packages/cli/test/json-stdout-purity.e2e.test.ts. Positive control on the same pass — PRs touching packages/cli/ at all → feat(cli): objectstack dev --cert/--key terminates TLS in the dev process, and the canonical origin follows the listener #17725, chore: version packages #17076 ⇒ the matcher fires, so the zero is a reading.
• FAMILY at :82, discoverFamily() at :129, the assertion at :209, describe.each at :248 — all read on origin/main today. ⚠️ Line numbers from a body written at 05:54Z: locate from the symbol, and if a line has moved, the symbol wins and you say so.

4. Acceptance

1. Reproduce the red first, on the tier that shows it: OS_TEST_TIERS=nightly pnpm --filter @objectstack/cli exec vitest run --project integration test/json-stdout-purity.e2e.test.ts. A fix whose original failure was never reproduced is not a fix, it is a guess that went green.
2. The same command green after, with the member driven — ⛔ not merely listed.
3. A control that can fail: show the driven case actually exercises migrate account-issuer (its output appears, its exit code is read), so a row that drives nothing cannot pass as one that does.
4. ⛔ Do not touch content/docs/releases/, and ⛔ do not edit the os-nightly-tiers marker line at the top of the card body — it is how the nightly finds this card instead of filing a new one nightly.
5. .changeset/: judge it. A test-only change to a nightly tier may warrant none; if you skip it, say why in the PR body rather than leaving the reader to guess.
6. Open the PR as a draft, and put a bare column-0 Clause-②: yes|no line in the body — no bullet, no bold, no blockquote, no backticks.

5. Mechanics

One worktree, branch exactly claude/issue-17633-json-stdout-family-account-issuer. ⛔ Never edit the shared checkout, ⛔ never git stash. Run the repo's fast checks and report exit codes. Return the os-dev-report JSON block; ⛔ report absences as absences.

---

Generated by Claude Code

[claude]

os-dev-report

{
  "issue": 17633,
  "status": "done",
  "branch": "claude/issue-17633-json-stdout-family-account-issuer",
  "pr": "https://github.com/objectstack-ai/objectstack/pull/17805",
  "premise_still_valid": true,
  "summary": "The premise held, so this is a test-only diff: one FAMILY row in packages/cli/test/json-stdout-purity.e2e.test.ts driving `os migrate account-issuer --json` with the bare form, which really boots. Driven by hand BEFORE the row existed, the command satisfies all three halves of the stdout-purity contract on its own — stdout is exactly one JSON document (bare JSON.parse succeeds), carries no kernel-logger record and no [StandaloneStack] line, and all three BOOT_DIAGNOSTICS are on stderr — so the dispatch order's stop-and-report branch for a purity DEFECT was not taken. CONFIG_MISS_FAMILY and the overlap assertion are deliberately unchanged: account-issuer.ts never imports utils/config.js, so it has no resolveConfigPath() refusal branch, and the shipped discoverConfigMissFamily() still returns the same ten members with overlap ['migrate meta']. Symbols located and confirmed still at the line numbers the card body recorded at 05:54Z (FAMILY :82, discoverFamily :129, reconciliation :209, describe.each :248). The PR says `Part of #17633`, not a closing keyword: test-nightly-tiers.yml 'files nothing, edits nothing and closes nothing' on green, so closing this card is a seat reading a later nightly as success — see open_questions.",
  "tests": "RED REPRODUCED FIRST at base 8da783206, before the edit, on the tier that shows it — `OS_TEST_TIERS=nightly pnpm --filter @objectstack/cli exec vitest run --project integration test/json-stdout-purity.e2e.test.ts`: '38 tests | 1 failed', 'AssertionError: expected [ meta resync, ...(12) ] to deeply equal [ meta resync, ...(11) ]', '+ \"migrate account-issuer\"', at test/json-stdout-purity.e2e.test.ts:209:30 — byte-for-byte the card's failure. os-verify-lock VERDICT command-exit 1. || GREEN AFTER, same command: 'Test Files 1 passed (1) / Tests 41 passed (41)' (38 -> 41: the three new per-member cases for `os migrate account-issuer --json` all pass). VERDICT command-exit 0. || ABLATION, two legs, each mutating this file on disk, each proving the mutation landed by git hash-object, each restored under trap ... EXIT INT TERM with restore verified by hash equality to the HEAD blob d30b0f4d06e56ca0ed0243207f7d2e42d6f52031 and an empty `git diff HEAD` — not by an exit code. No dist is involved: vitest loads this test file from source, so there is no built artifact for the mutation to fail to reach; stated rather than skipped. LEG A (positive control, the acceptance item 3 control): a temporary case read the captured run for 'migrate account-issuer' and asserted its payload and exit status, then was removed — printed 'ABLATION-A stdout: {\"error\":\"Cannot enumerate sys_account: ... Refusing rather than reporting an unread table as clean.\",\"code\":\"RESOURCE_CONFLICT\"}' and 'ABLATION-A exit code: 1', 42 passed (42). That payload belongs to no other family member, so the row drives the command it names. LEG B (mutation): the row's argv set to ['--drives-nothing'] -> 'Tests 2 failed | 39 passed (41)', with 'AssertionError: expected objectstack: INVOCATION ERROR - Nonex... to contain [StandaloneStack] no compiled artifact'. So a row that drives nothing cannot pass as one that does. REPORTED AS MEASURED, including the unflattering half: the THIRD per-member case, 'leaves no kernel-logger record on stdout', stayed GREEN through leg B — it is a pair of negative assertions, vacuously true of an empty stdout; it binds purity, not existence. The two that bind existence are enough for this row, and the trio is unchanged by this PR. || GATES: derived, not hand-listed — `node scripts/pm/dispatch-gates.mjs --commands` with no paths, then `--ran` with each recorded exit code: 'Run reconciliation - 48 derived, 47 run, 1 NOT-MEASURED, 0 UNRUN'. NOT MEASURED: pnpm check:dual-build-cjs-loads, reason: exit 3 'PREREQUISITE NOT MET - this gate reads built output, and some package has no dist/ ... This is NOT a pass: nothing was measured', naming twelve packages outside this card's build closure; it needs a whole-repo pnpm build, which CI does. check:nul-bytes green, plus a manual C0+DEL grep -naP sweep over the edited file: clean. Re-derived after a fetch that moved origin/main 7 commits: the derived set is identical, 0 new families. || pnpm --filter '@objectstack/cli^...' build -> VERDICT command-exit 0. pnpm --filter @objectstack/cli build && pnpm --filter @objectstack/cli typecheck -> VERDICT command-exit 0, with the coverage split stated rather than implied: tsconfig.json declares include:['src'], so the `tsc --noEmit` half does NOT reach test/; the half that reaches this diff is check:test-typecheck, which reports the test layer compiles under packages/cli/tsconfig.test.json. || JOINT re-check against the CURRENT main, not only the base: origin/main at 310760d22 touches neither packages/cli/src/commands nor packages/cli/test since 8da783206, and running the shipped discovery over origin/main's own tree returns exactly the thirteen members FAMILY carries after this PR. || node scripts/pm/check-clause2-carriers.mjs --pair 17805 -> exit 0, both carriers agree. || CHANGESET: none, measured not assumed. @objectstack/cli declares files:['dist','README.md','CHANGELOG.md']; after building the package, a string unique to this diff has 0 hits across all three paths while the positive control on the same pass — the command description that really does ship — has 1, in packages/cli/dist/commands/migrate/account-issuer.js. The matcher fires, so the zero is a reading. skip-changeset applied additively (POST .../labels) and confirmed by a contrastive read-back: read set {size/xs, tests}, target {skip-changeset}, union equals read-back exactly, 0 stripped. || NOT RUN LOCALLY, declared: packages/cli's integration tier beyond this one file, repo-wide pnpm lint, and the whole-repo build check:dual-build-cjs-loads needs.",
  "mcp_calls": "0 — every GitHub read and write on this run went through repo-scoped REST (probed first: GET /issues/17633 -> 200) or plain git; no MCP GitHub tool was called",
  "open_questions": [
    {
      "question": "Who closes #17633, and should this PR have closed it? The PR deliberately says `Part of #17633` rather than a closing keyword, verified with `node scripts/check-closing-keyword-parity.mjs --body` (all 3 shipped parsers: no closing declaration binds).",
      "options": [
        "A. Leave `Part of` (what shipped): test-nightly-tiers.yml states of its green path 'On green this workflow files nothing, edits nothing and closes nothing', so nothing automatic will close the card; a seat closes it after reading a later nightly as success. Cost: the card stays open across at least one nightly cycle and needs a human read.",
        "B. Switch to `Fixes #17633`: the merge closes the card immediately. Cost: it closes on the repair rather than on the confirmation, and if the next nightly is still red for any reason the workflow files a NEW card, losing this thread and the marker line's whole purpose."
      ],
      "recommendation": "A, because the card's own governing text points at the nightly as the instrument ('let the next nightly refresh this card') and the workflow closes nothing on green, so closure is a reading no merge can assert. If the PM seat prefers B, it is a one-line body edit on the PR before it lands."
    }
  ],
  "out_of_scope_findings": [
    "noted, not filed: in json-stdout-purity.e2e.test.ts the per-member case 'leaves no kernel-logger record on stdout' is a pair of negative assertions, so it passes vacuously against a run that never happened (measured in ablation leg B). It is correct for what it asserts and its two sibling cases in the same trio do bind existence. Successor: none in flight — no open PR holds this file, and widening it is a pin redesign, not this card.",
    "noted, not filed: the driven refusal payload of `os migrate account-issuer --json` carries code RESOURCE_CONFLICT for a missing sys_account table, via errorCodeFields() over the sql driver's deliberately unattributable DATABASE_ERROR. Recorded because it is what the driven run prints; I gathered no contract text and no repro of harm, so it is a reading and not a finding. Successor: none."
  ]
}

---

Generated by Claude Code