fix: the trial's mechanical faults -- approval label, import path, stats, annotate path, red kind

voyage-lekerepo end-to-end trial (2026-10-06), report points 8, 10, 12, 15, 16:

- approval-log: «Approve (Recommended)» / «Godkjenn (anbefalt)» is the
  approval it labels; the suffix never turns a hollow answer into a yes.
- trekexecute Phase 8: the state-file block imports atomic-write through
  ${CLAUDE_PLUGIN_ROOT}; a relative import only ran with cwd = plugin root
  (the test runs the block from another directory).
- trekreview, trekresearch, trekcontinue: stats go through stats-append like
  the other commands, and a failed write is reported, never skipped
  silently (closes the open STATE finding for all three). The schema
  fixture's stale line refs for these and trekplan are re-measured.
- annotate prints an absolute path, so file://{$ANNOT_HTML} is a live link.
- red-proof: `red_kind` = load-error | test-failure on a proven red.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

commands/trekresearch.md

@@ -774,11 +774,13 @@ You can:
 
 ### Stats tracking
 
-Write a session record to `${CLAUDE_PLUGIN_DATA}/trekresearch-stats.jsonl`
-(create the file if it does not exist).
+Append one record to `trekresearch-stats.jsonl` in the plugin data directory.
+Run it exactly like this. The record goes on stdin, and the writer resolves
+the directory: `CLAUDE_PLUGIN_DATA`, which the Bash tool env does not carry,
+else the directory `scripts/yardstick.mjs` reads.
 
-Record format (one JSON line):
-```json
+```bash
+node ${CLAUDE_PLUGIN_ROOT}/lib/stats/stats-append.mjs trekresearch <<'JSON'
 {
   "ts": "{ISO-8601 timestamp}",
   "question": "{research question (first 100 chars)}",
@@ -802,6 +804,7 @@ Record format (one JSON line):
   "contradictions": {N},
   "open_questions": {N}
 }
+JSON
 ```
 
 **The six measurement fields (v5.10).** `effort` is the grouping key — the
@@ -819,7 +822,9 @@ that could are prose the exporter allowlist denies. On a standard run the loop
 never arms, so `dimensions_baseline == dimensions`, both turn counters are `0`,
 and `dimensions_baseline_preserved` is `true` (nothing touched the list).
 
-If `${CLAUDE_PLUGIN_DATA}` is not set or not writable, skip tracking silently.
+The writer prints `{"written": true, ...}`. On `"written": false` (exit 1),
+print its `reason` in one line and continue. A tracking failure never blocks
+the main workflow, but it is reported, not skipped silently.
 
 ## Profile (v4.1)