2026-10-05 · CPH Network Reporting, CPH Pro Access
Adds a private lifetime Developer grant covering up to 15 explicitly activated owned sites, with included unlimited managed audio.
What changed
- Adds an explicit Developer license identity, a 15-site activation ceiling, lifetime access, no expiration and unlimited managed audio at a zero monthly service fee. Private grants are bound to the current canonical website.
- Uses a deployment-controlled owner registry with locked, atomic, append-only site allocation. Duplicate retries do not consume another slot and a sixteenth site is rejected. Reclaiming an activation requires a separately verified revocation workflow.
- Shows Developer status and allocated/remaining site capacity in the WordPress license settings. Rejects malformed, copied-to-another-site or revoked grants.
- Preserves legacy owner grants and paid customer plan terms. Cached customer responses must meet the same bounded validation as a fresh license response.
Verification
- Passed 82 new private grant checks, 51 existing reporter checks and 11 private Hub configuration checks; syntax validation passed.
- Passed 84 owner, invalid-cache and administrator-markup checks and 28 existing audio-client checks.
- Passed six registry tests, including real competing processes requesting the final activation slot, rejection of a sixteenth activation, atomic readback and private-file validation.
- Passed 26 isolated WordPress owner integration checks and 48 Hub regression checks with clean exit/stderr. The real private-file helper and license consumer validated the grant and administrator display; customer tables, Muse jobs, cron state, email and network calls remained unchanged.
- Every live deployment matched the reviewed package hashes and reread its effective private grant and Pro consumer under the actual PHP runtime account. The administrator output showed Developer, capacity and unlimited audio. Existing active-plugin options, OG settings and merchant flags were preserved.
- Verified the Free correction in the live PHP runtime and administrator output, then verified seven remaining Developer configurations and atomically reconciled the private registry while preserving allocation history. Fourteen internal registry checks passed, including revocation, released capacity, exact retries and prevention of unreviewed reactivation.
Rollout
Installed and verified on eight WordPress installations. Seven owned sites retain the shared lifetime Developer grant: seven of fifteen activations used, eight available, with unlimited managed audio at no monthly charge. One installation was subsequently corrected to Free at the owner’s request; its Developer and unlimited-audio entitlement were removed and its activation was released after verified revocation. Existing customer commerce and audio billing flags are unchanged. This entitlement does not install missing audio software.
Updating
- Back up the selected addon files and private owner configuration before deployment. Preserve the shared license identity, append-only allocation history, installation identifiers and existing product grants.
- Provision owner configuration outside every served directory with permissions readable only by the intended PHP runtime and deployment operator. Never include owner configuration or enrollment secrets in a distributed package.
- This release requires no customer order, paid subscription, payment connection or customer license conversion.
Scope and limitations
- The owned-site entitlement does not install missing audio software, start synthesis or guarantee audio delivery. Muse authentication, exclusive article checkout, content and legal eligibility, upload validation and completed-job locks remain in force.
- Unlimited refers to the managed-audio billing allowance; it does not remove concurrency, file-size, operational or security limits.
- Owner registration is controlled by the deployment operator. Public customer activation, payment and subscription terms are separate and unchanged.
- This scoped rollout does not enable reporting, launch the aggregate metrics site or add a new monitoring schedule.