b8b1b92226
Twenty-four Flux objects across eleven repos, none of them managed by Flux. Each repo declares its own GitRepository and Kustomization, which is the right ownership model, but nothing ever watched the directory those files live in — so editing one in git changed nothing until someone remembered to kubectl apply it. That cost real time twice this week: the CONTROL_PLANE_REF_NAME rollout looked applied and was not, and LLM_INPUT_COST failed the build with "variable not set" while sitting correctly in git. The gap is the bootstrap Kustomization that `flux bootstrap` would have created and flux-operator does not. Add one per repo, watching that repo's own ./dev, living in ./dev so it manages itself. Nothing moves between repos; each domain keeps its entrypoints. This is the first of eleven, starting with platform-llm because its cost settings are blocked behind exactly this. Needs one kubectl apply to exist. That is the last one this repo needs. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>