You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit cb1289d
Browse filesBrowse the repository at this point in the historyBrowse files
fix(plugin): review of 0.102.0 -- a suppressed spelling is answered only with the page its verdict named, confirmations allow for the read-to-store gap, crawler misses create no registry rows, no query strings, the tap obeys the master switch and lets go of an unsent body, the stored path falls back to declaredCanonical; v0.102.0
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: packages/plugin/METRICS.md
+8-4Lines changed: 8 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -196,13 +196,17 @@ Notes that bite:
196
196
a target by then (since v0.102.0 a spelling suppressed as a canonical verdict is answered, not
197
197
`has-target`). `unconfirmed` climbs right after the anchor and falls as the pass and the serve-time
198
198
checks confirm canonicals. If a route stays there, no check compares its `canonical`. `moved`
199
-
(v0.102.0, `entities.enabled`) is a page the registry has since heard re-slugged: it should be rare,
200
-
and should not persist for an entity, because the observation that moved the registry also adopted
201
-
the new canonical. `entity_serve_ms` (v0.102.0) is each evaluation's duration, every outcome: a
199
+
(v0.102.0) is a page the origin has since been heard naming another canonical: by the registry
200
+
(`entities.enabled`), or by the spelling's own canonical verdict when it is newer than the page's last
201
+
confirmation and did not name it. It should be rare. With adoption armed it should not persist for an
202
+
entity, because the observation that moved the registry also filed the new canonical; under the
203
+
adoption dry run, or past `maxPerHour`, it lasts until the new canonical renders by another path. `entity_serve_ms` (v0.102.0) is each evaluation's duration, every outcome: a
202
204
duration, so read its percentiles.
203
205
-**The entity registry is `prerender_ops` / `entity_canonical` and `canonical_adopt`** (v0.101.0,
204
206
`entities.enabled`). `entity_canonical`: one emit per observation of an entity's canonical, detail =
205
-
what it did to the registry (`new`, `moved`, `same`, `older`, `foreign`, `unreadable`, `error`),
207
+
what it did to the registry (`new`, `moved`, `same`, `older`, `foreign` — another entity's prefix, or a
208
+
query string — `untracked` — a crawler's proxied miss of an entity with no row, which creates none —
209
+
`unreadable`, `error`),
206
210
context = the observer: `probe`, `render` (a stored page, or a canonical verdict's declared canonical),
207
211
`check` (a serve-time check) or `origin` (a proxied origin document on an `entityServe` route; the last
208
212
two since v0.102.0). `moved` per day is the re-slug rate, and which observer moves it first says how
0 commit comments