docs(wording): reframe alerts and report from verdict to inquiry (tiltak 2)

BRIEF-vurdering-v2.md tiltak 2: "design for the investigator, not the
validator". The hook alerts stated short conclusions a reader can only
accept or dismiss ("Rapid-fire: N consecutive fast interactions",
"possible stuck/spiral", "Consider a break").

Each alert in tool-tracker.mjs now follows the form the read-dominant
edit-ratio message introduced in 2c9e2de — observation, the counter-signal
that changes how to read it, then what to check:

- burst: names the interval and that edits were among the calls, and asks
  whether each change was verified before the next
- edit ratio: carries the read percentage and asks what the remaining
  calls are doing and whether the approach is converging
- soft warning: closes on framing instead of prescribing a break
- hard warning: asks the model to name its observations and ask what they
  reflect; the required stop action is unchanged

commands/interaction-report.md gains the same rule for Observations and
trend reporting, plus an explicit "investigator, not validator" tone rule
and a "report the difference, not a label for it" rule.

Wording only — thresholds, heuristics, data model and required actions
are untouched. README examples and threshold-basis cells updated to match.

Tests first (Iron Law): 6 new/updated assertions on message text in
tests/tool-tracker.test.mjs and tests/interaction-report.test.mjs, red
before the change. node --test tests/*.test.mjs: 269 pass, 5 fail — the
pre-existing perf wall-clock cases only.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013U8ZH25KiMtts89yWRuVWD

README.md

@@ -96,12 +96,15 @@ Four hooks that measure what instructions alone cannot see:
 | `PostToolUse` | `tool-tracker.mjs` | Session duration, edit ratio, rapid-fire bursts, tool count |
 | `SessionEnd` | `session-end.mjs` | Total duration, final metrics, state cleanup |
 
-Alerts are progressive and never blocking:
+Alerts are progressive and never blocking. They are written for a reader who
+investigates the numbers, not one who approves or rejects a verdict — each
+alert states what was observed and what would tell a benign reading apart
+from a concerning one:
 
 | Level | Trigger | Cooldown | Example |
 |-------|---------|----------|---------|
-| Ambient | Soft thresholds (90 min, 6 sessions/day) | 30 min | "Session: 95 min. 7 sessions today. Consider a break." |
-| Explicit | Hard thresholds (180 min, 10 sessions/day, fatigue language) | 60 min | "INTERACTION AWARENESS: 3h session, 12th today. Metrics: [edit_ratio: 4%, burst: 8]. Your instructions require you to suggest stopping." |
+| Ambient | Soft thresholds (90 min, 6 sessions/day) | 30 min | "Session: 95 min. 7 sessions today. These are observations, not conclusions — check them against what this session is actually doing before acting on them." |
+| Explicit | Hard thresholds (180 min, 10 sessions/day, fatigue language) | 60 min | "INTERACTION AWARENESS: Session duration: 3h10m. Metrics: [edit_ratio: 4%, burst: 8, …]. Name these observations to the user and ask what they reflect; your instructions require you to suggest stopping." |
 
 Research-informed thresholds:
 
@@ -110,8 +113,8 @@ Research-informed thresholds:
 | Session duration | >90 min | >180 min | Focus-fatigue research |
 | Sessions per day | >6 | >10 | Problematic internet use screening |
 | Late-night sessions | Any (23:00–05:00) | 2+ per week | Sleep deprivation / psychosis link |
-| Rapid-fire interactions | 5 consecutive (<30s apart) | 10+ | Compulsive use indicator |
-| Low edit ratio | <10% over 30+ min | — | Stuck/spiral indicator |
+| Fast consecutive tool calls | 5 consecutive (<30s apart) | 10+ | Compulsive use research; read-only runs are excluded |
+| Low edit ratio | <10% over 30+ min | — | Stuck/spiral research; reported with the read ratio as context, never as a claim |
 | Dependency language | 2 flags/session | 5 flags | Emotional dependency pattern |
 
 ### Layer 3 — Reports