Enrich Amnion projections from authoritative Decapod evidence

[alexhraber]

Context

PR #2 distinguishes Pincher runtime observation from authoritative Decapod evidence and requires both validation and proof evidence before authoritative readiness. The first slice has no live Decapod enrichment path.

Scope

Add a read-only authority adapter that looks up sessions, todos and claims, workspaces, approvals/interlocks, validation, proof, and promotion state through Decapod’s supported CLI/RPC surfaces. Reconcile authority with Pincher runtime events without creating a parallel governance store.

Cover query minimization, deterministic reconciliation, stale markers, conflicting evidence, and authority unavailability. Keep claimed values, locally observed values, and verified/authoritative values as separate evidence classes.

Non-goals

No local SQLite governance database, cached authority that silently outlives freshness, optimistic completion, direct mutation of Decapod state, or replacement of Pincher execution events.

Acceptance criteria

1. Every displayed authoritative field identifies its Decapod reference and evidence state.
2. A local ready or validation.passed event cannot become authoritative without matching Decapod evidence.
3. Missing, failed, stale, unavailable, and conflicting authority are distinct view-model states.
4. Reconciliation is deterministic and preserves custody IDs.
5. Query plans are bounded and tested for the normal intent list and selected-intent detail path.
6. Authority failures never fabricate progress or hide blockers.
7. Tests prove that no second source of governance truth is persisted by Amnion.

Dependencies

PR #2 projection semantics; the published Pincher host contract; current Decapod RPC/CLI schemas.

Validation expectations

Run adapter/reducer integration tests, failure-path tests, Decapod schema/contract tests, cargo fmt/test/Clippy, and decapod validate with recorded evidence.

Related: #2