protocol

ci → green (verified run 29379537918: strict Rust, seven-crate publication dry-run, CLI, canonical type contract, live SpiceDB/Keto/OIDC/Jaeger integration, and both mandatory coverage ratchets)

coverage → Rust 75.07% remote / 69.72% floor / 80% target; TS CLI 41.24% remote / 21.51% floor / 70% target

Closed: PROTO-5

Commit 7332293 completes the mapping engine contract with DomainIn, Regex, IsTrue, and cloneable thread-safe Custom conditions; MappingRule idempotency and freshness controls; and MappingResult evaluation metadata.

Mapping freshness is operational through the lifecycle, not merely an evaluator flag: a recent successful idempotent rule skips both re-evaluation and the second Store write, while failed writes invalidate subject cache state and unverified claims never poison it.

Nineteen focused core tests and six lifecycle tests cover condition semantics, metadata counts, idempotent versus non-idempotent behavior, freshness hits, failed-write retry safety, and the zero-second-write guarantee. All workspace targets, strict Clippy, formatting, SDK type-contract tests, 51 CLI tests, seven-crate packaging, and live backend suites pass.

Program-wide

Wave 13 stayed within root/specs/08-CONCURRENT-PROGRAM-HANDOFF.md. Only Protocol mapping/lifecycle code, tests, dependency metadata, its gap checklist, and this Research ledger event changed; no UI-owned, product packages/ui, Portal, registry publication, or tag path was touched.