Files
hub/tasks/architecture/storage/add-spoke-reconnecting-state.md
glm-5.1 2b63cda1c7 Setup repo: migrate architecture specs, code stubs, and tasks from alkhub_ts
Copy architecture docs, ADRs, storage domain specs, research, reviews,
and 56 storage architecture tasks from the alkhub_ts monorepo. Adapt for
standalone @alkdev/hub repo structure (src/ not packages/hub/).

Sanitize all sensitive information:
- Replace private IPs (10.0.0.1) with localhost defaults
- Remove internal server hostnames (dev1, ns528096)
- Replace /workspace/ private paths with npm package references
- Remove hardcoded credentials from examples
- Rewrite infrastructure.md without private network details

Add Deno project scaffolding: deno.json (pinned deps), .gitignore,
AGENTS.md, entry point. Migrate existing code stubs (crypto, config
types, logger) with updated import paths.
2026-05-25 10:56:32 +00:00

36 lines
1.2 KiB
Markdown

---
id: add-spoke-reconnecting-state
name: Add Spoke 'reconnecting' Status or Document DB-Free Approach
status: completed
depends_on: []
scope: narrow
risk: low
impact: isolated
level: implementation
---
## Description
W06: The spoke status enum is only `connected`/`disconnected`. The spoke-runner.md describes a reconnection flow, but there's no `reconnecting` state. A spoke with a dropped WebSocket shows `disconnected`, indistinguishable from a permanently offline spoke.
Either add `reconnecting` to the spoke status enum, or document that reconnection is handled at the application layer (WebSocket reconnect timer) without a DB state change.
## Acceptance Criteria
- [ ] Either `reconnecting` added to `spokes.status` enum in `spokes.md` and `table-reference.md`, OR
- [ ] Document explicitly that reconnection is application-layer-only (no DB state change) with rationale
- [ ] `spoke-runner.md` reconnection flow section references the decision
## References
- docs/reviews/storage-architecture-review-2026-04-21.md#W06
- docs/architecture/storage/spokes.md:18
- docs/architecture/spoke-runner.md:130-136
## Notes
> To be filled by implementation agent
## Summary
> To be filled on completion