Release-control record for build proof, source context hygiene, runtime entry, environment checks, and post-deployment smoke review.
Platform owner access remains routed through the portal chooser before opening any workspace.
The deployment package excludes generated archives, local dependency folders, prior build output, audit debris, and private environment files while preserving public assets, route mirrors, verifiers, and documentation required by release checks.
The build gate runs repository hygiene, export integrity, store contract, public language, login, auth entry, portal integrity, upload/settings/connections, public banner, Justice For All, public filing, and ChatGPT connector checks before production build.
The application package builds for the standalone runtime entry and starts through the packaged server with the assigned port.
Active paid seats open through the portal chooser and preserve settings, connections, recovery, reports, exports, and privacy scope labels.
Deployment interruption handling is documented with a shortest-path recovery ladder, verification commands, and owner review points before another release attempt.
Portal chooser opens as the stable post-access destination for workspace selection.
Owner and paid-seat workspace selection remains available after sign-in.
Launch proof remains available before onboarding users.
Enterprise gates remain visible to the owner account.
Operations center remains available for incident and onboarding review.
Pro Se primary workspace opens through the paid-seat route family.
Attorney primary workspace opens through the paid-seat route family.
Family Communications protected workspace opens through the paid-seat route family.
Public conversion remains focused on active paid seats.
Public Justice For All route lock remains preserved.
Run the build-gate verifier and the paid-seat launch verifier before deployment.
Pass signal: Both verification commands complete cleanly before any release command is run.
Confirm generated output, local dependency folders, prior archives, and private environment files are not included in the deployment context.
Pass signal: The package contains source, scripts, docs, public assets, and required configuration examples only.
Treat source import warnings as release blockers until they are patched or explicitly accepted by the verifier contract.
Pass signal: Build logs show no unresolved route import warning and no missing verifier input.
After release, open secure access, portal chooser, active paid seats, account readiness, and public conversion routes.
Pass signal: Each route opens without login loops, empty dead ends, hidden settings, or institutional promotion in paid-seat navigation.
Open connections and recovery surfaces for Pro Se, Attorney, and Family Communications before inviting users.
Pass signal: Staged imports, destination controls, settings export, and interrupted-work recovery remain visible.
Review dependency installation, package lock integrity, source context size, and private file exclusions before retrying.
Proof: Dependency install completes from a clean package without requiring local cache state.
Patch the concrete route import/export contract and rerun the build gate before packaging again.
Proof: The route compiles without warning and the affected route remains in the route inventory.
Confirm successful sign-in targets the portal chooser and that the login route cannot be used as a next destination.
Proof: Auth entry and portal access verifiers pass.
Restore the paid-seat operational surfaces before onboarding users.
Proof: The paid-seat launch verifier confirms settings, connections, staged import, and recovery contracts.
Owner-facing control record for onboarding support, access recovery, import recovery, output review, and release interruption handling.
Use the portal chooser as the recovery point for users who reach the wrong workspace or return from a stale link.
Smoke the primary workspace and the settings/connections/recovery path before marking the account ready.
Keep records staged until the user confirms destination, scope, and merge intent.
Owner-facing record for the paid-seat release package, controlled configuration notes, responsive review, and final verification path.
Application source, public assets, route families, shared utilities, package manifest, lockfile, verifier scripts, and configuration examples remain in the release package.
Pro Se, Attorney, and Family Communications stay active for paid onboarding with settings, connections, recovery, reports, and export surfaces preserved.
Judicial Edition, Justice, Clerk, Judge, Prosecutor, Defender, and Law Court surfaces remain compatible and separated from active MRR navigation.
Production service URLs, allowed accounts, session secret, OAuth redirect values, and provider keys must be supplied through the deployment environment before release.
Deployment preflight verifies required values and reports optional provider configuration separately.
Google and Microsoft entries remain safe when provider configuration is unavailable, and Google local-origin handling avoids invalid 0.0.0.0 redirects during local review.
Login and Google SSO origin verifiers protect the post-login portal chooser contract.
Imported material stays staged until a person confirms destination, scope, and merge intent before promotion into a matter.
Paid-seat connections and recovery verification protects staged import review and recovery controls.