@tech-leads-club/harness-toolkit 0.16.4 → 0.16.5
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/bin/tlc-exec.d.mts +18 -0
- package/bin/tlc-exec.mjs +94 -2
- package/dist/doctor.mjs +78 -78
- package/dist/lessons-cli.mjs +33 -33
- package/docs/diagnose.md +13 -0
- package/package.json +1 -1
package/docs/diagnose.md
CHANGED
|
@@ -55,6 +55,19 @@ tlc harness doctor
|
|
|
55
55
|
state, and only the floor keeps running, because a limit an agent can turn off is not a limit. A pause flag that
|
|
56
56
|
appears without the CLI is a policy change, not a pause, and is ignored.
|
|
57
57
|
|
|
58
|
+
## The host says a hook returned no output
|
|
59
|
+
|
|
60
|
+
Every hook invocation leaves two lines in `~/.tlc/harness/state/hook-trace.jsonl`: `start`, written by the launcher
|
|
61
|
+
before the handler runs, and `end`, with the duration, exit status, signal and the verdict it printed. Each line
|
|
62
|
+
carries the host's `tool_use_id`, `generation_id` and `conversation_id`, never the tool input, so a refusal the host
|
|
63
|
+
reports can be matched to the invocation that produced it:
|
|
64
|
+
|
|
65
|
+
- no `start` for that tool call: the host never ran the launcher, or it died before its first line;
|
|
66
|
+
- a `start` with no `end`: the process was killed mid-run, usually by the host's own timeout;
|
|
67
|
+
- an `end` with a verdict: the harness answered, and the host discarded it.
|
|
68
|
+
|
|
69
|
+
The file rotates to `hook-trace.jsonl.1` at 5 MB.
|
|
70
|
+
|
|
58
71
|
## Node vs Bun
|
|
59
72
|
|
|
60
73
|
- Preferred: **Bun** on PATH — every hook runs the TypeScript source directly, ~1 ms per invocation.
|