The API's tags list names its Server-Timing phases: session, git, render #3914

I couldn't run bun x tsc --noEmit, so the type check is unconfirmed. bun install and bun x both fail here with "bun is unable to write files to tempdir: ReadOnlyFileSystem". bun test works, but the change is pushed without the type check you listed.

The tags list (GET /api/v1/repos/:owner/:name/tags) now names its Server-Timing phases in src/http/api.ts. It notes session first, wraps listRefs in timePhaseAsync(..., "git", ...), and builds the JSON in timePhase(..., "render", ...). The empty [] path and the success path both go through render. I added no import and touched no other handler.

A missing repository is still a 404 whose Server-Timing names session. The JSON body (name, oid, commit) is unchanged.

test/api-tags-timing.test.ts is new. It asserts session, git, render for the empty tags list and session alone for the 404, and passes with bun test. I did not run it against the old handler, so I haven't confirmed it fails without the change. It only covers the empty path, because the test repo has no tags. The success path with tags is covered by reading the code, not by a test.

To try it, fetch /api/v1/repos/<owner>/<name>/tags on the preview and read the Server-Timing header after app.

Closes #3899

I couldn't run bun x tsc --noEmit, so the type check is unconfirmed. bun install and bun x both fail here with "bun is unable to write files to tempdir: ReadOnlyFileSystem". bun test works, but the change is pushed without the type check you listed.

The tags list (GET /api/v1/repos/:owner/:name/tags) now names its Server-Timing phases in src/http/api.ts. It notes session first, wraps listRefs in timePhaseAsync(..., "git", ...), and builds the JSON in timePhase(..., "render", ...). The empty [] path and the success path both go through render. I added no import and touched no other handler.

A missing repository is still a 404 whose Server-Timing names session. The JSON body (name, oid, commit) is unchanged.

test/api-tags-timing.test.ts is new. It asserts session, git, render for the empty tags list and session alone for the 404, and passes with bun test. I did not run it against the old handler, so I haven't confirmed it fails without the change. It only covers the empty path, because the test repo has no tags. The success path with tags is covered by reading the code, not by a test.

To try it, fetch /api/v1/repos/<owner>/<name>/tags on the preview and read the Server-Timing header after app.

The full gate on land was red and named no test; the pull is open again.

GET /api/v1/repos/:owner/:name/tags now reports Server-Timing phases session, git and render, in that order. A missing repository still returns 404 and reports only session. The JSON body, the visibility check and the 404 are unchanged.

Why the gate was red: test/parity.test.ts ("a pull can be labeled, closed, reopened…") was failing, and it fails the same way with the base api.ts restored, so my change did not cause it. The test expected GET /issues/:n to return 404 for a pull's number. #3299 deliberately made that endpoint return the pull's data marked kind: "pull", so the test was wrong. I changed it to expect 200 and kind: "pull". That is the only change in this push.

Checks:

• bun scripts/gate.ts exits 0.
• test/api-tags-timing.test.ts and test/parity.test.ts pass.
• Six other test files that touch tags or the API (push-through, sealed-release, search-cache, migrate, proposal-token, and the api* tests) pass too.
• The type check did not run. bun install fails in my sandbox (read-only tempdir), so there is no node_modules, and the forge check will be the first to run it.
• I did not run the rest of the suite.

Not done: @sentinel's nit about adding a tag to the fixture so the non-empty render path is covered. It needs a tag-creating helper that I didn't find, so the timing tests still cover only the empty-tags response.

Parked by the crew: the check failed in the place it ran, not in the change, and failed the same way when it was run again