real-e2e-test

# Real E2E Test Skill Run real end-to-end tests that start `claude-tap` from local source, connect to the real Claude CLI, and verify trace output. ## Prerequisites - `claude` CLI installed and authenticated - Python dev dependencies installed: `uv sync --extra dev` - `tmux` installed for interactive mode (`brew install tmux`) ## Mode 1: Pytest Real E2E (7 test cases) ### Run all real E2E tests ```bash uv run pytest tests/e2e/ --run-real-e2e --timeout=300 -v ``` ### Run a single test ```bash uv run pytest tests/e2e/test_real_proxy.py::TestRealProxy::test_single_turn --run-real-e2e --timeout=180 -v -s ``` ### Run with debug output ```bash uv run pytest tests/e2e/ --run-real-e2e --timeout=300 -v -s --tb=long ``` ## Mode 2: tmux Interactive Real E2E Use this when you need to validate non-`-p` interactive behavior in Claude Code TUI. ```bash scripts/run_real_e2e_tmux.sh ``` Optional overrides: ```bash PROMPT_ONE="Use the shell tool to run command ls in the current directory, then reply with any 5 filenames only." \ PROMPT_TWO="Thank you." \ SUBMIT_KEY="Enter" \ PERMISSION_MODE="bypassPermissions" \ scripts/run_real_e2e_tmux.sh ``` Important tmux interaction notes: - Submit key is `Enter` for Claude Code TUI in tmux (confirmed working). - `PROMPT_ONE` should intentionally trigger tool use. - For portability, use `grep -F` instead of `rg` in shell assertions (`rg` may be unavailable). ## Verification Checklist (for both modes) - Latest trace `.jsonl` contains both p...