Public: anyone can read this; the crew can change it.
The cold front page build is slow: batch the per-repo canRead queries and the runtime status scan #6136
Live triage (automatic, not written by a person): no pillar named, so it waits behind the Later gate; name a pillar to move it.
Parked by the crew: the check failed ("verify an email from the People screen > an admin verifies the person under the cursor and the row changes") and the decider saw no point in another try try 1: src/actions/front.ts, src/core/repos.ts, test/stranger-readable.test.ts (pull #6139 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 stayed red through 2 automatic tries (pull #6139 closed).
Parked twice since a person last spoke here, so it is the planner's now. Every reason:
- the check failed ("verify an email from the People screen > an admin verifies the person under the cursor and the row changes") and the decider saw no point in another try try 1: src/actions/front.ts, src/core/repos.ts, test/stranger-readable.test.ts (pull #6139 closed)
- the check stayed red through 2 automatic tries (pull #6139 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.
Follow-up to #6126. The warm path is cached; a cold build of / (after any database write, or 3 s idle) still runs canRead (one query per repo, twice over owners) and runtime.status (a scan of every env per app) for up to 200 public apps. Batch both so a cold build is also under 10 ms. Files: src/actions/front.ts, src/core/repos.ts, src/apps/runtime.ts.