A record read back from a v1 store carries its catalog entry's schema name
as its type; a fresh write carries the definition's type. For a definition
that names its schema (type != schemaName) the store's push and delete
matched on type, so every rewrite of a read-back key appended a duplicate
(a global then refused to load: "has multiple persisted entries") and every
delete removed nothing on disk.
These tests pin the rule and fail at this commit; the next commit fixes the
store:
- read-back then rewrite (global and keyed) stays one record and reloads;
- read-back then delete stays deleted;
- the store matches a stored record by the written schema id, by an id the
write declares compatible, by schema name, and by type label (legacy
envelopes), each with a fixture only that rule reaches;
- another schema at the same key, and the same schema at another key, survive;
- a TS rewrite under a relabelled definition leaves one record that Rust, C#
and Python read as the rewritten value.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>