archetech / archon / 23015720892

94%

push

github

feat: Add change-registry command to change a DID's registry (#194)

* feat: Add changeRegistry to change a DID's registry after creation

Adds a `change-registry <id> <registry>` CLI command and supporting
`changeRegistry(id, registry)` method that updates didDocumentRegistration
to point to a new registry. Same-registry calls are a no-op. Gatekeeper
updateDID now queues the operation on the new registry when it differs
from the current one. Accepts any resolvable DID or alias.

Closes #153

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* test: Add unit and client tests for changeRegistry

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* test: Add changeRegistry unit and client tests

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* refactor: Move change-registry command to DID commands section

Relocate changeRegistry in keymaster.ts (after revokeDID), cli.ts (after revoke-did), and archon-cli.js (after revoke-did) to group it with DID operations rather than ID/wallet operations.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* fix: Restore InvalidParameterError guard in changeRegistry

Guard was accidentally dropped during method relocation.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* fix: Queue registry-change operations on the old registry

Queuing on the new registry broke the confirmation check, which
validates that each event's confirming registry matches the DID's
current registry. This caused the entire DID history after the
first registry change to be permanently marked unconfirmed.

The fix: always queue on the current (old) registry. The new registry
is still validated for support upfront. Subsequent operations
naturally queue on the new registry once the doc is updated.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* feat: Add Migrate dialog to gatekeeper web client

Adds a shared Migrate dialog to KeymasterUI allowing users to change
the registry for any o... (continued)

1755 of 1933 branches covered (90.79%)

Branch coverage included in aggregate %.

15 of 15 new or added lines in 3 files covered. (100.0%)

3751 of 3908 relevant lines covered (95.98%)

1177.58 hits per line