CLOUD_HANDOFF gains action=fix so fix clicks route to the fix flow, not a new trial

[Gandy2025]

What

• CONTRACT: CLOUD_HANDOFF (SKILL.md) now emits &action=fix on both usage surfaces (the step 5.1 fix→team conversion and the step 6.1 issue footer); the &report=<report_key> append rule is unchanged. The contract prose explains the split: same base handoff as the landing page for attribution, plus the fix discriminator so Cloud routes into the fix flow instead of starting another scan trial.
• docs/example-report*.md links updated to the same URL shape so the stale examples stop teaching the trial-relaunching format (the deeper example refresh flagged in production-scan: opt-in issue filing, fix-as-conversion, and S3 publish #24 is still pending).
• report-template.html needs no change — its CTA is deliberately link-free.
• Render smoke test: 17/17 passing locally; render-smoke CI covers this PR.

⛔ DO NOT MERGE until the Cloud side is deployed

This repo is merge-=-production (every new trial clones main). The consumer for action=fix ships in:

• feat(web): consume the production-scan fix handoff (action=fix) on /quickstart first-tree#1479 (web: parse the fix handoff, route to onboarding / direct fix chat)
• feat(skills): welcome skill recognizes the production-scan fix first chat first-tree#1480 (welcome skill: launch the fix bootstrap as the pre-selected first task)

Until BOTH are deployed to cloud.first-tree.ai, action=fix links would be treated as trial handoffs by the live web app (today's circular behavior — no worse, but not fixed). Merge this PR only after #1479 and #1480 are live.

🤖 Generated with Claude Code