Summary

The required audit status check (workflow .github/workflows/release-audit.yml) is failing on every branch — including the default branches — across 9 repositories. Root cause: the workflow checks out a shared harness repo that does not exist.

- name: Check out the shared release-audit harness
  uses: actions/checkout@...
  with:
    repository: Coding-Dev-Tools/release-audit   # <-- returns 404, repo missing
    ref: main

https://api.github.com/repos/Coding-Dev-Tools/release-audit → 404 Not Found. The checkout step therefore fails on every run, so the audit job can never go green. Because audit is a required check, this blocks the entire merge pipeline on the affected repos regardless of PR quality.

Affected repositories (9)

devforge-cli, crossrepo-dep-manager, api-contract-guardian, configdrift, schemaforge, json2sql, envault, deploydiff, apiauth

Evidence

• audit check = failure on the default branch of deploydiff, configdrift, schemaforge, envault (not just PRs) — i.e. pre-existing, not introduced by any PR.
• The harness repo Coding-Dev-Tools/release-audit returns 404 (authenticated and unauthenticated).

Fix options (owner decision needed)

1. Restore the harness — (re)create Coding-Dev-Tools/release-audit with audit.py and push it to main. The gate goes green and starts doing its intended 8-angle scoring.
2. Retire the gate — delete release-audit.yml from the 9 repos and remove audit from each branch protection required-checks list (branch protection changes require owner/admin UI access — the automation integration cannot edit protection rules).

Option 2 requires editing branch protection, which this maintenance routine cannot do (the integration token gets 403 on the branch-protection API), so it needs a human.

Filed automatically by the 2-hourly maintenance routine.

Generated by Claude Code