fix(fullsend): bump dispatch workflow to v0.39.0

[johnmcollier]

Summary

• Pin reusable-dispatch.yml to fullsend v0.39.0 so triage pre-scripts receive ISSUE_URL / FULLSEND_TRACKER.
• Vanilla playgrounds were still on v0.36.0 while agents@v0 already required those env vars.

Test plan

• Merge, then comment /fs-triage on a small issue and confirm the pre-script gets past ISSUE_URL

Made with Cursor

[fullsend-ai-review]

🤖 Finished Review · ❌ Failure · Started 2:48 PM UTC · Completed 2:49 PM UTC

Commit: 200c8ca · View workflow run →

[fullsend-ai-retro]

🤖 Finished Retro · ✅ Success · Started 2:49 PM UTC · Completed 2:57 PM UTC

Commit: 200c8ca · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $3.04

[fullsend-ai-retro]

Retro: PR #5 — bump dispatch workflow to v0.39.0

Timeline:

1. johnmcollier opened PR #5 — a 1-line change bumping .github/workflows/fullsend.yaml from reusable-dispatch.yml@v0.36.0 to @v0.39.0.
2. The review agent (run 33521605477) was dispatched but failed during pre-flight: the OpenShell sandbox proxy returned HTTP 403 when attempting HTTPS CONNECT to api.github.com, blocking all GitHub API access from within the sandbox.
3. The PR was merged by the author before the review failure was finalized. No human or agent review completed.

Assessment: The sole failure was an infrastructure issue — the sandbox proxy allowlist did not permit connections to api.github.com. This completely blocks any review agent from functioning, regardless of the code under review. The error message itself points to the OpenShell gateway network policy. This is a platform-level issue, not specific to this repo or this PR's content.

The PR itself was a trivial, well-understood infra config change on a playground repo. The author merging without review is reasonable given the context. One proposal filed for the sandbox connectivity issue.

Proposals filed

• Sandbox pre-flight fails: proxy blocks api.github.com (HTTP 403) (in fullsend-ai/fullsend)