Sentinel: red:01m5d7cqqygepyqh1der4pxcrz is past its budget: trevato/arm: main is red at 8190a91 — forge.json: check.run is required; 2 pull checks wait for it to pass. #3878

red:01m5d7cqqygepyqh1der4pxcrz is past its budget: trevato/arm: main is red at 8190a91 — forge.json: check.run is required; 2 pull checks wait for it to pass.

Evidence

• cause: red:01m5d7cqqygepyqh1der4pxcrz
• sentence: trevato/arm: main is red at 8190a91 — forge.json: check.run is required; 2 pull checks wait for it to pass.
• since: 2026-10-21T00:20:23.296Z
• href: [redacted]

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

What to look for when fixed: red:01m5d7cqqygepyqh1der4pxcrz is gone from the degraded list and the cause is fixed, not waited out.

Mechanical fix: Fix the failing test on main in one pull. This is the only issue for it: pulls red on the same test wait for main, and no other builder is handed it while this is open.

Found by the sentinel at 2026-10-21T00:20:34.172Z.

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

Still there at 2026-10-21T01:20:37.191Z, evidence now:

• cause: red:01m5d7cqqygepyqh1der4pxcrz
• sentence: trevato/arm: main is red at 044b88b — forge.json: check.run is required; 15 pull checks wait for it to pass.
• since: 2026-10-21T00:28:23.387Z
• href: [redacted]

Parked by the crew: the run ended without a pull: declined: this issue is about the trevato/arm repository, whose main is red at 8190a91 because its forge.json has no check.run. This clone is trevato/forge, and its forge.json already declares `chec

Parked by the crew: the run ended without a pull: declined: this issue is about trevato/arm, whose main is red at 8190a91 because its forge.json has no check.run. I checked again and nothing has changed since the first decline.

Parked twice since a person last spoke here, so it is the planner's now. Every reason:

1. the run ended without a pull: declined: this issue is about the trevato/arm repository, whose main is red at 8190a91 because its forge.json has no check.run. This clone is trevato/forge, and its forge.json already declares `chec
2. the run ended without a pull: declined: this issue is about trevato/arm, whose main is red at 8190a91 because its forge.json has no check.run. I checked again and nothing has changed since the first decline

The planner splits it, replaces it with a fresh issue, or defers it; a person can also say what to try. Nothing starts here until then, and the board lists it.

Replaced by #3895. This issue asks for a fix in trevato/arm (its forge.json lacks check.run), and a builder in a trevato/forge clone cannot make that fix, so the crew declined it twice. The bug on the forge side is that the sentinel files another repository's red main here as a builder issue; #3895 fixes that. trevato/arm's red main stays on the degraded list for its owner.