v0.12.0 — libid-contracts 0.13.0, and IdentityNames under a fresh name

The deploy tool takes libid-contracts 0.13.0, IdentityNames gets a fresh canonical name, and an apply --upgrade converges a proxy whose running implementation predates a getter the wiring reads.

Changes

• Pins libid-contracts / libid-identity / libid-profiles 0.12.0 → 0.13.0: GitHub's token request is revealed whole and every token body is held to its profile's field list on chain. Nothing libid-deploy calls changed shape.

• apply runs each requested upgrade inside that component's own step, before it reads or wires through the proxy. Previously every upgrade ran last, so a network whose IdentityNames predates proofVerifier() aborted at that read; now apply --upgrade identity-names finishes in one run. A guard fails the run if a requested component has no section. plan names the flag in its warning.

• IdentityNames deploys under a new canonical name, libid.IdentityNames.2: eden-testnet's libid.IdentityNames came from the pre-ceremony contract set and keeps that storage, and an in-place upgrade over a layout this repository no longer builds is not a thing to do. The old contract stays where it is, orphaned.

Addresses

One row moves; everything else is byte-identical to v0.11.0 and the circuit verifiers still carry circuits 0.4.0.

contract	was	now
contracts.identity_names	0xd467d48769c26faee36ba6b6fc9228f14aef6dd2	0xe78b53a183dd51763df44beb2500ddab9bb0329e

Consumers that record the address (libID harness and demo, usernames-indexer, the deployment's indexer manifest, keeper's e2e file) follow.