From faca1504a2296fba9631c45c9f01f3c252cbd0d8 Mon Sep 17 00:00:00 2001
From: Gabriel Schneider <gbrls@0x4200.cafe>
Date: Mon, 28 Sep 2026 13:51:15 -0300
Subject: docs: the log's restore record, not the Restore write's answer, says
 a Restore happened

The answer gets 200 ms to leave before the connections are cut, so a slow
client may see only the cut; the new log's 'restore <path>' record is what to
trust.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---
 .agents/skills/pardes-9p/SKILL.md | 3 ++-
 docs/fs.md                        | 4 +++-
 2 files changed, 5 insertions(+), 2 deletions(-)

diff --git a/.agents/skills/pardes-9p/SKILL.md b/.agents/skills/pardes-9p/SKILL.md
index 6b955eb4..f4542a50 100644
--- a/.agents/skills/pardes-9p/SKILL.md
+++ b/.agents/skills/pardes-9p/SKILL.md
@@ -228,7 +228,8 @@ newlines: read `n` bytes of text, never up to the next newline.
 A Restore puts a new editor under every client: the Restore write is
 answered, then every connection is hung up (their fids name the old
 editor's panes); dial again, and the new log names the restored panes then
-`restore <path>`. `Dump` writes `pardes-<date>-<time>.zon` under `DumpDir`
+`restore <path>` -- the authority, since a slow client may see the cut
+before the answer. `Dump` writes `pardes-<date>-<time>.zon` under `DumpDir`
 (`~/.local/share/pardes` by default) and logs `dump <path>`.
 Read the event implementation before building an interceptor. Close handles in
 `finally`, and disconnect after a socket timeout. The service shares four
diff --git a/docs/fs.md b/docs/fs.md
index ae5e27ad..7361c19e 100644
--- a/docs/fs.md
+++ b/docs/fs.md
@@ -116,7 +116,9 @@ and logs `dump <path>`, and `Restore` with no path takes the last one; a
 Restore puts a new editor under every client, so the write of it is
 answered and then every connection is hung up, their fids naming the old
 editor's panes: dial again, and the new log names the restored panes and
-`restore <path>`. Keeping connections across it would mean carrying serials
+`restore <path>`. The answer has 200 ms to leave before the cut, so a slow
+client may see only the cut; the log's `restore <path>` is what says the
+Restore happened. Keeping connections across it would mean carrying serials
 and opens into the new editor, which acme, whose Load only adds windows,
 never needed); and `Kill`, which
 does not quit but stops commands, as acme's does: bare, every command pardes
-- 
cgit v1.3