Process completed with exit code 1.

`Metadata-protocol: narrowed` says a key, value or requirement leaves the accept set an author writes against — a BREAKING narrowing by definition — while the `Clause-②:` line declares no `(narrowing)` arm, which is the signal `check-adr-0087-registration.mjs` and the queue guard read for exactly that. · declaration line: `Clause-②: no` · direction arm: none declared — the declaration names no widening and no narrowing · metadata-protocol line: `Metadata-protocol: narrowed` Correct the one that is wrong: add the arm — `Clause-②: no (narrowing)` or `yes (narrowing)` — beside `narrowed`, or a kind that is not `narrowed` beside the line as written. Full text in this step's log.

"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"

"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"

ADR-0087 exemption (no-migration-prescription): No key of any schema is added, removed, renamed or re-shaped, and no export or type changes. The narrowed face is the existing owner-stamp judge now reaching one more collection of a `packages[]` stack's top level: a residual dataset wearing another package's `_packageId`. No conversion can rewrite it, because which package owns the dataset is the author's decision (drop the stamp, or move the dataset into the `packages[]` entry of its owner), and the stack that carries it used to lose the dataset at boot anyway, so there is no working stored state for a migration to preserve.