spaxel/mothership/cmd
jedarden 231d7566cc fix(bf-243os): strip Fuse debug instrumentation; complete runtime sim->blob path
The runtime bridge produced zero tracked blobs from spaxel-sim CSI. Four
fixes land together to deliver bf-243os (strip + verify the path):

- main.go: app-lifetime ctx was a child of startupCtx, so startupCancel()
  killed the Phase-6 fusion loop at startup completion -> Fusion() never ran
  -> 0 blobs. Make ctx a child of context.Background().
- sim/verify.go: /api/blobs was 404ing (trimmed "/ws" but the node endpoint
  is /ws/node, leaving "/node"). Drop the WS path entirely and poll over
  12x500ms keeping the peak count (blobs are intermittent).
- sim/main.go: don't cancel() CSI streaming before -verify runs; tracked
  blobs decay to 0 once CSI stops, so verifying after cancel() saw an
  empty set.
- fusion.go: remove the transient bf-2eub9 FUSE-DBG instrumentation
  (debugFuseTick/debugEvery, dbg* accumulators, log block) now that the
  runtime sim->blob path is verified.

Verified: spaxel-sim -verify -> [SIM] PASS: 2 blobs detected for 2 walkers
(peak_blob_count=2 == walkers=2, exit 0); /api/blobs non-empty on 8 of 35
ticks; 0 rejects; fusion+tracker unit tests pass.

Co-Authored-By: Claude <noreply@anthropic.com>
2026-07-07 20:17:32 -04:00
..
mothership fix(bf-243os): strip Fuse debug instrumentation; complete runtime sim->blob path 2026-07-07 20:17:32 -04:00
sim fix(bf-243os): strip Fuse debug instrumentation; complete runtime sim->blob path 2026-07-07 20:17:32 -04:00
_parse_check.go feat: verify dashboard WebSocket feed supports events, alerts, BLE, triggers, health 2026-04-07 09:54:14 -04:00