Magnemo 0.6.5 — Sentinel at the gate

• The stage door is swept. Every note staged through the MCP stage tool or the CLI's magnemo stage passes Sentinel,
  the same sweep the inbox, the Room and the chest already ran: a secret-shaped value never lands (the note carries the
  redaction line and a sentinel:secret:<pattern> taint; the reply says HELD and names the pattern, never the value); an
  instruction-shaped line stages TAINTED beside a Sentinel ALERT note. Four doors, one sweep.
• A tainted note is never served to an agent — not by retrieve, not in the boot pack's digest — until a keyholder
  reads it and clears it: magnemo clear <id> --reason … (the short name for cleartaint; ledgered).
• magnemo doctor checks the network sentence instead of the README asserting it: network: transport stdio · listener none · outbound modules none from a static scan of the installed package, FAIL if a network module appears; and
  server: never connected until an MCP client has actually started this vault's server (the server now logs each session
  start to _ledger/connections.jsonl) — the CLI answering is not the server connecting.
• The one paste's step 6 keeps the same-session read and gets the restart back: approve, magnemo bootpack, then restart
  so the memory mounts for every later session. The CLI's stage reply names the word (magnemo yes <id>).
• The companion magnemo-mcp says requires-python >=3.11, the same as the engine it pins; docs/MCP.md says 3.11 too.