jedarden f5c35c65d6 docs(tb-2tc5): document normalized event API endpoint design decision ... 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>		2026-07-02 22:06:42 -04:00
..
decisions.md	docs(tb-163k): compile comprehensive test results from all 21 acceptance test runs	2026-07-02 19:54:09 -04:00
normalized-event-contract.md	docs(normalized-event-contract): add comprehensive harness-agnostic adapter contract specification	2026-07-02 09:38:57 -04:00
tb-1v8t-analysis.md	docs(tb-1v8t): analyze false positives and negatives in tmux detector	2026-07-02 17:16:32 -04:00
tb-2tc5-api-design-decision.md	docs(tb-2tc5): document normalized event API endpoint design decision	2026-07-02 22:06:42 -04:00
tmux-detector-design.md	docs(tmux-detector): add comprehensive detector poller design	2026-07-02 09:41:48 -04:00