Repository navigation
Advance recipe source custody to com.synexia - #13
Merged
hsoliwal merged 1 commit intoOct 18, 2026
Merged
Conversation
Canonical source commit: 215546d1ca0e724eb2c8e2e8ef6b4adce724733a Preserve exact source seals, execution evidence and native qualification holds.
hsoliwal
marked this pull request as ready for review
October 18, 2026 13:11
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.
This fork's reusable recipe source closure has been imported into
hsoliwal/com.synexia. This change advances the existing source-home controls and recipe entrypoints to that exact canonical import. Public build and proof callers still use their recorded provider revisions, so their source mirrors are retained.Source-home updates
.m3/README.mdThe dated custody binding is
.m3/SYNEXIA_RECIPE_SOURCE_CUSTODY_20261018.json. The two exact sealed packet mirrors, preimages, payloads and actual Maven logs are under.m3/recipe-source-custody-20261018/. Reusable recipe ownership is canonical; product source, APIs, native builds, runtime acceptance and promotion remain owned by this target.Canonical source commit:
215546d1ca0e724eb2c8e2e8ef6b4adce724733a. The full source custody ledger is sealed by SHA-256ebcfbd42a49eec806f0a4572af731828deda41f22c17250d34d49af985d78f1d.Verification
Both binding and execution-receipt packets ran through the original canonical Maven/Replay engine. Each packet passed plan, apply and two zero-change checks; all declared postimages match their exact seals. The execution receipt was generated after the binding actually ran and was then installed by its separate packet. All eight invocation logs are mirrored, and the original source checkout remained clean.
The original five-packet/22-target fixed-point subset belongs to Maven, Gradle and Eclipse UI; it makes no execution claim for this fork.
The current recipe census has SHA-256
cfa9edb42a99cb2e54a988b28de7078a3233fdc667c5e4d8f979675e0f767ee0and records the broader source admission, application and qualification results.Qualification limits
The canonical OpenRewrite SDK attempt stopped before compilation because
maven-resources-plugin:3.3.1was unavailable in the approved offline cache; it executed zero tests. The binding-only packets do not run native product qualification. Public mirrors remain until build and proof callers can use a qualified canonical handoff. No runtime promotion or automatic merge is authorized by these receipts.