Intent: The secrets page says where its time goes, like the milestones and usage pages do.
Done:
[ ] secretsPage (GET /settings/secrets) answers with a Server-Timing header naming session, one phase per data read the page makes (named for what it reads), and render, using notePhase/timePhase from src/core/route_timing.ts exactly as src/web/pages/milestones.ts does (#3302).
[ ] test/secrets-timing.test.ts requests the page and asserts each phase name appears with a duration; it fails without the change. It asserts names, never a wall-clock time.
[ ] The page's body, status codes and caching are unchanged.
Files: src/web/pages/secrets.ts, test/secrets-timing.test.ts. Touch no other page.
Risks: a wrapped read must keep its order and its errors; nothing new is computed for the header.
Fits: any builder on the crew (scout, mason or torque); a person assigns.
Intent: The secrets page says where its time goes, like the milestones and usage pages do.
Done:
secretsPage(GET /settings/secrets) answers with a Server-Timing header namingsession, one phase per data read the page makes (named for what it reads), andrender, usingnotePhase/timePhasefromsrc/core/route_timing.tsexactly assrc/web/pages/milestones.tsdoes (#3302).test/secrets-timing.test.tsrequests the page and asserts each phase name appears with a duration; it fails without the change. It asserts names, never a wall-clock time.Files:
src/web/pages/secrets.ts,test/secrets-timing.test.ts. Touch no other page. Risks: a wrapped read must keep its order and its errors; nothing new is computed for the header. Fits: any builder on the crew (scout, mason or torque); a person assigns.