create-manual-test-guidelisted

# Create Manual Test Guide Produce one self-contained HTML file that walks a human tester through verifying an implementation: how to set up, what to do, what to expect, and a checklist that exports its results back as Markdown. ## 1. Resolve the output directory The output directory is per-installer configuration, resolved in this order: 1. `${CLAUDE_PLUGIN_ROOT}/config.json` → `outputDir` (shared across this plugin's skills) 2. `config.json` next to this SKILL.md → `outputDir` (skill-level override) 3. Neither exists → read [config.example.json](config.example.json) for the expected shape, ask the user for a real absolute path, then write it to the skill-level `config.json` (git-ignored) so the question is never asked again. Honor `openAfterGenerate` (default `true`) from the same file. ## 2. Determine what to test - The user named a feature, branch, PR, or commit range → use exactly that. - Otherwise default to the current implementation: `git diff $(git merge-base main HEAD)...HEAD` on a feature branch, or `git diff HEAD` for uncommitted work. Confirm with the user if ambiguous. ## 3. Understand the behavior — derive scenarios from real code - Read the changed files and trace user-facing entry points (UI routes, API endpoints, CLI commands, config flags) with Grep/Glob. - Find out how the app is actually launched and configured (README, package scripts, docker-compose, `.env` examples) — setup instructions must be real commands, not guesses. - Der