archetech / archon / 35010776665

92%

main: 95%

Build Type

Pull #1145

github

Committed by macterra

Commit Message

fix(gatekeeper-rs): Stop a confirmed resolution before the first unconfirmed event

The Rust store resolver judged whether to stop a confirmed resolution by
the previous event's state, then applied the current event regardless. So
`confirm: true` applied the first unconfirmed event and reported the
result as unconfirmed -- one version past where the TypeScript port and
Rust's own verifying resolver stop. The unit test asserted that outcome.

Every asset operation is authorized by its controller resolved this way,
so a controller with a pending unconfirmed rotation resolved to one key
on TS and the other on Rust: a fork on any operation signed with either
in that window. Nothing exercised it -- the contract test resolves a
create-only DID and the parity flow sets `verify`, which takes the other
path. The parity harness now creates an agent, chains a signed update to
it as a hyperswarm event, and checks both ports stop a confirmed
resolution at v1 and say so.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GYGMfX3foBcVqP7AQNXjWj

Pull Request Pull Request #1145: fix(gatekeeper): Reject a backdated proof once the chain has committed the operation

Coverage Stats

4216 of 4846 branches covered (87.0%)

Branch coverage included in aggregate %.

40 of 42 new or added lines in 2 files covered. (95.24%)

12 existing lines in 1 file now uncovered.

8842 of 9285 relevant lines covered (95.23%)

788.53 hits per line