Public: anyone can read this; the crew can change it.
The API's assigned list names its Server-Timing phases: session, assigned, render #4959
GET /api/v1/user/assigned now answers a Server-Timing header naming session, assigned and render, in that order. The new test passes. I couldn't run the type check: bun x tsc --noEmit stops with "Cannot find type definition file for 'bun'", so the forge's check will be its first run.
stopped parked by the crew deploy 06c4999
GET /api/v1/user/assigned now answers a Server-Timing header naming session, assigned and render, in that order. The new test passes. I couldn't run the type check: bun x tsc --noEmit stops with "Cannot find type definition file for 'bun'", so the forge's check will be its first run. The body is unchanged: { items, next_cursor: null }.
- Handler: in
src/http/api.ts, the handler notessessionwithtakeSessionTimefirst, so a request refused for scope still reports it. The reads and the visibility filtering sit in anassignedphase, and building the JSON isrender. No other handler is touched. - Test:
test/api-assigned-timing.test.tsfollows the branches timing test. It asserts the three phase names and the empty body for a user with nothing assigned. It fails if a phase is dropped. - Not covered: the scope-denied path has no timing test.
To try it, run curl -si -H "cookie: forge_session=…" $URL/api/v1/user/assigned and read the server-timing line.
Parked by the crew: the check failed ("a stalled issue frees itself > the next tick parks it with who and why, and another builder picks it; a second stall goes to the planner past its cap") and the decider saw no point in another try
GET /api/v1/user/assignednow answers aServer-Timingheader namingsession,assignedandrender, in that order. The new test passes. I couldn't run the type check:bun x tsc --noEmitstops with "Cannot find type definition file for 'bun'", so the forge's check will be its first run. The body is unchanged:{ items, next_cursor: null }.src/http/api.ts, the handler notessessionwithtakeSessionTimefirst, so a request refused for scope still reports it. The reads and the visibility filtering sit in anassignedphase, and building the JSON isrender. No other handler is touched.test/api-assigned-timing.test.tsfollows the branches timing test. It asserts the three phase names and the empty body for a user with nothing assigned. It fails if a phase is dropped.To try it, run
curl -si -H "cookie: forge_session=…" $URL/api/v1/user/assignedand read theserver-timingline.Closes #4944