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.

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

0. Locate the target. Read the host-path table, then find verify-* under the active host's project skill root. Confirm that the candidate has launch and drive sections plus a feature map. If several candidates exist, ask which one. If none exist, stop and point at create-verification-skill instead of inventing a target.