Keep develop green

Find every workflow failing on develop, tell a real defect from the outside world changing, and land the fix.

Rendered from the repository at vibey-engine 4.4.0; regenerated by scripts/continuation_prompts.py, do not edit inside these markers.

  • Mode when GitHub runs it daily: act — may open a draft pull request; never merges, approves, releases or deletes.
  • What it is for: Find every failing workflow on the integration branch, fix its cause, and land the fix.
  • Decision records: 88, the newest 0088 — TypeScript, never JavaScript: the only authored form is typed, and the JavaScript that must exist is generated.
  • Lanes it keeps usable: CI, Branch health, Ruleset drift, Repository profile, Documentation deep scan, Self-healer.
  • Agent skills it relies on: .claude/skills/vibey-quality-gates/SKILL.md.

The prompt

You are keeping the integration branch of vibey (https://github.com/the-vibey-project/vibey)
green. Your working directory is a clone of it. Assume you remember nothing.

1. Read CLAUDE.md first; its non-negotiables bind you, and its "Commands worth memorizing"
   section is the exact gate sequence CI runs.
2. List what is red, latest run per workflow, from evidence:
     for w in .github/workflows/*.yml; do
       gh run list --workflow "$(basename "$w")" --branch develop --limit 1 \
         --json conclusion,databaseId,createdAt,event
     done
   A run that is "cancelled" or "action_required" is not a failure: say which it is.
3. For each failure, read the log (`gh run view <id> --log-failed`) and classify it before
   touching code:
   - a defect in this repository — fix it with a test that fails before the fix;
   - the world changed (a new security advisory, a dependency release, a runner image) — run
     the same check on develop to prove the pull request did not cause it; a new advisory
     with no fixed release is answered only by a declared, expiring exception in
     .github/advisory-exceptions.toml with evidence that nothing shipped reaches the code,
     and that file needs a person's approval to merge;
   - an operator act (a ruleset to delete, a secret to set, a credential to rotate) — do not
     do it; report the exact command and why it needs a person;
   - the gate working as designed (a review asking for a person) — report, do not bypass.
4. Fix one cause per pull request into develop, Conventional Commits, with the before/after
   evidence in the body. Never push to develop or main; never --no-verify, --admin, or a
   force-push to a branch you did not create; never weaken a check to make it pass.
5. Report every red workflow with its class, its fix or the reason it needs a person, and the
   PR links. A failure you could not explain is reported as unexplained, never as fixed.