Skip to content

Include scenario bindings in resource cache identity - #495

Merged
lo1tuma merged 2 commits into
mainfrom
moonlit-griffin-glen
Sep 29, 2026
Merged

lo1tuma merged 2 commits into
mainfrom
moonlit-griffin-glen

Conversation

@lo1tuma

@lo1tuma lo1tuma commented Sep 29, 2026

Copy link
Copy Markdown
Member

Reusable lifecycle boundaries previously could not represent scenario-dependent resource identity. Cache identity now distinguishes startup state while preserving safe owner reuse.

  • Acquire-timed bindings and dependency handle identity partition resource owners.
  • Request-routed bindings derive per-use views through exposeHandle(...) without reacquiring the owner.
  • Resource contexts, simulated HTTP handles, and the scenario contract follow the timing split.

Closes #194.

Acquire-timed scenario bindings now partition reusable resource owners. Request-routed bindings instead derive per-use handle views while preserving one acquired owner, and dependent resource identities include those views.
@lo1tuma
lo1tuma merged commit 58322ae into main Sep 29, 2026
5 checks passed
@lo1tuma
lo1tuma deleted the moonlit-griffin-glen branch September 29, 2026 04:22
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.

Implementation milestones

1 participant