# Preserved failures and corrections

1. Initial JC-001 Node parent harness could not launch its child: EPERM, no exit code. Its actual result was “Execution result unavailable; claim unverified.” Raw record: jc-001-blocked.json; original runner: jc-001-runner.mjs. This is not a successful conflict test. A progress message initially misstated it as success and was explicitly corrected after inspecting the record.
2. Initial build failed with EISDIR while trying to package the runs directory as a file. Tests executed afterward against the previous dist build and cannot validate the new pages. The fix uses an explicit public evidence-file allowlist. The initial test output remains in the task work folder.

3. Expanding navigation coverage to Operator Access exposed an overly exact older test: it rejected the valid aria-current="page" attribute on that destination. The assertion now permits that location marker while still requiring the same operator link. The failed transcripts are retained under docs/current/runs/navigation-assertion-failure.tap and packaging-before-assertion-fix.tap in the source package.

Corrections do not erase these observations. Subsequent results are separate records.