Preserve post-runtime blueprint steps across cache hits - #1819
Merged
Conversation
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
Preserve caller-specific post-runtime blueprint steps while retaining reusable prepared-runtime cache state.
What changed
How to test
npm run test:php-browser-preview-only-session; expect The PHP smoke passes and proves miss/hit hydration preserves each caller import without cross-session leakage..TMPDIR=/tmp npm run smoke -- --group package; expect The package build smoke passes..Compatibility
No public schema removal. Existing sessions without post_runtime_blueprint keep their current prepared-runtime refs; caller-specific sessions now hydrate the complete executable blueprint.
Evidence
AI assistance
Source relationships