4.1.0

4.1.0 — universal behavioral pack + MCP SDK in core

Every target now gets always-on memory instructions — including a brand-new opencode target — and the base install speaks MCP out of the box: mcp>=2.0,<3.0 moved into core dependencies, so one plain install is all an agent harness needs (ADR-0023).

Highlights

• Universal behavioral pack, new opencode target (#231/#232) — a new agents_md deployment kind injects a stamped, additive always-on digest of the three instruction files (recall at session start; checkpoint before compaction and session end; tag contract on every write; memory ops are PRIORITY tools) into each harness's native standing-instructions file: ~/.agents/AGENTS.md for the agents target (the one AGENTS.md-standard channel — Claude Code included), ~/.zcode/AGENTS.md for ZCode, and ~/.config/opencode/AGENTS.md for the NEW opencode target (OpenCode reads it natively; nested skills to ~/.config/opencode/skills/; MCP registered via an additive merge into ~/.config/opencode/opencode.json that preserves other servers and user-tuned values). The pi target receives the same pack as a standing system-prompt hint injected by the shipped bridge extension. The block engine never touches user content: deploy appends around it, update replaces only the stamped region, uninstall strips only the block; deploy/update/uninstall/verify report missing/stale/version-drift/content-drift. Fully backward compatible — copilot/cursor/hermes/generic-copilot/pi deploy maps unchanged.
• MCP SDK in core dependencies (ADR-0023, #234) — mcp>=2.0,<3.0 (bare; the upstream [cli] extra only added already-core deps) joined project.dependencies; the mcp extra remains as an empty compatibility alias. Before this change the base install could not run mnemos mcp-server — the primary agent-harness surface — and every fresh base install got a guaranteed mnemos doctor FAIL on MCP transport. Binding conditions implemented: an AST import-isolation guard pins the SDK to mnemos.mcp_server (a subprocess test proves the CLI import path never loads it), and the pip-audit/SBOM gate covers the unified profile. Net-new transitive deps ~1 MiB; doctor remediation strings and the EN/RU docs sweep now name the plain package everywhere.
• Docs overhaul: three-command quick start + RU admin mirrors — the README quick start is now three one-command steps (install the server → mnemos integration setup connects the harness AND deploys the behavioral pack → mnemos doctor), with every install variant delegated to the extended EN/RU getting-started guide — the <!-- version:… --> release-marker blocks moved there too, and sync-readme-version.sh follows them since #236. A docs-vs-code accuracy pass reconciled every operational doc against the real Typer CLI registrations, config/env forms, MCP tool registry and FastAPI routes (22/22 CLI subcommands and 26/26 MCP tools documented, ~80 broken anchors/links fixed), and the three EN admin pages that had no Russian counterpart are now mirrored 1:1 (EN/RU documentation synchronous).
• ADRs recorded — ADR-0023: MCP SDK moves into core dependencies as bare mcp>=2.0,<3.0 (implemented in this release; binding: lazy-import guard test, unified pip-audit/SBOM). ADR-0024: all harness connection consolidates into mnemos connect [harness] over the existing targets.yaml registry in three phases (4.1.0 alias + detect-all listing; 4.2 cursor/windsurf/claude-code targets + doctor on the registry; 4.3 Codex TOML-merge + legacy deprecation), with binding security controls.

Note on artifacts: no build assets are attached to this release and PyPI still carries 3.2.0 — distribution publication is a separate owner decision.

Full changelog: CHANGELOG.md — 4.1.0