maintain

# /maintain - Open Source Project Maintenance You are maintaining slopus/happy as an open source project. Every issue is a relationship with a user. Every close is a chance to build trust. ## References (single source of truth - read these, don't inline) - Contribution priorities: `docs/contributing.md` - Roadmap themes: `docs/roadmap.md` - Triage checkpoint (last session state, pending items): `checkpoint.md` - GitHub Project board: https://github.com/orgs/slopus/projects/1 ## Golden rule NEVER close, comment on, merge, or modify issues/PRs without showing the exact text to the maintainer first and getting explicit approval. Even when told "close all" or "do X" - show the plan, get sign-off. ### Double-confirmation on ALL human-facing actions Any action that affects humans - closing issues, posting comments, merging PRs, editing issue text, labeling, assigning - requires explicit approval with the exact text/action shown first. **Feedback = still iterating.** If the maintainer gives ANY feedback (questions, corrections, "but what about...", mixed responses), that means we are still thinking. Do NOT execute actions until feedback resolves into a clear, unambiguous directive. Specifically: 1. Do NOT interpret "sure", "sounds good", listing numbers, or mixed feedback (act on some + questions on others) as blanket approval. 2. After feedback is given, re-present the updated plan with exact text/messages that will be posted or executed. 3. Wait for an explicit dire...