David Alexandru IlieandGitHub a619237b1c Use a safe clock for Request Insights bookkeeping (#96274) ...

Draft replacement for #96267 after restructuring the Request Insights
stack.

## Summary

- Request Insights bookkeeping used `Date.now()`, which Cache Components
patches to detect unstable application wall-clock reads.
- Framework bookkeeping could therefore be incorrectly attributed to
user code.
- Implicit timestamps now use `performance.timeOrigin +
performance.now()`.
- Explicit OpenTelemetry timestamp inputs remain unchanged.
- Tests distinguish framework bookkeeping from a genuine application
`Date.now()` call.

## Verification

```bash
pnpm build-all
pnpm --filter=next types
pnpm --filter=next build
pnpm test-unit --runTestsByPath packages/next/src/server/lib/trace/local-span-recorder.test.ts packages/next/src/server/lib/trace/span-store.test.ts packages/next/src/server/lib/trace/request-insights.test.ts
pnpm test-dev-turbo test/development/app-dir/request-insights/request-insights.test.ts
pnpm test-dev-webpack test/development/app-dir/request-insights/request-insights.test.ts
```

<!-- NEXT_JS_LLM -->

2026-07-27 18:58:54 -04:00

..

app-date-now

Use a safe clock for Request Insights bookkeeping (#96274)

2026-07-27 18:58:54 -04:00

instant-insights

…

safe-clock

Use a safe clock for Request Insights bookkeeping (#96274)

2026-07-27 18:58:54 -04:00

layout.tsx

…

page.tsx

…