Summary

PR #561 adds the expected_outputs protocol to the bash tool and now covers:

• binary happy path
• failed-but-wrote
• unchanged suppression
• no-declaration backward compatibility
• indeterminate before state not producing false positives

Two lower-priority coverage gaps were intentionally deferred to keep the fixup small:

1. text file output recorded through text hash and BOM path
2. relative-path resolution through resolveExecutionPath / workdir

Why

These are non-blocking for the current correctness fix, but they should be locked by tests so the protocol remains stable for the common text-file case and for workdir-relative declarations.

Suggested checks

• Add a text-file expected_outputs test that verifies turn-change records a normal text file through textHash() and preserves the expected display shape.
• Add a relative-path expected_outputs test that uses workdir and confirms the runtime resolves and records the target path correctly.