[Bug] Prepare immutable Hatch dependencies against the sealed analyzer contract #522

The independent signed capsule review for PR #519 prepares BASE and HEAD separately through the released native Hatch controller. Current-head run 39393045704, job 118529015017, reports contracts pinned-version incompatibility on both sides against the sealed Z3 reference. The separate targeted-pytest failure remains unclassified and is not attributed to this dependency mismatch.

The original BASE 593656f675eaf4954b609aca51aa6504367dc02e and HEAD 7f12738157171831606d26203c0ebea80ca8b9a8 both have a satisfiable native Hatch/default dependency graph. A bounded Linux CPython 3.12 experiment prepares both unchanged trees with the authenticated Z3 5.1.0.0 constraint, real package consistency, solver and CrossHair checks. Authentic published SDK graph evaluation finds no conflicts. This is prospective feasibility, not current controller, descriptor, hosted review or protected authority acceptance.

The released Linux builder clears ambient environment and has no supported internal Hatch transport for the existing analyzer equality policy. A HEAD declaration alone cannot fix independently prepared BASE.

The bounded correction belongs to the code-review module. Derive the existing equality set from authenticated selected analyzer metadata and carry it internally to native Hatch creation. Preserve both original declarations, native manager selection, project installation and every post-build compatibility, inventory, review, privacy, signature and authority gate. Preserve existing named/matrix, alternate-config and ABI behavior outside the newly evidenced alignment path. Never retry a failed aligned build without its policy.

Acceptance requires spec, genuine failing-first tests, exact native transport and positive/negative proof, unchanged-path regression checks, cache and directly supplied descriptor substitution checks, and normal module verification/signing. Missing, filtered or substituted policy must not be claimed as aligned preparation. No general dependency profile, core protocol, forced reinstall, backend switch, analyzer-policy relaxation or warning waiver is included.

Delivery requires a coherent new signed module version, archive/checksum/sidecar/registry publication, canonical main promotion and legitimate independent adoption. Feature signing or copied source is not released-controller authority. No automatic merge is permitted.

Parent Feature #163, Epic #162. Baseline #473 is closed. This blocks hosted completion of #518. Implementation has no open code prerequisite; signed publication and independent adoption remain explicit delivery dependencies. Owner authorized useful guideline-compliant corrections in both repositories without waiting. Planning PRs #517 and core #770 remain untouched.