report: storebound report writes one shareable, self-contained readiness page (.storebound/reports/readiness-<date>.html; --md, --json, --no-open, --offline, --out) from scan, check and validate: a verdict per store (Ready to submit / N blockers / Not checked with the reason), findings per store by severity with guideline, evidence, fix and console button, the owner's compliance questions as a checklist, secrets masked; storebound.dev look, light / dark, print; desktop Checks > Report (same code path, opens through project_reveal) and its Markdown export on the same renderer; read-only MCP tool report

CHANGELOG.md

@@ -2,6 +2,14 @@
 
 ## Unreleased
 
+- **Shareable readiness report.** `storebound report` puts `scan`, `check` and `validate` into one self-contained HTML
+  page (`.storebound/reports/readiness-<date>.html`, inline CSS, no scripts, light / dark, print-friendly) and opens it
+  in the browser: a verdict per store ("Ready to submit", "N blockers", "Not checked" with the reason when a store key
+  is missing), findings per store by severity with guideline, evidence, fix and an Open in App Store Connect / Play
+  Console button, and the questions only the owner can answer as a checklist. Credentials, key ids, emails and the
+  review demo account are masked. `--md`, `--json`, `--no-open`, `--offline`, `--out`. The desktop's Checks tab has a
+  Report button (same code path) and its Markdown export uses the same renderer; MCP gets a read-only `report` tool.
+
 - **Remote config and remote paywalls (App Review 2.3.1, Play Deceptive behavior).** `storebound scan` (and
   `validate`; `check` as a warning) reports `remote-features` for both stores when the app ships a remote config /
   feature flag SDK (Firebase Remote Config, Statsig, LaunchDarkly, GrowthBook, Optimizely, PostHog feature flags,