curating-azure-deployment-learningslisted

# Curating Azure Deployment Learnings The feedback loop that keeps the [diagnosing-azure-deployment-failures](../diagnosing-azure-deployment-failures/SKILL.md) gotcha catalogue current. Capture lessons from real projects in `learnings/`, then promote recurring ones into the catalogue. > `learnings/` is **gitignored** in the plugin repo — learnings are private field notes (they name customers, subscriptions and costs). Only the *promoted* gotcha row is shared. The commit SHA recorded in a learning's Status line therefore points at the gotcha commit, and is for the author's own audit trail. Keep learnings in whichever private location suits you (`LEARNINGS_DIR` overrides the default for every script). ## When to invoke - A deployment problem was solved — capture it before it's forgotten - Reviewing accumulated `learnings/*.md` for promotion candidates - Triaging which learnings are project-specific vs broadly reusable ## The pipeline ``` Project hits a problem in the field ↓ Solve it — file a learning in learnings/{date}_{project}.md ↓ Periodically review learnings/ — what shows up across multiple projects? ↓ Promote recurring ones to skills/diagnosing-azure-deployment-failures/references/gotchas.md ↓ Mark the learning entry "✅ Promoted in commit {sha}" ``` ## Learning file format ```markdown --- project: trg-directory-content-crawl date: 2026-05-20 issues: - docker-hub-rate-limit - crawl4ai-pinning severity: medium promoted: false --- # Session Learnin