Sentinel: shared:01m23vygyffx5hg2f5vm8r74sr:2ml3f5dne9 is past its budget: trevato/forge: "concurrent checks > a fresh account's second check waits queued, naming the count; the owner's two run … #5195

shared:01m23vygyffx5hg2f5vm8r74sr:2ml3f5dne9 is past its budget: trevato/forge: "concurrent checks > a fresh account's second check waits queued, naming the count; the owner's two run …

Evidence

• cause: shared:01m23vygyffx5hg2f5vm8r74sr:2ml3f5dne9
• sentence: trevato/forge: "concurrent checks > a fresh account's second check waits queued, naming the count; the owner's two run at once; a freed slot starts the waiter" failed on 3 pulls in the last hour — the lane's red, not theirs; they wait for main's next green check, unparked.
• since: 2026-10-22T07:40:21.310Z
• href: /trevato/forge/issues/new

Pillar: P0 Trust: the forge says when it is not well, and is well again

What to look for when fixed: shared:01m23vygyffx5hg2f5vm8r74sr:2ml3f5dne9 is gone from the degraded list and the cause is fixed, not waited out.

Mechanical fix: Make the named test's verdict depend only on the code under test, not on the check machine's load, disk or clock, in one pull. Pulls red on it alone wait, unparked, for main's next green check.

Found by the sentinel at 2026-10-22T07:40:33.461Z.

Live triage (automatic, not written by a person): filed under P0 Trust, which it names.

Still there at 2026-10-22T08:41:18.585Z, evidence now:

• cause: shared:01m23vygyffx5hg2f5vm8r74sr:2ml3f5dne9
• sentence: trevato/forge: "concurrent checks > a fresh account's second check waits queued, naming the count; the owner's two run at once; a freed slot starts the waiter" failed on 3 pulls in the last hour — the lane's red, not theirs; they wait for main's next green check, unparked.
• first open: 2026-10-22T07:40:21.310Z
• total: 34 minutes in the day
• href: /trevato/forge/issues/5195