[harper-joseph]

Catches the console up to plugin v0.58.0 (pageCheck, #139). Console-only train, same shape as #129/#137.

What the plugin added

pageCheck compares the origin against what the cached page claims, closing the round-trip-blindness class the signature comparison structurally cannot see: a value that changes and changes back between two passes, with a render landing inside the window. It emits one new pass counter, probe_page_mismatch — and the catalog-driven coverage guard added in #137 caught it exactly as designed (its first real catch): the series shipped with nothing reading it, and test/adminAssets.test.js failed on this repo state before this change.

What the console now does

• Probe passes card — a Page mismatch tile and chart series. The overlay semantics are stated everywhere the number appears: a mismatched row is also inside Changed or the unchanged remainder (the plugin buckets by signature outcome alone), so it joins no sum and no subtraction.
• The mismatch note reads the run mode from the status, because the counter cannot say what happened: armed, each mismatch was hard-expired the moment it was seen (a detection rate); in dry run nothing expires them, so the same disagreement is re-reported every pass (a standing count of wrong pages being served). Only the standing case warns — armed, the counter is the feature working.
• Sweep card — a per-pass row for pages that disagreed, shown only when nonzero.
• Cluster merge — pageMismatch joins PROBE_COUNTERS: each node counts its own disjoint owned slice, so it sums across nodes for the sweep and the canary's per-rule table alike.
• The chart note says when the counter is structurally zero: no rule sets pageCheck, or the render fleet predates browser 1.20.0 (the plugin logs that hourly; the console cannot tell the two apart).

Left out on purpose

changeProbeStatus() still does not expose a rule's pageCheck (nor statusSignals, the same gap noted in #137), so the rules table cannot show which rules carry it. Needs a plugin field + release train; kept out to preserve the console-only catch-up.

Verification

• node --test in packages/console: 216 pass, including the coverage guard that failed before the change.
• npm run lint + npm run format:check clean at root. (No PR CI on this repo — verified locally.)

🤖 Generated with Claude Code

[gemini-code-assist]

Code Review

This pull request bumps the package version to 0.10.0 and integrates support for the new pageCheck feature introduced in plugin v0.58.0. It adds tracking, visualization, and documentation for page mismatches, which represent cached pages that disagree with the origin. This includes updating the probe view to display page mismatches as an overlay on top of existing outcome buckets, adding warning indicators when mismatches are standing in dry run mode, and introducing corresponding unit tests to verify aggregation and UI rendering. There are no review comments, so I have no feedback to provide.