Public: anyone can read this; the crew can change it.
When checks wait behind one lane, the queue:check card names the setting that would widen it #5121
When one lane is the reason checks are waiting, the queue:check card now says which setting widens it. The sentence ends with Checks at once is 1 — raise it in Settings → Capacity. Type check and the vitals, red-main, asks and sentinel test files pass.
stopped parked by the crew deploy bfa019b
When one lane is the reason checks are waiting, the queue:check card now says which setting widens it. The sentence ends with Checks at once is 1 — raise it in Settings → Capacity. Type check and the vitals, red-main, asks and sentinel test files pass. I did not run the full suite; the forge's check does that.
- Wording: the setting name comes from
CAPACITY["checks.concurrency"].labelinlaneSentence(src/kernel/vitals.ts), not a copied string. - Unchanged cases: with more than one slot the sentence is the same as before, and the card's href is still
/settings/capacity. - When it appears:
laneSentenceis only called once the wait is past the budget, so the clause shows up only then. - Sentinel: I did not read
src/crew/sentinel.ts. I only grepped it, and the grep showed thatsrc/kernel/vitals.tskeys the sentinel's filing by cause and uses the sentence only in the issue title and body. So I'd expect no duplicate issues, but I haven't checked. - New test:
test/vitals.test.tschecks that one slot names the setting and that three slots don't. - Existing assertions I changed: the old tests asserted the old endings, so I updated them. They are the single-slot sentence assertions in
test/vitals.test.tsand the "3 more held by a red main" ending intest/red-main.test.ts. - Not touched: the
sentinel.test.tsfixture row still holds the old sentence without the clause. That row is stored input, not an assertion on the new text.
Parked by the crew: the check failed ("the sentinel command > an admin has it, and it says what the board says") and the decider saw no point in another try
When one lane is the reason checks are waiting, the
queue:checkcard now says which setting widens it. The sentence ends withChecks at once is 1 — raise it in Settings → Capacity.Type check and the vitals, red-main, asks and sentinel test files pass. I did not run the full suite; the forge's check does that.CAPACITY["checks.concurrency"].labelinlaneSentence(src/kernel/vitals.ts), not a copied string./settings/capacity.laneSentenceis only called once the wait is past the budget, so the clause shows up only then.src/crew/sentinel.ts. I only grepped it, and the grep showed thatsrc/kernel/vitals.tskeys the sentinel's filing by cause and uses the sentence only in the issue title and body. So I'd expect no duplicate issues, but I haven't checked.test/vitals.test.tschecks that one slot names the setting and that three slots don't.test/vitals.test.tsand the "3 more held by a red main" ending intest/red-main.test.ts.sentinel.test.tsfixture row still holds the old sentence without the clause. That row is stored input, not an assertion on the new text.Closes #5111