dependabot-config-helperlisted

# dependabot-config-helper A Category 3 ops tool. The user runs this against a target repo (or a paste of an existing `dependabot.yml`) and gets either a from-scratch config or a reviewed-and-recommended-changes diff. Defaults come from `dependabot-strategy` research — config follows policy, not the other way around. ## When to use - Onboarding a new repo to Dependabot — generate a starting `dependabot.yml`. - Existing repo's Dependabot has gone off-rails (PR storm, ignored alerts, no security update path) — refactor. - Org-wide audit: are repos' configs consistent with the policy? - Adding a new ecosystem (npm + adding Docker, or Python + adding Terraform). ## When NOT to use - Strategic / policy questions → `dependabot-strategy`. - Individual alert triage / suppression → out of scope for v1. - Multi-repo sweeps to rewrite configs at scale — possible but the user should review the generated configs individually for now. ## Required inputs - **Target stack**: list of ecosystems present in the repo (npm, Maven, pip, Docker, Terraform, Go, etc.). - **Regulatory exposure**: same lens as `copilot-rollout-playbook` — PCI-DSS, SOX, GDPR. Affects schedule + auto-merge defaults. - **Team size + bandwidth**: affects `open-pull-requests-limit`. Small team → smaller limit + monthly cadence. Large team → larger limit + weekly cadence. - **Private registries used** (if any): for `registries:` block. - **Reviewer team handle**: for the `reviewers:` field. ## Bank-specific defaults