Public: anyone can read this; the crew can change it.
/review: one quiet column where each item says what, why it needs you, the crew's recommendation and the evidence #3257
Parked by the crew: the check failed ("reserved names > every top-level page of the forge is a reserved name") and the decider saw no point in another try (pull #4337 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 ("bun scripts/hollow.ts says so and exits 0") and the decider saw no point in another try (pull #4343 closed).
Parked twice since a person last spoke here, so it is the planner's now. Every reason:
- the check failed ("reserved names > every top-level page of the forge is a reserved name") and the decider saw no point in another try (pull #4337 closed)
- the check failed ("
bun scripts/hollow.tssays so and exits 0") and the decider saw no point in another try (pull #4343 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 #4383 (the page with title, repository, age and why; review becomes a reserved name and the page is linked, which fixes both earlier failures) and #4384 (recommendation and evidence). #3259 now waits on #4383 and #3258 on #4384.
Part 2 of #3247. It is a read-only page. Acting from it is the next issue.
Done looks like:
/review(signed in; anyone else goes to sign-in) lists the asks fromsrc/web/studio/asks.ts, one per row, newest decision first. Each row shows these without clicking away:- the title, repository and age - the
whysentence - the crew's recommendation and its reason - the evidence: diff stat, check result, preview link, and the before/after look when the pull has onesession,asks,render. Server time stays under 200 ms with 50 seeded asks.docs/DESIGN.md§5 already names (card,listCard,btn,.small,.muted). Add no class, colour literal,style=or off-scale size. Pull #3253 failed on this. If a class is truly needed, name it in §5d in the same pull./reviewtodocs/design/audit.mdand raise its "There are N top-level pages" count by one. Pull #3254 failed on this.bun test test/design-lint.test.ts test/design-audit.test.tsbefore the push, and both pass.test/review-page.test.tsseeds a handed-over pull, a stale pull and an issue the crew asked about. It finds exactly three rows, each with its why and recommendation.Files:
src/web/studio/review_page.ts(new),src/http/server.ts(route),docs/design/audit.md,test/review-page.test.ts. Risks: /asks stays as it is. Folding it into /review is a later decision for the owner.