From 6f3abac3b2f8d27e4a1812692a5d0ac544cdcb49 Mon Sep 17 00:00:00 2001
From: Claude <noreply@anthropic.com>
Date: Wed, 22 Apr 2026 21:54:18 +0000
Subject: [PATCH] fix(marmot-interop): peel .result wrapper when reporting Test
 10's B view
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Post-v0.2 wn wraps `--json groups show` output in {"result": {...}},
so `jq '{name, epoch}'` was reading the top level where those keys
don't exist — Test 10 always logged "B state: {name: null, epoch: null}"
and the operator couldn't tell whether the race produced the expected
converged state on wn's side.

Peel the .result wrapper before extracting the fields; same pattern
already used everywhere else in the script that parses wn JSON.
---
 tools/marmot-interop/marmot-interop.sh | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/tools/marmot-interop/marmot-interop.sh b/tools/marmot-interop/marmot-interop.sh
index 966c3e30e..745baa844 100755
--- a/tools/marmot-interop/marmot-interop.sh
+++ b/tools/marmot-interop/marmot-interop.sh
@@ -1084,7 +1084,10 @@ test_10_concurrent_commits() {
 
   step "verifying B's view is consistent (name + epoch)"
   local b_view
-  b_view=$(wn_b --json groups show "$gid" 2>/dev/null | jq '{name, epoch}' 2>/dev/null || echo "{}")
+  # Post-v0.2 wn wraps `groups show` output in {"result": {...}}; peel
+  # that wrapper before extracting the fields so the info log isn't
+  # "name: null, epoch: null" on every run.
+  b_view=$(wn_b --json groups show "$gid" 2>/dev/null | jq '(.result // .) | {name, epoch}' 2>/dev/null || echo "{}")
   info "B state: $b_view"
 
   prompt_human "Read the group name now shown in Amethyst."