"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): This diff moves `.objectui-sha` and the artefacts that travel with it: this console changeset, the re-recorded `scripts/sdui-manifest.record.json` and the regenerated `sdui.manifest.json`, the re-recorded `packages/sdui-parser/objectui-lockstep.json` and the re-measured pin citations in `packages/spec/src`, which carry their own `@objectstack/spec` patch changeset. It adds, removes or renames no ObjectStack-authorable key: no Zod schema, no spec declaration and no stored `sys_metadata` shape moves in it, so `objectstack migrate meta` has nothing here to rewrite, and this body carries no FROM/TO prescription of its own. The range carries two declared-breaking objectui changes, each by its author's breaking annotation and none by a declared `major`, and no commit subject carries `!`. The digest marked only the first. The second opens its annotation with a warning sign before the word (a `## ⚠️ BREAKING, priced as minor …` heading), which the digest's block-opener rule does not recognise, so its entry above was marked by hand. Each is answered here: (1) objectui#12254 (`e8fc452c3`): both dashboard surfaces draw a widget's legacy `component` envelope only for a `metric-card` node, in `@object-ui/plugin-dashboard`. `@objectstack/spec` already refuses `component` and inline `data` on a dashboard widget (`QUARANTINED_WIDGET_KEYS`, `ui/dashboard.zod.ts`) and declares no `custom` widget, so nothing authored here can reach that envelope; the six dashboard files under `examples/` author no `component` key. (2) objectui#12242 (`10aba37d1`): `@object-ui/types`' field metadata types turn `visible_on`, `currency`, `filterable`, `min_date`, `max_date`, `default_zoom`, `starting_number`, `schema` and `normalize` into `never` tombstones and change the `auto_number` / `object` type values to `autonumber` / `json`. No package or example in this repo depends on `@object-ui/types` (two code comments name it). No example field authors any of those members (the one `schema:` key under `examples/` sits on a `json_schema` validation rule, not on a field), and no example field declares `type: 'auto_number'` or `type: 'object'`. Scope of the claim, stated rather than implied: it is a claim about THIS diff, not a per-entry re-measurement of the upstream declared-breaking entries.