jochen
7a92224886
mesh/delivery-group group fix/383-a-proposal-reads-whole-on-the-phone checking: 0 of 2 member(s) ready
mesh/delivery superseded: a newer head of the same pull request
mesh/merge-gate pass: builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step; every machine composes with the change as it…
mesh/repo-check pass: its merge-check.sh passed
The operator saw "+ shares: media=‹path›" on the phone and could not tell what they were approving: a mount point, a share name or a private address is the thing being approved and must be readable. The ask now carries the change twice: the explanation under the content rule, as before, and the whole (asks.Ask.Whole), which the router shows only on a channel that proves who answers; only a value shaped like a secret is withheld there (outward.Secret, and the proposal is refused if one were left). The message is the headline, one line per key, who proposed it and when; the fingerprint and how to read the proposal whole are the Details answer's (asks.Ask.Details). The masking stays for conditions and for channels that prove nothing. The warrant binds as before: the ask's digest covers the whole and the Details, the act digest the exact values. Vendors mesh-sdk go at the commit that adds Whole and Details to an ask.