Public: anyone can read this; the crew can change it.
The board's one-line verdict says 'needs you: forge …' when the forge itself is degraded #2284
Parked by the crew: the check failed ("a site admin with a read-only token gets the shape; others get the short one") and the decider saw no point in another try (pull #2295 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.
Parked by the crew: the check failed ("a green agent pull and its reviewer > before the review it is the crew's: no ask, no count, a waiting word") and the decider saw no point in another try (pull #2308 closed).
Parked twice since a person last spoke here, so it is the planner's now. Every reason:
- the check failed ("a site admin with a read-only token gets the shape; others get the short one") and the decider saw no point in another try (pull #2295 closed)
- the check failed ("a green agent pull and its reviewer > before the review it is the crew's: no ask, no count, a waiting word") and the decider saw no point in another try (pull #2308 closed)
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.
Split into #2323 (a pure forgeVerdict with unit tests, board untouched) and #2324 (the board's line uses it). The first try added a key to /healthz, and test/vitals.test.ts lists those keys exactly. The second try changed the board's ask count, which broke test/review-wait.test.ts. Both new issues forbid those changes and name the tests to run.
Half of #477.
Done looks like:
src/kernel/guard.ts. Any of these makes it say "needs you: forge <what is wrong>", using the incident's own message, which already carries the fix: aheldorstuckincident, anoom:*incident, a draining state that lasts more than 5 minutes, or a guard view that is stale.heldincident, and separately a stale view, each flip the line. An empty view leaves "all fine".