[workshop-coverage] Workshop Coverage Status — 2026-09-14

**Run:** https://github.com/Azure/git-ape/actions/runs/34797208381
**Features assessed:** 8 agents, 15 skills, 0 core CI/CD workflows tracked in inventory (git-ape-plan/deploy/destroy live as onboarding-scaffolded templates, assessed separately)
**Coverage:** 18 / 23 fully covered (per inventory refs) · **Gaps found:** 5 (1 deferred, 4 addressed)
**Proposed this run:** draft PR (docs(workshops): align content with Deployment Stacks and previously uncovered skills)

No open `workshop-sync` issues were found this run, so scope was driven entirely by the inventory's 0-ref signals plus a factual-accuracy read of `workshops/track-3-platform-engineering/lab-06-destroy-lifecycle.md` against the real `git-ape-destroy.yml` template, which surfaced a drift bug independent of coverage counting.

### Gaps & proposed work

| Feature | Type | Persona / Track | Action | Status |
|---|---|---|---|---|
| `azure-requirements-gatherer` | agent | Beginner / T1 (already narratively covered in 3 labs) | Added glossary entry so the term resolves to a definition | In draft PR |
| `azure-resource-availability` | skill | Beginner / T1 | Named explicitly in Lab 2 Step 3 (behavior was already described, skill wasn't named); glossary entry added | In draft PR |
| `azure-rest-api-reference` | skill | Engineer / T2 | New "Going further" link in Lab 2 (web app + SQL); glossary entry added | In draft PR |
| `azure-stack-deploy` | skill | Beginner / T1 + Engineer / T2 | Cross-linked in T1 Lab 2 (local equivalent of chat deploy) and T2 Lab 2 "Going further"; glossary entry added | In draft PR |
| `azure-stack-destroy` | skill | DevOps/SRE / T3 | Cross-linked from T3 Lab 6 Step 4 as the local equivalent of `git-ape-destroy.yml`; glossary entry added | In draft PR |

### Content-accuracy fix (not a coverage gap, but corrected this run)

`workshops/track-3-platform-engineering/lab-06-destroy-lifecycle.md` Step 4 described the destroy workflow as "deletes the resource group" — this was stale. The actual `git-ape-destroy.yml` template (`.github/skills/git-ape-onboarding/templates/workflows/git-ape-destroy.yml`) reads `stackId` from `state.json` and runs `az stack sub delete --action-on-unmanage deleteAll --bypass-stack-out-of-sync-error true`, with resource-group deletion only as a legacy fallback for pre-Stacks deployments. Fixed in the draft PR; also removed a duplicate Steps 7–8 block that repeated the stale description.

Coverage detail

**Deferred / out of scope:**
- No `aws-*` or other out-of-program skills exist in this repo's `.github/skills/` today, so the "drop out-of-scope AWS content" scope filter had nothing to apply to this run.
- No new lab or new track was warranted — all five gaps fit as additions to existing "Going further" sections or existing step text within their current tracks, so no timing or track-count changes were needed.

**Persona ambiguity:** none this run — all five gaps mapped cleanly to an existing persona/track without needing a human tie-break.

**In sync (no action needed):** `azure-iac-exporter`, `azure-policy-advisor` (agent + skill), `azure-principal-architect`, `azure-resource-deployer`, `azure-template-generator`, `git-ape-onboarding` (agent + skill), `git-ape`, `azure-cost-estimator`, `azure-deployment-preflight`, `azure-drift-detector`, `azure-integration-tester`, `azure-naming-research`, `azure-resource-visualizer`, `azure-role-selector`, `azure-security-analyzer`, `prereq-check` — all referenced ≥1 time in `workshops/` per the inventory and spot-checked as still accurate to their source.

### Recommended next steps

- Next run: re-check `git-ape-destroy.yml` / `git-ape-deploy.yml` template drift periodically even absent a `workshop-sync` issue — these templates live under `.github/skills/git-ape-onboarding/templates/workflows/` and aren't watched by the deterministic sync workflow's feature-file grep, so behavior drift there can go unnoticed by that mechanism.
- Consider whether `azure-requirements-gatherer`'s "experimental and not production-ready" warning (from its agent frontmatter) should be echoed more prominently in Track 1/2 labs — currently the labs present its output as authoritative without repeating that caveat. Flagging for human judgment rather than changing content unilaterally.

> Generated by [Workshop Content Auto-Updater](https://github.com/Azure/git-ape/actions/runs/34797208381) · copilot · auto · 145.6 AIC · ⌖ 15.1 AIC · ⊞ 11.5K · [◷](https://github.com/search?q=repo%3AAzure%2Fgit-ape+is%3Aissue+%22gh-aw-workflow-call-id%3A+Azure%2Fgit-ape%2Fgit-ape-workshop-content-updater%22&type=issues)

The scope is described across the workshop coverage table, existing workshop labs, and .github/skills/git-ape-onboarding/templates/workflows/git-ape-destroy.yml. Start by reviewing the draft PR and comparing Track 1–3 workshop references with the listed skills and destroy workflow; done means the five gaps are covered and lab-06-destroy-lifecycle.md accurately reflects the template behavior.

Written by the indexing model from the issue text.