archetech / archon / 30458578474

90%

main: 90%

Pull #800

github

keymaster: keep a local agent's assets on the local registry

#798 made `ephemeralRegistry` follow a `local` `defaultRegistry`. That keys
off the wrong thing: Gatekeeper's rule is about the *controlling agent's*
registry, not the wallet-wide default, and the two diverge in both directions.

- A `local` agent under a non-`local` default still failed with
  `Invalid operation: non-local registry=hyperswarm` — the original bug.
- A non-`local` agent under a `local` default had its challenges sent to
  `local`, where they validate but never reach a remote verifier.

Enforce the invariant once, in `createAsset`: resolve the controlling agent
(confirmed, as Gatekeeper does, so a pending change-registry can't slip
through) and downgrade the operation to `local` when that agent is local.
This covers all six ephemeral call sites and any direct caller, so
`ephemeralRegistry` goes back to a constant.

Downgrading rather than rejecting: Gatekeeper would refuse the operation
outright, so a non-`local` registry on a local agent is unsatisfiable rather
than merely unusual. Gatekeeper cannot do this itself — `registration.registry`
is covered by the operation proof and by the CID the DID is derived from, so
rewriting it server-side would invalidate the signature and change the DID.

Python is brought to parity, including `create_challenge`, which was a bare
passthrough that set neither the ephemeral registry nor the one-hour expiry
its TypeScript counterpart has.

Documented in the Keymaster spec as 7.2 Registry selection.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

2986 of 3537 branches covered (84.42%)

Branch coverage included in aggregate %.

4 of 4 new or added lines in 1 file covered. (100.0%)

6183 of 6609 relevant lines covered (93.55%)

858.27 hits per line