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

feat: install codex release flows

Browse source
This commit is contained in:
matamune 2026-05-16 20:02:15 +00:00
parent 27979cb621
commit 39e843fb29
Signed by: matamune
GPG key ID: 3BB8E7D3B968A324
12 changed files with 922 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/pages/index.md
View file

@ -104,6 +104,8 @@ DATA_DIR=./data FEED_SOURCES_PATH=./feed-sources.json bun run --filter @peezy.te
- `apps/patch`: Patch service, feed poller, JSONL store, admin API, Discord
output, and workspace backend adapter.
- `flows/patch-moi-harness`: executable maintenance flow for the harness repos.
- `.codex/flows`: installed external flow capabilities, currently the Codex
release maintenance flows from the neighboring `../codex-flows` pack.
- `harness`: upstream and maintained fork repositories used for rehearsal.
- `.codex/workspace.toml`: optional repo-native workspace automation config.
- `docs`: this Tome documentation site.

15
docs/pages/reference/packages.md
View file

@ -44,6 +44,21 @@ 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:
```bash
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:

31
docs/pages/tutorials/dispatch-codex-release-flow.md
View file

@ -34,7 +34,32 @@ git status --short --branch
If `git status` shows local changes or untracked files, resolve them before an
automated rebase.
## 2. Point Patch at a workspace backend
## 2. Install the Codex release capabilities
The Codex release maintenance capabilities are installed from the neighboring
`../codex-flows` pack into `.codex/flows`:
```bash
codex-flows pack add ../codex-flows \
--include openai-codex-bindings \
--include peezy-codex-fork \
--apply
codex-flows pack doctor --json
```
The current local install pins `openai-codex-bindings` and `peezy-codex-fork`
in `.codex/pack-lock.json`. `@peezy.tech/flow-runtime@0.4.0` discovers
installed `.codex/flows/*` before source-owned `flows/*`, so the installed
Codex capabilities are visible to patch.moi while the harness remains a
source-owned repo flow.
Safe local verification stops at event matching and runner gating. The test
suite confirms that a stored `upstream.release` event for `openai/codex`
selects both installed Codex release steps, and that the Code Mode step still
requires `CODEX_FLOWS_ENABLE_CODE_MODE=1`. Do not fabricate a full
`openai/codex` release lifecycle just to exercise the flow.
## 3. Point Patch at a workspace backend
```bash
PATCH_WORKSPACE_BACKEND_URL=http://127.0.0.1:3586 \
@ -52,7 +77,7 @@ workspace flow capability. `PATCH_FLOW_BACKEND_URL` and
Leave `PATCH_WORKSPACE_BACKEND_URL` unset only when you intentionally want local
flow execution from the Patch process working directory.
## 3. Inspect the stored event
## 4. Inspect the stored event
```bash
curl http://127.0.0.1:3000/flow-events
@ -61,7 +86,7 @@ curl http://127.0.0.1:3000/flow-events
When `PATCH_ADMIN_TOKEN` is set, include either `Authorization: Bearer <token>`
or `X-Patch-Admin-Token: <token>`.
## 4. Keep completion workspace-owned, state app-owned
## 5. Keep completion workspace-owned, state app-owned
Patch dispatches the generic event. The installed Codex release flow or
workspace owns the work that happens next: