Skip to content

OH MY PM v0.3.0-rc.1

Pre-release
Pre-release

Choose a tag to compare

View all tags
@github-actions github-actions released this 26 Jul 18:46
v0.3.0-rc.1
1db4057

OH MY PM v0.3.0-rc.1

Release candidate for the v0.3 line — the Project Brain feature slice. This
is a release candidate, not a stable release. It is a prerelease; it is not
marked "latest" and does not supersede the published stable v0.2.0.

Included

  • Local Markdown Project Brain capture — derive project state from the
    configured Markdown documents, fully offline.
  • Minimized evidence — each observation persists a content fingerprint and
    allow-listed provenance only; never raw document bodies.
  • Deterministic snapshots and changes — the same inputs and injected clock
    produce the same snapshot state fingerprint and the same change set.
  • Capture-order history — memory history presents snapshots in real
    capture order (store format 2), newest capture first.
  • Preview-first memory CLI — capture, changes, status, history,
    export, delete. Mutating commands default to a zero-write preview and
    apply only with --apply.
  • Export and delete — copy committed memory to an explicit destination, and
    remove a project's memory with explicit confirmation.
  • Explicit store migration — the store-format 1 → 2 migration runs only on
    memory capture --apply --migrate-store, retains a backup, and never runs from
    a read.
  • Read-only project_changes MCP tool — a bounded, sanitized projection of
    already-captured memory over stdio.
  • Cross-platform installed qualification — the installed artifact is
    qualified on Windows, macOS, and Linux (Node.js 20+).

Safety

  • Project files are never modified. No command writes into the analyzed
    project directory.
  • Memory writes only through explicit CLI --apply. Previews and read
    commands write nothing and create no application-data directory.
  • The MCP server performs no Project Brain writes. project_changes is
    read-only; there is no Project Brain write tool.
  • No telemetry. The memory path performs no network access and emits no
    telemetry.
  • No cloud or database requirement. Memory lives in the local
    platform-standard application-data directory.
  • No raw body persistence by default. Evidence is minimized to fingerprints
    and allow-listed provenance.
  • Tokens are environment-only — never persisted, printed, or stored.

Not included

  • A stable v0.3 designation. This is a release candidate only.
  • GitHub memory capture. The memory CLI captures local Markdown only.
  • Restore / import / prune / repair. Not implemented.
  • Automatic migration. Migration is explicit and preview-first only.
  • HTTP / SSE / WebSocket MCP. The MCP transport is stdio only.
  • MCP write tools. There are zero Project Brain write tools.
  • A dashboard or UI.
  • Cloud sync.
  • Registry packages. All workspace packages remain private; nothing is
    published to npm, cargo, or any registry.

Compatibility

  • Node.js 20+.
  • Windows, macOS, and Linux.
  • Project Brain schema 1.
  • Project Memory store format 2.
  • Explicit v1 → v2 migration via memory capture --apply --migrate-store.

MCP surface

The v0.3 bundle exposes eleven read-only MCP tools over stdio, in exact
registration order:

project_brief
project_risks
project_next
project_handoff
github_project_brief
github_project_risks
github_project_next
github_project_handoff
provider_status
github_provider_diagnostics
project_changes

project_changes is the single new tool: a read-only, bounded, sanitized
projection of captured memory. The historical v0.2.0 artifact remains a
ten-tool surface and is unchanged by this release candidate.

Assets

oh-my-pm-v0.3.0-rc.1.tar.gz
oh-my-pm-v0.3.0-rc.1.zip
oh-my-pm-v0.3.0-rc.1-SHA256SUMS.txt

Both archives carry the same self-contained "project-brain" profile bundle
(eleven MCP tools, the bundled @oh-my-pm/project-memory package, the six memory
subcommands, Project Brain schema 1, store format 2). They are byte-reproducible
and have equivalent logical inventories.

Getting started

See getting-started-installed-rc.md
for download, checksum verification, preview-first installation, capture, status,
history, changes, export, delete, MCP client configuration, and the explicit
v1 → v2 migration command.

Feedback

As a release candidate, this build exists to gather feedback before a stable v0.3
designation. Please report issues against the v0.3.0-rc.1 tag.

Assets 5
Loading