Clarify grandfathered v5 licensing docs

docs/PULSE_PRO.md

@@ -17,7 +17,7 @@ User-facing plans map to internal tiers as follows:
 - **Cloud**: `msp` or `enterprise`
 
 Notes:
-- `lifetime` keeps the same runtime feature set as Pro, but lifetime and grandfathered recurring legacy entitlements remain uncapped for monitored systems and guest access.
+- `lifetime` keeps the same runtime feature set as Pro, but lifetime and grandfathered recurring legacy entitlements remain uncapped for monitored systems and guest access. Other migrated legacy paid installs can preserve monitored-system continuity without becoming uncapped.
 - Items marked **Cloud*** require the `enterprise` tier rather than the base `msp` tier.
 - If you are self-hosting, you can use capability keys and `GET /api/license/features` to discover exactly what is active in your instance.
 
@@ -59,6 +59,7 @@ Runtime rules:
 
 Migration policy:
 - Legacy recurring Pulse Pro subscriptions already active before the public v6 pricing cutover keep their grandfathered recurring price and uncapped monitored-system and guest capacity until cancellation.
+- Supported legacy paid v5 migrations outside that recurring grandfathered path can retain a monitored-system continuity floor for the migrated install where needed, but that continuity path is not the same as an uncapped entitlement.
 - Existing free users above the new Community cap are not hard-broken on rollout day.
 - During grace, existing monitoring keeps working.
 - During grace, only new counted-system additions are blocked until the user removes systems or upgrades.
@@ -69,6 +70,7 @@ Migration policy:
 |---|---|---|
 | Legacy recurring subscriber from a v5 or earlier Pulse Pro monthly/annual plan, already active before the public v6 pricing cutover | The install can migrate into the v6 activation model without forcing a repurchase. | The existing recurring price stays in place and monitored-system plus guest capacity remain uncapped while the subscription remains continuously active. |
 | Existing lifetime license holder | The license remains valid through the v6 licensing transition. | Lifetime remains permanently valid and monitored-system plus guest capacity stay uncapped. |
+| Legacy paid v5 license migrated into v6 outside the recurring grandfathered path | The install can still exchange into the v6 activation model. If its existing monitored estate exceeds the exchanged plan limit, the migrated install can retain a monitored-system continuity floor for that install. | The continuity floor preserves the existing migrated estate where needed, but it is not an uncapped entitlement. |
 | Former recurring subscriber who already canceled or later lapses/cancels | A later return is treated as a new paid purchase, not as a grandfathered renewal. | The old grandfathered price and uncapped capacity do not resume automatically; current public v6 pricing and caps apply. |
 | New self-hosted v6 purchase | The purchase uses the current Relay / Pro / Pro+ self-hosted plans. | Current public v6 monitored-system and guest caps apply. |
 

docs/UPGRADE_v6.md

@@ -123,14 +123,15 @@ If you are upgrading an existing free instance that already exceeds the new Comm
 
 #### v5 License Migration
 
-Pulse v6 uses the activation/grant model for active licensing, but it can migrate valid Pulse v5 Pro and Lifetime JWT-style licenses.
+Pulse v6 uses the activation/grant model for active licensing, but it can migrate valid Pulse v5 paid JWT-style licenses, including legacy Pro and Lifetime licenses.
 
 - If you upgrade an existing v5 instance and Pulse finds a persisted v5 license with no v6 activation state yet, v6 will try to auto-exchange it on startup.
 - If auto-exchange cannot complete, your old key is left in place and the instance will prompt you to retry activation manually.
 - In the v6 license panel, you can paste either:
   - a Pulse v6 activation key, or
-  - a valid Pulse v5 Pro/Lifetime license key, which Pulse will try to exchange automatically
+  - a valid Pulse v5 paid license key, which Pulse will try to exchange automatically into the v6 activation model
 - If the exchange service cannot complete the migration, retry from the v6 license panel or use the self-serve retrieval flow to fetch the current v6 activation key. Email is only a backup copy of that key.
+- The exchanged v6 entitlement depends on the original cohort. Lifetime, active pre-cutover recurring Pro, and other migrated legacy paid installs do not all land on the same monitored-system policy.
 - Legacy recurring Pulse Pro subscriptions already active before the public v6 pricing cutover keep their grandfathered recurring price and uncapped monitored-system and guest capacity until cancellation. If they cancel and later return, current v6 pricing and limits apply.
 
 #### Paid Upgrade Truth Table
@@ -139,6 +140,7 @@ When an existing paid user asks what changes for them specifically, use this rul
 
 - Legacy recurring Pulse Pro subscriptions from v5 or earlier that were already active before the public v6 pricing cutover keep their current recurring price and uncapped monitored-system plus guest capacity while the subscription remains continuously active.
 - Existing lifetime customers remain permanently valid and uncapped.
+- Legacy paid v5 licenses migrated into v6 outside the recurring grandfathered path can retain a monitored-system continuity floor for the migrated install where needed, but that continuity path is not the same thing as an uncapped entitlement.
 - Former recurring customers who already canceled, or who cancel and later return, do not resume the old grandfathered pricing or uncapped capacity automatically; they re-enter on current public v6 pricing and limits.
 - New self-hosted v6 purchases use the current Relay / Pro / Pro+ plan caps.
 

docs/releases/V6_RC_OPERATOR_SUPPORT_PACK.md

@@ -68,6 +68,10 @@ Use this cohort breakdown:
   capacity while the subscription remains continuously active.
 - Existing lifetime customers:
   remain permanently valid and uncapped.
+- Legacy paid v5 licenses migrated into v6 outside the recurring grandfathered
+  path:
+  can retain a monitored-system continuity floor for the migrated install where
+  needed, but that continuity path is not the same as an uncapped entitlement.
 - Former recurring subscribers who already canceled or later lapse:
   any later return uses current public v6 pricing and caps rather than
   resuming the old grandfathered terms.