0%

Shadow Parity and Reversible Cutover

Goal

  • Prove the installed platform preserves effective behavior before any consumer or legacy path switches.

Files

  • CREATE scripts/harness_dist/shadow.py
  • CREATE scripts/harness_dist/tests/test_shadow_parity.py
  • CREATE scripts/harness_dist/tests/test_reversible_cutover.py
  • MODIFY plans/harness-dist-rollout/plan.json through plan_corpus writers

Work Items

  • Run legacy copy distribution and installed-platform projection against identical fixtures without letting shadow mode alter legacy output.
  • Compare logical artifact inventory, tailored content, effective provider instructions/skills, project-state preservation, migration plan, and consumer test/lint receipts.
  • Emit a machine-readable parity report that requires complete scenario coverage and zero unresolved divergence before cutover.
  • Select the new path only for newly activated projects, preserve existing activations, and prove python -m scripts.harness_dist ai-os cutover --rollback --project <root> restores the legacy activation with a rollback receipt and unchanged project-owned state.

Verification

  • Write failing positive, negative, interruption, concurrency, and idempotency cases before implementation.
  • Pin the consumer-visible outcome through the real CLI/runtime entry point.
  • Run focused pytest and the owning runtime self-test with a 150-second test timeout.
  • Run python -m scripts.harness_dist verify --root . when distributed artifact classification changes.