Manager Canary Dispatch

To validate manager-native canary dispatches safely, initiate a live canary in your workspace using the --manager-native-submit flag. This enforces fail-closed checks, ensuring safe, auditable automation runs with run-bus evidence.

When a canary dispatch fails with repo_select_failed, it indicates an issue with repo targeting during the automation run. Diagnose the failure by verifying the explicit workspace configuration and the correctness of the live repository targets.

Announcing RUN START and RUN END is required for canary workflows to enforce hands-off operation during active runs. This mechanism provides auditable run-bus evidence, ensuring guardrails are maintained throughout the automation validation process.

No, you cannot use manager-native canary dispatches without specifying a workspace. The validation process requires explicit workspace usage alongside the --manager-native-submit flag to ensure correct scope and artifact generation for the automation run.

The best way to triage manager_no_new_cascade_after_submit errors is to validate live cascade tracking. Diagnose the failure by checking artifact content verification and ensuring cascade discovery completed successfully within the active manager automation workflow.

You need fail-closed checks for automation validation whenever running Anti-Gravity Manager-native canary dispatches across live repository targets. These checks ensure safe, auditable automation by enforcing guardrails and verifying artifact content during active runs.