[roboco-app]

Goal: when the integration base branch's CI is red, open exactly one P0 base-red incident with a single owner, and close it when green. Context from intake: PR #1158 (no Python changes) failed 'Python quality gate' and 'Entire Gates' because the base was red; the $119.39 task 'Fix ruff-format violation in release-certificate doc (CI Python quality gate red)' was opened for the same cause; devs resubmitted unchanged heads (d6a26717).

Build in roboco/services (new module, e.g. base_red_incident.py; services own DB writes and side effects, routes stay thin, respect .roboco/conventions.yml placement):

• Incident model + Alembic migration (project_id, base_branch, status open/closed, owner_task_id, owner_agent slug, opened_at, closed_at, consecutive_red count, closed_reason/cleared_by). At most one open incident per project+base (unique partial index or equivalent).
• Detection: read the CI check state of the base branch HEAD by REUSING the existing CI-status plumbing (roboco/services/git.py e.g. _resolve_ci_head_sha and the forge/* providers, plus ci_watch_engine.py); do not add new HTTP clients. Open an incident only after N consecutive red readings (configurable, default 2-3); close on the first green reading after open; avoid flapping (pending/unknown readings neither count as red nor close). A CI lookup error must fail open (no incident opened, no gate), logged.
• Ownership: one named owner when opened (the fix task, or the agent/cell that owns it). Create or record the owner's fix task id and send a formal notification to the owner so other cells do not rediscover the failure.
• Public interface that the gate leaf consumes (keep these signatures exactly): async get_open_incident(project_id) -> BaseRedIncident | None (exposes owner_task_id, owner_agent, base_branch, opened_at); async is_owner_task(task_id) -> bool; async clear(project_id, cleared_by: str, reason: str) -> BaseRedIncident | None (manual clear path, audited).
• Wire the periodic check into the existing engine/loop (ci_watch) rather than a new scheduler, and expose a thin manual-clear route only if an existing admin route pattern fits.
• Tests (80% coverage on new code): opens only after consecutive reds, single incident, closes on green, no flapping on pending, fail-open on lookup error, clear().
  Run make gate / make quality before submitting.

[github-actions]

Thanks for opening your first pull request on RoboCo!

Quick checklist before review (most of these are enforced by CI, but worth a glance):

• make quality — ruff format check, ruff check, mypy, pytest (≥80% coverage), and the rest of the gate
• Panel changes pass pnpm lint and pnpm exec tsc --noEmit (run from panel/)
• No # noqa / # type: ignore shortcuts; pre-existing violations in touched files are fixed
• Added an entry under ## [Unreleased] in CHANGELOG.md
• Signed the CLA (the bot will prompt you on this PR)
• Signed your commits — master requires verified signatures (SSH signing setup)
• Updated any affected docs under docs/

See CONTRIBUTING.md for the full workflow and the Code of Conduct for the community standards we follow.

Welcome aboard — a maintainer will review shortly.

[github-actions]

All contributors have signed the CLA. Thank you!
_{Posted by the CLA Assistant Lite bot.}