docs: row 70 brief update, the PATH wrapper runs a pinned copy since row 85

Rows 85 (#1579) and 130 (#1625) changed what the three doc places must
say: the wrapper execs a pinned copy's scripts/mosaic, the human commands
run only from the bus's tree, and queue writes stay on the checkout.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

docs/plans/2026-10-11_mosaic-on-path-docs.md

@@ -25,6 +25,17 @@ working checkout, and `mosaic queue` refuses there ("this queue code ...
 is not under the canonical root"), so queue work stays on
 `scripts/mosaic` in the canonical checkout.
 
+Update, Sage 2026-10-15: row 85 (#1579) and row 130 (#1625) changed the
+facts. `scripts/stack-copy.sh wrapper ID` now rewrites the Q81 wrapper's
+last line to exec `scripts/mosaic` from a read-only pinned copy under
+`~/.local/share/mosaic-stack/copies/<full id>`, keeping the Q81 marker
+and the lease line to `mosaic-old`. The human commands and `--tester`
+run only from the tree the bus runs from, so on a pinned host the
+checkout's `scripts/mosaic` exits 3 with `human-required` or
+`tester-required` for them. Queue writes still go through the checkout.
+The three places above still say the old thing. Line numbers moved:
+TOOLS.md now has it in the seat-launch paragraph near line 175.
+
 ### Owner and reviewer
 
 Owner: Sage. Reviewer: Filbert.
@@ -38,10 +49,14 @@ Owner: Sage. Reviewer: Filbert.
 ### What ships
 
 - Each place says `scripts/mosaic` is the repository wrapper. A host may
-  also put it on PATH as `mosaic`, pinned to a pushed commit. On Jason's
-  host that's the Q81 wrapper, and the estate CLI is `mosaic-old`.
-- Each says `mosaic queue` refuses from a pinned copy, so queue commands
-  run as `scripts/mosaic queue` in the canonical checkout.
+  also put `mosaic` on PATH as a wrapper that runs a pinned copy's
+  `scripts/mosaic` (`scripts/stack-copy.sh wrapper`, TOOLS.md "Stack
+  copies"). On Jason's host the estate CLI is `mosaic-old`.
+- Each says which to use: the human commands on a pinned host go through
+  `mosaic` on PATH, and queue commands run as `scripts/mosaic queue` in
+  the canonical checkout, because `mosaic queue` refuses from a copy.
+  Each links the CLI README's "One pinned copy" section rather than
+  repeating it.
 - No code change. The cli, queue and seat node suites and every
   `scripts/test-*.sh` still pass. The queue dispatch test reads
   `scripts/mosaic`, and a header edit must not move its seat usage text.