# Version Coherence Gate (PROC-NEW-1)

At QA start (Phase 2 step 2/3), run version/artifact coherence gate before deep test execution. Re-check before final `QA Complete`.

## Required checks

1. Identify planned target version from plan frontmatter/summary and read any `Release Lane Semantics` section. Distinguish product roadmap epic labels from package semver/tag lanes.
2. Verify same package semver/tag lane in modified release artifacts (example: `package.json`, `CHANGELOG.md`, release/deployment docs, roadmap entries if touched), unless the plan explicitly says no bump/tag or push-without-tag.
3. Record `Version Coherence Gate: PASS|FAIL` token in QA doc at QA start.
4. If environment installs deps during validation, verify installed version matches plan spec; record divergence.
5. Before final status, confirm no version artifact changed since start-gate pass; if changed, re-run gate.

## Interim fail-soft note (limited)

Before final QA gate, QA may record interim `FAIL-SOFT NOTE` only if both true:
1. mismatch belongs to intentionally deferred artifact slice
2. defer owner is assigned in artifact with closure condition

Interim note does not clear gate.

## Fail condition (final gate hard-fail)

If any version mismatch unresolved at final QA decision, do not set `QA Complete`. Mark `QA Failed` with mismatch list and handoff.