mesh-cli: say an outcome not known, and hold the module to placing one file (review of hq ADR 0272)

A line whose answer did not come in time is said as possibly run, with
its call, never as nothing having run. A test holds the module to one
archive resource unpacking one compiled Go bundle into /usr/local/bin.
The README says the MESH_VERB refusal is a courtesy and the controller is
the gate. SDK pinned at the go/cli branch's newest commit until go/v0.1.9.

modules/mesh-cli/cmd/mesh-cli/main_test.go

@@ -93,3 +93,14 @@ func TestAnEngineThatDoesNotAnswerIsSaid(t *testing.T) {
 		t.Fatalf("exit %d, said %q", code, errOut.String())
 	}
 }
+
+// An outcome not known is said as such — the line may have run — and never as nothing having run.
+func TestAnOutcomeNotKnownIsSaid(t *testing.T) {
+	t.Setenv("MESH_VERB", "")
+	engine(t, cli.NotKnown("call-4", "no answer within 6m0s"))
+	var out, errOut bytes.Buffer
+	code := run(context.Background(), []string{"push", "laptop"}, &out, &errOut)
+	if code == 0 || !strings.Contains(errOut.String(), "may have run") || !strings.Contains(errOut.String(), "call-4") {
+		t.Fatalf("exit %d, said %q", code, errOut.String())
+	}
+}