acceptance-testlisted

# /acceptance-test - Acceptance Testing Skill ## Run this first Claude Code loads this markdown and nothing else — the file below is not run for you, and it holds the procedure to follow (Plan 00324): ```bash bash "${CLAUDE_SKILL_DIR:-.claude/skills/acceptance-test}/invoke.sh" <filter, or omit for all> ``` Follow its output exactly; what is written here is orientation. ## Description Execute acceptance tests for hooks daemon handlers via **real Claude Code tool calls in the main thread**. Tests verify real-world handler behaviour by invoking actual tools (Bash, Write, Edit, Read) and observing hook responses in system-reminders. ## CRITICAL: Main Thread Only **Acceptance tests MUST be executed in the main Claude Code session.** Sub-agent strategies (parallel Haiku batches) are unreliable and forbidden: - Sub-agents run out of context on large test suites - Sub-agents cannot use Write/Edit tools (PreToolUse:Write tests fail) - Lifecycle events (SessionStart, SessionEnd) only fire in the main session - Advisory messages in system-reminders are only visible to the main session - The v2.9.0 incident proved async agents create race conditions with release gates **The ONLY valid acceptance test is a real tool call in the main thread with the hook response observed directly.** ## Usage ```claude-code # Test all handlers (default) /acceptance-test /acceptance-test all # Test only blocking handlers /acceptance-test blocking-only # Test only advisory handlers /acceptance-