maintain-verification-skill

# Maintain a verification skill Keep a repository's `.bb/skills/verify-<app>/` usable by the next agent. ## Locate and scope Read repository instructions and the target verification skill. If several apps are plausible and the request does not identify one, ask which. If none exists, report that and point to `create-verification-skill`; do not invent an audit target. A request to explain maintenance does not authorize running it. Edit only the verification skill directory, its feature map, and its owned helpers. Report product regressions separately. Do not rewrite the expected behavior to match a broken app. Preserve only explicitly requested feature subsets and real product boundaries. ## Read source Check the index against its feature files. Read each feature's source entry points and compare its recipe with current routes, labels, CLI flags, defaults, and persistence behavior. Record a concrete source citation for each suspected drift and one concise live recipe per feature. Reconcile the feature inventory against current routes, commands, settings, plugins, platform clients, and action menus. Document omitted features even when their live prerequisites are unavailable. Preserve an explicitly requested subset, but do not infer a scope limit from gaps left by an earlier generator. Work directly unless delegation is authorized. When source review is delegated, keep browser driving with one owner and reconcile findings before editing. Concurrent reviewers must not man...