Public: anyone can read this; the crew can change it.
One screen answers “is everything fine?”: the asks inbox, reborn as all fine / these need you #357
Check · Review · Land · Live done — Landed and live in production.
`/asks` is now the one screen for "is everything fine?". It leads with *All fine* or *N things need you*, then the decision cards, then a card per forge-health sentence for a site admin. I ran `tsc` and the studio, web, landing, decide, autonomy, vitals, notify and asks test files; all pass. I did not run the whole suite or the full forge `check` command.
shipped production is serving it deploy 206648f
Sign in to join this conversation.
new above
offline
/asksis now the one screen for "is everything fine?". It leads with All fine or N things need you, then the decision cards, then a card per forge-health sentence for a site admin. I rantscand the studio, web, landing, decide, autonomy, vitals, notify and asks test files; all pass. I did not run the whole suite or the full forgecheckcommand.The studio's asks panel and header count that the issue describes don't exist on
main. I built them rather than reuse them./asksis a new route insrc/http/server.ts, drawn bysrc/web/studio/asks_page.ts. It is server-rendered, every button is a plain form post, and a signed-out reader is sent to sign in.src/web/studio/asks.tsnow holdsforgeNeedsFor(an admin's/api/v1/healthneeds, nothing for anyone else),askCountForandaskSentence. The count is the same list the cards come from plus the health needs.askCountForon every studio page, which costs a few grouped reads. The palette's "Asks you" now goes to/asks./asks, and absent when nothing asks. This changes what lands there: a crew pull with no check used to show on that list; now only the stopped, green and paused-at-ceiling cases do.docs/STUDIO.mdhas an "The asks" section, andtest/asks.test.tsis added to thecheckinforge.json.New
test/asks.test.tscovers:/asks;In
test/web-apps.test.tsI dropped the assertions that the dashboard lists "Bot did a thing" under Needs you, because the old definition no longer holds. I tried replacing them with a forced green check, but the live runtime's own check run raced it and the test was flaky, so the new asks tests cover that instead.Not done: no live region on
/asks(it's plain first paint), and the TUI dashboard's inbox is unchanged.To try it, sign in, open
/asks, or click Asks in the studio header.🤖 Generated with Claude Code
Closes #346