manpengan
ebaf9c8f9a
docs: add pre-implementation spikes section to design spec
...
Three spikes gating the implementation plan:
- Spike 1: pane mode capability (tmux split + cleanup)
- Spike 2: data source stability (SQLite fields + JSONL event names)
- Spike 3: inline fallback safety (scroll region + terminal cleanup)
Each spike has goal, verification method, pass criteria, and fallback decisions.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com >
2026-03-22 08:59:01 +08:00
manpengan
9176bd9c1b
docs: tighten design spec with risk assessment and mode hierarchy
...
- Add confidence/risk assessment section (confirmed, unverified, risks)
- Explicitly frame inline mode as degraded fallback, not peer to pane
- Clarify renderer shared boundary (layout output only, not terminal control)
- Add SQLite schema versioning and JSONL protocol instability mitigations
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com >
2026-03-22 08:56:03 +08:00
manpengan
e38e56ba3e
docs: add codex-hud design spec and original plan
...
Design spec covers dual-mode architecture (tmux pane + inline fallback),
SQLite/JSONL data layer, HUD layout, installation, and error handling.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com >
2026-03-22 08:48:25 +08:00
