4dcc06af2b
Verify the sim/header-side half of the tokenless-sim REJECT root cause against current source (second link of the bf-34lwt split). Three facts re-checked against current source: - Sim supplies its token ONLY as the X-Spaxel-Token HTTP header on the WS dial — cmd/sim/main.go:313, mothership/cmd/sim/main.go:633, mothership/cmd/sim/scenario.go:318 (all three connect paths). - The hello JSON map the sim sends has NO token field — cmd/sim/main.go:348-359, mothership/cmd/sim/main.go:652-665, mothership/cmd/sim/scenario.go:331-342. Only "--token" hits are CLI flag defs, never a JSON body key. - The mothership NEVER reads that header on the WS path — grep 'X-Spaxel-Token' mothership/ excluding _test.go and cmd/sim/ returns zero hits. HandleNodeWS (server.go:455-469) passes r straight to Upgrade; the only Header ref on the path is the outbound w.Header().Set response header. Conclusion: header ignored -> hello.Token (message.go:22) empty -> tokenOK (server.go:513) always false. The "have the sim supply valid tokens" option is currently DEAD. Companion to bf-5ig3e (validator half); both roll up into bf-34lwt. Co-Authored-By: Claude <noreply@anthropic.com> Bead-Id: bf-29wyl |
||
|---|---|---|
| .. | ||
| notes | ||
| plan | ||
| research | ||
| ci-accessibility-integration.md | ||
| ci-benchmark-integration.md | ||