v1.1.2 — ZMediumToMarkdown 4.0.0 compatibility

⚠ Compat fix for ZMediumToMarkdown 4.0.0. If you were getting exit-2 / "Cannot prompt for consent on a non-interactive stream" errors after upgrading the gem, this release fixes it.

What's new

• `spawnGemOnce` now sets `ZMTM_TOS_ACCEPTED=1` in the gem's child-process environment. ZMediumToMarkdown 4.0.0 ships a first-run Terms-of-Use gate that refuses to run on a non-TTY stream — and the MCP stdio transport is always non-TTY (we set `stdio[0]='ignore'`). The env var is the gate's documented escape hatch. On gem versions < 4.0.0 it's silently ignored; `REQUIRED_ZMEDIUM_VERSION` stays at 3.5.2.

• README adds a "Terms of Use note" section. Installing this MCP server is acceptance of the gem's Terms on the operator's behalf — it has to be, because there's no way to surface a click-wrap prompt over stdio. Anyone who'd rather give that consent themselves is told to skip the MCP wrapper and run `ZMediumToMarkdown` directly in a Terminal.

Migrating

Just upgrade. No config or env changes on your side:

```bash
npm install -g mcp-medium-reader@1.1.2
```

If you also upgrade ZMediumToMarkdown to v4.0.0 (recommended — older versions don't carry the explicit consent gate at all), the MCP layer keeps it transparent.

Verification

• `npm run build` clean
• `npm test` — 40 tests / 7 files / 0 failures

1.1.0

First launch 🚀