feat(evidence): project canonical trust status consistently across every surface

[akougkas]

Problem

The same underlying run is summarized differently across terminal output, monitor results, evidence inspection, reports, and external control surfaces. Users must understand several subsystem vocabularies before they can answer four basic questions: who claims this, what was observed, what was independently checked, and what remains unknown.

Goal

Project the canonical trust model consistently across operator-facing surfaces, showing one compact answer first and preserving drill-down to detailed records.

Dependencies

Blocked by #154 and #157.

Scope

• Define one compact human-readable projection and one bounded machine-readable projection.
• Apply them to dispatch/monitor output, evidence CLI/reporting, TUI receipt views, ACP where trust facts are exposed, and exported reports.
• Keep detailed receipt and evidence artifacts available for inspection.
• Standardize wording for sealed, grounded, independently reviewed, inferred, approximated, bypassed, unknown, and not applicable.

Acceptance criteria

• Every surface gives the same trust verdict for the same canonical input fixture.
• The primary projection answers claimant, observation, independent verification, and uncertainty without requiring receipt internals.
• A sealed artifact is never worded or styled as independently verified unless independent verification exists.
• Approximated and bypassed runtimes remain visibly distinct from mediated execution.
• Machine projections are bounded, versioned, and contain references to the detailed source artifacts.
• Golden/contract tests cover TUI text, CLI text/JSON, monitor results, evidence reports, and applicable ACP payloads.
• Documentation includes a compact trust-status glossary and examples of commonly confused states.

[akougkas]

Partially covered by 0.3.4: receipt inspection, evidence bundles, monitor output, and worker evidence now derive trust facts from one canonical derivation (#157, af8fe97c), and bundles carry trust-status.json. Still open for 0.3.5: the TUI, CLI evidence listing, and dispatch board render their own trust wording rather than projecting the six-axis status.