Preserve useful evaluation context in rejected-update evidence

nimmo commented

2026-09-09 05:09:25 +01:00

Owner

Long Nix evaluation traces could exhaust the excerpt budget on outer module frames and omit the actual error. Reserve part of the existing line budget for final source locations and the rest for named evaluation contexts and errors, preserving the final diagnostic under the byte limit. Keep shared redaction and omit numbered source snippets.

Refs nimmo/nixos-config#205. Companion configuration change: 7bc9a85 on fix/remediation-evaluation-evidence enables --show-trace and tightens advisory reporting.

Validated with incident protocol regressions (long traces, generic-frame noise, redaction, missing/empty logs, byte limits), remediation integration/regression suites using the built package, ShellCheck, and combined nixos-config flake checks. Subsequent real-model replay with the companion text-file read fix correctly identified the pi-coding-agent rename failure; recorded in config issue #205. Replaying the exact #204 candidate showed why retaining a simple trace tail was insufficient: pi-coding-agent nativeBuildInputs context precedes many generic alias frames. The final selector retains that named context and the final rename error within existing limits.

No incident schema, fingerprint, automatic repair eligibility, publication authority, or deployment behavior changes. Deployment and new scheduled model evidence remain pending integration.

Long Nix evaluation traces could exhaust the excerpt budget on outer module frames and omit the actual error. Reserve part of the existing line budget for final source locations and the rest for named evaluation contexts and errors, preserving the final diagnostic under the byte limit. Keep shared redaction and omit numbered source snippets. Refs https://git.nimmog.uk/nimmo/nixos-config/issues/205. Companion configuration change: 7bc9a85 on fix/remediation-evaluation-evidence enables --show-trace and tightens advisory reporting. Validated with incident protocol regressions (long traces, generic-frame noise, redaction, missing/empty logs, byte limits), remediation integration/regression suites using the built package, ShellCheck, and combined nixos-config flake checks. Subsequent real-model replay with the companion text-file read fix correctly identified the pi-coding-agent rename failure; recorded in config issue #205. Replaying the exact #204 candidate showed why retaining a simple trace tail was insufficient: pi-coding-agent nativeBuildInputs context precedes many generic alias frames. The final selector retains that named context and the final rename error within existing limits. No incident schema, fingerprint, automatic repair eligibility, publication authority, or deployment behavior changes. Deployment and new scheduled model evidence remain pending integration.

nimmo added 1 commit

2026-09-09 05:09:27 +01:00