Default radio profile crossover to off

docs/_javascript/firmware_picker.js

@@ -2145,11 +2145,11 @@
       section("Companion tempradio2: transmit on both", [
         { label: "Transmit on both", commands: ["set radio2.cross on"],
           text: "After setting tempradio2 to rxtx, run this to send new messages on both radio and tempradio2. rxtx enables transmission on the second profile; cross on enables copying between the two profiles." },
-        { label: "Default isolation", commands: ["set radio2.cross auto"],
-          text: "Keep ordinary local messages on radio and local LoRa OTA traffic on tempradio2. With auto, a permanent and a temporary profile remain isolated." },
+        { label: "Default isolation", commands: ["set radio2.cross off"],
+          text: "Keep ordinary local messages on radio and local LoRa OTA traffic on tempradio2. Off disables copying between profiles, including two permanent profiles." },
         { label: "Check", commands: ["get tempradio2", "get radio2.cross", "get radio2.status"],
           text: "Confirm tempradio2 is active in rxtx mode. TX=a,b reports primary and secondary transmit counts." },
-      ], "radio2.cross is saved and stays set after tempradio2 expires or the node reboots. Turning it on also allows OTA traffic to cross profiles. RX-only mode still prevents transmission on the second profile. Use Default isolation to restore auto when needed.");
+      ], "radio2.cross is saved and stays set after tempradio2 expires or the node reboots. Turning it on also allows OTA traffic to cross profiles. RX-only mode still prevents transmission on the second profile. Use Default isolation to restore off when needed.");
     }
     if (full || infrastructure) {
       toggle("Device power saving", "set powersaving", "get powersaving",

docs/_javascript/preset_test.js

@@ -431,8 +431,8 @@
       primaryCancel:
         "get tempradioat\ndel tempradioat all",
       companionCancelBefore:
-        "get tempradioat2\ndel tempradioat2 all\nset radio2.cross auto",
-      companionCancelDuring: "set tempradio2 off\nset radio2.cross auto",
+        "get tempradioat2\ndel tempradioat2 all\nset radio2.cross off",
+      companionCancelDuring: "set tempradio2 off\nset radio2.cross off",
       companionLeaveIn30:
         "set radio2.cross on\ndel tempradioat2 all\nset tempradio2 " +
         tuple + ",rxtx,30",

docs/firmware_picker.md

@@ -438,7 +438,7 @@ set radio2.cross on
 
 This copies new messages to both `radio` and `tempradio2`. The setting is saved,
 outlasts the temporary session and reboot, and also allows OTA traffic to cross
-profiles. **Default isolation** copies `set radio2.cross auto`; **Check** shows
+profiles. **Default isolation** copies `set radio2.cross off`; **Check** shows
 the temporary profile, crossing policy and per-profile transmit counters.
 See the [two-profile setup guide](radio_profiles.md#companion-messages-on-both-profiles).
 

docs/preset_test.md

@@ -293,7 +293,7 @@ clock</code></pre>
           <p class="preset-test-note">
             Crossing is saved independently and remains <code>on</code> after the
             temporary second profile ends. Restore its previous value after the
-            test; <code>auto</code> is the normal default.
+            test; <code>off</code> is the normal default.
           </p>
         </article>
       </div>
@@ -342,7 +342,7 @@ clock</code></pre>
           <pre><code data-command="companion-cancel-during"></code></pre>
           <button type="button" data-copy-command="companion-cancel-during">Copy restore commands</button>
           <p class="preset-test-note">
-            If <code>get radio2.cross</code> was not <code>auto</code> before the
+            If <code>get radio2.cross</code> was not <code>off</code> before the
             test, restore that recorded value instead.
           </p>
           <h4>Leave in 30 minutes</h4>
@@ -352,7 +352,7 @@ clock</code></pre>
             These commands clear any absolute second-profile schedule and give
             the test profile a fresh 30-minute lease. The saved second profile
             returns at expiry, but crossing remains <code>on</code>; afterward,
-            restore the value you recorded before the test (<code>auto</code> is
+            restore the value you recorded before the test (<code>off</code> is
             the normal default).
           </p>
         </article>

docs/radio_profiles.md

@@ -189,8 +189,8 @@ messages between the two profiles. `TX=a,b` reports primary and secondary
 transmit counts. Crossing also applies to OTA traffic.
 
 The crossing setting is saved and remains enabled after the temporary session
-ends or the node reboots. Run `set radio2.cross auto` to restore the default
-isolation between permanent and temporary profiles. The firmware picker's
+ends or the node reboots. Run `set radio2.cross off` to restore the default
+isolation between profiles. The firmware picker's
 Companion tempradio2 instructions include both choices and the status commands.
 
 ## Companion TX routing by contact or channel
@@ -806,7 +806,7 @@ set radio2.cross on
 set radio2.cross off
 ```
 
-| Active primary | Active secondary | `auto` (default) | `on` | `off` |
+| Active primary | Active secondary | `auto` | `on` | `off` (default) |
 | --- | --- | --- | --- | --- |
 | `radio` | `radio2` | Cross | Cross | Isolated |
 | `tempradio` | `tempradio2` | Cross | Cross | Isolated |
@@ -816,6 +816,9 @@ set radio2.cross off
 This table describes MeshCore profiles. A Meshtext secondary profile is
 always isolated, including with `radio2.cross on`.
 
+New configurations default to `off`. An explicitly saved `auto`, `on`, or `off`
+setting is preserved across firmware updates and reboots.
+
 These are the global rules used by Companion targets set to `auto`; an explicit
 contact/channel choice above overrides crossing for its own outbound packets.
 Ordinary crossing respects `rx`. The infrastructure-only `tx.reply ... force`