Verify assurance coverage across participant roles (ASR-510) #257

This issue owns the coverage summary across adversarial, defensive, non-adversarial, autonomous-service, and mixed-control participants. #220 owns contract conformance, #221 owns author scenarios, and #256 owns replay/history assurance.

Done when

• Publish a matrix of required role/control-mode cases, supported realizations, applicable contracts, checks, evidence, and remaining gaps.
• Reuse existing suites and add only missing cases. Each required role must have explicit positive and negative coverage.
• Exercise participant-as-actor/target, isolation of observations and authority, denied actions, and role/control transitions where supported.
• Identify whether each result establishes schema validity, semantic conformance, runtime enforcement, or native execution; a fixture cannot stand in for the latter.
• Keep unsupported cases visible. State the acceptance threshold and reconcile ASR-510 only when every required row meets it.

Prerequisites: #220, #221, and #256. Consume specialist modular/mixed-backend results from #1071/#1017/#1018 when claiming those capabilities; this issue does not require every backend or prove cross-backend equivalence.

Current implementation and remaining acceptance

• Consume completed Verify modular control obligations and realized effect outcomes #1071/Verify executable mixed-backend capability claims #1017/Demonstrate mixed control using executed mappings and backend evidence #1018 evidence and retain its exact configuration and controlled-provider/native distinction.
• Preserve unsupported combinations in the coverage matrix; separate passing control arrangements do not establish their joint support or universal replay/equivalence.

Review basis

Reviewed against origin/dev at 0fd7ca30b1f17965263533e1a610731e4ab8ad8a on 2026-10-29. These links identify the baseline; implementation must use the current governed contracts.

• implementations/python/packages/raes_conformance/conformance/report.py
• docs/explain/reference/modular-control-conformance.md
• docs/explain/reference/revised-control-semantics.md
• docs/decisions/adrs/adr-110-reusable-mixed-control-policies-and-occurrences.md
• docs/decisions/adrs/adr-095-participant-decision-epoch-state-cut-and-delivery-semantics.md
• implementations/python/packages/raes_processor/compiler/participant_behaviors.py

Requirements

• ASR-510 — Multi-Role Participant Assurance Coverage