feat(raijin): apply assembly dispositions - #897
Merged
TorinAsakura merged 3 commits intoAug 17, 2026
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 17537f592b
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
TorinAsakura
force-pushed
the
feat/raijin-assembly
branch
from
August 17, 2026 23:24
17537f5 to
895c2bc
Compare
TorinAsakura
merged commit Aug 17, 2026
5a462d0
into
pre-v3/architecture-foundation
10 of 13 checks passed
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.
Task
How to verify
Main scenario
Context: A Raijin checkout uses the checked
.yarn/releases/yarn.mjsunder the repository PnP/ESM configuration.Action: Build the private assembly and invoke the checked runtime through the repository Yarn entrypoint.
Expected result: Yarn reports
4.14.1; all 38 accepted commands remain available from 44 bundled plugins.Context: The private assembly has no source-development or package-publish lifecycle.
Action: Run two clean
yarn cli:buildoperations.Expected result: Both builds materialize byte-identical runtime files and regenerate metadata from the checked artifact.
Retained patch proofs
dynamic-require.mjsdynamicRequireNoCachewithTypeError: Cannot read properties of undefined (reading 'indexOf').yarn raijin:generateexecuted by the checked PnP/ESM runtime during materialization.1, replacement0before patch; source0, replacement1after patch.module.children, and the unpatched canonical build plus metadata route passes.nbind.mjs--versionfails withReferenceError: _a is not definedin the legacy nbind payload.1, replacement0before patch; source0, replacement1after patch.yoga-layout-prebuiltto a released Ink version using the maintained Yoga mechanism, and the unpatched canonical runtime route passes.The former
.cjsto.mjspatch is removed; runtime filename/update ownership remains with #842.Proofs
yarn cli:build, twice:yarn raijin:smoke:cli: