Round 6. One High, and it is round 5's own fix: bounding the payload scan to
256KB to make it fast reintroduced the truncating read that round 5 had just
removed. A payload whose filler pushes session_id past the cap returns nothing,
the record files under `unknown-session`, and that fire reads as NEVER HAVING
HAPPENED. My nested-field test could not see it — its identities sit before only
1000 bytes of filler.
The cap is now a fast path with an unbounded fallback, so it is an optimisation
rather than a correctness dependency. Verified with identity 400KB deep.
Also this round:
- The field helper was defined inside a function and so was globally scoped under
a short generic name, able to collide with a hook's own function. Namespaced
and unset after use.
- WITHDRAWN: the generalised redirect-order guard. Four iterations, each fixing a
false positive or negative the last introduced, and review then constructed
more of both. Deleted rather than patched a fifth time, per the withdrawal
precedent in docs/guard-inventory.md — a weak detector is itself the
symptom-keyed mistake. The narrower exec-only guard is retained: a sound match
on a fixed keyword, covering every case that has actually occurred.
- The signal A/B compared only status and timing and DISCARDED stdout/stderr. It
now compares both, which surfaced a real difference: on a group kill with a
live child, bash prints a job-control notice the control does not. Isolated to
"the exit handler does work, so the shell lives ~50ms longer" — inherent to the
sink's purpose. Exempted narrowly, by the signal word only, and documented as a
measured limit rather than papered over.
Refs: #776
Decisions-Edit: yes
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>