A repository's tell page's Server-Timing names its phases: session, each read, render #3538

GET /:owner/:name/tell now sends a Server-Timing header with session, repo, access and render phases, written the same way src/web/pages/milestones.ts does it. The new test and the existing tell-toolbar test pass. The type check did not run: bun x tsc --noEmit failed here with "bun is unable to write files to tempdir: ReadOnlyFileSystem". I pushed anyway, so the forge's check is the first type check this change gets.

• Phases: session is the time the server already spent on the session. repo is loadRepo. access is mayDirectCrew, the page's only other read. render covers the composer and the page or fragment, and it is also set for ?in=place.
• Unchanged: the body, status codes and caching, and the order and errors of the wrapped reads. The not-found and sign-in-first early returns are as before.
• Left out: those early returns send no render phase, because nothing is rendered. Milestones behaves the same way. No other page is touched.
• Test: test/tell-here-timing.test.ts requests the page and ?in=place and checks each phase name has a duration. It checks names only, never a wall-clock time.

To try it, sign in, then run curl -sI -b <cookie> https://<host>/<owner>/<name>/tell and read server-timing.

🤖 Generated with Claude Code

Closes #3508

GET /:owner/:name/tell now sends a Server-Timing header with session, repo, access and render phases, written the same way src/web/pages/milestones.ts does it. The new test and the existing tell-toolbar test pass. The type check did not run: bun x tsc --noEmit failed here with "bun is unable to write files to tempdir: ReadOnlyFileSystem". I pushed anyway, so the forge's check is the first type check this change gets.

• Phases: session is the time the server already spent on the session. repo is loadRepo. access is mayDirectCrew, the page's only other read. render covers the composer and the page or fragment, and it is also set for ?in=place.
• Unchanged: the body, status codes and caching, and the order and errors of the wrapped reads. The not-found and sign-in-first early returns are as before.
• Left out: those early returns send no render phase, because nothing is rendered. Milestones behaves the same way. No other page is touched.
• Test: test/tell-here-timing.test.ts requests the page and ?in=place and checks each phase name has a duration. It checks names only, never a wall-clock time.

To try it, sign in, then run curl -sI -b <cookie> https://<host>/<owner>/<name>/tell and read server-timing.

🤖 Generated with Claude Code