@msn-control/liftoff 0.5.1 → 0.6.1

package/docs/existing-repositories.md

@@ -68,7 +68,11 @@ liftoff update
 liftoff update --apply
 ```
 
-Update is a read-only drift check unless `--apply` is present.
+In an interactive terminal, plain update reports drift and impact, then asks
+with a default of No before applying safe managed changes. Local or user-owned
+conflicts require a separate default-No overwrite decision. Redirected and
+JSON checks remain read-only and prompt-free; use `--apply` for explicit
+automation consent.
 
 ## Existing non-Liftoff application
 

package/docs/safety-and-consent.md

@@ -50,24 +50,39 @@ Individual project files use temporary-file replacement. Initialization keeps
 backups for replaced files and records created files and directories. A handled
 merge failure restores or removes those entries in reverse order.
 
-`liftoff update --apply` preflights all affected paths and applies generated
-file, move, delete, and manifest mutations as one rollback-capable
-transaction. Schema upgrades are committed only after the other mutations
-succeed. A corrected retry converges from the restored state.
+An accepted interactive update or `liftoff update --apply` preflights all
+affected paths and applies generated file, move, delete, and manifest mutations
+as one rollback-capable transaction. Schema upgrades are committed only after
+the other mutations succeed. A corrected retry converges from the restored
+state.
 
 If automatic rollback itself cannot safely restore a path because another
 process changed it, Liftoff reports the incomplete rollback rather than
 overwriting unknown bytes.
 
+Update snapshots exist only for rollback after a failed transaction. Liftoff
+does not retain them as backups after success.
+
 ## Update ownership
 
-`liftoff update` is read-only by default:
+Plain `liftoff update` always reports drift before any write:
 
 - Clean generated files remain unchanged.
-- New, missing, untouched-upgrade, and clean-move states can be applied.
+- In an interactive terminal, new, missing, untouched-upgrade, clean-move, and
+  recorded-state changes are summarized and offered through a default-No
+  confirmation.
+- With redirected input or output, or with `--json`, update remains a
+  prompt-free read-only check unless `--apply` is explicitly supplied.
 - Developer edits that also differ from the current template are conflicts.
-- Conflicts are skipped unless `--apply --force` is explicitly supplied.
+- Safe-update consent does not authorize conflicts. Interactive conflicts are
+  listed by portable relative path and require a separate default-No overwrite
+  confirmation; automation uses `--apply --force`.
 - Orphans are reported and left on disk for manual review.
+- Dependency definitions may be updated, but update never installs
+  dependencies.
+
+All interactive decisions are collected before preflight or mutation.
+Declining the safe update changes nothing and leaves drift exit code 2.
 
 Power Apps reconciliation reads only the packaged immutable starter. It does
 not fetch the upstream repository. Workload kind and user-edited starter

package/docs/troubleshooting.md

@@ -67,14 +67,21 @@ hand-edited unsafe path.
 
 ## Update reports conflicts or orphans
 
-`liftoff update` does not write. Review the report:
-
-- Apply safe changes with `liftoff update --apply`.
-- Developer conflicts remain untouched unless you explicitly use
-  `liftoff update --apply --force`.
+In an interactive terminal, `liftoff update` shows an impact summary and asks
+before applying safe managed changes. The default answer is No.
+
+- Local or user-owned conflicts are listed separately and require their own
+  default-No overwrite confirmation.
+- With redirected input or output, review the report and apply safe changes
+  with `liftoff update --apply`.
+- For prompt-free conflict replacement, use `liftoff update --apply --force`
+  only after reviewing every listed path.
 - Orphans are never deleted automatically.
+- Update reports dependency-definition impact but does not install
+  dependencies.
 
-Commit local work before applying when possible.
+Commit or copy local work before overwriting. Transaction rollback protects a
+failed update, but Liftoff keeps no backup after success.
 
 ## Power Apps dependencies or CLI are missing
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@msn-control/liftoff",
-  "version": "0.5.1",
+  "version": "0.6.1",
   "description": "Interactive CLI for governed GenAI, API, and Power Apps code app projects.",
   "type": "module",
   "license": "GPL-3.0-only",