-
v6.1.1 Stable
released this
2026-10-05 16:43:28 +00:00 | 215 commits to main since this releaseA patch release.
/trekexecuteno longer loses its telemetry when the harness
does not exportCLAUDE_PLUGIN_DATA, its progress-file prose now matches its
own validator, and no agent is pinned below reasoning efforthigh.Fixed
lib/stats/event-emit.mjsfalls back to the same data directory as
stats-appendand the yardstick whenCLAUDE_PLUGIN_DATAis unset, instead
of skipping silently. Everywritten: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-declinedandgates_mode_flag_override
are known events./trekexecutePhase 8, Phase 9 and thegates_mode_flag_overriderecord 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
/trekexecuteuse the
validator's vocabulary (in_progress,completed,plan_version).
progress-validatornow accepts the run statusstoppedand the step
statusblocked, both of which the command writes. A legacypassedstep
is still treated ascompletedon resume. architecture-mapper,dependency-tracer,git-historianandtask-finder
pineffort: high(wasmedium). No agent is pinned belowhigh; the rest
follow the session.
Downloads
-
Source code (ZIP)
0 downloads
-
Source code (TAR.GZ)
3 downloads