chore(release): 6.1.1 — /trekexecute writes what it promises

S117 fixes (8a56187..84a0621) plus the /trekreview remediation (cb68c4f).
/trekreview verdict WARN (0 BLOCKER, 3 MAJOR, 1 MINOR, 1 MAJOR suppressed
for length); every finding closed red -> green. Operator approved the
release 05.10 (decision 15).

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

CHANGELOG.md

@@ -4,6 +4,38 @@ All notable changes to this project will be documented in this file.
 
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 
+## v6.1.1 — 2026-10-05 — /trekexecute writes what it promises
+
+A patch release. `/trekexecute` no longer loses its telemetry when the harness
+does not export `CLAUDE_PLUGIN_DATA`, its progress-file prose now matches its
+own validator, and no agent is pinned below reasoning effort `high`.
+
+### Fixed
+
+- `lib/stats/event-emit.mjs` falls back to the same data directory as
+  `stats-append` and the yardstick when `CLAUDE_PLUGIN_DATA` is unset, instead
+  of skipping silently. Every `written:false` (failed write, usage error,
+  `payload-not-json`) exits 1 with a reason. The CLI also runs when it is
+  invoked through a symlink or a path with a space.
+- `main-merge-approved`, `main-merge-declined` and `gates_mode_flag_override`
+  are known events.
+- `/trekexecute` Phase 8, Phase 9 and the `gates_mode_flag_override` record all
+  write through a writer that resolves the directory. A failed write is printed
+  in one line and the run continues.
+- Phase 8 passes each event payload on stdin through a quoted heredoc
+  (`event-emit.mjs --payload -`), so the shell expands nothing in it. Before,
+  the plan path went into a single-quoted argument: a path with a quote
+  character broke the shell parse, and a quoted pair could run a command
+  substitution.
+- The progress-file schema and status rules in `/trekexecute` use the
+  validator's vocabulary (`in_progress`, `completed`, `plan_version`).
+  `progress-validator` now accepts the run status `stopped` and the step
+  status `blocked`, both of which the command writes. A legacy `passed` step
+  is still treated as `completed` on resume.
+- `architecture-mapper`, `dependency-tracer`, `git-historian` and `task-finder`
+  pin `effort: high` (was `medium`). No agent is pinned below `high`; the rest
+  follow the session.
+
 ## v6.1.0 — 2026-10-05 — The yardstick's use counter gets a source
 
 The use row in `scripts/yardstick.mjs` now counts an order as used only when