weekly-curatorlisted

# Weekly curator Keep the awesome-agentic-engineering list fresh, high-signal, and LEAN. This list is bounded: each section has a maximum in `.github/section-caps.txt`, and a full section only gains an entry by displacing a weaker one. This skill DRAFTS a pull request; a human reviews and merges it. Never merge, never push to main. That human gate is the anti-slop guardrail, and it is the whole point: adding slop damages the maintainer's reputation, which is what the list exists to build. ## Scope Agentic engineering means building and shipping software by directing AI coding agents across the SDLC: coding agents and harnesses, loop and context engineering, spec-driven development, evals, review, and production case studies. Keep resources that are about engineering software WITH agents. Out of scope: building agent applications or products (agent frameworks, RAG chatbots) and general LLM or ML research. ## The cap (what "lean" means here) Every section has an entry cap in `.github/section-caps.txt`. Read that file each run; never hardcode the numbers. CI (`.github/check-caps.py`) fails any PR that pushes a section over its cap, so a bare add into a full section is not an option. When a section is full, you displace, you do not append. ## Steps 1. Read `README.md`, `CONTRIBUTING.md`, and `.github/section-caps.txt` for the current scope, categories, format, quality bar, and caps. 2. Maintain existing entries: - Check every link in `README.md` still resolves (follow r