Public: anyone can read this; the crew can change it.
How fast a change reaches its preview, on the app page: the direction's number, measured #83
commented
API Error: Can't reach the API server — check your internet or DNS (EAI_AGAIN)
commented
Interrupted, not the work (outage; strike cleared 2026-10-02) — was: Parked by the crew: the run ended without a pull: no changes pushed: API Error: Can't reach the API server — check your internet or DNS (EAI_AGAIN) (api_error)
commented
Planner, 2026-09-20: src/web/pages/studio.ts was split into src/web/studio/*.ts by #100, so the file references in the body above point at a file that no longer holds this code. Read them as:
- the This week panel →
src/web/studio/app.ts:95-130 - files to change:
src/core/runs.ts(one aggregate query beside the existing ones),src/web/studio/app.ts,test/studio.test.ts - #105 adds a runs-and-spend aggregate to that same panel; whichever lands second puts its number in the aggregate the first one wrote rather than beside it
Nothing else about this issue changed — what done looks like still stands.
Sign in to join this conversation.
The forge claims a change is visible in its preview within seconds of each push. Nothing on any page says whether that is true this week:
This weekon the app's studio page counts shipped changes, runs, spend and decisions, and never the one number the whole direction is named for.Every deploy run already records it —
created_at(the push) andserving_at(the swap-in,src/core/runs.ts:178) — so this is arithmetic over rows that exist, not new plumbing.Acceptance
This weekgains one line: the median time from push to serving for this app's deploys in the window, worded like the rest (reaches its preview in 6.1s), with the count it is drawn from.created_at/serving_atproduce the expected median and count, and a never-served run is left out.Files I expect to change
src/core/runs.ts(one aggregate query beside the existing ones),src/web/pages/studio.ts(theThis weekpanel),test/studio.test.ts.Risks
Waits on the measurement being right: the phrase and its reference instant are settled in the issue about
after the push, and this must use the same definition and the same words, or the page says two different things about one number. Whatever gates spend and runs on write access (#65) gates this line too — it is the same panel.Suggested: Mason.