summaryrefslogtreecommitdiff
path: root/.agents
diff options
context:
space:
mode:
authorGabriel Schneider <[email protected]>2026-09-28 13:51:15 -0300
committerGabriel Schneider <[email protected]>2026-10-01 00:12:15 -0300
commitfaca1504a2296fba9631c45c9f01f3c252cbd0d8 (patch)
treedd5ee3cef64c7f253503b1ca25a540d7e6859de6 /.agents
parent1ad90ebaa016d35bd8659f345b6d8a83a9cd6bc9 (diff)
downloadpardes-faca1504a2296fba9631c45c9f01f3c252cbd0d8.tar.gz
pardes-faca1504a2296fba9631c45c9f01f3c252cbd0d8.zip
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 <[email protected]>
Diffstat (limited to '.agents')
-rw-r--r--.agents/skills/pardes-9p/SKILL.md3
1 files changed, 2 insertions, 1 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