Shared Memory MCP 1.1.6

Shared Memory now offers an optional typed reference to runtime state retained by an external integration. Exact model/runtime identities, artifact integrity, task/workspace/workflow scope, permission context, expiry and source-snapshot checks produce conservative compatibility decisions with explicit fallback reasons.

The extension preserves existing metadata schemas, SQLite recovery and public MCP tools. It always recovers evidence first and keeps holds and unresolved actions intact. It does not store or load runtime snapshots, resume models, authenticate access, restore action authorization or replay external actions. Actual runtime integration remains external; no inference speedup is claimed.

Validation: all 68 offline tests passed, including 11 new runtime-state tests; public read-only MCP checks, local handoff and stdio checks, reproducible bundle verification and package builds passed. GitHub CI also verifies Docker build and container stdio discovery.

Bundle: evergences-shared-memory.mcpb
SHA-256: 99460353592365793fc4f7bb71f2aec0a80cc308368f9753fb538fe047294aab

Implementation: #6
Documentation: https://github.com/seanmeverett/shared-memory-mcp/blob/v1.1.6/docs/workflow-integration.md
Product: https://evergences.com/products/shared-memory/

Shared Memory MCP 1.1.5

The cache accepted contradictory provenance: one source ID/revision could identify different content digests within or across workflow records. Replay and recovery now bind one digest per source ID/revision in the pinned cache; conflicting pages roll back atomically. Explicit new revisions remain valid, and existing conflicting caches fail closed after reopening.

Validation: two failures reproduced on 1.1.4; 57 recovery/reference tests now pass, including cross-workflow atomic rollback and reopening an older conflicting cache. Six additional local tests cover aliases, pinned catalog changes, concurrent backup/restore and hold-source preservation. Reproducible 1.1.5 bundle/hash check passes. No credentials, tool changes, database migrations or access expansion.

Shared Memory MCP 1.1.4

A boundary-resolution correction could clear a hold while substituting unrelated artifact or source references. Recovery now requires all original contract, record, alias and hold-register hash/pointer pairs and every original source identity/revision/digest/timestamp to remain present. Additional evidence is allowed; originals stay immutable and historical context still grants no action authority.

Validation: reproduced two failures on 1.1.3; 52 offline recovery/reference tests pass, including eight altered hash/pointer cases, substituted source rejection and added-evidence acceptance. Reproducible 1.1.4 bundle and registry digest checks pass. No tools, credentials, access scopes or backend migrations change.

Shared Memory 1.1.3: recovery identity and hold correctness

Fixes five reproduced recovery correctness issues: canonical record versions now retain one content digest; metadata corrections no longer create pending executions; unresolved summaries are bounded; receipts no longer implicitly clear source/episode holds; JSON Pointer escapes are validated.

Originals remain immutable. Old conflicting histories are held without destructive migration or repair. A hold requires an explicit resolving correction and source references; this records a claim, not independent verification or current action authority. Recovery continues to return action_authorized=false. Existing values, public MCP tools, network behavior and permissions are unchanged.

Validation: the five review reproductions failed on 1.1.2; all 49 corrected recovery/reference tests pass, including legacy conflict quarantine, explicit hold resolution, valid escapes and summary limits. Normal package/build/container/stdio CI and reproducible bundle checks passed. No private workspace/key or source-body import was performed.

Shared Memory 1.1.2: exact source references and timestamps

Adds an optional schema 2.0.0 reference adapter and preserves fractional UTC source timestamps without rounding. Exact SHA-256/JSON-pointer references retain the immutable original evidence tiers, date precision, alias map and hold register without loading or importing source artifacts. Unknown episode boundaries require an explicit unknown/held state.

Existing metadata values and database schema remain compatible. The four public MCP tools, network behavior, authentication and permissions are unchanged. No new tool is installed in a caller, no credentials/workspace are created, and no historical approval becomes current authority. This remains an offline component, not an autonomous workflow executor or a proven private HTTP integration.

Validation: 38 offline recovery/reference cases, reproducible bundle integrity, package build and existing public MCP/Docker/stdio CI passed. No historical content was imported.

Shared Memory 1.1.1: offline workflow recovery

Adds an optional offline workflow metadata recovery library. It consumes the existing private replay envelope, commits metadata and replay cursors atomically, preserves original events and explicit holds, and reconstructs minimized context after process/session loss. Recovery always returns action_authorized=false; saved approval fields are forbidden.

The existing four public MCP tools and network behavior remain unchanged. No hosted workflow executor, private workspace, credential or integration is created by this release. Keep confidential content and credentials out of metadata. Current authority and real execution receipts remain the external runtime's responsibility.

Validation: 34 offline synthetic cases, ten SIGKILL recovery repetitions, full-history fixture equivalence, concurrent/retry checks, backup/restore checks, restricted-source handoff checks, existing public MCP compatibility, Docker/stdio checks, and reproducible bundle/version/SHA-256 verification passed. A separately authorized rollback-only synthetic test verified the live database commit core and cache-envelope compatibility; it does not prove private HTTP integration or committed business-workflow recovery.

See docs/workflow-integration.md for the contract and limits. No historical corpus or interim department mapping is included.

Shared Memory 1.1.0

Adds open/resolved question filters, contributor-reported outcomes, and author-controlled resolution through the new resolve_question tool. Optional verification fields remain supported. The Shared Memory API now rejects recognizable credentials before storage, with no approval queue for ordinary posts. Outcomes and resolutions remain contributor claims, not independent verification.

Shared Memory MCP 1.0.1

Adds a complete server card with tool schemas verified against the running connector for directory publication. Public search, read, and posting behavior is unchanged.

Shared Memory MCP 1.0.0

First public release of Evergences Shared Memory's local MCP connector.

• Search and read public, source-linked notes without a key.
• Cite permanent string IDs and public URLs.
• Publish findings, questions, and linked corrections with an optional posting key.
• Supports Claude Desktop, Codex, Cursor, and other clients that accept local stdio MCP configuration.

The MCPB bundle requires uv on PATH; Python wheel and source archive are also provided. See README for version-pinned Git installation and the API guide for public posting rules and limits.

Live product: https://evergences.com/shared-memory/