Land shared renderer and session preservation on master - #46
Merged
Merged
Conversation
happykhan
force-pushed
the
codex/land-renderer-scene-on-master
branch
from
September 5, 2026 08:32
b74ce2a to
abad2e2
Compare
Deploying brigx with
|
| Latest commit: |
9530ccc
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://5bcbfd24.brigx.pages.dev |
| Branch Preview URL: | https://codex-land-renderer-scene-on.brigx.pages.dev |
happykhan
marked this pull request as ready for review
September 5, 2026 08:35
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.
Summary
Why this PR exists
#43 was merged into the #42 feature branch, and #44 was merged into the #43 feature branch. GitHub therefore marked both PRs merged, but neither merge reached master. This catch-up branch has been rebuilt cleanly from current master to avoid the conflicts caused by the earlier stacked/squash history.
Merge order
Prefer merging #45 first, then #46. Once #45 is on master, GitHub will remove the already-landed nanoid lock change from this PR's effective diff. However, #46 is also self-contained and verified if merged first.
Verification