Implement allod change workflow

vnprc-agent commented

2026-06-23 00:08:20 +01:00

Contributor

Goal

Implement the allod change workflow as the reusable CLI interface for safe codebase changes by agents or humans.

Design docs

User story: allod/strategy/user-stories/pr-harness-user-story.md
Dev plan: allod/strategy/dev-plans/pr-harness-script-dev-plan.md

Supersedes notes#36, which started as a "PR workflow subagent" idea. The design moved to a tool-first workflow: a script in allod/tools that mechanically handles the risky git/PR steps instead of relying on an agent retaining workflow rules in context.

Command surface

allod change begin [-d <description>] [<repo-path>]   # worktree + branch setup
allod change record -m <msg> [-f <file>...]            # stage + commit + push
allod change submit -t <title> -B <body-file> [--base] [--depends-on]  # PR creation
allod change cleanup <worktree-path>                   # worktree teardown

record and submit are separate commands. Most ceremony touchpoints only need record; PR creation is a distinct step via submit. See the dev plan for full interface contracts and rationale.

Done when

Acceptance tests from the dev plan pass for begin, record, submit, and cleanup.
Tests verify the tool never amends and never force-pushes.
Tests verify protected-branch safety checks refuse with actionable messages.
Tests verify PR creation requires ## Validation.
Manual smoke test works from a protected repo.

## Goal Implement the `allod change` workflow as the reusable CLI interface for safe codebase changes by agents or humans. ## Design docs - User story: `allod/strategy/user-stories/pr-harness-user-story.md` - Dev plan: `allod/strategy/dev-plans/pr-harness-script-dev-plan.md` Supersedes notes#36, which started as a "PR workflow subagent" idea. The design moved to a tool-first workflow: a script in allod/tools that mechanically handles the risky git/PR steps instead of relying on an agent retaining workflow rules in context. ## Command surface ```bash allod change begin [-d <description>] [<repo-path>] # worktree + branch setup allod change record -m <msg> [-f <file>...] # stage + commit + push allod change submit -t <title> -B <body-file> [--base] [--depends-on] # PR creation allod change cleanup <worktree-path> # worktree teardown ``` `record` and `submit` are separate commands. Most ceremony touchpoints only need `record`; PR creation is a distinct step via `submit`. See the dev plan for full interface contracts and rationale. ## Done when - Acceptance tests from the dev plan pass for `begin`, `record`, `submit`, and `cleanup`. - Tests verify the tool never amends and never force-pushes. - Tests verify protected-branch safety checks refuse with actionable messages. - Tests verify PR creation requires `## Validation`. - Manual smoke test works from a protected repo.

vnprc closed this issue

2026-06-24 15:24:43 +01:00

vnprc-agent referenced this issue

2026-06-24 20:03:01 +01:00

Add allod change workflow harness #69

vnprc-agent reopened this issue

2026-06-24 20:03:01 +01:00

vnprc-agent commented

2026-06-24 20:03:19 +01:00

Author