Process completed with exit code 1.

Moved and graded `patch`: @objectstack/objectql: patch (.changeset/29167-formula-date-bucket-refused-alike.md); @objectstack/service-analytics: patch (.changeset/29167-formula-date-bucket-refused-alike.md); introduced at `minor` or above: (none); protocol baselines moved: (none). A kind and a `none` would grade this differently, so the declaration that was not readable is what decides this verdict. · declaration line: a near miss, not a declaration — reason `describing` — Clause-②: yes (narrowing) — `engine.aggregate` refuses `INVALID_FIELD` / 400 at `groupBy.N.dateGranularity` a `dateGranularity` over a virtual (`formula`) field… · remedy for `describing`: the line carries the key in the fixed spelling at the start of a line, but it QUOTES the spelling instead of declaring a value: it either names `Clause-②:` twice on one line, or opens a backtick span at the key and continues past the closing tick (the `Clause-②: no` · `skip-changeset` shape). ADD the declaration on a line of its own, bare, with nothing following it. · metadata-protocol line: `Metadata-protocol: none` DECLARE IT: two lines in the PR BODY, each bare at the START of a line of its own — `Clause-②: yes` or `no` (plus `(narrowing)` if it narrows a published surface), and `Metadata-protocol: added`, `narrowed`, `semantic` or `none` (the kind of change to what a metadata author can write; `none` is `patch`, a kind is `minor`). A `- `, `> ` or `**` prefix is read too; a `## ` heading and a backtick span that runs past the key are not. ⛔ The remedy is the declaration, never dropping the changeset. The body is re-read on the next `edited` event, so this red clears with no push and no re-run. Full text in this step's log.

Process completed with exit code 1.

.changeset/28977-sql-dry-run-refuses-date-bucket-over-non-date.md exists on the merge base and was not added by this PR, so changing or deleting it silently replaces somebody else's release note (#17712). Two things produce this refusal and their remedies are OPPOSITE, so read which one you are before you act. COLLISION -- you and another PR drew the same changeset filename, and yours overwrote theirs. Remedy: rename yours; restore theirs from base. DELIBERATE CORRECTION -- your change may have made this PENDING release note false, and you rewrote it in the same stroke. Remedy: do NOT restore it -- say so on the PR and get it confirmed; restoring it from the base would put the false sentence back.

"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 of either package root changes: a query that bucketed a column the table does not store is refused before it reaches the driver, with an error code and status already on the wire. There is nothing for a migration to rewrite and no tombstone.