archetech / archon / 35014041324

92%

main: 95%

Build Type

Pull #1145

github

Committed by macterra

Commit Message

fix(gatekeeper-rs): Normalize metadata timestamps and stop the verify path leaking the confirmed flag

The parity harness's backdating phase stamps operations the way clients
do, with millisecond precision, and fell at its first comparison: the
TypeScript port reports every metadata timestamp as UTC at second
precision (generateStandardDatetime) while Rust echoed the input. Every
fixture uses second-precision literals, so no DID's `created`, `updated`
or `deleted` had ever been compared across the ports with a real stamp.
standard_datetime applies the same normalization in both Rust resolvers.

A test that the two Rust resolvers agree -- the store resolver behind a
plain resolution and the verifying one behind verify=true -- found on its
first run that the verifying path stops a confirmed resolution at the
right version but commits `confirmed: false` before breaking, reporting
v1 as unconfirmed where the store path and TypeScript report it
confirmed. The same local-then-commit ordering fixes it.

The confirm-ordering fork lived in the gap between those two resolvers,
and a single port's unit test had enshrined it; the new test guards the
gap directly, and a TypeScript test now pins the confirm semantics on
that side too, with and without verification.

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%)

789.53 hits per line