OH MY PM v0.3.0
OH MY PM v0.3.0
Stable Project Brain foundation for the v0.3 line. This stable release is the
validated promotion of the v0.3.0-rc.1 prerelease — no product behavior changed
between the validated candidate and this stable release; only the version string
moved from 0.3.0-rc.1 to 0.3.0 (plus CI-only artifact-action maintenance and
documentation).
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 — equal inputs and injected clock
produce equal snapshot state fingerprints and equal change sets. - Capture-order history —
memory historypresents 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 → 2migration runs only on
memory capture --apply --migrate-store, retains a backup, and never runs from
a read. - Read-only
project_changesMCP 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.
- 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_changesis
read-only; there are zero Project Brain write tools. - No telemetry, no context upload, no network in the memory path.
- No cloud or database requirement. Memory lives in the local
platform-standard application-data directory. - No raw body persistence by default.
- Tokens are environment-only — never persisted, printed, or stored.
- No registry publication. All workspace packages remain private.
Not included
- GitHub memory capture (the memory CLI captures local Markdown only).
- Restore / import / prune / repair.
- Automatic migration (migration is explicit and preview-first only).
- HTTP / SSE / WebSocket MCP (stdio only).
- MCP write tools (zero Project Brain write tools).
- A dashboard or UI.
- Cloud sync.
- Registry packages.
Compatibility
- Node.js 20+ (the product runtime baseline; unchanged by the CI move to
Node 24 for GitHub Actions JavaScript actions). - Windows, macOS, and Linux.
- Project Brain schema 1.
- Project Memory store format 2.
- Explicit
v1 → v2migration viamemory capture --apply --migrate-store.
Promotion lineage
This stable release was promoted from the validated prerelease v0.3.0-rc.1
(tag target 1db4057b7dfb31cae7f0d6db593928ee1287ef85) after the recorded
post-publication validation
(v0.3.0-rc.1-post-publication-validation.md)
returned GO FOR v0.3.0 STABLE PREPARATION. The immutable v0.1.0,
v0.2.0-rc.1, v0.2.0, and v0.3.0-rc.1 releases are unchanged.
MCP surface
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 Project Brain read tool. The historical v0.2.0
artifact remains a ten-tool surface and is unchanged.
Assets
oh-my-pm-v0.3.0.tar.gz
oh-my-pm-v0.3.0.zip
oh-my-pm-v0.3.0-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.md for
download, checksum verification, preview-first installation, capture, status,
history, changes, export, delete, MCP client configuration, and the explicit
v1 → v2 migration command.