bab620fb61
Only one pull request appeared because the sweep was scoped to one project at one proposal per hour - a throttle I set deliberately while nothing had ever run, not a limit of the mechanism. It has now run, so it widens to every project whose job also has a write allowlist: ariadne, metis, soteria and bstein-dev-home. The rest are left out because without allowed prefixes nothing is patchable, and a sweep would spend a SonarQube call to discover it has nowhere to write. Still one proposal per project per hour. The backlog is 139 findings on Ariadne alone; the constraint that matters is how many pull requests a person will actually read, not how many the mechanism could open. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
titan-iac
Flux-managed Kubernetes desired-state config for bstein.dev.
Canonical source URL:
ssh://git@scm.bstein.dev:2242/bstein/titan-iac.git
Scope
This repo contains cluster configuration consumed by Flux:
- platform/infrastructure manifests
- service manifests and kustomizations
- operational scripts for render/reconcile workflows
Apply model
I use Git + Flux as the source of truth and avoid manual in-cluster edits for durable changes.