[Mirr0ch1]

Summary

Adds optional two-way bridges that let CodeBuddy Code and oh-my-pi read and edit OpenCode's workspace memory, so the same decisions, preferences, and project facts follow you between harnesses. The README now presents memory sharing as a project feature: CodeBuddy Code and oh-my-pi are supported today, more local harness agents are in progress.

Stacked on #9. This branch builds on the V2 adapter. The commits after feat: add OpenCode V2 plugin adapter are specific to this PR. Please merge #9 first; GitHub will then reduce this PR to the bridge diff.

What changed

CodeBuddy Code

• Added src/codebuddy-bridge.ts, a filesystem bridge between the JSON workspace store and CodeBuddy's Markdown memory.
• OpenCode writes opencode-<id>.md topic files plus one marked block in CodeBuddy's MEMORY.md.
• CodeBuddy topic files are indexed in the OpenCode prompt; shared: true imports them into JSON memory.
• Edits to opencode-*.md are imported back; deleting one supersedes the memory.

oh-my-pi (local backend)

• Added src/oh-my-pi-bridge.ts, a line-oriented bridge for omp's plain-Markdown local memory backend.
• OpenCode exports memories as - [opencode:<id>] <text> lesson lines in ~/.omp/agent/memories/<encoded-workdir>/learned.md.
• oh-my-pi lessons are indexed in the OpenCode prompt; up to 12 recent lessons are imported as omp-tagged JSON memories.
• Editing an exported line updates the memory, deleting it supersedes it, and deleting/re-adding an oh-my-pi lesson mirrors the imported copy.
• memory_summary.md, MEMORY.md, and skills/ are owned by oh-my-pi's consolidation pipeline and are never written.

Shared plumbing

• Wired both bridges into src/runtime.ts, so V1 and V2 adapters support them.
• Added atomicWriteText to the storage layer for generated Markdown mirrors.
• Added tests/codebuddy-bridge.test.ts and tests/oh-my-pi-bridge.test.ts, plus a V2 adapter integration test for each bridge.
• Documented both bridges in README.md, docs/architecture.md, docs/configuration.md, AGENTS.md, and CHANGELOG.md.

Ownership model

Both bridges only write files/lines OpenCode owns and never rewrite another agent's content.

Target	OpenCode-owned	Target-owned
CodeBuddy	opencode-<id>.md, one marked block in MEMORY.md	All other topic files and index lines
oh-my-pi	- [opencode:<id>] ... lines in learned.md	Other - <lesson> lines, memory_summary.md, MEMORY.md, skills/

• Per-workspace hashes live in codebuddy-bridge.json / oh-my-pi-bridge.json beside workspace-memory.json, preventing write/read loops.
• Credential-looking content is skipped or redacted unless includeSensitive is enabled.
• Neither bridge requires hooks or patches in the target agent.

Configuration

{
  "plugins": [
    {
      "package": "opencode-working-memory",
      "options": {
        "codeBuddyBridge": { "includeGlobal": true, "includeSensitive": false },
        "ohMyPiBridge": { "includeSensitive": false }
      }
    }
  ]
}

Both bridges are disabled unless their option object is present. oh-my-pi requires memory.backend: local in ~/.omp/agent/config.yml.

Verification

• npm run typecheck
• npm test: 565 passing (including 15 new bridge tests)
• npm run build
• npm run check:package-integrity
• V2 adapter tests confirm each bridge runs from session.hook("context") and exports the expected files.

Scope and follow-ups

• CodeBuddy is detected through ~/.codebuddy; oh-my-pi through ~/.omp/agent (both overridable).
• oh-my-pi's mnemopi, hindsight, and sharpshooter backends are intentionally out of scope; only the plain-Markdown local backend is bridged.
• Both bridges stay off by default because they write outside OpenCode's data directory.