Johannes Merz b64aaab40a fix: WS upgrade auth — multi-token bearer not validated ... Problem: isAuthenticated() for WS upgrade only checked legacy single token. iOS bearer token (from POST /pair → createToken()) was rejected → 403 on WS. Fix: - warmTokenCache(): pre-load all multi-tokens into a sync Set on startup - validateBearerSync(): O(1) sync lookup against the cache - createToken(): adds to cache immediately on creation - isAuthenticated(): checks validateBearerSync() as third fallback		2026-05-16 03:12:43 +02:00
..
routes	feat(T-1.5/1.6/1.7): stream+input+snapshot routes, sessions CRUD, commands, side-channel, health endpoint	2026-05-15 11:35:55 +02:00
server.ts	fix: WS upgrade auth — multi-token bearer not validated	2026-05-16 03:12:43 +02:00
types.ts	refactor(T-1.0): carve server.ts into server/ sub-modules	2026-05-15 10:57:52 +02:00
upgrade.ts	feat(T-1.5/1.6/1.7): stream+input+snapshot routes, sessions CRUD, commands, side-channel, health endpoint	2026-05-15 11:35:55 +02:00
util.ts	feat(T-1.5/1.6/1.7): stream+input+snapshot routes, sessions CRUD, commands, side-channel, health endpoint	2026-05-15 11:35:55 +02:00