OH MY PM v0.6.0

OH MY PM v0.6.0

Canonical omp command migration and public surface stabilization.

omp is now the canonical command. This is a command namespace migration — not a
product rename, and not a data migration. If you do nothing, everything you
already have keeps working.

Changed

• omp, omp-mcp, and omp-install are canonical. They are the commands
  shown in help output, examples, and all active documentation.
• ohmypm, ohmypm-mcp, and ohmypm-install are now supported compatibility
  aliases. They were canonical in v0.5. They are not deprecated: demoting a
  name that was canonical one minor version ago would retroactively withdraw a
  promise. Each emits one notice on stderr.
• oh-my-pm, oh-my-pm-mcp, and oh-my-pm-install remain deprecated
  aliases. Each emits one deprecation notice on stderr.
• Generated MCP client configuration invokes omp-mcp. The server key is
  unchanged (see below), so regenerating does not create a duplicate entry.
• An install now writes twelve shims — six commands, each with a POSIX and a
  Windows .cmd launcher. The release bundle ships nine executables.
• command-surface.json moves to schema version 2, adding a machine-checked
  product identity block and the two distinct alias classes.

Alias behavior, for both classes:

• stdout is byte-identical to the canonical command's, so a piped --json
  invocation stays parseable.
• The notice goes to stderr only, exactly once per invocation.
• Exit codes are identical.
• The MCP stdio stream is never touched: the notice is written before the
  transport connects, so it cannot desynchronize JSON-RPC.

No removal is scheduled for either alias family.

Unchanged

Identity	Value
Product name	OH MY PM
Package scope	@oh-my-pm/*
Environment prefix	OH_MY_PM_*
Project data directory	.oh-my-pm/
User data directory	~/.oh-my-pm/
Install layout	lib/oh-my-pm/versions/<version>/
Release archives	oh-my-pm-v0.6.0.{tar.gz,zip}
MCP server key	oh-my-pm

Also unchanged:

• Project Memory — schema 1, store format 2. No data migration.
• MCP — the same twelve read-only tools, in the same order, with the same
  schemas and annotations. stdio transport only, zero write tools.
• CLI — every command, JSON output schema, Markdown report structure, and
  exit code.
• Provider behavior and the read-only policy: no project file is ever
  modified, no project context is uploaded, no telemetry is emitted.
• No Dashboard, no HTTP server, no registry publication.

Upgrading

Nothing is required. To adopt the canonical names:

# before
ohmypm brief ./project --json

# after — identical output
omp brief ./project --json

Optionally regenerate your MCP client configuration with omp mcp-config. An
existing configuration naming ohmypm-mcp or oh-my-pm-mcp keeps working.

See the v0.6 migration guide for full before/after examples.

Verification

This release was built and qualified by the manually dispatched
Release v0.6 Stable workflow, which:

• refuses any version other than 0.6.0 and any confirmation other than
  RELEASE v0.6.0;
• verifies the immutable v0.5.4 base lineage
  (288337a9514150b7a5973d9d9410f7186567520f) before building;
• builds a deterministic, reproducible omp-cli-namespace bundle and verifies
  its declared command surface, MCP tool inventory, and product identity;
• qualifies the installed artifact on Ubuntu, macOS, and Windows;
• exercises all three command families for stdout parity, stderr-only notices,
  exactly-one-warning behavior, and MCP protocol cleanliness;
• publishes only after approval of the protected github-release environment.

Known limitations

Unchanged from v0.5 and still future work:

• ApplicationResult<T> is not yet adopted by every workflow return type.
• Provider diagnostics keep their own report shape.
• Advanced side-effect analysis is not implemented.
• No Dashboard.

Requirements

Node.js 20+. No other runtime dependency; a source checkout is not required
after installation.