feat: add deploy workflow targets

[onutc]

Summary

• add full, backend, and frontend targets to the manual ClawHub deploy workflow
• make backend-only runs skip the Vercel wait while frontend/full runs still validate Vercel
• update deploy docs to explain the new targets and the current Vercel limitation

Verification

• ruby -e 'require "yaml"; YAML.load_file(".github/workflows/deploy.yml")'\n- git diff --check

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
clawhub	Ready	Preview, Comment	Apr 3, 2026 7:36am

[greptile-apps]

Greptile Summary

This PR adds full, backend, and frontend deploy targets to the manual GitHub Actions deploy workflow, with conditional steps gating Convex and Vercel operations on the resolved target. Documentation in AGENTS.md, CLAUDE.md, docs/deploy.md, and docs/troubleshooting.md is updated consistently. The implementation is clean and the logic in the Resolve deploy mode step correctly maps targets to output flags used throughout the job.

Confidence Score: 5/5

This PR is safe to merge — no blocking issues found.

All changes are documentation and workflow configuration. The conditional gating logic is straightforward and correct. The backend target intentionally skips the Vercel wait and runs smoke tests against the existing production frontend, which is clearly documented. No P0/P1 issues were identified.

No files require special attention.

_{Reviews (1): Last reviewed commit: "feat: add deploy workflow targets" | Re-trigger Greptile}