feat(tools): pull-doc holt ein Server-Dokument in ein git-Worktree und committet es datiert (D88)

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

docs/examples/werkbaum.werkbaum

@@ -140,8 +140,9 @@
     " same instant is the expensive one.
     - [^] #col.point: A shared pointer: !!! focuses a node for everyone (XS)
     - [-] #col.pad: Borrow an Etherpad — it merges, we render (L)  %% built, then removed, see D78
-    - [ ] #col.git: Git as the shared store (L)
+    - [~] #col.git: Git as the shared store (L)
       | [ ] #col.git.pr: A file in a repository, changed by pull request (S)  %% works today, no code
+      | [x] #col.git.pull: A script pulls the server document and commits it (S)  %% tools/pull-doc, dated commits — see D88
       | [?] #col.git.auto: The backend commits every change (L) :#be.scaffold
         - [?] #col.git.hist: History and restore (M)
           - [?] #col.git.diff: Diff between two versions (S)
@@ -886,6 +887,11 @@
   go through a pull request, a link renders it. For a plan that changes weekly
   rather than per second this is often the better answer.
 
+#col.git.pull
+  The tools/pull-doc script fetches a server document (a ?live= link works too)
+  and commits it into a git worktree — date, title and version in the message,
+  no commit when nothing changed. Run from cron, a shared plan archives itself.
+
 #col.git.auto
   The server turns every change into a commit. History, restore and branches
   follow from that, with commit granularity as the open question.