datatug / datatug-core / 38811279653

100%

push

github

feat(sessioncontext): recover native operations without redispatch (#373)

A local or hosted Detective retry must resolve its original acceptance before consulting mutable Check/Case definitions, and must distinguish the first dispatch claim from a replay. Add metadata-only ResolveOperation, backed by the operation receipt and accepted work committed atomically with the private pin, plus ClaimDispatchOnce with a first-claim flag that is false on errors, transaction callback replay, and repeated claims.

The trusted pin command can bind a host-computed canonical client request digest. Receipt/work/client-operation links are validated, and transport recovery rejects legacy acceptances without that digest. Empty digests preserve the previous internal acceptance hash. Existing ClaimDispatch remains compatible. Both adapters must compare the stored client digest before mutable reads; native absence alone never authorizes execution. A native accepted-but-not-started continuation still needs its own durable journal and fencing proof.

Validation: complete sessioncontext suite passes at 100% statement coverage; focused vet passes. Tests cover content revocation and redaction without private reads, disabled accounts, cross-actor/project/namespace access, corrupt mappings, changed-body conflicts, legacy hash compatibility, one first-claim winner, callback-retry flag reset, and failed claims returning no dispatch permission. Actual OVDB SQLite tests cover persistence across reopen/redaction and same-transaction fence visibility with rollback. No routes or capabilities are activated, and no hosted adapter race-conformance claim is made.

Root owns independent review, WB landing and release. This follow-up completes the agreed provider port inventory for the local and hosted adapters.

Source commits:

- 56dd506b1a01 feat(sessioncontext): recover native operations without redispatch
- ed79b3411a22 fix(sessioncontext): independently bind recovery metadata to receip... (continued)

95 of 0 new or added lines in 0 files covered. (NaN%)

17405 of 17405 relevant lines covered (100.0%)

1.0 hits per line