pgh publish flagged hyperident@0.2.3 as content-differing across apps: this repo declares keet-identity-key 3.2.0 while every published 0.2.3 copy (pgh, pgh-sidecar, pear-git-v3, hypermosh-shell) declares 3.1.0. Same version, different dependency — the exact skew class that makes "same version" meaningless in the shared dep store. Runtime impact is nil: keet-identity-key 3.1.0 and 3.2.0 are wire-identical (only the compact-encoding dep range differs, and c-e@2/@3 are wire-compatible), so mixed copies interoperate. But the content DID change, so it gets a version. Consumers rebuilt after this declare 0.2.4; existing 0.2.3 installs stay valid until they rebuild. Found while publishing favela-web 0.2.29 — overriding the warning would have carried the drift forward instead of naming it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>