go/asks: an ask may carry its Details whole, for a channel that proves who answers (hq issue 383)

The review of mesh-controller #304: a settings proposal with more than three keys showed only the names
of the rest, and its Details could carry no value under the content rule, so Approve bound values the
operator never saw. WholeDetails carries every value whole for the note on a proving channel, held to
the secret rule alone, as Whole is; it is digested only when given.

go/asks/asks.go

@@ -174,6 +174,12 @@ func (a Ask) Digest() string {
 		canonical(&b, a.Whole)
 		canonical(&b, a.Details)
 	}
+	// WholeDetails (novox/hq issue 383, the review of mesh-controller #304) follows only when given, so every
+	// ask without it digests as it did before it existed.
+	if a.WholeDetails != "" {
+		canonical(&b, "whole-details")
+		canonical(&b, a.WholeDetails)
+	}
 	sum := sha256.Sum256([]byte(b.String()))
 	return "sha256:" + hex.EncodeToString(sum[:])
 }
@@ -207,6 +213,12 @@ type Ask struct {
 	// (Message.Note), after what the ask's options do and when it expires — never in its body (novox/hq
 	// issue 639).
 	Details string `json:"details,omitempty"`
+	// WholeDetails are the Details with their exact values whole, shown in place of Details where Whole is shown
+	// in place of the explanation (a kind that proves who answers, given the ask's answers): every value an
+	// approval sets, whole, so the person reads exactly what they approve (novox/hq issue 383). Held, like
+	// Whole, to the secret rule alone; the router refuses the ask when a secret's shape is left in it. Empty,
+	// Details are shown everywhere.
+	WholeDetails string `json:"whole-details,omitempty"`
 }
 
 // What an ask's explanation is held to, so it reads at a glance on a phone (novox/hq issue 639): a summary