Recompile analytics-review with gh-aw v0.86.2 (fixes Copilot CLI ENOENT on toolcache hit)

[amjithtitus09]

Why

The first post-merge dry-run of the analytics reviewer (run 32010839654, workflow_dispatch against PR #146) failed — but not in our workflow logic. All our pre-steps passed:

• ✅ JIRA fetch wrote jira-ticket.md
• ✅ Skills checkout (pinned SHA) OK
• ✅ sqlglot lint OK
• ❌ "Execute GitHub Copilot CLI" → spawn /usr/local/bin/copilot ENOENT

Root cause (upstream gh-aw bug): the v0.85.4 compiled harness hardcoded /usr/local/bin/copilot, but on runners with a toolcache hit the install step used /opt/hostedtoolcache/copilot-cli/1.0.78 and only appended to GITHUB_PATH — never staging the binary at the hardcoded path. Fixed upstream in gh-aw v0.86.2 — see github/gh-aw#52464 (also #51068, #52327).

What changed

Upgraded the gh-aw extension v0.85.4 → v0.86.2 and ran gh aw compile. Generated files only:

• .github/workflows/analytics-review.lock.yml — lock metadata now shows compiler_version: v0.86.2; frontmatter_hash/body_hash are identical to before, confirming the source .md files are untouched.
• .github/aw/actions-lock.json — github/gh-aw-actions/setup pin bumped to the v0.86.2 SHA.

The fix is visible in the lock's "Execute GitHub Copilot CLI" step: it now resolves the binary with command -v copilot (which finds toolcache installs via PATH), stages it to ${RUNNER_TEMP}/gh-aw/bin/copilot, and the harness invokes that staged path instead of the hardcoded /usr/local/bin/copilot. Fails fast with a clear error (exit 127) if the CLI genuinely isn't installed.

Compile output: 0 errors, 0 warnings (one informational tip about copilot-requests: write billing — not adopted; we keep COPILOT_GITHUB_TOKEN to match care_fe).

After merge

Re-run the dry-run:

gh workflow run analytics-review.lock.yml -f pr_number=146