bird-agentlisted

# BIRD Config Agent Use the current `@birdcc/cli` project model instead of treating every `.conf` file as BIRD. Prefer parser-backed diagnostics and read-only discovery before changing a configuration. ## Safety invariants 1. Do not publish or commit unredacted BGP passwords, peer addresses, ASNs, communities, or private route-policy details. Read [`references/safety.md`](references/safety.md) before handling production material. 2. Do not write config files by default. Run formatting in check mode first. Pass `--write --confirmed` to the wrapper only after the user explicitly authorizes the edit. 3. Treat `birdcc init --write` and `--force` as writes. Start with `birdcc init . --dry-run --json`. 4. Use `bird -p -c <file>` for a read-only daemon parse check; do not start or reload BIRD unless the user explicitly requests the operational change. 5. Do not infer that a generic `.conf` file is BIRD from its extension alone. Require a canonical name, an explicit project config, or parsed BIRD declarations. ## Workflow 1. Run `uv run scripts/detect_bird_context.py --root .` from the skill directory. Inspect `project_config`, candidate files, installed tool versions, and the read-only `birdcc_project_detection` report. 2. Read [`references/project-config.md`](references/project-config.md) when discovery is ambiguous, the repository has multiple routers, or no project config exists. Prefer `bird.config.json`; accept `birdcc.config.json` only as a comp