docs(m1): record the probe twice, once per session-location setting

Cowork exposes session location as a toggle ("Only on this computer"), which
the probe's four bullets cannot express: each holds one value, and the file was
written as if session mode were a property of the machine to be discovered
rather than a setting that can be flipped.

So the probe is now run twice, off then on, into a two-run table in the Results
section, with a second table saying how to read the pair. The three outcomes are
all useful and lead somewhere different -- the toggle is the lever (and then it
belongs in README and in every Verifiser i Cowork step, not a footnote); host
MCP is dead whatever the setting (degradation branch, and jobbsok-tools is not
built on an assumption); or host MCP runs even in cloud mode, which contradicts
the documentation and is exactly what research/03 dimension 4 flagged as
unverified.

Off is run first because it is the current default and a fresh install returns
to it -- one click away from being lost for free.

Section A now says to probe both sides of the setting rather than just read it,
and carries an honesty marker: that this toggle controls session location is an
inference from its label and subtitle, not something any documentation read so
far names by that string. The probe settles it.

The four bullets, the allowed answers and the Verify command are untouched.
Checked rather than assumed: on a fully answered copy the verify regex still
matches exactly 4 lines and exits 0 -- for the `lokal VM`/`ja` filling and for
the `sky`/`nei` one -- so the added tables cannot become false positives. The
live file still exits 1, as it must while the probe is open.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

docs/cowork-probe.md

@@ -39,6 +39,36 @@ selects the degradation branch below.
 | `- python3:` | Run the `probe-versjon` skill; does it succeed in invoking `python3`, and which version does it report? | `ja` or `nei`, followed by the reported version | |
 | `- CLAUDE_PLUGIN_ROOT:` | Run `probe-versjon`; does it print a resolved absolute path, or the literal variable name? | `ja` or `nei` | |
 
+### Two-run record: is the session-location setting the lever?
+
+Cowork exposes `Only on this computer` as a **toggle**, which means session mode
+is a setting rather than a property of this machine -- something the four
+bullets above cannot express, since each holds one value. Anthropic's
+documentation says local MCP servers do not run in cloud sessions, and cloud has
+been the default since 2026-07-07; whether a cloud-default session on this Mac
+still spawns host-side servers via the desktop app is recorded as **unverified**
+in `research/03-cowork-plugin-compatibility.md`, dimension 4. So run the probe
+twice and fill this in **before** writing the bullets above. The off run is the
+cheap one to lose: it is the current default, and a fresh install returns to it.
+
+| Run | `Only on this computer` | `probe-tools` listed? | `probe_ping` answers? | Manifest version | Date |
+|---|---|---|---|---|---|
+| 1 | off (current default) | | | | |
+| 2 | on | | | | |
+
+How to read the pair:
+
+| Run 1 (off) | Run 2 (on) | What it means |
+|---|---|---|
+| no | yes | The toggle is the lever. Operator decision 7 works, but only with it on -- which then belongs in `README.md` and in every `Verifiser i Cowork` step, not in a footnote. |
+| no | no | Decision 7's Cowork half is dead whatever the setting. The degradation branch below applies, and `jobbsok-tools` is not built on an assumption. |
+| yes | yes | Host-side MCP runs even in cloud mode. That contradicts the documentation and is the most interesting of the three -- research 03 flagged exactly this as unverified. Record what you saw, verbatim. |
+
+Then write the session-mode bullet above as the mode that produced the better
+result, and put what the other run gave in its Measured column. If both runs
+agree, say so there too: an agreement that was measured reads differently from
+one that was assumed.
+
 ### What is already known, and what is not
 
 Measured 2026-09-04 from Claude Code, before the probe was built:
@@ -110,11 +140,19 @@ looking for whether sessions run **on this machine** or **in the cloud**.
 
 Write `lokal VM` or `sky`.
 
-**Do this one first**, because it very likely decides question B below:
+**Do not just read this setting -- probe both sides of it.** It is a toggle, so
-Anthropic's documentation states that local MCP servers do not run in cloud
+the documented claim that local MCP servers do not run in cloud sessions is
-sessions. If you answer `sky` here and `ja` to `- Host-MCP:`, that combination
+testable here rather than merely quotable. Leave it as you found it for the
-contradicts the documentation and is a much more interesting result than either
+first pass, run sections B through E, then flip it, start a fresh session and
-answer alone -- say so in the Measured column.
+run B through E again. Record both in "Two-run record" above; that table also
+says how to read the pair. Five minutes buys the difference between "Cowork
+cannot do this" and "Cowork can do this if one setting is on", which are very
+different findings for the milestone.
+
+One honesty marker: that this toggle controls session location is an inference
+from its own label and subtitle -- a local VM stops when the machine sleeps, a
+cloud session does not -- and no documentation read so far names this exact
+string. The probe is what settles it.
 
 ### B. Install the probe plugin (needed for C, D and E)