# ClaimPrism 0.10.0 Commercial Release Readiness

This checklist is the final gate before any public 0.10.0 tag, Freemius deployment or commercial publication.

The WordPress.org-submitted `0.6.0` package remains separate and frozen while under review unless the WordPress Plugins Team explicitly requests a change.

## Automated gates

- [x] Plugin header and runtime version are 0.10.0.
- [x] WordPress readme Stable tag is 0.10.0.
- [x] Repository CI builds an installable 0.10.0 package.
- [x] WordPress + WooCommerce integration suite passes on packaged plugin.
- [x] Official WordPress Plugin Check passes in current CI.
- [x] Free-package stripping regression protects premium-only implementation boundaries.
- [x] Governance foundations are covered by focused runtime/integration tests where implemented.

## Commercial UX gates already validated

- [x] Dark ZEODEC dashboard and Claim Governance visual alignment validated.
- [x] First-run onboarding validated on a fresh WordPress site.
- [x] Starting the first scan removes the first-run onboarding and returns to the normal dashboard state.
- [x] Free mode and Pro licensing state were exercised locally during upgrade-path validation.
- [x] Free-to-Pro value panel validated after the first-run state.
- [x] Zero-findings post-scan empty state no longer instructs the user to run a first scan.
- [x] Review Priority wide-screen layout gap corrected and visually validated.

## Customer documentation gates

- [x] `readme.txt` describes current Free and Pro capabilities without certification/compliance claims.
- [x] `README.md` reflects the current 0.10.0 governance architecture and Commercial 1.0 state.
- [x] `docs/GETTING-STARTED.md` covers installation, first scan, findings, Free/Pro boundaries and the Pro governance workflow.
- [x] Product-state documentation records the Commercial 1.0 onboarding and upgrade-path work.

## Manual gates still required before commercial deployment

These checks are intentionally not marked complete unless they have been performed against the final commercial candidate or are directly covered by prior targeted validation.

- [ ] Clean install of the final 0.10.0 commercial ZIP on a fresh WordPress site after the final candidate is selected.
- [ ] Final activation and representative scan complete without PHP warnings or fatal errors on that candidate.
- [ ] Upgrade from the currently deployed/previous Pro build preserves findings, review state, monitoring, evidence and schedule configuration.
- [ ] Deactivate/reactivate on the final candidate preserves stored workflow data and resumes scheduling safely.
- [ ] Administrator retains full ClaimPrism access.
- [ ] ClaimPrism Manager retains operational controls and reviewer assignment without broad WordPress administration.
- [ ] ClaimPrism Reviewer sees only assigned workflow items and cannot reassign findings.
- [ ] Reviewer status/note changes remain visible to Manager/Admin with append-only history.
- [ ] WooCommerce product scan detects the known regression fixture on the final candidate and the dashboard remains usable.
- [ ] Final generated Free package remains useful and exposes no Pro-only workflow controls.
- [ ] Freemius licensing, checkout/upgrade and licensed Pro activation are smoke-tested on the final deployment candidate.

## Release decision boundary

Passing this checklist does not itself authorize publication. Public tag/release creation, Freemius commercial deployment and any release communication require an explicit CEO/Product Owner release decision.

Do not replace or mutate the WordPress.org `0.6.0` submission while its review is pending unless the Plugins Team requests a change.