ck-verify-maintainlisted

# Maintain a verification skill Keep the verification map useful as its project changes. Use the project's own interface: an application, CLI, service, public library, or analysis workflow. This skill maintains an existing verification method; project-specific commands and acceptance criteria belong to that method. ## Scope and outcomes Choose the scope from the request before running checks: - **Scoped maintenance:** a concrete change or stale recipe defines the affected paths. Trace shared setup, assertions, and helper consumers to include any paths the change can invalidate. Other recipes remain outside this pass. - **Full-map audit:** the user requests a full audit or a verdict on the whole verification map. Inspect and exercise every mapped recipe and supported entry point, and check for material missing coverage. When the request only names a concrete repair, use scoped maintenance. If it requests maintenance without identifying a scope, inspect recent changes to bound a useful pass; clarify only when choosing full or scoped would materially change the requested verdict or resource cost. New or changed user capabilities need scoped maintenance even when the existing verification commands are unchanged. Discover their source entry points as well as checking current map rows; an unlisted feature cannot reveal itself through a stale recipe alone. Reconsider the scope when shared setup, authentication, build configuration, or helper changes affect many paths; when se