omh-ai-slop-cleaner

# Ai Slop Cleaner This is a Hermes-native `ai-slop-cleaner` workflow skill. ## Why This Exists `ai-slop-cleaner` exists to keep `maintenance` work explicit, evidence-backed, and inside the Hermes/executor boundary instead of relying on ad hoc chat narration. ## Do Not Use When - The request is casual chat, a status-only acknowledgement, or another workflow has stronger routing evidence. - The user needs implementation, review, CI, merge, or external publishing evidence that has not been delegated or observed. ## Examples Good example: - Prompt: $ai-slop-cleaner remove duplicated router branches and lock behavior with regression tests before refactoring. - Expected behavior: Plan cleanup, preserve behavior, delete or simplify code, and prove it with targeted tests. - Why: The request is maintenance cleanup with regression risk. Bad example: - Prompt: ai-slop-cleaner: treat casual chat or unaccepted work as if this workflow already produced verified results. - Expected behavior: Ask a clarification question or route to a narrower workflow instead of forcing `ai-slop-cleaner`. - Why: The request lacks the required inputs or would overclaim work that Hermes did not observe. ## Completion Checklist - The selected coding or runtime owner is named before any implementation claim. - Prepared handoff, dispatch, execution, verification, review, CI, and merge states are separated. - The final status cites observed runtime evidence or keeps the work prepared_not_observed. - W...