test(framework): a real session per tool, on Windows and on Linux

Start with the existing cli / Windows job and the platform-specific exclusions for persona.e2e.test.ts and telemetry-multi-tool.e2e.test.ts, then trace the CLI entry points that journal and report tool activity. Run real Claude Code, Codex, Copilot, Cursor, and OpenCode sessions on Windows and Linux; done means each supported session journals and reports correctly, with Windows privacy expectations documented.

Every probe behind this layer was run on macOS. Most of that is no longer true, and this
ticket was rewritten on 2026-09-03 to say what is left rather than what was once unknown.

Settled since it was opened

Windows went green for the first time on 2026-09-03 (#749), and it earned its place
immediately: it found two real defects that macOS could not. A mode assertion that measured
the platform rather than the repair, and check reporting "its script is not executable, so
git will not run it" about a hook git runs — an unknown printed as a fault on every Windows
run.

Two e2e files stay excluded there, each for a stated platform reason, not a workaround:
persona.e2e.test.ts needs /usr/bin/expect, and telemetry-multi-tool.e2e.test.ts puts an
extensionless #!/bin/sh stand-in on PATH, which Windows resolves by PATHEXT and never by
a shebang.

POSIX modes carry no information on Windows. Measured, not read from documentation:
statSync().mode & 0o777 reports 0o666 for every writable file whatever it was chmod'ed
to, and 0o444 when read-only. So 0700/0600 on the journal is not a privacy guarantee
there — it is a no-op, and any claim resting on it must say so.

What is actually left

• One real session per tool, on Windows and on Linux, that journals and reports. With the
  tool's own binary, not a stand-in. CI proves the chain against captured payloads; it does
  not prove that a real Claude Code, Codex, Copilot, Cursor or OpenCode session on those
  platforms writes what the reader expects.
• What replaces the mode bits on Windows, if anything does. Either the journal's privacy
  rests on the directory ACL and that is stated, or it is stated that it rests on nothing.

Done when

• The figures are written where each platform expects them, and where they are written is stated per platform.
• The journal's privacy on Windows is established by observation, and if POSIX modes mean nothing there, that is written down rather than implied.
• One real session per tool that runs on the platform, on Windows and on Linux, journals and reports.

That last box overlaps #694, which proves the same chain under load. Whichever runs first
should carry both.