peezy-tech/patch.moi
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
patch.moi/docs/pages/reference/packages.md

2.4 KiB
Raw Blame History

title description
Packages Workspace packages in the patch.moi monorepo.

Packages

@peezy.tech/patch

The Bun service in apps/patch. It exports no public package API; its runtime entry point is src/server.ts.

Responsibilities:

  • Poll configured feeds.
  • Normalize entries into FeedSignal records.
  • Store JSONL state.
  • Submit generic FlowEvent triggers through the patch.moi workspace backend adapter.
  • Serve admin inspection, retry, and replay endpoints.

The service package does not store patch contents. Maintained patch stacks live in Git repositories operated on by local workspaces or forge runners.

@peezy.tech/patch-docs

The Tome documentation package in docs. Build it with:

bun run docs:build

Root Workspace

The repository root owns shared scripts and dev dependencies. It installs @peezy.tech/codex-flows so repo-native workspace commands are available:

bun run workspace:doctor
bun run workspace:tick
bun run workspace:run:harness

Those commands are operator automation around the repo. They do not replace the Patch service package or its DATA_DIR state.

Installed Flow Capabilities

External flow capabilities are installed under .codex/flows and tracked in .codex/pack-lock.json. The current install brings in the Codex release maintenance flows from the sibling ../codex-flows repository:

codex-flows pack doctor --json

openai-codex-bindings and peezy-codex-fork both match upstream.release events for openai/codex. They are installed capabilities, not patch.moi product state. patch.moi still records feed-owned flow events, workspace dispatches, and maintenance attempts under DATA_DIR.

Related Runtime Packages

These published packages define the current patch.moi integration baseline:

Package Published version patch.moi use
@peezy.tech/codex-flows 0.3.4 repo-native workspace commands and CLI automation
@peezy.tech/flow-runtime 0.4.0 local flow discovery, matching, execution, and Bun flow helpers
@peezy.tech/flow-backend-convex 0.4.0 optional generic durable flow backend for future service experiments

patch.moi product state still belongs in the Patch service JSONL store by default. flow-backend-convex should be considered only when patch.moi needs a generic durable flow event/run backend; it is not the default home for feed signals, workspace dispatch records, or maintenance attempts.