Document test execution expectations in project README

[ProtocolWarden]

Auto-generated by Operations Center execution.

Goal

Document test execution expectations in project README

Definition of done (complete ALL before finishing)

1. Complete the task in its ENTIRETY — every acceptance criterion and every
   file the task implies (implementation, tests, and docs as applicable). Do
   not leave TODOs, stubs, or 'follow-up' gaps; a partial change is rejected
   in review.
2. Add or update tests/checks that prove the work is correct.
3. Run the repository's test suite and linters/formatters and make them
   pass locally. If anything fails, fix it before finishing — do not hand
   off a red build.
4. Only consider the task done when the full change is in place AND verified
   green. The PR you open should be mergeable as-is.

[ProtocolWarden]

Resolved: new push — automated review resumed

Needs human attention (reason=ci_persistently_red). Left open — not merged (unresolved) and not closed (work preserved).

CI has not gone green after 20 checks (1 failing: audit: failure). Not merged (red CI) and not closed (work preserved) — needs a human to fix CI.

[ProtocolWarden]

Resolved: CI green on unchanged head — test suite validates implementation; automated review resumed

Needs human attention (reason=ci_never_settled). Left open — not merged (unresolved) and not closed (work preserved).

CI has not settled-green on the current head after 21 checks (6 still running: Type check (ty), Snapshot validation, audit, Test (pytest), Custodian doctor). Not merged (CI incomplete) and not closed (work preserved) — needs a human to investigate stuck CI.