Maintain skills

Keep this library's sourced skills current with their upstreams while keeping the light local adaptations that fit them to this setup. The adaptation contract defines that setup and how to decide each upstream change; read it before deciding anything. The maintenance guide gives the helper commands, runtime state, checks, and branch rules the steps use.

Run one of two modes:

• Upstream, the default: adopt upstream changes since each skill's reviewed position, import new upstream skills, and review skills whose files changed since the last run.
• Audit, when the user or the scheduled prompt asks: do the upstream work, then work through the fidelity backlog and review every other skill against current tools, documentation, and repository conventions.

Only an explicitly named subset of skills narrows either mode.

Use /pstack-swarm throughout. Give each worker one slice, such as a source group, a batch of skills, or a repair, with the exact local revision, the immutable candidate, the adaptation contract, its evidence requirements, and the files it may write. Workers do their slice directly without starting another coordinator. The coordinator fetches sources, owns the coverage ledger, canonical documents, and integration, and collects every worker's result; a failed or missing result stays pending. Without delegation, work sequentially and note the lost independence in the run's report.

1. Resume

Read repository guidance. Open the library worktree the maintenance guide describes and run the helper there. Load the newest checkpoint and the waiting questions from runtime state. Read new owner comments on the open maintenance PRs and on the PRs the waiting questions link to. Run inventory --resume with the checkpoint, and reconcile it with the actual SKILL.md files, including untracked ones.

Complete when: you hold the checkpoint, the waiting questions, every new owner comment, and the inventory with its changedSince list.