test(core): add getResponseMeta-paths integration test (non-GC angle)

[ntucker]

Stacks on #3925.

Adds packages/core/src/controller/__tests__/getResponseMeta-paths.ts alongside the existing getResponseMeta-countRef.ts to cover the journey-mutation bug from a second, non-GC angle.

The two tests are complementary:

Test	Consumer of paths	Failure mode it locks in	Fires under ImmortalGCPolicy?
getResponseMeta-countRef.ts (existing)	GCPolicy.createCountRef({key, paths}) → entityCount	Under-counted entity reaped while still referenced	No (GCPolicy-only)
getResponseMeta-paths.ts (new)	entityExpiresAt(paths, state.entitiesMeta) → expiresAt → hooks' refetch gate	2nd+ subscriber observes a too-late expiresAt and never triggers entity-expiry refetch	Yes

The new test asserts a property a normal hook user can observe — every subscriber to the same endpoint must receive the same expiresAt from Controller.getResponseMeta() — without poking implementation-detail state like gcPolicy['entityCount']:

const FOO_1_EXPIRY = 100;
const FOO_2_EXPIRY = 1_000_000;
// state has Foo|'1' and Foo|'2' with above expiries
const m1 = controller.getResponseMeta(ep, state);  // miss
const m2 = controller.getResponseMeta(ep, state);  // hit
const m3 = controller.getResponseMeta(ep, state);  // hit

expect(m1.expiresAt).toBe(FOO_1_EXPIRY);          // earliest
expect(m2.expiresAt).toBe(m1.expiresAt);          // same
expect(m3.expiresAt).toBe(m1.expiresAt);          // same

The state shape (endpoints slot populated, no top-level meta.expiresAt) corresponds to real-world cases where entityExpiresAt(paths, …) is the only thing computing the endpoint's effective expiresAt: SSR hydration, controller.set(Entity, …), or useQuery. The resulting expiresAt flows directly into useSuspense / useCache / useFetch / useDLE / useLive's refetch gate if (Date.now() <= expiresAt && !forceFetch) return;, so a too-late value silently suppresses refetch on the 2nd+ subscriber.

Verification

• On the fix: both tests pass.
• Reintroduce the buggy paths.shift() (and remove the journey-at-write change): m3.expiresAt returns 1_000_000 (FOO_2_EXPIRY) instead of 100 (FOO_1_EXPIRY) — the new test fails at line 81; the existing countRef test also fails as it did pre-fix.
• yarn jest --selectProjects ReactDOM --testPathPatterns "packages/(normalizr|core|endpoint)" — passes.

No production code changes.

  

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs-site	Ignored	Preview	Apr 28, 2026 0:57am

[changeset-bot]

⚠️ No Changeset found

Latest commit: 92d57e0

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.21%. Comparing base (059b0e3) to head (92d57e0).
⚠️ Report is 1 commits behind head on fix/journey-mutation-on-result-cache-hit-scalar.

Additional details and impacted files

@@                               Coverage Diff                                @@
##           fix/journey-mutation-on-result-cache-hit-scalar    #3929   +/-   ##
================================================================================
  Coverage                                            98.21%   98.21%           
================================================================================
  Files                                                  154      154           
  Lines                                                 3018     3018           
  Branches                                               604      604           
================================================================================
  Hits                                                  2964     2964           
  Misses                                                  11       11           
  Partials                                                43       43           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.