Verify modular control obligations and realized effect outcomes #1071

Publish conformance coverage for the revised provider, composition, and effect contracts at the actual shared-runtime boundary.

Acceptance criteria

• Cover applicable subsets, mandatory coverage, predecessor dependencies, optional failure, admitted support strength, phase decisions, and conflicting results.
• Exercise real operation dispatch for each claimed effect kind, including an inject, a control transition, cancellation/refusal, and a non-IFC mechanism. Verify zero prohibited execution after denial.
• Check authored recovery requirements, invocation authority, stale coordinates, duplicate handling, restart, and agreement between durable outcomes and backend readback.
• Package the suite for separately installed backend consumption. Separate contract/runtime conformance from concrete backend realization; bind each claim to its supported subset and evidence.

Prerequisites: #1369, #1370, #1357, #1358, #1361.

References: Diagnosis, Diagnosis.