Observed live 2026-08-31 ~20:00Z: a user created org Micavacado-LLC through the Forgejo UI. create_org would have rejected the name (^a-z0-9*$), but Forgejo's own org creation has no such rule — so the platform could not govern it: the ground reconciler never birthed <org>/gitops, and the dispatcher deferred every offer with org ground not born yet, forever. The user sat in a silent dead end for 40+ minutes.
Hand-fixed tonight: renamed to micavacado-llc (org was empty; sole member micavacado), ground births on the next tick.
Choose one systemic fix:
Decision
What to do
Normalize
The ground reconciler detects a non-conforming org name and renames it to the lowercase form (safe while the org has no repos), leaving a note issue in the born ground.
Refuse loudly
The reconciler files ONE issue in the org's first repo (or notifies the owner) saying the name is un-governable and how to rename it — never a silent defer loop.
Either way, the dispatcher's org ground not born yet defer should carry a why when the cause is the name.
Observed live 2026-08-31 ~20:00Z: a user created org
Micavacado-LLCthrough the Forgejo UI.create_orgwould have rejected the name (^a-z0-9*$), but Forgejo's own org creation has no such rule — so the platform could not govern it: the ground reconciler never birthed<org>/gitops, and the dispatcher deferred every offer withorg ground not born yet, forever. The user sat in a silent dead end for 40+ minutes.Hand-fixed tonight: renamed to
micavacado-llc(org was empty; sole membermicavacado), ground births on the next tick.Choose one systemic fix:
Either way, the dispatcher's
org ground not born yetdefer should carry a why when the cause is the name.🤖 Generated with Claude Code
https://claude.ai/code/session_012svX9LqUGpR2s9QCSk2Awd