# Issue 8640 baseline runtime

Runtime: ed9b7ca9c53843ea1e6b466bf7d52928d10e7db0, Linux local web dev server. Provider fixture from 97e3dfff0a440adf89f63d6ae94affecde48c30e, unchanged semantics from 18b44f70eb. Isolated worktree home; no public PR mutation.

Chrome 154.0.0.0 headless, desktop user agent, no device emulation, DPR 2, 1440x900 CSS viewport, light theme, default font scaling. Fixture timestamps fixed; real application clock and production refresh intervals unchanged.

- 03:01:52 UTC: provider returned original title; panel rendered original title and 1 of 2 running checks.
- 03:02:37.632: recording began with original title.
- 03:02:38: changed only fixture title and updatedAt to title stage. No Refresh or navigation during observation.
- 03:02:37: one locator failed due unsupported exact attribute; corrected text locator timed out. Checks remained collapsed during the recording. No successful UI action occurred during the passive observation window.
- 03:03:41.813 and .872: provider returned changed title in the same server process (PID 1957027).
- 03:03:56: read-only DOM observation still reported original heading.
- 03:04:14.280: endpoint screenshot still original; recording stopped. No browser disconnect or server restart during this recording.
- After recording, expanded Checks for a supplemental endpoint screenshot. This is not part of the passive timing proof.

Fixture limitations: raw merge.conflicts normalized to schema-accepted unknown identically on both revisions. Activity displays an unreadable fixture-response error and remains outside the proof. This is a deterministic provider-response fixture through the real server/RPC/client, not a production-host integration test. No CI-completion or unchanged-refresh recording claimed for baseline.