validate-repo.sh: flag a missing Agent label at onboarding #376

Closed
opened 2026-07-11 02:59:41 +00:00 by igor · 0 comments
Collaborator

Follow-up from #375 (greenlight gate fail-closed).

bin/validate-repo.sh prints the onboarding readiness checklist but doesn't check whether the repo has the custom Agent label. sharktankdb.com was onboarded without it, which is what let the pre-#375 gate fail open (Forgejo ignores a labels=Agent filter naming a label the repo lacks).

With #375 merged, a missing Agent label is now safe (the grind claims nothing there) — but it's a silent footgun: a repo meant to be agentic that lacks the label just does no issue work, with no signal. Add an Agent-label presence check to the validation checklist so onboarding flags it.

Low priority — the fail-closed fix removed the danger; this is the "so you notice" half.

Follow-up from #375 (greenlight gate fail-closed). `bin/validate-repo.sh` prints the onboarding readiness checklist but doesn't check whether the repo has the custom **`Agent`** label. sharktankdb.com was onboarded without it, which is what let the pre-#375 gate fail open (Forgejo ignores a `labels=Agent` filter naming a label the repo lacks). With #375 merged, a missing `Agent` label is now **safe** (the grind claims nothing there) — but it's a silent footgun: a repo meant to be agentic that lacks the label just does no issue work, with no signal. Add an `Agent`-label presence check to the validation checklist so onboarding flags it. Low priority — the fail-closed fix removed the danger; this is the "so you notice" half.
Sign in to join this conversation.
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
joshtronic/igor#376
No description provided.