Validation and release readiness · Docs

Check the delivered foundationLink to section

Starter Pro connects account creation, workspace onboarding, invitations and a first project to a persisted application. Its validation follows those journeys.

Packaging

Standalone buyer package

The exported ZIP is checked outside the monorepo before packaging succeeds.

Frozen installation, empty-database migrations, unit tests and production build
First-user browser journey through accounts, workspaces and project work
Your acceptance: install the delivered release with your own environment

PostgreSQL regressions

Billing reconciliation

Signed events use a simulated provider to check persisted subscription and invoice behavior.

Simultaneous, duplicate and reordered events
Failed payments, cancellations and replay after failure
Your acceptance: validate your Stripe sandbox, webhook destination and offered plans

Browser coverage

Product and interface journeys

Onboarding, live workspace access, task/comment persistence and account flows are exercised together.

English/French, Customize, mobile/desktop, both themes and accessibility
Your acceptance: check domain rules, permissions, content and branding

Environment checks

Operational recovery

Configuration diagnostics, health/readiness and a backup/restore drill use synthetic data.

Your acceptance: configure monitoring and alert destinations
Verify accessible, recoverable production backups with your operator

What automated coverage establishes

The required CI gate waits for source validation and the selected browser suite. A skipped or missing selected check cannot make the gate pass. Provider interception keeps these tests independent of live email and payments. It does not establish live delivery or a successful real transaction. Your launch acceptance includes your own email and Stripe configuration.

How the packaging gate worksLink to section

Extract and installLink to section

Export the standalone source and extract it outside the monorepo. Install the supplied lockfile without relying on workspace dependencies.

Migrate and compileLink to section

Apply the committed migrations to an empty disposable database, run unit checks and compile the extracted production application.

Complete a first-user journeyLink to section

Exercise registration, verification, sign-in, workspace creation, invitation and project work. Reload to verify persistence, then remove the temporary database and retain the local validation evidence.

Know what you receiveLink to section

The ZIP includes a standalone manifest, lockfile, reviewed dependency patches, Prisma migrations and buyer guides. PYCOLORS_RELEASE.json records its version, source commit and source-file hashes. Save it with the original delivery before customizing the application. Intentional edits naturally change file hashes.

The included docs/quickstart.md, docs/customization.md, docs/upgrading.md, docs/operations.md and docs/support.md remain available with your source.

Billing ownership and limits

Application billing belongs to the user account. Workspace creation and resource quotas are configurable and uncapped by default. Organization-owned billing requires its own ownership and migration design. The source licence, your application's subscription and an agreed implementation service are distinct purchases.

Continue your setupLink to section

Included scopeReview the source and product workflows.Billing acceptancePrepare your Stripe sandbox checks.Production operationsConnect monitoring and rehearse recovery.Implementation and supportDefine the scope and handover of an engagement.