fix: tier 2 respects open onboarding tickets #9

Merged

joshtronic merged 2 commits from devel into master

2026-05-16 21:57:57 +00:00

joshtronic commented

2026-05-16 21:55:46 +00:00

Owner

Fix: maintenance_eligible now checks for an open Igor-authored
onboarding ticket on the repo before considering cooldown. If the
ticket exists and is open, the repo is ineligible -- doesn't enter
the candidate pool for tier 2.

Once the human closes the onboarding ticket (signaling fixed), tier
1 re-validates and either onboards the repo or reopens the ticket.
Tier 2 only sees the repo as eligible after onboarding succeeds and
tier 1 has cloned it.

One extra API call per repo per tier-2 dice-roll. At solo-dev scale
the cost is trivial.

Co-Authored-By: Claude Opus 4.7 (1M context) noreply@anthropic.com

Bug observed in dogfood: tier 2 picked joshing.you for a maintenance pass even though there was an open Status/Needs More Info onboarding ticket on it (filed by tier 1's discovery gate). Tier 1 had refused to clone joshing.you because it failed validation; tier 2 happily cloned it anyway and ran auto-detected audits on a repo Igor already declared not-ready. Fix: maintenance_eligible now checks for an open Igor-authored onboarding ticket on the repo before considering cooldown. If the ticket exists and is open, the repo is ineligible -- doesn't enter the candidate pool for tier 2. Once the human closes the onboarding ticket (signaling fixed), tier 1 re-validates and either onboards the repo or reopens the ticket. Tier 2 only sees the repo as eligible after onboarding succeeds and tier 1 has cloned it. One extra API call per repo per tier-2 dice-roll. At solo-dev scale the cost is trivial. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

joshtronic added 1 commit

2026-05-16 21:55:46 +00:00

fix: tier 2 respects open onboarding tickets

Lint / check-sync (push) Successful in 4s

Details

Lint / check-sync (pull_request) Successful in 4s

Details

aefa5efa85

Bug observed in dogfood: tier 2 picked joshing.you for a maintenance
pass even though there was an open Status/Needs More Info onboarding
ticket on it (filed by tier 1's discovery gate). Tier 1 had refused
to clone joshing.you because it failed validation; tier 2 happily
cloned it anyway and ran auto-detected audits on a repo Igor already
declared not-ready.

Fix: maintenance_eligible now checks for an open Igor-authored
onboarding ticket on the repo before considering cooldown. If the
ticket exists and is open, the repo is ineligible -- doesn't enter
the candidate pool for tier 2.

Once the human closes the onboarding ticket (signaling fixed), tier
1 re-validates and either onboards the repo or reopens the ticket.
Tier 2 only sees the repo as eligible after onboarding succeeds and
tier 1 has cloned it.

One extra API call per repo per tier-2 dice-roll. At solo-dev scale
the cost is trivial.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

joshtronic added 1 commit

2026-05-16 21:55:51 +00:00