Repository navigation
Define map ownership and pinned consumer hash checks - #41
Merged
Merged
Conversation
* Implement pinned map consumer updates and integrity checks * Run consumer action from its pinned implementation directory
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Map refinements are still being authored in Arduino AutoStory branches after the map import. Define the ownership and update process so PokemonSimulation owns map corrections and Arduino consumes a pinned, verified export.
The design retains vendored JSON for offline builds, pins a PokemonSimulation commit and manifest SHA-256, and specifies a required consumer check against that exact remote manifest and complete map inventory. Corrections land here first; consumer PRs update the lock/export and dependent route logic. It also covers source-input provenance, retired builders, native reader tests and the remaining rollout steps.
The inspected map edits in dayfine/Arduino-Source#226 are examples only. No map fixes are imported, no Arduino files are modified, and neither the integrity gate nor milestone 1 is claimed complete. This is documentation only; the plan links the process and leaves implementation/adoption pending.
Validation: reviewed the five map diffs and builder-table change at #226 head
e572a3036fb270f4cc0fbd6b66442872b0c0bd1a;git diff --checkpasses. No runtime code changed.