# Admatic Visual Reference Recovery Stack 5.14.2

## Coordinated versions
- Admatic Core 2.14.3
- Kit Factory 2.13.1
- Site Installer 5.13.1
- Remote Worker 1.6.2
- Admatic Theme 1.14.2
- Canonical Project State: `admatic.project-state.v3`
- Staging Contract: `admatic-staging-3` with Core compatibility baseline `2.14.1`

## Fixed: false Core/staging contract mismatch
The 5.14.1 bundle accidentally shipped the Core 2.14.2 MCP-tools patch with `core: 2.14.2` in its stack-contract file, while every staging component correctly retained the coordinated `core: 2.14.1` compatibility baseline. Core compared the two decoded JSON objects with strict PHP array equality, so the paired staging site was marked inactive even though the staging preflight passed all 17 checks.

Core 2.14.3 fixes the issue in two layers:
- The Core package contract is restored to the coordinated 2.14.1 staging compatibility baseline, so existing staging installations remain package-compatible.
- Core now compares contracts semantically, ignores JSON key order, and allows Core patch releases within the same major/minor line while still rejecting changes to Kit Factory, Site Installer, Remote Worker, Theme, Elementor minimums, package schema, prompt contract, project standard, or other contract fields.

No staging reinstall or re-pairing is required for a staging site already showing the 5.14.1 versions. Replace Core centrally, then run **Run all health checks** once.

## Visual-reference recovery retained
- Persisted reference screenshots remain bundled as `design-reference` QA evidence and imported into staging Media Library.
- Missing Reference Geometry V2 may be recovered only from persisted design-reference evidence.
- Region-weighted desktop/tablet/mobile comparison, three correction passes, and same-project rerendering remain mandatory.
- Genuine header, hero, section, typography, imagery, or footer failures still block release.

## Installation
1. On `dev-admatic.dk`, replace Admatic Core with `admatic-core-2.14.3.zip`.
2. Do not reinstall the staging stack when it already reports Site Installer 5.13.1, Kit Factory 2.13.1, Remote Worker 1.6.2, and Theme 1.14.2.
3. In Core, click **Run all health checks**. The existing paired staging target should become active and ready.
4. Continue the existing project. Do not create a replacement project or replace its persisted media.
