Queue-flake anchor: scripts/liveness/check-liveness.test.ts #20089
Description
scripts/liveness/check-liveness.test.ts has ejected 3 pull requests from the merge
queue within a rolling 24 hours — 1 independent hit once
GitHub's speculative stacking is accounted for. This issue is the single place for
that conversation; it is refreshed by the merge-queue-triage workflow on every
further ejection.
| PR | stack | queue build |
|---|---|---|
| #20079 | S1 · root | 36088336600 |
| #20086 | S1 · inherited | 36089109896 |
| #20087 | S1 · inherited | 36089293345 |
stack column is read out of the queue
branch names: GitHub builds each queued PR on top of the previous entry, so a
build whose BASE commit IS another victim's queue HEAD contains that victim's
tree by construction. A single deterministic break therefore ejects every PR
behind it, and the raw victim count climbs with QUEUE DEPTH until the owner
lands a fix. Start with the root above; an inherited row is a bystander until shown otherwise.
This issue is a NAME, not a diagnosis. The workflow that files it reads the
failing test file path out of the job logs and counts PRs; it does not
know whether this is a flake, a load/timing cliff, a semantic conflict between
queued PRs, or a real regression, and it does not act on any of those. No test is
skipped, quarantined or re-queued by it, and no PR is labelled by it — weakening
a gate stays a human act.
What to do with it: read one victim PR's triage comment for the failure REASON
line beside the FAIL line (a timeout and an assertion are the same FAIL line and
opposite diagnoses), decide the cause, and close this issue with the fix or with
the reason it is not one.
Last refreshed by queue build 36089293345 (PR #20087).
Filed by the merge-queue-triage workflow (#4859, aggregation #10128).
Activity
objectstack-fleet commentedon Sep 25, 2026
Closed
completed— not a flake: one deterministic break in PR #20079's own tree, fixed on that PR and landedTriage seat #6015 ·
session_01CRZSc7dU8oDStbTbSwhuZe· 2026-09-25T04:36Z. Read: this anchor, the queue-triage comments on the three PRs, andorigin/maina8bcce6.domain:cliseat (5826161939on fix(plugin-hono-server): drop the retired ui-plugin arm from UI auto-discovery #20086) and thedomain:servicesseat (5826175275on fix(plugin-approvals, plugin-security, service-messaging, service-realtime): nine titleFormat-only system objects declare a title pointer instead of taking the raw id #20087) read it: the liveness gate's key-mention check found one unanchored citation,permission/objects.allowExport→packages/plugins/plugin-hono-server/src/current-user-endpoints.ts. PR feat(objectql,plugin-security,core): the server answers current_user.can() in an option's visibleWhen #20079 movedannotateEffectiveApiOperationsout of that file, so the ledger pointer named a file that no longer names the key. One cause, 20 failing cases in one test file.mainand landed, as3c48234andd4c897e.allowExportevidence inpackages/spec/liveness/permission.json(its contract review5826495609recordscheck:livenessexit 0 at the new head and the control red at the old ledger) and landed as0318faf. At that commit the entry citespackages/core/src/security/effective-object-permissions.ts#annotateEffectiveApiOperations.