Skip to content

fix: adopt stock Recoil 2026.07.04 engine profile - #22

Merged
EHotwagner merged 1 commit into
mainfrom
routine/bar-stock-recoil-20260704-consumer-side-20261002
Oct 2, 2026
Merged

EHotwagner merged 1 commit into
mainfrom
routine/bar-stock-recoil-20260704-consumer-side-20261002

Conversation

@EHotwagner

Copy link
Copy Markdown

Summary

Adopt the producer's selected stock Recoil 2026.07.04 identity from HighBar #15.

  • Keep the consumer contract byte-identical to the producer and require 2026.07.04 in native catalogue readiness and stock trace normalization.
  • Update current-profile trace fixtures and their engine-bound revision. Preserve and explicitly reproduce the old hash-algorithm golden while refusing its old profile at new admission.
  • Record the selected update, exact archive/source/headless hashes and remaining native qualification in BARC-01.5f.

Merge follows producer source delivery. Wire revision and queue policies are unchanged; historical attempts are preserved. Installed old packets are not new-engine evidence.

Verification

  • Official archive digest and extracted binary --version: verified.
  • Matching current-engine HighBar plugin compiled and installed in the separate version directory; four native test targets and Lua observer/float-ABI checks passed in the producer work.
  • Producer/consumer contract and retained vector byte identity: passed.
  • Stock contract vectors: passed.
  • Stock trace normalization: 11/11 checks passed, including old-profile refusal and historical golden reproduction.
  • Broker.NativeProof.fsproj Release build: passed, zero warnings/errors.
  • git diff --check: passed.

No game startup, Count1 or useful-play acceptance is claimed. Existing complete-record policy/source qualification is unchanged. This change does not reopen completed V2 acceptance.

@EHotwagner
EHotwagner merged commit 6bbe4fd into main Oct 2, 2026
@EHotwagner
EHotwagner deleted the routine/bar-stock-recoil-20260704-consumer-side-20261002 branch October 9, 2026 16:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant