@inoku/lepan 0.7.67 → 0.7.69

package/README.md

@@ -112,6 +112,21 @@ already exist, use **My devices** on a paired phone to invite another device. An
 interrupted first claim must be resumed on the original phone with its original
 invitation. Ordinary `--upgrade` does not renew invitations.
 
+### Reconnect after forgetting the only phone
+
+Run `npx --yes @inoku/lepan@latest --recover-device Owner` on the computer hosting
+Leither, substituting the existing account name or user ID. Scan the displayed
+QR code to reconnect to that same account. This node-operator action preserves
+account keys, files, backups, and other devices. The reconnect invitation is
+private and expires in ten minutes; rerun the same command if it expires before
+being claimed. The account service briefly restarts, while Leither keeps running.
+Normal phone-to-phone invitations still require device-manager approval.
+
+First-account pairing prepares the file catalog before opening Files and adds
+`Getting started with LePan.txt` once. The guide can be renamed or deleted and is
+not duplicated when another phone joins. First setup also grants each account
+write access only to its own node staging directory when Leither requires it.
+
 An existing installation is backed up before replacement. The explicit `--upgrade` path requires the saved application and key-auth owner state before changing files, synchronizes the same published application MID, and does not rerun device or domain setup. This release intentionally does not migrate the earlier password-owner prototype. Application files are active only after Leither advances the application from `cur` to `last`; a publication timeout leaves the prior `last` version serving users.
 
 Source code and design documentation are maintained separately. No device key, identity bundle, PPT, publisher key, or node-specific application MID is included in these release assets.

package/USER_MANUAL.md

@@ -156,8 +156,11 @@ Within ten minutes of the invitation being printed:
 3. Enter **Your name** and a name for this device.
 4. Tap **Scan QR code** and point the phone at the terminal or saved image. You can also use **Paste node identity** or **Choose identity file**.
 
-The phone creates its own device key, claims the node, and opens your new, empty
-personal drive. You are now the node's first user and its **administrator**, and
+The phone creates its own device key, claims the node, and opens your personal
+drive after its file list is ready. Files contains **Getting started with LePan.txt**,
+a short guide to Files, Backups, connecting other phones, and keeping access to
+your account. It is added once per account; reconnecting a phone does not duplicate
+it, and deleting or renaming it does not cause it to return. You are now the node's first user and its **administrator**, and
 this phone is a **device manager**.
 
 You can close the setup screen without pairing to look around the app. Tapping an
@@ -360,12 +363,26 @@ What remains true:
 - **Other users are unaffected.** Their drives and devices keep working.
 - **Recovery needs the node operator.** Contact whoever runs the node.
 
-For node operators: LifeDrive does not yet include a repair command that binds a
-new device to an existing user. The setup invitation (`--household`) only works
-on a node that has no users, so it cannot be used for this. Until the repair
-command exists, recovering a user who has lost every device needs help from the
-LifeDrive maintainers. Do not delete or edit `.lifedrive-household/` to try to
-work around it: it holds every user's authority and the authorization journal.
+For node operators: run this on the computer hosting Leither, replacing `Owner`
+with the existing account name (quote names containing spaces), or its exact user
+ID if names are duplicated:
+
+```bash
+npx --yes @inoku/lepan@latest --recover-device Owner
+```
+
+The account service briefly stops to issue a private reconnect invitation, then
+starts again before the QR code is shown. Scan it under **Settings → Set up users**
+on the phone. It enrolls a new device manager into the same account; account keys,
+Files, Backups, and other devices are preserved. A reconnect invitation expires
+in ten minutes unless that phone has already begun claiming it. Treat it as a
+private account-access key. An expired, unclaimed code can be replaced by rerunning
+the same command. Once connected, remove access for the forgotten device from
+**My devices**. Leither itself stays running.
+
+The node operator's local access authorizes this recovery; ordinary device
+invitations still require approval from a paired device manager. `--household`
+remains first-account setup and cannot replace an existing account.
 
 ### 5.4 Prevent lockout
 

package/bin/lifedrive.js

@@ -42,7 +42,7 @@ async function showPairingCode(resultPath) {
   // The child writes this only after setup succeeds. Never scrape its output:
   // it can contain node keys as well as the mobile device's pairing identity.
   const pairing = JSON.parse(fs.readFileSync(resultPath, "utf8"));
-  if (pairing.version !== 1 || !["lifedrive-device-identity", "lifedrive-node-setup"].includes(pairing.type)) {
+  if (pairing.version !== 1 || !["lifedrive-device-identity", "lifedrive-node-setup", "lifedrive-user-identity"].includes(pairing.type)) {
     throw new Error("Unsupported pairing data");
   }
   const directory = fs.readFileSync(`${resultPath}.directory`, "utf8");
@@ -52,7 +52,7 @@ async function showPairingCode(resultPath) {
   // The node enforces expiry and returns account details after a successful claim.
   // Keep the full invitation in the import file, and leave legacy identities intact.
   // iOS still requires certificate_sha256 even when Leither transport uses a key.
-  const qrPayload = pairing.type === "lifedrive-node-setup"
+  const qrPayload = pairing.type !== "lifedrive-device-identity"
     ? JSON.stringify(Object.fromEntries([
       "type", "version", "app_id", "node_id", "endpoint", "transport",
       "transport_key", "certificate_sha256", "request_id", "secret",
@@ -65,12 +65,12 @@ async function showPairingCode(resultPath) {
   // Keep a private copy even when QR generation succeeds.
   fs.writeFileSync(identityPath, payload, { flag: "wx", mode: 0o600 });
   const options = { errorCorrectionLevel: "M", margin: 4, scale: 8 };
-  const privacyNote = pairing.type === "lifedrive-node-setup"
+  const privacyNote = pairing.type !== "lifedrive-device-identity"
     ? "Keep it private. This invitation expires ten minutes after creation."
     : "This contains your device private key. Keep it private and delete it after pairing.";
   const renewalHint = pairing.type === "lifedrive-node-setup"
     ? "\nInvitation expired? Run this again on the node:\n  npx --yes @inoku/lepan@latest --household\n"
-    : "";
+    : pairing.type === "lifedrive-user-identity" ? "\nInvitation expired? Run the same reconnect command again on this computer.\n" : "";
   let modules;
   try {
     const QRCode = require("qrcode");
@@ -153,6 +153,7 @@ function windowsArguments(values) {
   const valueOptions = new Map([
     ["--leither-root", "-LeitherRoot"],
     ["--storage-max-gb", "-StorageMaxGB"],
+    ["--recover-device", "-RecoverDevice"],
   ]);
   const switches = new Map([
     ["--no-install-leither", "-NoInstallLeither"],

package/dist/lifedrive-bundle.tar.gz

@@ -1,4 +1,4 @@
 [diffend] Oversized file quarantined before diffing.
 name: package/dist/lifedrive-bundle.tar.gz
-size: 44139682 bytes
-sha256: 2173717546eb881f72dce0fdd7a5a6727bfc5286b4c23f948528b9d8f1a2fde8
+size: 44204388 bytes
+sha256: b1d6c652dbda51b836a30778abb722774fd28559373cee7efe2670991d7297b7

package/dist/lifedrive-bundle.tar.gz.sha256

@@ -1 +1 @@
-2173717546eb881f72dce0fdd7a5a6727bfc5286b4c23f948528b9d8f1a2fde8  lifedrive-bundle.tar.gz
+b1d6c652dbda51b836a30778abb722774fd28559373cee7efe2670991d7297b7  lifedrive-bundle.tar.gz

package/dist/lifedrive-install.ps1

@@ -8,6 +8,7 @@ param(
     [switch]$LeitherService,
     [switch]$Upgrade,
     [switch]$Household,
+    [string]$RecoverDevice,
     [switch]$Help
 )
 
@@ -28,6 +29,7 @@ Windows options:
   --leither-service         Configure Leither startup only.
   --upgrade                 Upgrade an existing Windows LePan installation.
   --household               Set up household users or renew an unclaimed setup invitation.
+  --recover-device USER     Reconnect a phone to an existing account name or user ID.
 
 Run Windows Terminal or PowerShell as Administrator. Windows setup supports
 native x64 Windows 10/11 and Windows Server; WSL and Git Bash are not required.
@@ -35,6 +37,10 @@ native x64 Windows 10/11 and Windows Server; WSL and Git Bash are not required.
 }
 
 if ($Help) { Show-Usage; return }
+if ($RecoverDevice) {
+    if ($Upgrade -or $LeitherService) { throw "Use --recover-device separately from --upgrade and --leither-service." }
+    $Household = $true
+}
 if ($Upgrade -and $LeitherService) { throw "Use -Upgrade and -LeitherService separately." }
 if ($StorageMaxGB -lt 0) { throw "Leither storage must be a positive whole number of gigabytes." }
 if ($StorageMaxGB -eq 0 -and $env:LIFEDRIVE_STORAGE_MAX_GB) {
@@ -469,7 +475,7 @@ if ($Upgrade) {
     return
 }
 try {
-    & (Join-Path $root "lifedrive-identity\setup-node.ps1") -LeitherRoot $root
+    & (Join-Path $root "lifedrive-identity\setup-node.ps1") -LeitherRoot $root -RecoverDevice $RecoverDevice
 } catch {
     if ($identityTaskStopped) {
         try { Start-ScheduledTask -TaskName $identityTaskName } catch {}

package/dist/lifedrive-install.sh

@@ -12,6 +12,7 @@ LEITHER_SERVICE_ONLY=0
 LEITHER_SERVICE_BOOTSTRAPPED=0
 HOUSEHOLD_CONFIG=""
 HOUSEHOLD_SETUP=0
+RECOVER_DEVICE=""
 STORAGE_MAX_GB="${LIFEDRIVE_STORAGE_MAX_GB:-}"
 setup_command_args=()
 setup_arg_count=0
@@ -29,6 +30,7 @@ Installer options:
   --release-base URL        Alternate GitHub Release asset base URL.
   --upgrade                 Upgrade an existing LePan without changing device authorization.
   --household              Set up household users or renew an unclaimed setup invitation.
+  --recover-device USER    Reconnect a phone to an existing account, using its name or user ID.
   --household-config FILE   Install mobile-led household setup using a private service configuration.
 
 Setup options are forwarded to lifeDrive-setup.sh. Common examples:
@@ -53,6 +55,12 @@ while (( $# )); do
     --household)
       HOUSEHOLD_SETUP=1
       ;;
+    --recover-device)
+      shift
+      [[ $# -gt 0 && -n "$1" && "$1" != --* ]] || { echo "--recover-device requires an existing account name or user ID" >&2; exit 2; }
+      RECOVER_DEVICE="$1"
+      HOUSEHOLD_SETUP=1
+      ;;
     --household-config)
       shift
       [[ $# -gt 0 && -f "$1" ]] || { echo "--household-config requires a configuration file" >&2; exit 2; }
@@ -103,6 +111,10 @@ while (( $# )); do
   shift
 done
 
+if [[ -n "$RECOVER_DEVICE" ]] && (( operation_count )); then
+  echo "Use --recover-device separately from --upgrade and device-management options." >&2
+  exit 2
+fi
 if (( operation_count > 1 )); then
   echo "Choose only one of --upgrade, --add-device, --list-devices, or --revoke-device." >&2
   exit 2
@@ -942,7 +954,7 @@ chmod 700 "$LEITHER_WORKDIR/lifeDrive/"*.sh
 export LIFEDRIVE_WORKDIR="$LEITHER_WORKDIR"
 export LIFEDRIVE_LEITHER_PATH="$LEITHER_WORKDIR/Leither"
 if (( HOUSEHOLD_SETUP )); then
-  /bin/bash "$LEITHER_WORKDIR/lifedrive-identity/setup-node.sh" "$LEITHER_WORKDIR"
+  /bin/bash "$LEITHER_WORKDIR/lifedrive-identity/setup-node.sh" "$LEITHER_WORKDIR" "$RECOVER_DEVICE"
   exit 0
 fi
 if [[ -n "$HOUSEHOLD_CONFIG" ]]; then

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@inoku/lepan",
-  "version": "0.7.67",
+  "version": "0.7.69",
   "description": "Install LePan and its Leither runtime on Linux, macOS, or Windows",
   "os": [
     "linux",