feat(issue-10): broadcast hub state changes over WebSocket #12
No reviewers
Labels
No labels
area/android
area/device
area/hardware
area/linux-hub
area/protocol
area/server
area/testing
area/ui
kind/bug
kind/chore
kind/docs
kind/feature
state/blocked
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
rznz/signal-lost!12
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/10-websocket-state-broadcast"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Issue
Closes #10
Summary
Hardware events and session reset now broadcast authoritative state to connected WebSocket clients without polling. A lifespan-managed FIFO worker serializes mutations and advances a process-local revision; independent bounded outboxes isolate slow or disconnected subscribers. Existing puzzle rules, REST endpoints and JSON ping/pong behavior remain intact.
Acceptance Criteria
Verification
Documentation and architecture
AI assistance
Prompt log: docs/prompts/10-websocket-state-broadcast.md.
Review
Review requested from echo1.
Integration correction
Commit
e569268shields WebSocket child cleanup from surrounding ASGI cancellation and adds a deterministic regression that fails before the fix. Full Python suites passed 16/16 in five consecutive runs; fresh live Uvicorn/socket smoke passed. AnyIO is now declared directly; dependency package versions are unchanged. New evidence is recorded in follow-up task #11 because prior completed task memory is frozen.