Flesh out PLAN.md with two-architecture implementation detail #1
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Expand the planning document to specify both viable data-source architectures (OTEL-native via Prometheus, and ccusage-sourced with a JSONL tail for the tach) to implementation-ready detail. Include exact Docker Compose stack, Claude Code env config, PromQL queries, daemon code sketches for each architecture, hardware stepper motor choice (X27.168 + SwitecX25 library), ESP32 wiring, and a six-phase delivery plan.
Doc-only change. No runtime code introduced.