1. [P1] The structured-value refusal was in the wrong place and killed the
fix. It went into BuildCLIArgs, which env.Dispatch runs for BOTH
transports before handing off to whichever Dispatcher is configured — so
it blocked the remote /mcp door too, and the native-field handling that
is the whole point of this change was never reached.
Moved into ExecDispatcher, which IS the stdio door. My own test could not
see this: it called mapItemCreate directly, so it vouched for the mapper
and not for the path that reaches it — CONVE-19's exact shape, in a unit
where I had already written binding tests for the other half.
The tests are now split along the two claims the first version conflated:
nested values REACH the dispatcher (the remote door is unblocked), and
refuseStructuredFieldsOverCLI refuses them at the CLI door naming the
transport.
2. [P2] The CLI warning sat after the `--format json` early return, so the
caller most likely to have sent a mistyped key — one piping stdout into a
parser — was the one caller who never saw it. Moved above the return, and
out of the `ref != ""` branch it was also trapped in. Still stderr.
3. [P2] A nil value in fields_patch DELETES the key (store/items.go), so
reporting it as an undeclared field told the caller a field was stored
that the same request removed. Filtered at the patch site, not inside
UndeclaredFieldKeys, because nil means "store JSON null" on the
full-fields path where reporting it is correct.
Gates: gofmt clean, go vet clean, go test ./... 29 packages ok.
Claude-Session: https://claude.ai/code/session_011Q4b1iHtJtSyMs7BA2ySxo
xarmian
2cf9f0035a