Hard-cut review profiles to the current engine contract

[forhappy]

What changed

• remove all Compass release-number parsing, ordering, floors, and allowlists from review/history profile reconstruction
• treat persisted compass_version as provenance only, then replace all engine-owned fields with the running engine contract
• validate the complete reconstructed user-option shape and hard-fail unsupported fields or malformed values
• reconcile comparisons when one, both-different, or both-matching preferred realizations use noncurrent engine identities
• require exact requested profiles only for review reconciliation and explicit history builds; query and export continue reading the selected immutable historical realization
• preserve explicitly requested fingerprints as exact immutable selections

Root cause

Review used Compass release numbers as a proxy for profile compatibility. It also bypassed current-engine reconstruction when both revisions already had preferred realizations, especially when their profiles matched. A globally applied preferred-profile check then risked making read-only historical query and export rebuild selected history under mutable repository configuration.

Contract policy

Normal review does not parse, order, or allowlist a persisted Compass release string. It reconstructs the profile under the current engine and validates the actual supported option contract. If that profile shape changes in the future, Compass should hard-cut to the new contract and reject unsupported shapes rather than add release-specific migrations.

Compass version remains in the extraction fingerprint as engine provenance. Exact fingerprint comparisons and queued materialization profiles retain strict identity checks; these are integrity checks, not release compatibility policy. Binary self-update semver selection is unrelated and remains intact.

User impact

Compass review rebuilds a current comparable pair whenever persisted user options remain supported and identical, regardless of the persisted engine-version text. Historical realizations remain immutable and queryable. Different user options or unsupported shapes fail explicitly.

Verification

• cargo fmt --all -- --check
• cargo clippy -p compass-cli --all-targets --all-features --locked -- -D warnings
• cargo test -p compass-cli --test review_cli --locked (7 passed)
• cargo test -p compass-cli --test history_cli --locked (24 passed)
• unit regressions cover non-semver, numerically future-looking, and current engine identities plus unsupported shape rejection
• cargo test -p compass-cli --test compass_product --locked (8 passed)
• sh scripts/check_product_boundary.sh
• cargo clippy --workspace --lib --bins --locked -- -D warnings
• cargo test --workspace --lib --bins --locked