Maintain a verification skill

A feature map rots the moment the app changes. This skill is the upkeep loop for a skill generated by /create-verification-skill (or any project-local verification skill with a feature map). The unit of rigor is the feature, not every sentence: cover every feature file from source and exercise every feature live, without terminalising every bullet.

Each spawn below names a role from the pstack profile (written by /setup-pstack, always in your context). Spawn it with the profile's spawn recipe, passing that role's value as the model. A role with no line, or the value inherit, means no model override. If the harness rejects the model, retry with inherit and say so. With no profile in context, follow the fallback in the setup-pstack skill (references/profile-template.md) and tell the user once that /setup-pstack was not run. The spawns here name no role, so they run with no model override.

Outcomes

Pick one, and say which:

• clean — every feature got source and live coverage; nothing worth shipping. No branch, no PR.
• changed — one PR ships proven doc, harness, or map corrections.
• blocked — coverage could not finish or a proven fix could not ship safely. Say exactly what blocked it.

Edit scope

Only edit the verification skill's own directory (its SKILL.md, features/, and any harness scripts it owns). Never edit product code during a run: a behavior the map describes that the app no longer does is either doc drift (fix the map) or a product regression (report it, don't paper over it in docs).

Pass