Block a user
series has no per-step timeout, so one hung model call stalls the whole run indefinitely
Correction to this issue's Environment note
The note says the host "did not reboot (/proc/uptime 121651s afterwards) — it lost only its ZeroTier path, filed separately". That is wrong.…
series --list claims to enumerate every extraction but covers 1 of 16 hooks-to-go checks
Correction to this issue's own list
I claimed nine of the sixteen "run with no caller-specific arguments" and named run-parity-check and run-witness-check among them. **Two of those three…
check-wiring covers only the analytics plugins, not the busiest hook producers
Correction to my own report above — landed
Correction to my own report above — landed 9b3b534
kotkan/claude-plugin-hook-instrument#95 is fixed (v0.31.0, 8a517c4, verified an ancestor of origin/main), and establishing its real…
check-wiring covers only the analytics plugins, not the busiest hook producers
Fixed and landed —
Fixed and landed — f223181 + 3dc175b
main at 3dc175b, verified on origin/main.
Verified live, not from the collected run
out/** is unregenerable and was read-only to me, so…
check-wiring covers only the analytics plugins, not the busiest hook producers
check-wiring covers only the analytics plugins, not the busiest hook producers
Plan (posted before first edit — unattended session, no interactive plan gate)
Re-derived on emmett, 2026-09-08
ls -d ~/projects/claude-plugins/*/hooks/hooks.json → **16 plugins…
check-wiring covers only the analytics plugins, not the busiest hook producers
collect_ia still scans only profiles[0]; offload-scan --root is repeatable now
playbook omits the drill-down tools its own conclusions need
route group samples 5 transcripts, reported as fleet telemetry