Test mixed reconciliation states and preservation invariants #24

Goal

Test mixed states and preservation invariants: existing label uses, dependencies, canonical statuses, file overlap, scopes, and stronger protection.

Observations

• Mixed states (some modules applied, some adapted, some left) are the common real case.
• Existing label uses and dependencies must survive reconciliation.
• Stronger existing protection is preserved unless an exact, separately reviewed, explicitly approved weakening diff exists; the existing contract allows one review or admin bypass.

Decision gate

Approve the mixed-state fixture set and the weakening review path before implementing assertions.

Acceptance criteria

• Mixed-state fixtures reconcile to the expected per-module outcome.
• Existing label uses, dependencies, and canonical statuses are preserved.
• File overlap and scope conflicts are detected, not overwritten.
• Stronger protection is preserved; weakening requires the exact reviewed and approved diff.

Verification

• Mixed-state suite -> all fixtures pass with the expected final state.
• Preservation checks -> pre-existing objects remain unchanged; weakening without the approved diff is refused.

Release checkpoint

Remaining risk: fixtures approximate live state. No weakening fallback is allowed.

Tracking

Roadmap item: B04-03. All acceptance criteria remain pending; publication does not grant approval or release authority.

Dependencies

• Depends on Enforce headless decisions with a versioned migration contract #23 (B04-02).