Skip to content

Required check 'Dispatch path and outcome contracts' fails on main since the automation quarantine (#571) #587

Description

@hyperpolymath

Problem

scripts/tests/dispatch-paths.sh calls scripts/dispatch-runner.sh. Since #571 (fa1ec2a), the runner refuses every call with exit 78 (BLOCKED: repository directive enforcement is not qualified; dispatch is quarantined (including --dry-run)). The test treats that exit as a failure.

The context is required on main, and it is red on main head 8a4f983. Every PR therefore inherits a failing required check.

Evidence: PR #586, job 111852349821. The failure reproduces locally on origin/main.

Acceptance criteria

  • Dispatch path and outcome contracts is green on main.
  • The quarantine is not weakened. Either:
    • the contract test asserts the quarantine (exit 78 plus the BLOCKED message) for every dispatch path while enforcement is unqualified, or
    • it runs the path/outcome assertions through a test-only seam that cannot be reached in production.
  • A planted control: removing the quarantine interlock makes the test fail. Without it, a green test proves nothing.
  • docs/AUTOMATION-QUARANTINE.adoc records how the contract test behaves while dispatch is quarantined.

Deferral issue under AGENTS.md §5c item 3, filed from #586.

Activity

  1. added
    automationBots, schedulers, dispatch, self-healing, fan-out
    bugSomething is broken or behaves incorrectly
    on Oct 5, 2026
  2. added a commit that references this issue on Oct 5, 2026
    b578cf4
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    automationBots, schedulers, dispatch, self-healing, fan-outbugSomething is broken or behaves incorrectly

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions