Skip to content

OH MY PM v0.5.1

Choose a tag to compare

View all tags
@github-actions github-actions released this 01 Aug 12:57
v0.5.1
49e2cbb
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

OH MY PM v0.5.1

Maintenance release. It fixes two internal problems and adds no user-facing
capability.

  1. Active documentation no longer matched the shipped product.
  2. Shared application logic lived inside the CLI package, so the MCP server had
    to depend on the CLI to reuse it.

Everything you can observe is unchanged from v0.5.0. No migration is
required.

Release lineage

There is no v0.5.0 tag and no v0.5.0 GitHub release. The v0.5.0 work
merged to main as a source candidate and was never published.
Latest published stable, and immutable base v0.4.0
v0.5.0 superseded, unpublished source candidate
v0.5.1 prepared; would be the first published stable of the v0.5 line

No existing release tag is moved, replaced, recreated, or deleted, and no
v0.5.0 tag is invented. Merging the v0.5.1 pull request publishes nothing.

What changed

Active documentation corrected to match the actual system

The repository shipped five release lines while parts of its documentation
stayed frozen at v0.2 and v0.3. The corrections are not cosmetic — several
claims inverted reality:

Document Was Now
project-memory/README.md "Nothing invokes it yet" lists the seven CLI subcommands and two MCP tools that invoke it
runtime/src/index.ts "no CLI or MCP surface invokes the Project Brain Runtime" describes the surfaces that do
installer/README.md "does not write files ... will be added in a later phase" documents the shipped transactional prefix install
docs/architecture.md the initial scaffold and a "planned" architecture the implemented system, all layers, and the enforced boundaries
README.md the 0.3.1 source line, ten MCP tools, "early-stage" the current source line, twelve tools, the shipped capability table
mcp-server/README.md eleven tools, project_timeline absent all twelve in registration order, zero write tools
cli/README.md six memory subcommands, ten MCP tools seven subcommands, twelve tools
docs/getting-started.md v0.2.0 as latest stable, four shims, eleven tools v0.4.0, eight shims, twelve tools
docs/roadmap.md v0.4.0 "prepared but not published", v0.4 active v0.4.0 published, v0.5.1 active, explicit states
docs/security-model.md project data in .oh-my-pm/ inside the project the application-data boundary the code enforces

Historical documents were deliberately left alone. docs/releases/**,
docs/v0.3/**, docs/v0.4/**, the v0.2 stabilization audit, and superseded
CHANGELOG entries are point-in-time records; their old versions and tool counts
were true when written and remain historically accurate.

A new validator, pnpm validate:docs, keeps them honest. It derives every
expectation from a canonical source — version.json, command-surface.json,
the MCP tool registration sites, and the memory subcommand allowlist — so it
introduces no second source of truth.

Shared application boundary

New private workspace package @oh-my-pm/application. CLI and MCP are now
presentation adapters over the same typed use cases.

CLI ───────────┐
MCP ───────────┼──> Application ──> Runtime / Providers / Project Memory
Future UI ─────┘                    └──> Planner / Skills / Kernel

The Future UI line is architectural context only. This release includes no
Dashboard.

The modules were moved, not copied, so no orchestration is duplicated. The MCP
server's dependency on @oh-my-pm/cli is removed from its manifest and from
every import.

See the application boundary and
the v0.5.1 scope.

What did not change

Surface v0.5.1
Canonical commands ohmypm, ohmypm-mcp, ohmypm-install
Compatibility aliases oh-my-pm, oh-my-pm-mcp, oh-my-pm-install — no removal scheduled
CLI commands, grammar, options, defaults unchanged
CLI exit codes and stdout/stderr separation unchanged
CLI JSON and Markdown output unchanged
MCP tools twelve read-only, zero write, exact same registration order
MCP schemas, annotations, error codes unchanged
MCP transport stdio only
Memory subcommands seven
Project Brain schema 1
Project Memory store format 2
Storage paths and record formats unchanged
Release line / bundle profile v0.5 / ohmypm-cli-namespace
Node.js runtime 20+
npm publication none; packages remain private
  • No new user-facing feature.
  • No new command.
  • No new MCP tool.
  • No schema or store-format change.
  • No migration is required.
  • No Dashboard is included.
  • No release is published by merging the pull request.

Upgrading

Nothing to do. An existing installation, an existing MCP client configuration,
and an existing Project Brain store all keep working unchanged. deprecatedSince
remains 0.5.0 — the aliases were deprecated then, and that fact is unchanged.

Verification

Public compatibility was verified against a pre-refactor build:

  • CLI stdout, stderr, and exit codes byte-identical across seventeen
    representative invocations, including error paths. The only difference is the
    version and kernelVersion fields, which report 0.5.1.
  • The MCP tool list, registration order, input and output schemas, and
    annotations compared byte-for-byte against a captured v0.5.0 server response:
    identical.
  • Both compatibility aliases still warn on stderr only, never on stdout.

New enforcement:

  • pnpm validate:docs — documentation truth
  • pnpm validate:boundaries — the application boundary, with guards verified by
    injecting each violation
  • mcp-server/test/application-boundary.test.ts — the twelve-tool contract and
    the absent CLI dependency

Related issues

Closes #23, #24, #25, #26, #27.

Assets 5
Loading