feat(settings): add the Add OTP, Add code and Manage entry forms with a PIN queue for locked entries

The full phone settings form (README 10.2) and its processing (10.3) as one
resumable job: Import, Add OTP, Add code, Manage, then the About fields.
Forms are applied only when their switch is on, cleared afterwards (secret
first; only the secret after a problem), deduplicated by keyed hash, and
report into their Result field and the results screen.

- Add OTP validates per README 10.4; Add code runs the real encoder
  (CodeCheck, a job for 2D codes) and caches 2D codes on the way in.
- Manage entry: edit, move, require/drop PIN, replace, counter, delete.
  Changes to locked entries are sealed under "q" and applied only after
  the PIN is entered under "Phone changes" in the menu.
- About: catalog (800 characters max), version, storage use.
- "Encrypt names" now applies to new and existing entries.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

1 files changed, 19 insertions, 0 deletions

diff --git a/source/storage/Vault.mc b/source/storage/Vault.mc
index 46c8de2..88054e0 100644
--- a/source/storage/Vault.mc
+++ b/source/storage/Vault.mc
@@ -31,6 +31,9 @@ class Vault {
     var lockout as Lockout;
     // The "Erase locked entries after 10 wrong PINs" setting (off by default).
     var eraseAfterFailures as Boolean = false;
+    // The "Encrypt names" setting: new entries keep their names in the
+    // encrypted part (existing ones are converted by AboutScan).
+    var encryptNames as Boolean = false;
 
     private var _store as Persist.Backend;
     private var _meta as Dictionary<Application.Storage.KeyType, Application.Storage.ValueType>;
@@ -126,6 +129,7 @@ class Vault {
             throw new VaultError(VaultError.LIMIT, "at most " + MAX_ENTRIES + " entries");
         }
         entry.id = newId();
+        entry.namesEncrypted = encryptNames;
         entry.fingerprint = keyManager.fingerprint(entry);
         if (entry.created == 0) {
             entry.created = Clock.nowUnix(0);
@@ -156,6 +160,21 @@ class Vault {
         _store.deleteValue("x." + entry.id); // the cached matrix may be stale
     }
 
+    // Re-seal an entry with or without encrypted names ("Encrypt names").
+    // Nothing else changes, so the barcode cache stays. Throws NOT_FOUND,
+    // LOCKED, DAMAGED or FULL.
+    function setNamesEncrypted(id as String, encrypted as Boolean) as Void {
+        var entry = open(id);
+        entry.namesEncrypted = encrypted;
+        try {
+            write("e." + id, seal(entry));
+        } catch (e instanceof VaultError) {
+            entry.wipeSecrets();
+            throw e;
+        }
+        entry.wipeSecrets();
+    }
+
     // ---- Encoded barcode cache (README 12.2) -----------------------------
 
     // Store an encoded matrix for a code entry, sealed with the entry's own