docs(#585): the handbook stops saying a share is a link #591

Merged

Cordy merged 1 commit from docs-585 into main

2026-09-18 01:25:10 +00:00

Cordy commented

2026-09-18 01:20:54 +00:00

Owner

The #585 docs run, written from what shipped in v0.6.212/213 and verified live — not from issue intent. Seven surfaces:

sharing.md — rewritten. Opens with the three-way table (account here → grant; no account → public link; own instance → peering), then Sharing with people and groups: the addressee model, the two roles, the search-only picker and why it refuses a blank query, group grants following membership, the structural re-share refusal (quoting the server's own error), and the #571-item-4 encryption paragraph — a grant moves no key material, the server opens the owner's file for the recipient, server-side transparent encryption not end-to-end. That paragraph is written to serve #238 as well: it names why peering re-encrypts to the recipient's key instead of granting into the sender's tree. Internal link and the Shares view get their sections; all the public-link content (modes, CLI, protection claims, file drop, operator notes) is kept verbatim under "Public links".
index.md — the Pages-table description no longer says links-only.
groups.md — grant addressees join the list of what groups are good for, with the membership-follows consequence.
file-browser.md — the Shares view mention now names the two tabs.
encryption.md — the operational note claiming "share links over encrypted content are not yet supported" was stale by five months (#175 shipped v0.6.4). Replaced with the current truth, plus the grants boundary.
README.md — a Sharing-with-people-and-groups feature bullet beside the links one.
ARCHITECTURE.md — §6 gains the grants paragraph (store shape, /shared overlay, resolveOwned refusal, ShareInternalDisabled, search-only recipients endpoint); the §4 historical clause "encrypted-content share links remain out (#19)" corrected to what shipped.

Held back on purpose: what a recipient is offered under /shared. #588 changes that behaviour and its PR carries the matching sentence, so doc and code land together.

Two roles are documented as the design, not a gap: the rev-2 mockup settled "roles are Can view / Can edit, with upload a public-link checkbox rather than a per-person role", and share.go/grantCreate enforce exactly that. #589 is being closed as superseded on the same evidence.

The #585 docs run, written from what shipped in v0.6.212/213 and verified live — not from issue intent. Seven surfaces: - **`sharing.md`** — rewritten. Opens with the three-way table (account here → grant; no account → public link; own instance → peering), then Sharing with people and groups: the addressee model, the two roles, the search-only picker and why it refuses a blank query, group grants following membership, the structural re-share refusal (quoting the server's own error), and the #571-item-4 encryption paragraph — a grant moves no key material, the server opens the owner's file for the recipient, server-side transparent encryption not end-to-end. That paragraph is written to serve **#238** as well: it names why peering re-encrypts to the recipient's key instead of granting into the sender's tree. Internal link and the Shares view get their sections; all the public-link content (modes, CLI, protection claims, file drop, operator notes) is kept verbatim under "Public links". - **`index.md`** — the Pages-table description no longer says links-only. - **`groups.md`** — grant addressees join the list of what groups are good for, with the membership-follows consequence. - **`file-browser.md`** — the Shares view mention now names the two tabs. - **`encryption.md`** — the operational note claiming "share links over encrypted content are not yet supported" was stale by five months (#175 shipped v0.6.4). Replaced with the current truth, plus the grants boundary. - **`README.md`** — a Sharing-with-people-and-groups feature bullet beside the links one. - **`ARCHITECTURE.md`** — §6 gains the grants paragraph (store shape, /shared overlay, resolveOwned refusal, ShareInternalDisabled, search-only recipients endpoint); the §4 historical clause "encrypted-content share links remain out (#19)" corrected to what shipped. **Held back on purpose:** what a recipient is offered under /shared. #588 changes that behaviour and its PR carries the matching sentence, so doc and code land together. **Two roles are documented as the design, not a gap:** the rev-2 mockup settled "roles are Can view / Can edit, with upload a public-link checkbox rather than a per-person role", and `share.go`/`grantCreate` enforce exactly that. #589 is being closed as superseded on the same evidence.

Cordy added 1 commit

2026-09-18 01:20:56 +00:00