archetech / archon / 34718547812

95%

push

github

fix(gatekeeper): Authorize against the key the proof names (#1132)

Both gatekeeper ports took verificationMethod[0] whatever key the proof
named, each with a TBD saying so. A DID that published a second key could
not sign with it, and a proofPurpose cannot be enforced against a key
nobody looked up.

Safe for everything anchored, checked against the BTC-mainnet store rather
than assumed: rotation replaces the identity key in place, so index 0 is
the named key for all 43,020 operations. Update and delete operations name
their controller (11,442) or, for agents, themselves (1,730).

Absent verificationMethod means the controller has not been imported yet
and defers; an empty array, or a named method the document does not list,
is a refusal. The import state machine treats those differently, so a
throw in the wrong place would retry an unverifiable operation forever.

Both test harnesses signed asset updates under the asset's own DID, a key
that exists nowhere and that no keymaster emits. They name the signer.

Closes #1130.

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

4169 of 4792 branches covered (87.0%)

Branch coverage included in aggregate %.

17 of 20 new or added lines in 1 file covered. (85.0%)

8807 of 9245 relevant lines covered (95.26%)

772.35 hits per line