Derive identity-map entries from successor claims a caller ACCEPTED
(issue #4955). The engine never calls this on its own output: a successor
claim is a suggestion, and only a human turns it into identity
(04-identity.md §4.5).
Every claim is 1:1 by construction. A self-claim is dropped. A here that
two accepted claims name for different bases yields NO entry at all — the
same contradiction the sidecar refuses at parse, refused here so a
createIdentityMapSidecar call downstream does not throw on an artifact a
UI assembled from clicks. Two heres on one base are left in, as the
sidecar leaves them, for resolveKeyAliases to judge against the models.
Derive identity-map entries from successor claims a caller ACCEPTED (issue #4955). The engine never calls this on its own output: a successor claim is a suggestion, and only a human turns it into identity (
04-identity.md§4.5).Every claim is 1:1 by construction. A self-claim is dropped. A
herethat two accepted claims name for differentbases yields NO entry at all — the same contradiction the sidecar refuses at parse, refused here so acreateIdentityMapSidecarcall downstream does not throw on an artifact a UI assembled from clicks. Twoheres on onebaseare left in, as the sidecar leaves them, forresolveKeyAliasesto judge against the models.