Constrain restore installation to session root

docs/internal/command-restore.md

@@ -62,6 +62,9 @@ Execution order and safety:
 - manifest replacement is validated before rename;
 - each committed object is verified against its declared checksum, size, and
   generation before installation;
+- installation reopens the selected session root, creates only validated
+  missing directory components with workspace modes, and rejects symlinked or
+  non-regular ancestors and leaves before replacement;
 - a committed manifest already verified during discovery is retained for the
   matching restore action and revalidated before installation, avoiding a
   second body transfer;

docs/internal/workspace.md

@@ -74,6 +74,8 @@ syntax and exact deletion scope belong in [CLI](../cli.md#clean) and
 - campaign-aware session root is mandatory.
 - manifest-driven stage state is durable across runs.
 - cleanup guardrails prevent destructive root/out-of-scope deletion.
+- restore installation is confined to validated relative paths beneath the
+  selected session root.
 - ordinary workspace paths retain group-writable directory and file modes across
   nested creation, replacement, and Notarius promotion.
 

docs/operations.md

@@ -451,6 +451,10 @@ Restore treats a local leaf symlink or any symlinked ancestor beneath the
 selected session root as a conflict, even when the linked content matches the
 selected remote object. `--force` does not override that conflict.
 
+Before each install, restore validates the destination again beneath the
+selected session root. A target changed into a symlink, directory, or other
+non-regular entry is not overwritten.
+
 Restore writes an execution report at `reports/restore-latest.json`.
 
 If restore fails after beginning installation, it leaves a durable

docs/roadmap/implementation.md

@@ -470,7 +470,7 @@ symlink and classify its target as an already matching regular file.
 
 ## Stage 6 — Install Restore Results Through The Session Root
 
-**Status: Pending**
+**Status: Completed**
 
 ### Goal
 

docs/troubleshooting.md

@@ -564,6 +564,9 @@ Safe fix:
 - rerun with `--force` only when remote state should overwrite an eligible
   regular local file; repair a symlink or other non-regular conflict first.
 
+If the filesystem changed after the plan was printed, rerun restore after
+repairing the destination; installation performs the same safety check again.
+
 Relevant reference: [Operations: Restore Workflow](./operations.md#restore-workflow).
 
 ## Restore current-state discovery failure