Skip to content

OH MY PM v0.1.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 17 Jul 11:50
v0.1.0
45a43fb

OH MY PM v0.1.0 — release candidate

This document describes the portable v0.1.0 release bundle. It is a release
candidate: v0.1.0 has not been publicly released or tagged, and there is no
official download yet.

What the bundle contains

The bundle directory oh-my-pm-v0.1.0/ contains:

  • bin/oh-my-pm.mjs — the local CLI entrypoint
  • bin/oh-my-pm-mcp.mjs — the local MCP stdio server entrypoint
  • node_modules/ — the compiled production dependency tree, including the real
    Rust/WASM Kernel (generated-node/oh_my_pm_kernel_bg.wasm)
  • examples/markdown-project/ — the fictional example project
  • README.md, CHANGELOG.md, docs/getting-started.md
  • RELEASE.json — deterministic release metadata
  • SHA256SUMS — SHA-256 checksums for every bundled file

Requirements

  • Node.js 20+

Bundle users do not need Rust, pnpm, or a repository checkout. The build
machine needs the development toolchain; the consumer of the bundle does not.
There are no external integrations in v0.1.0, and there is no npm package.

Release archives

The release is distributed as two deterministic archives plus a checksum file:

oh-my-pm-v0.1.0.tar.gz
oh-my-pm-v0.1.0.zip
oh-my-pm-v0.1.0-SHA256SUMS.txt

Each archive expands to a single top-level oh-my-pm-v0.1.0/ directory. Verify
and extract, then run directly:

sha256sum -c oh-my-pm-v0.1.0-SHA256SUMS.txt   # verify the downloaded archives

tar -xzf oh-my-pm-v0.1.0.tar.gz               # or: unzip oh-my-pm-v0.1.0.zip
node ./oh-my-pm-v0.1.0/bin/oh-my-pm.mjs status
node ./oh-my-pm-v0.1.0/bin/oh-my-pm-mcp.mjs

Given the same verified bundle and toolchain, both archives are byte-identical
across independent builds, so their SHA-256 values are reproducible.

Running the CLI

node ./oh-my-pm-v0.1.0/bin/oh-my-pm.mjs status
node ./oh-my-pm-v0.1.0/bin/oh-my-pm.mjs brief ./project --markdown
node ./oh-my-pm-v0.1.0/bin/oh-my-pm.mjs risks ./project --markdown
node ./oh-my-pm-v0.1.0/bin/oh-my-pm.mjs next ./project --markdown
node ./oh-my-pm-v0.1.0/bin/oh-my-pm.mjs handoff ./project --markdown

Running the MCP server

node ./oh-my-pm-v0.1.0/bin/oh-my-pm-mcp.mjs

The server communicates over stdio only. Its four read-only tools are
project_brief, project_risks, project_next, and project_handoff. Each
tool accepts a local project root.

Project configuration

Each analyzed project may include an optional root-level oh-my-pm.config.json
that selects which Markdown documents are read via include/exclude glob rules
and may lower the default file/byte limits. See the getting-started guide for
details.

Read-only and privacy guarantees

  • No project file is modified
  • No project context is uploaded
  • No telemetry is emitted
  • No HTTP endpoint is exposed (MCP is stdio-only)
  • No external provider integration in v0.1.0

Current limitations

  • local Markdown projects only
  • deterministic extraction, no LLM
  • no external providers
  • no write-back
  • no npm package yet
  • no official GitHub Release yet

Verifying a bundle

From a repository checkout:

node tools/check-release-bundle.mjs --bundle ./oh-my-pm-v0.1.0

The verifier validates RELEASE.json, checks every SHA256SUMS entry, runs the
bundled CLI workflows, and drives the bundled MCP server over stdio — all
against the bundle's own dependency tree, with no dependency on the repository.

Checksums can also be verified independently:

cd oh-my-pm-v0.1.0 && shasum -a 256 -c SHA256SUMS
Assets 5
Loading