Test and Release Hardening

[PhilipWoulfe]

Epic H: Test and Release Hardening

Summary

Strengthen automated validation and release controls so migration changes ship with confidence and controlled rollout safeguards.

Why This Epic

Migration touches critical data pathways. Robust contract tests, deterministic fixtures, and release guardrails are needed to reduce regressions and production risk.

Goals

• Expand automated tests for contracts, idempotency, and workflow behavior.
• Prove deterministic reconciliation outputs.
• Validate end-to-end admin governance flows.
• Formalize release readiness and canary strategy.

Non-Goals

• Replacing existing CI platform.
• Building unrelated test suites outside migration scope.

User Stories

Story H1: Add contract tests for generic questions API payloads

As an integrator, I want stable payload contracts so consumers are protected from breaking changes.

Story H2: Add migration golden-file tests for deterministic reconciliation

As a developer, I want golden tests so ordering and values remain stable across refactors.

Story H3: Add E2E admin flow for kickoff, review, approve, promote

As a QA engineer, I want full admin journey coverage so governance workflows are verified end to end.

Story H4: Add DB idempotency tests run twice with no duplicates or drift

As a platform maintainer, I want repeat-run DB assertions so migration writes remain safe.

Story H5: Add release checklist and canary process for migration features

As a release manager, I want a checklist and canary rollout path so production risk is reduced.

Definition of Done

• Contract, golden-file, E2E, and idempotency suites are in CI.
• Deterministic reconciliation behavior is validated across reruns.
• Release checklist and canary process are documented and used for migration changes.