Shadow mode proves only its named component boundary

Shadow mode proves only the bounded component's no-side-effect contract, not that the scheduled workflow around it is read-only. When testing existing records, name the exact effect boundary, inspect component-specific telemetry, and separately account for normal upstream and downstream mutations. A read-only shadow component may still emit approved operational telemetry.

Do not treat an empty live-cohort database dashboard as evidence about shadow execution when enrollment is intentionally live-only; shadow evidence may exist only in operational disposition logs. This distinction does not prove that the wrapper is unsafe or establish current deployment health or configuration. Those require authoritative runtime checks.