E2E worktree test: add a TESTING.md file documenting how to run azlin tests. Create the file in the worktree and verify it exists.

[rysweet]

Task Description

E2E worktree test: add a TESTING.md file documenting how to run azlin tests. Create the file in the worktree and verify it exists.

Requirements

● Check existing worktrees (shell)
│ cd /home/azureuser/src/azlin && ls worktrees/feat/ 2>/dev/null && git --no-pager worktree list
│ 2>/dev/null | head -5
└ 7 lines...

Ambiguity Resolution — Final Requirements

No significant ambiguity remains. All requirements are clear and actionable. Here are the minor decisions made:

Decisions Made

Decision	Choice	Rationale
Which worktree?	Create new dedicated worktree (feat/testing-docs)	Existing ones are for other tasks; clean separation
Where in worktree?	Root-level TESTING.md	Follows convention of README.md, CHANGELOG.md at repo root
Python test docs?	Mention briefly as legacy, focus on Rust	Python CLI retired per project history
Golden file scripts?	Document with caveat they need pre-populated data	Scripts exist but golden dir may be empty
scripts/run_tests.sh?	Exclude — it's a stale Python runner	Would mislead users

Final Unambiguous Requirements

1. Create worktree: git worktree add worktrees/feat/testing-docs -b feat/testing-docs
2. Create TESTING.md in that worktree root with:
   • Quick-start: RUST_MIN_STACK=8388608 cargo test --all (+ note about .cargo/config.toml)
   • Unit tests: location, how to run per-crate
   • Integration tests: rust/crates/azlin/tests/*.rs
   • CLI parity tests: rust/crates/azlin-cli/src/parity_tests.rs
   • Golden file comparison: rust/scripts/capture_golden.sh + compare_golden.sh
   • Agentic scenarios: tests/agentic-scenarios/ with gadugi-test
   • E2E scenarios: tests/e2e/
   • Real Azure tests: scripts/test_agentic_integration.sh (requires creds)
   • Linting: cargo clippy --all -- -D warnings
   • CI pipeline: .github/workflows/rust-ci.yml
   • Known gaps: no real-Azure tests in CI
3. Verify: test -f worktrees/feat/testing-docs/TESTING.md

Requirements are clear. Ready for design phase.

✅ Copied bin
✅ Copied agents/amplihack
✅ Copied commands/amplihack
🔐 Set execute permissions on 43 hook files
✅ Copied tools/amplihack
🔐 Set execute permissions on 5 hook files
✅ Copied tools/xpia
✅ Copied context
✅ Copied workflow
✅ Copied skills
✅ Copied templates
✅ Copied scenarios
✅ Copied docs
✅ Copied schemas
✅ Copied config
✅ Copied tools/statusline.sh
✅ Copied AMPLIHACK.md
✅ CLAUDE.md is current version
💾 Backup created at /home/azureuser/.claude/settings.json.backup.1774836411
📋 Found existing settings.json
🔒 XPIA security hooks directory found
🔒 XPIA security hooks configured (3 hooks)
✅ Settings updated (10 hooks configured)
✓ Rust recipe runner available
✓ Disabled GitHub MCP server to save context tokens - using gh CLI instead
Using gh CLI with account: rysweet
To re-enable GitHub MCP, just ask: 'please use the GitHub MCP server'
✓ XPIA security defender ready (/home/azureuser/.amplihack/bin/xpia-defend)
✓ Staged 6 hooks to .github/hooks/

Acceptance Criteria

• All explicit requirements met
• Tests passing
• Philosophy compliant
• Documentation updated

Classification

Generated via default-workflow recipe