R-204 item 3: a restore says what it restored, and what it did not (v0.198.0)

mode=unit restores the recovery unit — the app's definition, configuration
and database dumps — and NOT the customer's own files: RestoreOffboxScratch
passes --include <unit path> and the userdata in the same snapshot is excluded
by it. The outcome was one sentence for both modes and named neither scope,
so on the last step of a disaster recovery the customer was told the app had
been restored after the thing they were looking for had not been.

restoreScratchOutcomeMsg states what came back, what did not, and the next
step that gets it. The wizard's intent card states its scope before the choice.
The full-restore size gate is untouched and pinned as unchanged; the default
stays unit, since all three wizard forms set mode explicitly.

controller/internal/web/templates/backups_restore_wizard.html

@@ -74,8 +74,12 @@
      harmless first, irreversible-looking last. -->
 
 <div class="settings-card">
-    <h3>1. Ellenőrzés külön mappába</h3>
-    <p>A mentés tartalma egy külön ellenőrző mappába kerül — az élő adataid nem változnak.</p>
+    <h3>1. Ellenőrzés külön mappába (beállítások és adatbázis)</h3>
+    <!-- R-204 item 3: this card's scope is stated BEFORE the choice, not only in the outcome. It
+         restores the recovery unit only; the customer's own files stay in the backup. Saying „a
+         mentés tartalma" here was how a disaster-recovery customer chose the one intent that does
+         not return their documents. -->
+    <p>Az alkalmazás beállításait és adatbázisát hozza vissza egy külön ellenőrző mappába. A saját fájljaidat (dokumentumok, képek, feltöltések) <strong>nem</strong> hozza vissza — azokhoz a 3. pont teljes visszaállítása kell. Az élő adataid nem változnak.</p>
     <div class="form-actions">
         <form method="POST" action="/backup/offbox/restore">{{.CSRFField}}
             <input type="hidden" name="app" value="{{.App}}">