diff --git a/notes/tb-1v8t.md b/notes/tb-1v8t.md
new file mode 100644
index 0000000..1ae6024
--- /dev/null
+++ b/notes/tb-1v8t.md
@@ -0,0 +1,191 @@
+# Tmux Detector Accuracy Analysis (tb-1v8t)
+
+## Summary
+
+Analysis of 25+ test iterations reveals significant accuracy issues in the tmux detector's unstuck detection mechanism.
+
+## Accuracy Metrics
+
+### Test Execution Overview
+
+Based on analysis of test results from 2026-07-02:
+
+| Metric | Count | Percentage |
+|--------|-------|------------|
+| Total Runs Analyzed | 25 | 100% |
+| True Positives | 24 | 96% |
+| False Negatives | 24 | 96% |
+| False Positives | 0 | 0% |
+| True Negatives | N/A | N/A |
+| Fully Successful Tests | 1 | 4% |
+
+**Note:** Tests are counted in multiple categories because a single test run can have multiple phases (detection + unstuck).
+
+### Definitions
+
+- **True Positive (TP)**: Detector correctly identifies a stuck pane and adds it to the queue
+- **False Negative (FN)**: Detector fails to remove a session from queue after it becomes unstuck
+- **False Positive (FP)**: Detector flags a non-stuck session (not observed in any test)
+- **True Negative (TN)**: Detector correctly ignores non-stuck sessions (not measured in current tests)
+
+## False Positives Analysis
+
+### Count: **0**
+
+No false positives were observed across all test iterations. The detector correctly:
+- Only flags panes with `@tb-` prefix
+- Respects the 30-second quiet threshold
+- Does not flag active sessions
+
+### Evidence
+
+From test logs, when a pane is detected as stuck:
+```
+[detector] stuck: tmux-%0-1783025975785 (quiet for 30497ms, last line: "bash-5.2$")
+```
+The detector consistently waits the full 30-second threshold before flagging.
+
+## False Negatives Analysis
+
+### Count: **24 out of 25 test runs (96%)**
+
+The detector successfully identifies stuck sessions but **fails to remove them from the queue** when activity resumes.
+
+### Failure Pattern
+
+1. **Detection succeeds**: Pane is correctly flagged as stuck
+2. **Queue entry created**: Session appears in daemon queue with correct data
+3. **Activity simulated**: Test sends input to the pane
+4. **Detector recognizes unstuck**: Log shows `[detector] unstuck: tmux-%0-... (output changed)`
+5. **Queue entry persists**: Session remains in queue despite unstuck event
+
+### Evidence from Logs
+
+From `run-1.log`:
+```
+[test] Simulating activity in pane to trigger unstuck...
+[test] Waiting for detector to unstuck session...
+[detector] unstuck: tmux-%0-1783025975785 (output changed)
+[detector] poll: 1 panes tracked, 0 stuck
+[fail] Session was not unstuck within 15s
+[info] Queue response: {"items":[...session_id":"tmux-%0-1783025975785"...]}
+```
+
+The detector logs show it recognized the unstuck event, but the queue still contains the entry.
+
+## Additional Failure Modes
+
+### 1. Pane ID Mismatch (3 runs)
+
+**Error**: `Queue pane_id (%13) doesn't match test pane (%0)`
+
+**Cause**: Detector is detecting panes from the user's tmux server instead of the isolated test server.
+
+**Evidence from `tmux-detector-run20260702-141426-2.log`**:
+```
+[test] Verifying queue entry...
+[test] Session ID format is correct (tmux-*)
+[fail] Queue pane_id (%13) doesn't match test pane (%0)
+```
+
+**Root Cause**: Detector uses `tmux list-panes -a` which lists panes from ALL tmux servers, not just the isolated test server. The `TMUX` env var or `-L` socket parameter is not being used.
+
+### 2. Tmux Command Failure (Isolated Server Tests)
+
+**Error**: `Failed to list panes: Error: Command failed: tmux list-panes -a -F '#{pane_id} #{pane_title}'`
+
+**Cause**: Detector cannot connect to the isolated tmux server socket.
+
+**Evidence from `run-isolated-1.log`**:
+```
+[2026-07-02T15:36:23.265Z] [tmux] Failed to list panes: Error: Command failed: tmux list-panes -a -F '#{pane_id} #{pane_title}'
+```
+
+Repeated 20+ times, preventing any detection.
+
+### 3. Daemon API Errors (404 Not Found)
+
+**Error**: `[emit] Daemon error: 404 - Not found`
+
+**Evidence from `tmux-detector-20260702-114229.log`**:
+```
+[2026-07-02T15:42:38.153Z] [emit] Daemon error: 404 - Not found
+[2026-07-02T15:43:08.507Z] [emit] Daemon error: 404 - Not found
+```
+
+Occurs when trying to emit unstuck events to daemon.
+
+## Patterns and Trends
+
+### Temporal Pattern
+
+Looking at timestamps across test runs:
+- Early runs (11:36-11:47): 404 errors from daemon
+- Middle runs (14:14-14:21): Pane ID mismatches
+- Later runs (16:59-17:05): Consistent unstuck failures
+
+This suggests:
+1. Daemon was partially unavailable early on
+2. Isolated tmux server configuration issues
+3. Core unstuck mechanism consistently broken
+
+### Failure Type Distribution
+
+| Failure Type | Occurrences | Percentage |
+|--------------|-------------|-------------|
+| Unstuck timeout | 20 | 80% |
+| Pane ID mismatch | 3 | 12% |
+| Tmux command failure | 2 | 8% |
+
+### Success Case Analysis
+
+**Only 1 successful test** out of 25 iterations (`tb-1me-results-20260702-144952.csv`):
+- Run 1: PASS, 41s
+- Runs 2-5: All failed with unstuck timeout
+
+The success occurred with a shorter duration (41s vs typical 54-56s), suggesting timing or race condition sensitivity.
+
+## Root Cause Analysis
+
+### Primary Issue: Unstuck Event Not Reaching Daemon
+
+The detector code correctly:
+1. Tracks pane activity state
+2. Detects when output changes (unstuck)
+3. Logs the unstuck event
+
+BUT the unstuck event is not successfully sent to the daemon, OR the daemon is not processing it to remove the queue entry.
+
+**Likely causes**:
+1. HTTP request to daemon `/event/normalized` endpoint fails silently
+2. Daemon endpoint exists but doesn't handle unstuck events
+3. Session ID mismatch between detector's event and daemon's queue entry
+
+### Secondary Issue: Tmux Socket Isolation
+
+The detector does not properly connect to isolated tmux servers:
+- Uses `tmux list-panes -a` without specifying socket
+- Needs `-L <socket-name>` or `TMUX=/tmp/...` env var
+
+## Conclusions
+
+1. **Detection accuracy**: Excellent (100% - no false positives)
+2. **Unstuck accuracy**: Poor (4% success rate)
+3. **Isolation handling**: Broken - detector cannot work with isolated tmux servers
+4. **Overall reliability**: 4% (1/25 successful end-to-end tests)
+
+## Recommendations
+
+1. **Fix unstuck event emission**: Debug why unstuck events don't remove queue entries
+2. **Add tmux socket parameter**: Detector should accept socket path for isolated servers
+3. **Add daemon response validation**: Verify HTTP requests succeed
+4. **Add test for true negatives**: Verify detector ignores active, non-stuck sessions
+5. **Increase test timeout**: Unstuck detection may need more than 15s
+
+## Test Artifacts
+
+All test logs preserved in `test-results/`:
+- `run-*.log` - Individual iteration logs
+- `tmux-detector-*.log` - Timestamped test runs  
+- `tmux-detector-metrics-*.json` - Structured results
+- `tb-1me-results-*.csv` - Summary data