Repository navigation
[M3] Restore bootstrap runtime and pin canonical recipe ownership - #12
Merged
Merged
Conversation
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.
The standalone M3 bootstrap initializes OpenRewrite without SLF4J on its runtime classpath, causing LoggerFactory linkage failures before recipe execution. Apply the existing GEF OpenRewrite recipe to the exact matching POM preimage; its observed SDK output adds the pinned SLF4J API runtime dependency. Compiler settings, existing tests and product source remain unchanged.
Canonical recipe source and proof: https://github.com/hsoliwal/com.synexia/pull/12270 at
8ffbde7414f33de549c1363f64c33d75bfed2564,synexia-openrewrite-recipes/recipe-crates/public-fork-recipe-custody-20261017/qualification/eclipse-bootstrap-runtime.Validation: Java 21, Maven 3.9.11, actual OpenRewrite SDK execution, exact pre/post hashes, fixed point and refusal/scope cases. The unchanged focused module suite passes 1 tests, with zero failures, errors or skips. The source-first packet retains failing baselines and complete logs. Broader product, native, graphics and GPU qualification is not claimed.
This is a reviewable draft; no default-branch mutation or merge is requested.
Canonical bootstrap ownership
The added
.m3/openrewrite-recipes/SYNEXIA_HANDOFF.tsvrecords both canonical bootstrap owners, exact source blobs, the immutable qualification revision and its two-source-file scope. Both public source files were re-read at this PR's prior head and still match the qualified source; the metadata target was absent.This file is the actual Result of
com.synexia.m3.PublicForkBootstrapCustodyEclipsePlatform20261018from Synexia #12268, published sourceba9bffb6fe95bb88ee5d3fcbef6445418d09734c. The 19-file canonical execution closure was read back exactly before Java 21/Maven 3.9.16 validate, lint/compile, both JUnit contract tests, and the named SDK run. The seven-fork batch produced seven metadata Results, zero fixed-point Results and seven identical serial replays; drift and duplicate inputs are refused. This fork's generated metadata SHA-256 is3b64ed5257487412ee0248ddd052dc9db92bececbdde37168b2cc7e047d71ac7.The original two bootstrap recipes were separately executed against their exact source files, with zero first-pass and fixed-point changes. The metadata explicitly records
EXACT_BOOTSTRAP_SOURCE_FILESandwhole_repository_qualification=NOT_ESTABLISHED. Canonical recipe ownership and target authoring-copy custody are recorded; broader product/runtime gates retain their existing scope. Receipts:docs/M3-SCALE/runs/20261017-public-fork-recipe-consolidation/bootstrap-custody-20261018in Synexia.