A settings proposal reads at a glance, its values whole where the sender is proven (issues 383 and 639) #304

Merged

mesh-admin merged 5 commits from fix/383-an-ask-reads-at-a-glance into main 2026-10-13 19:22:07 +00:00

Conversation 13 Commits 5 Files Changed 10

+629 -87

5 Commits

Author	SHA1	Message	Date
jochen	deef9421a2	A change's line the router would refuse is named with its value withheld, or refused at propose (the review of #304) ... {a:1, b:2, c:3, password:hunter2} was proposed with "+ password: hunter2" in its Details: the router withheld the line unnamed and Approve set a value the operator never saw (ADR 0347 §1, §3, §4). Each line is now judged as the router judges it, masked under the content rule and whole under the secret rule; a line refused is said "+ password (value withheld)", and any line the router would still refuse is refused at propose in the controller's words, never echoing a secret-shaped key. SDK at mesh-sdk 5933eb7 (no two asks digest the same).	2026-10-13 20:45:25 +02:00
jochen	3c19e9ee93	A settings proposal's summary says the layer is sent at once by a walk (ADR 0344 with ADR 0345) ... Rebased on #305: Approve now sends the layer by a walk, so the summary's "takes it at its next push" was false. The summary says it is set and sent at once by a walk to where it reaches, one machine at a time, each judged; the rest of what Approve does (onApprove) leads the Details, beside every key whole.	2026-10-13 20:45:25 +02:00
jochen	3d94f87bb0	The glance's cut says only what the note holds there: whole beside the whole details, else in the note (ADR 0347)	2026-10-13 20:45:25 +02:00
jochen	4644f25edd	A settings proposal carries every key with its whole value in its Details (issue 383) ... The review of #304: with more than three keys the ask showed only the names of the rest, a long value was cut without a word, and the Details held no key, so Approve bound values the operator never saw. The Details now list every key uncut — masked, and whole in WholeDetails for a channel that proves who answers — before who proposed it and the fingerprint; the glance says what it cut. Vendors mesh-sdk at f474544 and captures its conformance events there.	2026-10-13 20:45:25 +02:00
jochen	c58e0a571e	A settings proposal reads at a glance, its values whole where the sender is proven (issues 383 and 639) ... The operator could not read the settings proposals on the phone: the change, the fingerprint and a how-to paragraph in one wall of plain text, and the values masked as ‹path› and ‹address›, so the approval was blind. The ask is now a summary of what changes where ("Changes 3 setting(s) of mounts on shanks; approved, the layer is set at once and shanks takes it at its next push."), then at most three points, one key each (more keys: the first two and the names of the rest). Who proposed it, the fingerprint and how to read it whole are its Details, which the router notes after the answers. The change is carried twice: under the content rule, and whole (asks.Ask.Whole), shown only on a channel that proves who answers, a value shaped like a secret withheld in both (from the earlier work on issue 383, #202). Vendors mesh-sdk at 9588871 (fix/639-an-ask-reads-at-a-glance: Message.Note, asks.Glance), and captures its conformance events at that commit.	2026-10-13 20:45:25 +02:00