All four bullets answered by the operator in a live Cowork session. The step's
Verify goes from exit 1 to exit 0, which is the whole point of having written
it as a `test` rather than a count-and-eyeball: it was red for a reason and is
now green for a reason.
- Sesjonsmodus: sky
- Host-MCP: ja
- python3: ja 3.11.15
- CLAUDE_PLUGIN_ROOT: ja
Host-MCP is `ja` on both halves of the rule, not just the first. The connector
was listed AND `probe_ping` returned `probe-tools 0.0.1, python 3.14.0 @
/usr/local/bin/python3` -- a macOS path and the host interpreter, against the
sandbox's 3.11.15 [GCC 13.3.0]. The call crossed from the cloud session to this
Mac. That was the prediction stated before the call, so the test could have
falsified it.
Consequence recorded alongside the capability, because it is a cost: a
plugin-declared MCP tool in Cowork needs this machine awake, connected and
carrying the right Python. A cloud session elsewhere reaches nothing. The
degradation branch is therefore also the answer to "this Mac is asleep" -- a
routine state, not an exceptional one.
Run 2 of the two-run record was dropped rather than quietly skipped. It was
designed on the expectation that the off run would fail; it did not, and the
default configuration already gives a working host-side server. Confirming that
local mode also works has low value against its cost, so it is deferred with
the reason stated and named as the first thing to try if the cloud path breaks.
One negative result worth keeping: an individual tools/call does NOT reach
main.log. `grep -c probe_ping main.log` returned 0 both before and after a
successful call. The check script already refused to read that absence as an
answer; this records why that caution was correct.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Kjell Tore Guttormsen
8f0c2fa360