Skip to content
Source
Sign inSign up
TanStack/db

fix(db): preserve deferred demand and prepare SSR snapshots #2229

MergedKyleAMathews(GitHub profile, opens in a new tab)merged 31 commits intomain fromrefs/pull/2229/headmerged by KyleAMathews(GitHub profile, opens in a new tab)

Showing 73 changed files with 58 additions and 13 deletions (loading 70).

x
0 of 73 viewed, 73 left
24 additions and 10 deletions.agents/skills/oracle-authoring/SKILL.mdModified
View file
@@ -19,21 +19,35 @@
Work in this order when a production change is part of the task:
​
1. State the law and its authority.
-2. Extend the history grammar, driver, or observation until generated
+2. Inventory the materially affected public receiving paths and their promised
+ observation cuts. Include required real-host receiving witnesses in this
+ pre-edit gate; a controlled core witness does not supply their evidence.
+3. Extend the history grammar, driver, or observation until generated
histories reach the state where the law matters. Declare that state with
- `createOracleReach` (ORC-015).
-3. Run the extended oracle on the unchanged production code and record the RED
- failure.
-4. Change production, with the oracle running after each attempt.
-5. Record the GREEN result and a hostile mutant that fails.
+ `createOracleReach` (ORC-015) for each required receiving path.
+4. Run those comparisons on unchanged production. Record the defect's RED
+ result and the neighboring guarantees' results. A setup failure or missing
+ required witness blocks production edits; repair the test path first.
+5. Change production, with the oracle running after each attempt.
+6. Record the GREEN result and a hostile mutant that fails.
​
-Do not change production before step 3. If a model rule disagrees with
+Do not change production before step 4. Retrospective runs or a documented
+process gap do not satisfy this gate. If a model rule disagrees with
production, find its authority before you edit either one. A rule that you