Note

    cutover-evidence-system

    Repo-canonical workflow for preflight reruns, normalized compare output, master-pack generation, a...

    Document Metadata

    • title: Cutover Evidence System
    • description: Repo-canonical workflow for preflight reruns, normalized compare output, master-pack generation, and post-cutover reuse.
    • status: evolving
    • lastUpdated: "2026-04-19 13:47 ET (America/New_York)"
    • owner: Engineering

    Cutover Evidence System Use the cutover evidence system to keep pre-cutover and post-cutover p

    Cutover Evidence System

    Use the cutover evidence system to keep pre-cutover and post-cutover proof in one repo-canonical structure.

    Goals

    • Normalize the current pre-cutover baseline into one trustworthy packet.
    • Re-run the automated cutover checks from repo-level commands instead of reconstructing the workflow from multiple docs.
    • Keep Maggie-owned manual evidence explicit without turning manual screenshots into the storage layer.
    • Reuse the same compare schema after cutover so Dawn, pre-cutover headless, and final-domain post-cutover results can live in one CSV.

    Commands

    • pnpm cutover:preflight
      • Runs the automated cutover stack, captures command output, and writes a timestamped run directory under docs/evidence/active/cutover-runs/<timestamp>/.
      • Output contract:
        • run-manifest.json
        • summary.md
        • summary.json
        • compare.csv
    • pnpm cutover:compare
      • Writes a normalized compare CSV into the current master-pack date directory.
      • Uses the latest cutover run automatically when one exists.
    • pnpm cutover:master-pack
      • Generates the canonical current baseline packet under docs/evidence/active/cutover-master/<date>/.
      • Output contract:
        • master-pack.md
        • master-pack.json
        • compare.csv

    Default Command Coverage

    The automated preflight includes:

    • pnpm build
    • pnpm test:unit
    • pnpm test:e2e
    • pnpm seo:audit
    • pnpm parity:audit
    • pnpm shopify:audit:analytics-baseline
    • pnpm shopify:audit:channel-readiness
    • pnpm agent:catalog:audit
    • pnpm growth:reports:cycle when likely Google credentials are present

    Important Flags

    • pnpm cutover:preflight -- --dry-run
      • Writes the run structure without executing commands.
    • pnpm cutover:preflight -- --base-url https://example.com
      • Targets a different URL for seo:audit, parity:audit, channel readiness, and Playwright base-url wiring.
    • pnpm cutover:preflight -- --state final_domain_post
      • Uses the same output contract for a post-cutover final-domain run.
    • pnpm cutover:preflight -- --skip-e2e
      • Skips Playwright when the runtime is not appropriate.
    • pnpm cutover:preflight -- --skip-growth
      • Skips the 1085 growth reporting cycle even if credentials appear available.

    Canonical Storage Model

    • Source of truth:
      • repo artifacts under docs/evidence/
    • Current timestamped automated runs:
      • docs/evidence/active/cutover-runs/<timestamp>/
    • Current canonical baseline packet:
      • docs/evidence/active/cutover-master/<date>/master-pack.md
    • Optional downstream spreadsheet view:
      • import compare.csv into Google Sheets if you want a live operator surface

    Do not use Sheets as the evidence store.

    Maggie-Owned Manual Gates

    The automation does not replace the true manual blocker tail. Maggie still owns:

    1. Review the programmatic GSC supplement and decide whether one Page Indexing export is still required.
    2. If required, capture the Page Indexing export.
    3. Capture Shopify Analytics 404s.
    4. Capture Shopify Analytics Web Performance.
    5. Confirm the 1045 CMS keep-vs-move split and empty defer bucket.
    6. Run collaborative walkthrough/sign-off for 1075, 1076, and 1077.
    7. Approve launch-window timing and go/no-go readiness.

    The system keeps these manual blockers visible in the generated master pack rather than burying them inside stale packet prose.

    Post-Cutover Reuse

    • Run pnpm cutover:preflight -- --state final_domain_post --base-url https://www.rockpaperscisso.rs once the final domain is live.
    • Regenerate pnpm cutover:master-pack.
    • Import the refreshed compare.csv into Google Sheets if you want side-by-side operator review.
    • Feed new deltas back into the existing 1077 remediation queue instead of creating a second comparison system.

    Provenance