Skip to content

Preserve post-runtime blueprint steps across cache hits - #1819

Merged
chubes4 merged 1 commit into
mainfrom
fix/1812-post-runtime-cache-v2
Jul 16, 2026
Merged

Preserve post-runtime blueprint steps across cache hits#1819
chubes4 merged 1 commit into
mainfrom
fix/1812-post-runtime-cache-v2

Conversation

@chubes4

@chubes4 chubes4 commented Jul 16, 2026

Copy link
Copy Markdown
Collaborator

Summary

Preserve caller-specific post-runtime blueprint steps while retaining reusable prepared-runtime cache state.

What changed

  • Cache only shared runtime steps, append each caller's post-runtime tail after cache selection, and persist a session-specific hydratable blueprint ref.

How to test

  1. Run 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..
  2. Run 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

  • AI assistance: Yes
  • Tool(s): Homeboy and OpenCode
  • Model: openai/gpt-5.6-terra
  • Used for: Diagnosed the prepared-runtime cache interaction, drafted the implementation and regression coverage, and orchestrated verification; Chris reviews and owns the change.

Source relationships

@chubes4
chubes4 merged commit e52ea2f into main Jul 16, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Preserve post-runtime blueprint steps across prepared runtime cache hits

1 participant