infra/scripts/t3-dispatch
Viktor Barzin c64ead0112 t3-dispatch: re-pair on present-but-invalid t3_session cookie
The dispatcher only re-paired on an ABSENT cookie. After the 2026-06-09
auth-schema rollback wiped all server-side sessions, browsers kept dead
30-day t3_session cookies; the dispatcher proxied them straight through
and t3 rendered its pair page ("all users must pair again").

Now a present cookie on a top-level document navigation is validated via
the instance's /api/auth/session and re-paired on authenticated:false.
Gated to document navs (Sec-Fetch-Dest: document, else Accept: text/html)
so XHR/asset/WebSocket sub-requests are never answered with a 302; fails
open (proxy through) on any validation error. Unit + handler tests added.

[ci skip]

Co-Authored-By: Claude <noreply@anthropic.com>
2026-06-09 15:51:08 +00:00
..
go.mod t3code: devvm dispatch + auto-pair service (Go) 2026-06-02 19:24:30 +00:00
main.go t3-dispatch: re-pair on present-but-invalid t3_session cookie 2026-06-09 15:51:08 +00:00
main_test.go t3-dispatch: re-pair on present-but-invalid t3_session cookie 2026-06-09 15:51:08 +00:00