You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
chore: v0.2 wave follow-ups -- status column, 401 version header, last_row_id over-report, conformance vocabulary #25
Worker 401 path escapes the version header (from PR docs(#4): raise X-Http-Sql-Version emission from SHOULD to MUST #16): now that X-Http-Sql-Version is MUST, the D1 worker's auth-failure response path (Hono app.onError / early 401) must be verified to carry the header; the reviewer flagged it as unverified.
D1 last_row_id over-reporting (from PR fix(#6): narrow lastInsertId to string or null #17): D1 returns meta.last_row_id = 0 on SELECT/UPDATE/DELETE, now emitted as "0" -- a misleading lastInsertId for statements that inserted nothing. Map 0-on-non-INSERT to null, or verify D1's actual semantics and document.
Resolved en route, recorded so nobody re-files: PR #19's exclusion of lastInsertId from the tagged-value MUSTs was justified by its then string|number union; #17's narrowing to string-or-null makes the exclusion permanently coherent (a decimal string loses nothing). No action.
Done When
Each numbered item fixed or explicitly dispositioned on this card
Closed by operator ruling (2026-08-29): none of the four items is a transport-spec matter. The version header on the 401 path and lastInsertId being null for a non-inserting statement are already normative (sections 9 and 6.1) and are reference-server bugs if they misbehave; the checks vocabulary and the implementations.md status column are repository housekeeping. If any of them needs doing it is filed against the implementation, not the spec.
Activity
ssilvius commentedon Aug 29, 2026
Closed by operator ruling (2026-08-29): none of the four items is a transport-spec matter. The version header on the 401 path and lastInsertId being null for a non-inserting statement are already normative (sections 9 and 6.1) and are reference-server bugs if they misbehave; the checks vocabulary and the implementations.md status column are repository housekeeping. If any of them needs doing it is filed against the implementation, not the spec.