f5c35c65d6
Document the rationale for choosing Option 1 (/event/normalized endpoint) over Option 2 (server-side adapter wrapper). Key points: - Separates harness-specific detection from harness-agnostic core - Simplifies adapter implementations (clean JSON, no header synthesis) - Scales to multiple harnesses without adapter chains - Improves error clarity and testability Includes: - Decision rationale comparing both options - Endpoint implementation details - Event schema reference - How tmux detector submits events - Migration path for future adapters Co-Authored-By: Claude <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| notes | ||
| plan | ||
| research | ||