manual-test-planning

## Project Context - personal config directory: !`bash "${CLAUDE_PLUGIN_ROOT}/scripts/han-config-dir.sh" 2>/dev/null || echo "$HOME/.claude"` - project .han/config.md: !`cat .han/config.md 2>/dev/null || echo ""` As your first action, use the Read tool on `.han/config.md` inside the `personal config directory` path above. A read that returns no file is no personal configuration: continue silently. When that file or the `project .han/config.md` probe supplies content, apply it per [config-rule.md](../../references/config-rule.md), which governs precedence between the two files, relative-path resolution, and what to do with a file that reads but cannot be used. ## Operating Principles - **Group outcomes only when the steps are identical.** A test verifies a single outcome, or a group of related outcomes only when the exact same steps produce every outcome in the group. If any outcome needs a different or additional step, it gets its own test, BECAUSE a person following one step list can only check the outcomes those steps actually produce. - **Every test states its expected outcomes.** A step list without an expected outcome is not a test. Each test's detail section ends with the outcome or outcomes the person should observe, so they can tell pass from fail on the spot. - **No manual tests means no document.** When the supplied context contains nothing a person can test by hand, say so clearly and ask for more context instead of writing a file. Never invent or p...