DL-210

Forge integration testing adds two live-contract tiers above the DL-174 hermetic pyramid: (1) a hermetic golden-fixture replay leg (committed go/internal/forge/testdata/ fixtures replayed through the stub RoundTripper, an untagged Go test riding moon affected-detection on every forge-affected PR + the main/nightly sweep, no ci.yml project enumeration) and (2) a //go:build livegithub live-credentials oracle (same scenarios against a throwaway RigelBuild/compass-forge-testbed + a Linear test team under test-only bot PATs ≠ the server_only production secrets), REQUIRED on forge-affected PRs + nightly, covering GitHub and Linear co-equally (the GitHub-only F1 reviewer≠author 422→APPROVE headline; Linear’s PR/review family is ErrUnsupported, not a scenario). This is a NEW secret-bearing per-PR CI step — a standalone decision, NOT an amendment: D2’s full-stack deterministic tier (compass-dogfood-e2e/design.md:815-830) stays secret-free and unchanged; a forward pointer next to D2 records the carve-out. Fork-PR secret safety: the same-repo-head-guarded step goes vacuously green on fork heads (GitHub withholds secrets there); accepted, with the push-to-main run + a maintainer same-repo re-push convention as the catch (0 forks today)

Status: Active (Matt, 2026-08-18)

Record: ../../server/compass-forge-integration-testing/design.md#approach