History

matamune 81ea91e387 Some checks failed check / check (push) Failing after 3s Details Adopt codex-flows 0.3.5 surfaces		2026-05-18 00:07:15 +00:00
..
exec	Adopt codex-flows 0.3.5 surfaces	2026-05-18 00:07:15 +00:00
fixtures	Add patch maintenance harness flow	2026-05-16 05:40:42 +00:00
schemas	Add patch maintenance harness flow	2026-05-16 05:40:42 +00:00
flow.toml	Record maintenance outcomes from workspace runs	2026-05-16 05:50:00 +00:00
README.md	feat: add workspace flow harness smoke	2026-05-16 19:55:05 +00:00

README.md

patch-moi-harness Flow

This flow is the first executable patch.moi maintenance harness. It consumes a generic upstream.release event for peezy-tech/patch-moi-harness, then uses Git state in harness/fork to keep the maintained fork on top of the upstream release tag.

The default behavior is local and reviewable:

fetch the configured upstream remote
switch to the maintained fork branch
rebase onto the release tag when the tag is not already an ancestor
run the configured package checks
emit candidate branch refs in the FLOW_RESULT artifacts
leave pushes disabled unless CODEX_FLOW_PUSH=1 is set

Useful overrides:

CODEX_FLOW_FETCH=0 bun run harness:flow
CODEX_FLOW_PUSH=1 bun run harness:flow

The fixture event is fixtures/upstream-release-v0.1.3.json. It should be a no-op rebase against the current harness fork while still verifying the package surface and reporting the local maintained branch as the candidate ref.

The repo also exposes an experimental workspace-owned flow smoke task:

cd ../codex-flows
bun run workspace:backend --cwd /home/peezy/meta-workspace/patch.moi

CODEX_WORKSPACE_BACKEND_WS_URL=ws://127.0.0.1:3586 \
CODEX_FLOW_FETCH=0 CODEX_FLOW_PUSH=0 \
bun run workspace:run:harness-flow

That task requires a running Codex workspace backend and writes backend event/run state, not patch.moi DATA_DIR maintenance-attempt state.