v0.25.2

Added

• Report upload (Probe Cloud preview): ci.head_sha, the job's identity token and retries. ci.head_sha is the commit under test (the push commit, or pull_request.head.sha from the event payload on a pull request); like ci.base_branch and ci.default_branch it is optional and a missing or garbled event file never fails the upload. When the job has permissions: id-token: write, the CLI requests the GitHub Actions identity token for the audience in hosted.audience / PROBE_CLOUD_AUDIENCE (default probe-cloud) and sends it as X-Probe-Attestation (at most 4,096 characters) to the configured endpoint only; it is never printed or logged, is redacted like the license key, and --upload-dry-run shows only attestation: present|absent. A busy service (HTTP 429 or 503) is retried with backoff for up to hosted.retry_window (default 5 minutes) and then gives a warning; the run is never failed. The endpoint can be set with PROBE_CLOUD_URL, and a successful upload prints one line naming the endpoint host. The hosted service is still not live. All additive: the report JSON and its schema value do not change.
• Upload envelope: ci.default_branch, and ci.base_branch is documented. A hosted report upload (--upload-report, or --upload-dry-run to preview it) gains an optional ci.default_branch, the repository's default branch, read from the GitHub event payload when it names one. ci.base_branch, the branch a pull request targets, is sent only for the pull_request and pull_request_target events. Both fields are optional: a missing or unreadable event file only adds a warning.

Docs

• Docs site: tutorials (login test, GitHub Actions, flaky tests), a "Why FlutterProbe" comparison with sourced claims, the Probe Cloud design-partner offer and preview page (the hosted service is not live yet), a sample dashboard at /demo/, install and quick-start in first-run order, and recipe examples with quoted placeholders that probe lint accepts.