docs: record the in-app accept, the update notice and translocation (P11a)
check / check (push) Waiting to run
portable-macos / portable (macos-latest) (push) Waiting to run
portable-windows / portable (windows-latest) (push) Waiting to run
two-user / two-user (push) Waiting to run

The interface spec gains `books.start`'s allocated `update_waiting` field
and says only the owner can accept it. The packaging and architecture
notes now describe the lease intent, the viewer's notice and "Check for
updates", and the translocated-app refusal instead of listing them as not
built. The testing record names each new test and the mutation targets it
gives P12. The plan's P11a status and As-built block record what landed
and what still waits: the Mac trial, the Windows installer (P11c's) and
signing (D-64).
This commit is contained in:
swaits committed 2026-11-05 08:29:20 -07:00
1 parent e2754898d8
commit 7b1774512b
5 files changed
+98 -9

No files matched your search

+8 -1
View File
@@ -124,7 +124,8 @@ settings-and-conventions section says how to use them.
codes), backup: { last_at, through_seq, stale }, prompts: [{ name, args
}], needs_attention: { items: [{ id, severity, kind, title, tool?, args?
}], counts: { kind: n } }, truncated?, handbook_sections,
format_upgrade?: { guard, format, adds, how }, next_steps: [{ tool |
format_upgrade?: { guard, format, adds, how }, update_waiting?: { version,
staged_at, how }, next_steps: [{ tool |
prompt, args?, why, required }], isolation }`. The connect text names it
as the first call. `book.url` is the book's path on this server
(`/b/ID/mcp`), never a path on a disk. `you` is the token's own facts
@@ -145,6 +146,12 @@ settings-and-conventions section says how to use them.
(below); its next step comes first, before anything else, at every
start until it is done: `books.handbook {section: "format-upgrade"}`,
"Tell the human first: …".
`update_waiting` is there only while the host has downloaded and checked
a newer version of wanderbooks (`<root>/updates/staged/`): its version,
when it was staged (UTC, RFC 3339) and how it may be accepted. Only the
owner can accept it, in the app (Books, then Update) or with
`wanderbooks update` at a terminal; no tool can. Its next step asks the
agent to tell the human, and nothing changes until they accept.
`isolation` is `same_user (advisory)` locally (D-32): the books are
hidden from agents in the owner's own account, not locked against them.
On the owner's own machine, where the server runs as a separate account