feat(ci-cd-tools): use bktide snapshot as primary investigation tool

[technicalpickles]

Summary

• Update working-with-buildkite-builds skill to use npx bktide@latest snapshot as the primary tool for investigating build failures
• Simplify investigation workflow from multiple MCP tool calls to a single command
• Update all bktide references to use @latest for fresh installs
• Fix hardcoded org bug in wait-for-build.js script

Changes

Tool hierarchy reorganization:

• bktide snapshot is now the primary approach (parses URLs, captures metadata, annotations, and logs)
• MCP tools are now fallback for when bktide isn't available or for specific operations (wait_for_build, unblock_job)

Workflow simplification:

# Before: Multiple tool calls to parse URL, get build, find job UUID, get logs
# After:
npx bktide@latest snapshot <buildkite-url>
cat ./tmp/bktide/snapshots/<org>/<pipeline>/<build>/steps/<step-id>/log.txt

Files updated:

• SKILL.md - Main skill documentation
• references/tool-capabilities.md - Capability matrix and tool guidance
• references/annotation-patterns.md - Added snapshot method
• references/troubleshooting.md - Updated decision tree
• scripts/*.js - Updated to use @latest, fixed bugs

Test plan

• Run npx bktide@latest snapshot <url> on a failed build
• Verify logs are captured in snapshot directory
• Verify skill guidance is clear and actionable

🤖 Generated with Claude Code