K2GO-386 docs(app-backstop): fix stale debug-receiver Javadoc after the reorient

The debug hook doc still described the old stop-and-stay-down path (set
desired=DOWN, box stays down). After the L3b reorient the debug hook runs the
FORCED path: it always CONTAINs, reaps and reclaims, then leaves desired=UP and
lets the reconciler relaunch the box. It never advances the escalation count.
Correct the class Javadoc to match. Device-verified on HD1901.

Author: luisguzman-adfa

controller/app/src/debug/java/org/appdevforall/k2go/diskguard/debug/DebugDiskGuardReceiver.java

@@ -9,8 +9,8 @@
 
 /**
  * DEBUG-ONLY. K2GO-386 device-verify hook. Forces one disk-guard check with an injected floor so the
- * full protective path (set desired=DOWN → reap the box → reclaim the runaway log → notify) can be
- * verified on device WITHOUT first filling ~58 GB. Lives in src/debug, so it never ships in release.
+ * protective path (reap the box -> reclaim the runaway log -> restart) can be verified on device WITHOUT
+ * first filling ~58 GB. Lives in src/debug, so it never ships in release.
  *
  * <p>Exported (it is the whole point — an adb-reachable surface, unlike the app's non-exported
  * services), mirroring {@link org.appdevforall.k2go.delivery.debug.DebugDeliveryReceiver}. A huge
@@ -23,8 +23,10 @@
  *   --el floor_bytes 999999999999
  * </pre>
  *
- * Watch it act in logcat: {@code adb logcat -s K2Go-DiskGuard}. Because it sets desired=DOWN, the box
- * stays down after the reap; re-enable the server from the app to bring it back.
+ * Watch it act in logcat: {@code adb logcat -s K2Go-DiskGuard}. The debug hook runs the FORCED path,
+ * which always CONTAINs: it reaps and reclaims, then leaves the server desired=UP and asks the
+ * reconciler to relaunch a fresh box. It never advances the real escalation count, so repeated
+ * triggers cannot stop the box.
  */
 public final class DebugDiskGuardReceiver extends BroadcastReceiver {