Add Copilot CLI, Qwen Code, Pi, and Cline to Pitot

[bigboateng]

Summary

• add supervised Pitot adapters for GitHub Copilot CLI, Qwen Code, Pi, and Cline
• ship a Pi TypeScript extension and Cline Unix/PowerShell response bridges
• expand the canonical supervisor from 6 adapters / 18 cells to 10 adapters / 30 Ubuntu, macOS, and Windows cells
• project the new integration artifacts and setup documentation into the public Pitot distribution

Why

Pitot's single adapter supervisor should make every shipped host visible in its registry, local E2E harness, generated README, platform workflow matrix, reporter, and public projection. Adding all four through that boundary prevents supported-but-unreported adapters.

Cline's native PreToolUse event covers every tool, so its bridge explicitly passes non-shell tools through while supervising execute_command. Pi's extension translates its native blocking result into Pitot's stable hook envelope.

Impact

Users can connect Copilot CLI and Qwen Code directly to pitot hook, install the shipped Pi extension, or install the platform-appropriate Cline bridge. Initial evidence remains truthfully reported as hook-subprocess verification.

Validation

• GOWORK=off go test ./...
• GOWORK=off go test -tags windtunnel ./...
• python3 -m unittest discover -s labs/15-pitot/tests -p 'test_*.py'
• python3 labs/15-pitot/scripts/pitot_adapter_supervisor.py check
• python3 labs/15-pitot/scripts/build_pitot.py --check
• bash labs/15-pitot/scripts/check_import_boundary.sh
• all four new E2E scripts, including Pi and Cline allow/block translation and Cline non-shell pass-through