Release 2.1.201 (2026-08-23)

Testing

• stub relay push in report-ready e2e tests (#2879) The report-ready e2e tests ran in a temp repo with no origin, so report-ready's real relay-ref push (git push --force origin, github_transport.write) failed with 'could not read from remote' — which retry.is_retryable() treats as transient. git.run then burned the full 4-step backoff (~30s of real time.sleep) before report-ready swallowed the non-fatal failure. The 11 report-ready tests that reach the push cost ~386s, ~96% of the whole suite's wall-clock and nearly all of the ~7min vrg-validate test stage.

Add an autouse fixture stubbing vrg_pr_workflow.GitHubTransport for the module, so the relay push is a no-op. The two tests that assert on the transport re-patch it locally and keep exercising the real contract, which is also covered by test_github_transport.py. Production behaviour is unchanged; this is test hygiene only.

The file now runs in ~1s (was ~386s) and the full vrg-validate drops from ~7:10 to ~0:29.

CI Evidence: All gates passed — full audit bundle available. Download →