[Epic] Keep shipped skills and documentation accurate, secure, and lean

## Problem statement

Links, references, examples, metadata, token budgets, generated snapshots, and security guidance drift as Azure and the plugin evolve. Small defects compound into inaccurate or inefficient user experiences.

## Outcome

Shipped skills and documentation remain current, secure, internally consistent, and within maintainable token budgets.

## Goals

- Maintain references, links, examples, metadata, and terminology
- Enforce token and progressive-disclosure budgets
- Apply secure authoring and sensitive-data guidance
- Keep generated and published content synchronized

## Non-goals

- Building net-new Azure scenarios
- Treating security as a final documentation review only

## Success criteria

- [ ] Structural, reference, token, and security checks pass continuously
- [ ] Deprecated guidance is removed or migrated promptly
- [ ] User-facing examples remain executable and current

## Dependencies

Skill validators, token analysis, service documentation, security review, and release synchronization.

Start with the listed skill validators, token analysis, service documentation, security review, and release synchronization dependencies to map the work across shipped skills and documentation. Done means the structural, reference, token, and security checks pass, deprecated guidance is removed or migrated, examples remain current, and generated content stays synchronized.

Written by the indexing model from the issue text.