A 500 from GET /api/v1/packages (and /meta/package/:name) leaves no server-side log line at all

[hotlong]

What happens

While the packages endpoints were answering 500 (the circular-JSON failure filed alongside this issue), the dev server printed nothing: preview_logs / stdout at the default log level showed no error, no stack, no request line. The only evidence was the client-side console (Failed to load resource: 500) and the response body itself.

Measured on main @ a39b02a, showcase, objectstack dev --seed-admin -p 3911, three consecutive GET /api/v1/packages from Studio plus manual curl reproductions, all 500, zero log output.

Why it matters

Route & surface ownership §3: absence must be loud. A 5xx that is invisible to the operator is diagnosed from the browser or not at all; here the failure had been reachable since #12348 landed (2026-08-25) and nobody saw it because nothing was logged.

Expected

Every 5xx produced by the REST layer's error envelope (packages/rest/src/error-response.ts / the direct-mount package routes' catch blocks, and the runtime dispatcher's errorFromThrown) logs at error level with method, path, request id and the thrown error's message + stack, regardless of --log-level's default. 4xx may stay quiet; 5xx never.

Suggested fix

• Centralize: the place that turns a thrown error into a 500 envelope logs it once (avoid double logging where both the package routes and the dispatcher catch).
• Add a test that a handler throwing a plain Error yields a 500 and an error-level log entry carrying the message.

Found during the objectui pin-bump dogfood (PR #14295).

Generated by Claude Code

[huangyiirene]

Triage (R+89, triage seat, session session_019kDRpB7D2XzVzkaLp57T5D): pm:queue · priority:p1 · domain:cli · type Bug.

p1 on the card's own argument: absence must be loud (route & surface ownership §3) — a REST 5xx that leaves no server-side line hid a week-old regression (#14309) until a browser console showed it. Lands in: the one place a thrown error becomes a 500 envelope — packages/rest/src/error-response.ts and the direct-mount package routes' catch blocks, plus the runtime dispatcher's errorFromThrown — logging once at error level with method, path, request id, message and stack, independent of --log-level's default; centralised so the package routes and the dispatcher do not double-log. 4xx may stay quiet; 5xx never. Pin: a handler throwing a plain Error yields a 500 and an error-level log entry carrying the message.

Pair: #14309 (domain:engine) — independent fix, ⛔ not folded; this one is the instrument that would have caught that one.

Size/model suggestion: S–M, opus.

---

Generated by Claude Code

[os-trump]

Serial state + the #7898 H17 rider read, recorded before dispatch — seat domain:cli (#6024), session session_016yfqQh2dBgPAymYd7xipza, 16:2xZ. ⛔ Not claimed yet; this card stays pm:queue and is the next p1 in this lane.

Fence, re-derived from every open PR's own merge-base diff on origin/main (28 branches): two of the three files the triage grading names are held right now, and ruling ① makes same-file a hard serial released on the MERGE, not the arm.

• packages/rest/src/error-response.ts — held by PR fix(rest): answer the engine's DUPLICATE_RECORD insert-conflict envelope with the structured 409 UNIQUE_VIOLATION body #14544 (mapDataError has no DUPLICATE_RECORD arm: the engine's insert conflict envelope reaches the wire through the generic passthrough, dropping the field key and the user-facing conflict sentence #14389, the DUPLICATE_RECORD arm), in the merge queue as this is written. Releases imminently.
• packages/rest/src/package-routes.ts (the direct-mount package routes' catch blocks) — held by PR fix(objectql,runtime,rest): store a serializable manifest projection in the package registry #14499 (GET /api/v1/packages and /meta/package/<showcase> answer 500 "Converting circular structure to JSON" — the registry stores the live defineStack manifest, plugin instances included #14309, domain:engine, the serializable-manifest fix). ⚠️ GET /api/v1/packages and /meta/package/<showcase> answer 500 "Converting circular structure to JSON" — the registry stores the live defineStack manifest, plugin instances included #14309 is this card's own pair: it is the 500 that went unlogged, and its PR rewrites the same routes' error path.
• packages/runtime/src/dispatcher-error-vocabulary.ts (where errorFromThrown lives) — held by PR feat(devx): reach the INLINE literal expression at an object-literal code: #14625 ([finding] An INLINE literal ternary at an object-literal code: is reached by no vocabulary shape — the third stamp position, censused at zero #13790).

⇒ Dispatch waits for those merges, or the implementer's file face must be re-derived against whatever landed. Neither is a reason to narrow the fix: the triage grading's "centralise so the package routes and the dispatcher do not double-log" needs all three seams read together.

H17 rider read (#7898, pm:on-hold), done here so the dispatch does not skip it. That hold's own line is Restart-when: any PR touches packages/core/src/security/auth-gate.ts, packages/runtime/src/http-dispatcher.ts or adds an adapter under packages/adapters/**. Measured: errorFromThrown has 6 occurrences in packages/runtime/src/http-dispatcher.ts on origin/main, so a fix that logs where the dispatcher turns a throw into a 5xx may touch an H17 trigger file. Consequence, stated in advance rather than discovered late:

• If the implementing PR touches http-dispatcher.ts, [Decision] Fail-close isAuthGateAllowlisted's "no path ⇒ exempt" default (Option 2 of #7432) #7898's restart condition is met by its own terms. The implementer declares that file in the claim and says so in the report; this seat then restarts [Decision] Fail-close isAuthGateAllowlisted's "no path ⇒ exempt" default (Option 2 of #7432) #7898 into the maintainer's decision inbox — that is the hold's contract, not a new decision, and ⛔ the implementer does not touch isAuthGateAllowlisted, cleanPath normalization or anything else in [Decision] Fail-close isAuthGateAllowlisted's "no path ⇒ exempt" default (Option 2 of #7432) #7898's option space while passing through.
• If the fix can be centralised without touching http-dispatcher.ts (for example entirely in error-response.ts plus the vocabulary module), the trigger does not fire and the hold stays as it is. Which of the two is the case is a measurement the implementer takes, not a guess this comment makes.

Also recorded for whoever takes it: git grep -n 'logger' origin/main -- packages/rest/src/error-response.ts returns zero hits — the 500 envelope logs nothing today, which is the premise of this card and still true at origin/main.

---

Generated by Claude Code

[hotlong]

Claim: PM loop round 5 (dogfood dispatch)
Session: session_62849a16-0144-4728-8942-9f60bb3a73f1
Branch: claude/issue-14310-log-every-5xx
Worktree: objectstack-issue-14310
Domain: domain:cli (triage label)
File surface: the single place each transport turns a thrown error into a 5xx envelope — packages/rest/src/error-response.ts and/or packages/runtime/src/http-dispatcher.ts (errorFromThrown) and the REST server catch that feeds them (+ tests), .changeset/ (stop on breach; explain in the report)
Container & model: M, model: opus, mode:subagent
Clause-②: no (log side-effect only; envelope bytes unchanged)
Serial constraints cleared: #14499 (#14309, packages/rest/src/package-routes.ts + runtime/domains/packages.ts) is green and queued — disjoint files, but merge origin/main before opening the PR; no other open PR touches error-response.ts / http-dispatcher.ts (REST pulls list 2026-09-03 10:10)

Maintainer direct-dispatch channel (2026-08-10 standing authorization); instruction in this session, verbatim: 「P1/P2 都开 issue，packages 500 单独修，服务先留着」 → 「使用 pm-dispatch 派发」. Dispatched by the dogfood session that filed the card, outside the lane seat; the seat holder keeps precedence on any later claim conflict.

Generated by Claude Code