Security model, files and peer tasks: what the 2026-08-30 review found and fixed
Four repairs to the pages, all from measurements rather than restatement:
- the wrapped-row scrub was documented as an accepted ceiling; it was measured and is
the MAJORITY case ((L-1)/W, so 79% for the 64-hex key at 80 columns, certain below
64), and it is closed in 0.22.1. The remaining case is an escape sequence inside the
value.
- the free-text answer is raw keyboard access and now says what that meant: it was the
one participant text that skipped stripControl, so a CR submitted claude's field and
typed the rest as a second, unattributed prompt. Plus the adversarial input set the
relay was actually driven with.
- jam-uploads/ confinement is a NAME filter, and a name filter cannot see a
filesystem: a dangling symlink carried an upload out of the directory until the write
became exclusive. And the quota is counted at grant time now, not only at write time.
- the peer result's agent-facing copy is fenced, and a result could close that fence.
Also: a result's text never reaches /peers log at all.
Plus what the invite blob is worth (nothing — every field is re-checked server-side on
every use, driven), what its address list is and is not, and the one thing a stranger
can learn pre-approval: the roster, name by name, in knock or token mode.
Peer-Tasks: the two switches, how to say no, and the open question
A page for the one feature where something the host's agent asks for costs
another human money and attention. It leads with the two switches held by two
different people, and it gives "how to say no" its own section — a decline, a
one-way `never` for that client session that no host can clear, a cancel for a
task already running, and closing the client.
The compliance frame is a section rather than a footnote. Every task is one
person choosing in the moment to spend their own quota on work they were shown in
full, which is ordinary individual usage of each account; whether a coordinated
multi-account fan-out counts as ordinary individual usage is NOT settled, and the
page says so plainly instead of reassuring anybody.
Home gains the row and loses the "not built yet" line for peer tasks.