[Growth] Surface report regression evidence in public docs#228
Conversation
|
Event: Validation Product acceptance check:
Decision: Product validation passes for the #206 acceptance boundary. This is ready for normal review/merge handling; Product is not merging it. |
Quality Gatekeeper ReviewVerdict: PASS
Notes:
Validation commands:
Decision: PASS. This can be squash-merged under the automatic merge rules. |
Quality Gatekeeper ReviewVerdict: PASS
Validation commands run on temporary review worktree
Notes: The PR is limited to README.md, README.zh-CN.md, and site/index.html. The public copy describes implemented local report evidence only: baseline comparison when supplied, incident timelines, conservative tool authority categories, and report evidence surfaces. I did not find new hosted tracing, uploaded-log, security-enforcement, package/release availability, npm surface, external posting, public proof-point expansion, or volatile exact live-run aggregate claims. |
Closes #206
Summary
User-facing value
First-time evaluators can now see that reports explain regressions with local baseline deltas, incident timeline evidence, and tool authority categories instead of only generic health or slow-run summaries.
Adoption rationale
This makes the post-v0.4.6 report model legible on the main public docs while keeping the positioning local-first and evidence-oriented.
Scope
No Go source, release, tag, package publish, npm, Homebrew, or external posting work.
Test plan
Safety checklist