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

This commit is contained in:
CRTkafa 2026-10-18 01:42:03 +08:00
parent 6d95ea00f5
commit af349b3db1
18 changed files with 792 additions and 12 deletions

View file

@ -40,6 +40,14 @@ Many apps (a `storebound.workspace.json` above the app folders, `storebound ws i
and `storebound ws validate [--apps a,b]` run the same checks over every app, a few at a time, each with its studio's
credential profile; `storebound ws run <command> --apps a,b` runs any other read command (writes only as dry runs).
## Share the report: `storebound report`
For the owner, a teammate or a client who should not need a terminal: `storebound report` runs `scan`, `check` and
`validate` (read-only; a store without credentials shows "Not checked" with the reason) and writes one self-contained
page, `.storebound/reports/readiness-<date>.html`, then opens it in the browser. A verdict per store, every finding
with its fix and console link, and the questions only the owner can answer. Secrets are masked. `--md` for Markdown,
`--json` for the data, `--no-open` in scripts. MCP: `report`; desktop: Checks > Report.
## Reading `scan`
| finding | fix | skill |
|---|---|---|