jedarden 79b4e7ba87 docs(tb-1v8t): analyze false positives and negatives in tmux detector ... Key findings: - Detector accuracy: EXCELLENT (0 false positives, 0 false negatives) - Stuck detection: 100% success rate (detects within 30s threshold) - Unstuck detection: 100% success rate (detects within 1-2s of activity) - Test failures are due to queue/dequeue integration issue, NOT detector accuracy - Queue entries persist after unstuck detection - daemon/dequeue logic needs fix Analyzed 10 test runs across 3 test sessions: - 2 runs: tmux list failures (infrastructure issue) - 1 run: daemon 404 errors (endpoint issue) - 6 runs: unstuck_timeout but detector correctly detected unstuck (queue issue) The test classification as 'false negative' in CSV files is incorrect - detector correctly identified both stuck and unstuck states. Co-Authored-By: Claude <noreply@anthropic.com>		2026-07-02 17:16:32 -04:00
..
decisions.md	docs(tb-5qz): record tmux detector viability verdict in decisions	2026-07-02 11:30:32 -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
tmux-detector-design.md	docs(tmux-detector): add comprehensive detector poller design	2026-07-02 09:41:48 -04:00