Repository navigation
Refresh agent skills after query lifecycle fixes - #17
Merged
Merged
Conversation
ConsoleTVs
marked this pull request as ready for review
October 24, 2026 12:44
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
Document request ownership, serialized mutations and recovery, superseded fetches, caller-owned opt-in broadcasting, preserved stale views, and fresh Suspense resource retain/release and migration. Correct nullish configuration, refetch, generator cleanup, and React 19.2 requirements. No runtime changes.
Evidence
After: Checked against merged runtime PRs Fix request ownership across overlapping fetches #12–Stabilize fresh React Suspense requests #16; 113 source tests passed across 15 files. Four tests extracted from the documented core/React/resource examples passed and type-checked with TypeScript.
npm run buildexited successfully and emitted bundles, but declaration generation reported the existing Solid/React JSXTS2786diagnostic atsrc/solid/components/QueryProvider.tsx:80. This docs-only change does not address it. Tests also emitted negative-timeout warnings.Merge Danger
Door: two-way
Documentation-only; can be reverted without changing runtime behavior or published APIs.
Blast Radius: guidance
Future agents consume these API and migration instructions. No ticket; parent session sequences readiness and merge.