continuous-refactoring 0.1.0__tar.gz → 0.3.0__tar.gz

{continuous_refactoring-0.1.0 → continuous_refactoring-0.3.0}/.gitignore

@@ -1,4 +1,6 @@
 .scratchpad/
+tmpdir/
+.pytest_cache/
 
 # Byte-compiled / optimized / DLL files
 __pycache__/

{continuous_refactoring-0.1.0 → continuous_refactoring-0.3.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: continuous-refactoring
-Version: 0.1.0
+Version: 0.3.0
 Summary: Continuous refactoring loop for AI coding agents
 Project-URL: Repository, https://github.com/bigH/continuous-refactoring
 Project-URL: Issues, https://github.com/bigH/continuous-refactoring/issues
@@ -23,16 +23,43 @@ Description-Content-Type: text/markdown
 
 # continuous-refactoring
 
+[![GitHub repo](https://img.shields.io/badge/github-repo-green)](https://github.com/bigH/continuous-refactoring)
+[![PyPI](https://img.shields.io/pypi/v/continuous-refactoring.svg)](https://pypi.org/project/continuous-refactoring/)
+[![Tests](https://github.com/bigH/continuous-refactoring/actions/workflows/test.yml/badge.svg)](https://github.com/bigH/continuous-refactoring/actions/workflows/test.yml)
+[![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](https://github.com/bigH/continuous-refactoring/blob/main/LICENSE)
+
 Small, test-gated cleanup commits by an AI coding agent.
 
 Think of it as a supervised janitor loop: the agent proposes a cleanup, your tests decide if it stays.
 
+Here's [an article](https://artisincode.com/essays/how-i-use-unspent-tokens/) I wrote about it.
+
 ## Install
 
+Try it without installing:
+
+```bash
+uvx continuous-refactoring --help
+```
+
+Or install it with [uv](https://docs.astral.sh/uv/guides/tools/):
+
 ```bash
 uv tool install continuous-refactoring
 ```
 
+Or with [pipx](https://pypa.github.io/pipx/):
+
+```bash
+pipx install continuous-refactoring
+```
+
+Or with pip:
+
+```bash
+pip install continuous-refactoring
+```
+
 For a checkout:
 
 ```bash
@@ -67,15 +94,18 @@ continuous-refactoring run \
   --max-attempts 2
 ```
 
-That keeps sweeping targets until it runs out, hits your caps, or starts failing.
+That runs up to 10 refactor actions, then stops sooner if the finite target file
+runs out or the loop starts failing. Use `run --focus-on-live-migrations` when
+you want the loop to work only on eligible live migrations; it bypasses target
+selection and `--max-refactors`.
 
 ## What it does
 
-- Resolves a target from `--targets`, `--globs`, `--extensions`, or `--paths`, with optional natural-language scoping via `--scope-instruction`.
+- Resolves each source action from `--targets`, `--globs`, `--extensions`, or `--paths`, with optional natural-language scoping via `--scope-instruction`.
 - Runs the agent with a refactoring prompt + your "taste" guidelines.
 - Runs your validation command (default: `uv run pytest`).
 - If green and there's a diff, it commits locally and leaves the branch for you to inspect.
-- Repeats until it runs out of targets, hits the retry budget, or stacks too many failures.
+- Repeats until it spends the action budget, exhausts a finite target file, hits the retry budget, or stacks too many failures.
 
 ## Requirements
 
@@ -89,6 +119,8 @@ That keeps sweeping targets until it runs out, hits your caps, or starts failing
 ```bash
 # 1. Register the repo (creates a project dir under ~/.local/share/continuous-refactoring)
 continuous-refactoring init
+# Or keep project taste in the repo:
+continuous-refactoring init --in-repo-taste
 
 # 2. (Optional) Write your refactoring taste — either edit the file, have an agent interview you,
 #    or refine an existing draft collaboratively
@@ -113,13 +145,18 @@ continuous-refactoring run \
 
 | Command | What it does |
 |---|---|
-| `init` | Registers this directory as a project, creates a default `taste.md`, and can store `--live-migrations-dir`. |
+| `init` | Registers this directory as a project, creates a default `taste.md`, and can store `--live-migrations-dir` or `--in-repo-taste`. |
 | `taste` | Prints the active taste file path. Add `--interview` to have an agent author it, `--refine` to iteratively improve an existing taste doc, `--upgrade` to refresh stale taste dimensions, `--global` for the shared file, and `--force` to let `--interview` overwrite custom content after writing a `.bak`. |
 | `run-once` | Single pass on one resolved target. No retry. If there is a diff and validation passes, it commits locally and prints the diffstat. |
-| `run` | The loop. Iterates targets, retries on failure, and commits successful targets locally. |
+| `run` | The loop. Iterates refactor actions, retries on failure, and commits successful changes locally. Add `--focus-on-live-migrations` to bypass targeting and work only on eligible live migrations. |
 | `upgrade` | Checks that the global config manifest is current, rewrites it idempotently, and warns if the global taste file is stale. |
-| `review list` | Lists migrations flagged for human review (`awaiting_human_review`). |
-| `review perform <migration>` | Starts an interactive agent session to resolve a flagged migration's review. Requires `--with`, `--model`, and `--effort`. |
+| `migration list` | Lists visible migrations. Add `--status <status>` or `--awaiting-review` to filter. |
+| `migration doctor <slug-or-path>` | Validates one visible migration's consistency. |
+| `migration doctor --all` | Validates every visible migration plus internal transaction state. |
+| `migration review <slug-or-path>` | Starts staged review for a migration awaiting human review. Requires `--with`, `--model`, and `--effort`. |
+| `migration refine <slug-or-path>` | Records feedback for a planning or unexecuted ready migration and runs one staged planning revision. Requires `--message <text>` or `--file <path>`, plus `--with`, `--model`, and `--effort`; add `--show-agent-logs` to mirror the planning agent. |
+
+Legacy `review list` and `review perform <migration>` remain compatibility aliases; prefer `migration list --awaiting-review` and `migration review`.
 
 ## Targeting / Useful flags
 
@@ -130,21 +167,46 @@ Target resolution is first-match-wins:
 
 These flags are not mutually exclusive, but only the highest-priority populated source is used.
 
-- `--targets path/to/targets.jsonl` — explicit list; one JSON object per line with `description`, `files`, optional `scoping`, `model-override`, `effort-override`. Effort overrides use `low`, `medium`, `high`, or `xhigh`.
-- `--globs 'src/**/*.py:tests/**/*.py'` — colon-separated globs; each matched file becomes its own target.
-- `--extensions .py,.ts` — shorthand that expands to `**/*.py`, `**/*.ts`; each matched file becomes its own target.
-- `--paths a.py:b.py` — literal paths, all treated as one target.
-- `--scope-instruction "clean up the auth module"` — extra free-text scoping. If file-based targeting resolves nothing, this becomes the useful fallback context.
+- `--targets path/to/targets.jsonl` — explicit finite list; one JSON object per line with `description`, `files`, optional `scoping`, `model-override`, `effort-override`. Effort overrides use `low`, `medium`, `high`, or `xhigh`. If `--max-refactors` is omitted, `run` processes the file once and stops.
+- `--globs 'src/**/*.py:tests/**/*.py'` — colon-separated globs matched once against tracked files from `git ls-files`; each refactor action samples one matched file, so files can repeat.
+- `--extensions .py,.ts` — shorthand that expands to `**/*.py`, `**/*.ts` against tracked files from `git ls-files`; each refactor action samples one matched file, so files can repeat.
+- `--paths a.py:b.py` — literal user-provided paths, all treated as one grouped target; each refactor action reuses that group.
+- `--scope-instruction "clean up the auth module"` — extra free-text scoping. If selected file patterns resolve nothing, this becomes the useful fallback context.
+
+If `--globs` or `--extensions` match no tracked files and there is no
+`--scope-instruction`, `run` completes successfully with zero refactor actions.
+`--paths` is literal input and is not filtered through `git ls-files`.
 
-If you provide none of `--targets`, `--globs`, `--extensions`, or `--paths`, then `run` and `run-once` require `--scope-instruction`.
+If you provide none of `--targets`, `--globs`, `--extensions`, or `--paths`,
+then `run` and `run-once` require `--scope-instruction`; the driver still
+random-samples tracked files from `git ls-files` for each action and uses the
+scope text as context for that target.
 
 ### Migrations & taste flags
 
 - `init --live-migrations-dir PATH` — enables the larger-refactoring workflow for this project. The path is stored repo-relative in the project registry and created if missing.
+- `init --in-repo-taste [PATH]` — stores this project's taste file in the repo and remembers the repo-relative path. Defaults to `.continuous-refactoring/taste.md`; re-run `init --in-repo-taste ...` to choose a different path.
+- `migration list` — shows visible migrations; `--awaiting-review` narrows to human-review handoffs.
+- `migration doctor <slug-or-path>` / `migration doctor --all` — read-only consistency checks. Doctor reports problems; it does not repair them.
+- `migration review <slug-or-path> --with ... --model ... --effort ...` — resolves an `awaiting_human_review` migration through a staged workspace.
+- `migration refine <slug-or-path> (--message <text>|--file <path>) --with ... --model ... --effort ... [--show-agent-logs]` — adds user feedback to a planning or unexecuted ready migration and resumes planning through the `revise` step when reopening ready work.
 - `taste --refine` — opens a collaborative editing session for the taste file. The agent keeps refining until you tell it to write, then the session ends automatically after the settled write.
 - `taste --upgrade` — re-interviews for taste dimensions added since your last version. No-op when already current; use `taste --refine` if you want to rework the doc anyway.
 - `taste --force` — only applies to `--interview`; it allows a customized taste file to be overwritten after backing it up to `taste.md.bak`.
 
+Canonical migration commands:
+
+```bash
+continuous-refactoring migration list
+continuous-refactoring migration list --status planning
+continuous-refactoring migration list --awaiting-review
+continuous-refactoring migration doctor <slug-or-path>
+continuous-refactoring migration doctor --all
+continuous-refactoring migration review <slug-or-path> --with codex --model gpt-5 --effort high
+continuous-refactoring migration refine <slug-or-path> --message "split the risky phase" --with codex --model gpt-5 --effort high
+continuous-refactoring migration refine <slug-or-path> --file feedback.md --with codex --model gpt-5 --effort high
+```
+
 ### Shared `run` / `run-once` flags
 
 - `--with`, `--model` — required agent backend/model selection.
@@ -159,10 +221,11 @@ If you provide none of `--targets`, `--globs`, `--extensions`, or `--paths`, the
 
 ### `run`-only flags
 
-- `--max-attempts N` — per-target retry budget. `1` = no retry, `0` = unlimited (which means permanently broken targets will never give up).
-- `--max-refactors N` — cap the number of targets per run. Required unless you use `--targets`.
-- `--max-consecutive-failures N` — bail after N targets fail in a row. Default 3.
-- `--sleep SECONDS` — pause between completed targets. Useful when you want a long batch without hammering the repo or your agent budget.
+- `--max-attempts N` — per-action retry budget. `1` = no retry, `0` = unlimited (which means permanently broken actions will never give up).
+- `--max-refactors N` — cap the number of refactor actions per run. Required unless you use `--targets` or `--focus-on-live-migrations`.
+- `--focus-on-live-migrations` — bypass target selection and `--max-refactors`; iterate eligible live migrations until they are done, deferred, blocked, or the failure budget trips.
+- `--max-consecutive-failures N` — bail after N actions fail in a row. Default 3.
+- `--sleep SECONDS` — pause between completed actions. Useful when you want a long batch without hammering the repo or your agent budget.
 - `--commit-message-prefix TEXT` — subject prefix for successful refactor or migration-plan commits. Default `continuous refactor`.
 
 ## Safety behaviors
@@ -179,22 +242,36 @@ If you provide none of `--targets`, `--globs`, `--extensions`, or `--paths`, the
 Each run writes to `$TMPDIR/continuous-refactoring/<run-id>/`:
 
 - `summary.json` — rolling status, counts, per-attempt stats
-- `events.jsonl` — structured event log
+- `events.jsonl` — structured event log with call roles such as `classify`,
+  `planning.<step>`, `phase.ready-check`, `phase.execute`, and
+  `phase.validation`
 - `run.log` — human-readable log
 - `attempt-NNN/[retry-NN/]refactor/` — per-attempt agent + test stdout/stderr
+- `baseline/initial/` — baseline validation stdout/stderr before work starts
+- `classify/` — classifier agent stdout/stderr
+- `scope-expansion/` — scope candidates, selection, and bypass reason
+- `attempt-NNN/[retry-NN/]planning/<step>/` — planning agent stdout/stderr for
+  migration planning steps
+- `phase-ready-check/` — phase precondition agent stdout/stderr
+- `attempt-NNN/[retry-NN/]phase-execute/` — phase agent and validation logs
+- `migration-probes/action-NNN/` — migration probe logs during normal `run`
+  actions, including planning, phase ready-checks, and phase execution
 
 Mixed-effort runs are auditable: summaries and call events record the default effort, max allowed effort, requested effort, effective effort, source, and whether the request was capped.
 
-The path prints at startup. Grep it when something goes sideways.
+The path prints at startup. Grep it when something goes sideways. Failed
+non-commit decisions also write durable XDG snapshots under the project failure
+directory, usually
+`~/.local/share/continuous-refactoring/projects/<uuid>/failures/`.
 
 ## Taste files
 
 The taste file is a short bullet list of your refactoring preferences. It gets injected into every agent prompt.
 
-- Project taste: `~/.local/share/continuous-refactoring/projects/<uuid>/taste.md`
+- Project taste: `~/.local/share/continuous-refactoring/projects/<uuid>/taste.md`, or the repo-local path chosen with `init --in-repo-taste [PATH]`
 - Global taste: `~/.local/share/continuous-refactoring/global/taste.md`
 
-Project taste wins over global. Use `taste --interview` to bootstrap one, `taste --refine` to rework it with an agent, or edit the file directly any time.
+Project taste wins over global. Use `taste` to print the active path, `taste --interview` to bootstrap one, `taste --refine` to rework it with an agent, or edit the file directly any time.
 
 ## Larger refactorings
 
@@ -213,7 +290,7 @@ This tells the CLI where to store migration artifacts. The path is repo-relative
 Each `run` / `run-once` tick now checks for eligible migration work before falling back to single-commit cleanups:
 
 1. **Classify** — a classifier agent reads the target and decides: `cohesive-cleanup` (one-shot path) or `needs-plan` (migration path).
-2. **Plan** — for `needs-plan` targets, a six-stage planning workflow runs: generate approaches → pick best → expand into phases → review → revise → final review. Artifacts land under `<live-migrations-dir>/<migration-name>/`.
+2. **Plan** — for `needs-plan` targets, each automation action runs exactly one planning step: approaches, pick-best, expand, review, optional revise/review-2, then final-review. Accepted steps update `.planning/state.json`, store stdout under `.planning/stages/`, and publish through a staged transaction. Failed current-step output stays in run artifacts and is not resume input.
 3. **Execute** — each phase is a self-contained unit of work. The tick picks the oldest eligible migration, checks whether its current phase precondition is satisfied, and executes it on the current branch. Phase completion is judged against the phase file's `## Definition of Done`; commit message identifies the migration as `migration/<name>/<phase-file>.md`.
 
 ### Migration directory layout
@@ -222,14 +299,20 @@ Each `run` / `run-once` tick now checks for eligible migration work before falli
 <live-migrations-dir>/
   <migration-name>/
     manifest.json          # status, phases, wake-up schedule
+    .planning/
+      state.json           # durable planning cursor and accepted step refs
+      stages/              # accepted planning stdout, suffixed on repeats
     plan.md                # the expanded plan
     approaches/            # candidate approaches considered during planning
     phase-1-<name>.md      # per-phase specification
     phase-2-<name>.md
     ...
+  __transactions__/        # internal staged publish state
   __intentional_skips__/   # migrations rejected at final review
 ```
 
+Do not edit `.planning/` or `__transactions__/` by hand. Use `migration doctor` when the shape looks wrong.
+
 ### Wake-up rules
 
 Migrations don't run on every tick. The scheduler now separates **activity** from
@@ -263,7 +346,7 @@ Before executing a phase, a ready-check agent verifies that the current phase pr
 
 - **ready: yes** — phase executes; on green tests, the phase is marked done, any prior deferral markers are cleared, and the migration advances immediately to the next phase.
 - **ready: no** — manifest activity is bumped, a retry cooldown is started, and a future `wake_up_on` is recorded when needed; the tick moves on.
-- **ready: unverifiable** — the migration is flagged `awaiting_human_review` and put on cooldown. Automated migration ticks skip flagged migrations until review clears the flag. Use `review list` to find it and `review perform <migration> --with ... --model ... --effort ...` to resolve it interactively.
+- **ready: unverifiable** — the migration is flagged `awaiting_human_review` and put on cooldown. Automated migration ticks skip flagged migrations until review clears the flag. Use `migration list --awaiting-review` to find it and `migration review <slug-or-path> --with ... --model ... --effort ...` to resolve it interactively.
 
 Human-facing migration references use the relative phase spec path, for example `phase-2-failure-report.md`. The manifest cursor stores the phase `name`, not a numeric index.
 

{continuous_refactoring-0.1.0 → continuous_refactoring-0.3.0}/README.md

@@ -1,15 +1,42 @@
 # continuous-refactoring
 
+[![GitHub repo](https://img.shields.io/badge/github-repo-green)](https://github.com/bigH/continuous-refactoring)
+[![PyPI](https://img.shields.io/pypi/v/continuous-refactoring.svg)](https://pypi.org/project/continuous-refactoring/)
+[![Tests](https://github.com/bigH/continuous-refactoring/actions/workflows/test.yml/badge.svg)](https://github.com/bigH/continuous-refactoring/actions/workflows/test.yml)
+[![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](https://github.com/bigH/continuous-refactoring/blob/main/LICENSE)
+
 Small, test-gated cleanup commits by an AI coding agent.
 
 Think of it as a supervised janitor loop: the agent proposes a cleanup, your tests decide if it stays.
 
+Here's [an article](https://artisincode.com/essays/how-i-use-unspent-tokens/) I wrote about it.
+
 ## Install
 
+Try it without installing:
+
+```bash
+uvx continuous-refactoring --help
+```
+
+Or install it with [uv](https://docs.astral.sh/uv/guides/tools/):
+
 ```bash
 uv tool install continuous-refactoring
 ```
 
+Or with [pipx](https://pypa.github.io/pipx/):
+
+```bash
+pipx install continuous-refactoring
+```
+
+Or with pip:
+
+```bash
+pip install continuous-refactoring
+```
+
 For a checkout:
 
 ```bash
@@ -44,15 +71,18 @@ continuous-refactoring run \
   --max-attempts 2
 ```
 
-That keeps sweeping targets until it runs out, hits your caps, or starts failing.
+That runs up to 10 refactor actions, then stops sooner if the finite target file
+runs out or the loop starts failing. Use `run --focus-on-live-migrations` when
+you want the loop to work only on eligible live migrations; it bypasses target
+selection and `--max-refactors`.
 
 ## What it does
 
-- Resolves a target from `--targets`, `--globs`, `--extensions`, or `--paths`, with optional natural-language scoping via `--scope-instruction`.
+- Resolves each source action from `--targets`, `--globs`, `--extensions`, or `--paths`, with optional natural-language scoping via `--scope-instruction`.
 - Runs the agent with a refactoring prompt + your "taste" guidelines.
 - Runs your validation command (default: `uv run pytest`).
 - If green and there's a diff, it commits locally and leaves the branch for you to inspect.
-- Repeats until it runs out of targets, hits the retry budget, or stacks too many failures.
+- Repeats until it spends the action budget, exhausts a finite target file, hits the retry budget, or stacks too many failures.
 
 ## Requirements
 
@@ -66,6 +96,8 @@ That keeps sweeping targets until it runs out, hits your caps, or starts failing
 ```bash
 # 1. Register the repo (creates a project dir under ~/.local/share/continuous-refactoring)
 continuous-refactoring init
+# Or keep project taste in the repo:
+continuous-refactoring init --in-repo-taste
 
 # 2. (Optional) Write your refactoring taste — either edit the file, have an agent interview you,
 #    or refine an existing draft collaboratively
@@ -90,13 +122,18 @@ continuous-refactoring run \
 
 | Command | What it does |
 |---|---|
-| `init` | Registers this directory as a project, creates a default `taste.md`, and can store `--live-migrations-dir`. |
+| `init` | Registers this directory as a project, creates a default `taste.md`, and can store `--live-migrations-dir` or `--in-repo-taste`. |
 | `taste` | Prints the active taste file path. Add `--interview` to have an agent author it, `--refine` to iteratively improve an existing taste doc, `--upgrade` to refresh stale taste dimensions, `--global` for the shared file, and `--force` to let `--interview` overwrite custom content after writing a `.bak`. |
 | `run-once` | Single pass on one resolved target. No retry. If there is a diff and validation passes, it commits locally and prints the diffstat. |
-| `run` | The loop. Iterates targets, retries on failure, and commits successful targets locally. |
+| `run` | The loop. Iterates refactor actions, retries on failure, and commits successful changes locally. Add `--focus-on-live-migrations` to bypass targeting and work only on eligible live migrations. |
 | `upgrade` | Checks that the global config manifest is current, rewrites it idempotently, and warns if the global taste file is stale. |
-| `review list` | Lists migrations flagged for human review (`awaiting_human_review`). |
-| `review perform <migration>` | Starts an interactive agent session to resolve a flagged migration's review. Requires `--with`, `--model`, and `--effort`. |
+| `migration list` | Lists visible migrations. Add `--status <status>` or `--awaiting-review` to filter. |
+| `migration doctor <slug-or-path>` | Validates one visible migration's consistency. |
+| `migration doctor --all` | Validates every visible migration plus internal transaction state. |
+| `migration review <slug-or-path>` | Starts staged review for a migration awaiting human review. Requires `--with`, `--model`, and `--effort`. |
+| `migration refine <slug-or-path>` | Records feedback for a planning or unexecuted ready migration and runs one staged planning revision. Requires `--message <text>` or `--file <path>`, plus `--with`, `--model`, and `--effort`; add `--show-agent-logs` to mirror the planning agent. |
+
+Legacy `review list` and `review perform <migration>` remain compatibility aliases; prefer `migration list --awaiting-review` and `migration review`.
 
 ## Targeting / Useful flags
 
@@ -107,21 +144,46 @@ Target resolution is first-match-wins:
 
 These flags are not mutually exclusive, but only the highest-priority populated source is used.
 
-- `--targets path/to/targets.jsonl` — explicit list; one JSON object per line with `description`, `files`, optional `scoping`, `model-override`, `effort-override`. Effort overrides use `low`, `medium`, `high`, or `xhigh`.
-- `--globs 'src/**/*.py:tests/**/*.py'` — colon-separated globs; each matched file becomes its own target.
-- `--extensions .py,.ts` — shorthand that expands to `**/*.py`, `**/*.ts`; each matched file becomes its own target.
-- `--paths a.py:b.py` — literal paths, all treated as one target.
-- `--scope-instruction "clean up the auth module"` — extra free-text scoping. If file-based targeting resolves nothing, this becomes the useful fallback context.
+- `--targets path/to/targets.jsonl` — explicit finite list; one JSON object per line with `description`, `files`, optional `scoping`, `model-override`, `effort-override`. Effort overrides use `low`, `medium`, `high`, or `xhigh`. If `--max-refactors` is omitted, `run` processes the file once and stops.
+- `--globs 'src/**/*.py:tests/**/*.py'` — colon-separated globs matched once against tracked files from `git ls-files`; each refactor action samples one matched file, so files can repeat.
+- `--extensions .py,.ts` — shorthand that expands to `**/*.py`, `**/*.ts` against tracked files from `git ls-files`; each refactor action samples one matched file, so files can repeat.
+- `--paths a.py:b.py` — literal user-provided paths, all treated as one grouped target; each refactor action reuses that group.
+- `--scope-instruction "clean up the auth module"` — extra free-text scoping. If selected file patterns resolve nothing, this becomes the useful fallback context.
+
+If `--globs` or `--extensions` match no tracked files and there is no
+`--scope-instruction`, `run` completes successfully with zero refactor actions.
+`--paths` is literal input and is not filtered through `git ls-files`.
 
-If you provide none of `--targets`, `--globs`, `--extensions`, or `--paths`, then `run` and `run-once` require `--scope-instruction`.
+If you provide none of `--targets`, `--globs`, `--extensions`, or `--paths`,
+then `run` and `run-once` require `--scope-instruction`; the driver still
+random-samples tracked files from `git ls-files` for each action and uses the
+scope text as context for that target.
 
 ### Migrations & taste flags
 
 - `init --live-migrations-dir PATH` — enables the larger-refactoring workflow for this project. The path is stored repo-relative in the project registry and created if missing.
+- `init --in-repo-taste [PATH]` — stores this project's taste file in the repo and remembers the repo-relative path. Defaults to `.continuous-refactoring/taste.md`; re-run `init --in-repo-taste ...` to choose a different path.
+- `migration list` — shows visible migrations; `--awaiting-review` narrows to human-review handoffs.
+- `migration doctor <slug-or-path>` / `migration doctor --all` — read-only consistency checks. Doctor reports problems; it does not repair them.
+- `migration review <slug-or-path> --with ... --model ... --effort ...` — resolves an `awaiting_human_review` migration through a staged workspace.
+- `migration refine <slug-or-path> (--message <text>|--file <path>) --with ... --model ... --effort ... [--show-agent-logs]` — adds user feedback to a planning or unexecuted ready migration and resumes planning through the `revise` step when reopening ready work.
 - `taste --refine` — opens a collaborative editing session for the taste file. The agent keeps refining until you tell it to write, then the session ends automatically after the settled write.
 - `taste --upgrade` — re-interviews for taste dimensions added since your last version. No-op when already current; use `taste --refine` if you want to rework the doc anyway.
 - `taste --force` — only applies to `--interview`; it allows a customized taste file to be overwritten after backing it up to `taste.md.bak`.
 
+Canonical migration commands:
+
+```bash
+continuous-refactoring migration list
+continuous-refactoring migration list --status planning
+continuous-refactoring migration list --awaiting-review
+continuous-refactoring migration doctor <slug-or-path>
+continuous-refactoring migration doctor --all
+continuous-refactoring migration review <slug-or-path> --with codex --model gpt-5 --effort high
+continuous-refactoring migration refine <slug-or-path> --message "split the risky phase" --with codex --model gpt-5 --effort high
+continuous-refactoring migration refine <slug-or-path> --file feedback.md --with codex --model gpt-5 --effort high
+```
+
 ### Shared `run` / `run-once` flags
 
 - `--with`, `--model` — required agent backend/model selection.
@@ -136,10 +198,11 @@ If you provide none of `--targets`, `--globs`, `--extensions`, or `--paths`, the
 
 ### `run`-only flags
 
-- `--max-attempts N` — per-target retry budget. `1` = no retry, `0` = unlimited (which means permanently broken targets will never give up).
-- `--max-refactors N` — cap the number of targets per run. Required unless you use `--targets`.
-- `--max-consecutive-failures N` — bail after N targets fail in a row. Default 3.
-- `--sleep SECONDS` — pause between completed targets. Useful when you want a long batch without hammering the repo or your agent budget.
+- `--max-attempts N` — per-action retry budget. `1` = no retry, `0` = unlimited (which means permanently broken actions will never give up).
+- `--max-refactors N` — cap the number of refactor actions per run. Required unless you use `--targets` or `--focus-on-live-migrations`.
+- `--focus-on-live-migrations` — bypass target selection and `--max-refactors`; iterate eligible live migrations until they are done, deferred, blocked, or the failure budget trips.
+- `--max-consecutive-failures N` — bail after N actions fail in a row. Default 3.
+- `--sleep SECONDS` — pause between completed actions. Useful when you want a long batch without hammering the repo or your agent budget.
 - `--commit-message-prefix TEXT` — subject prefix for successful refactor or migration-plan commits. Default `continuous refactor`.
 
 ## Safety behaviors
@@ -156,22 +219,36 @@ If you provide none of `--targets`, `--globs`, `--extensions`, or `--paths`, the
 Each run writes to `$TMPDIR/continuous-refactoring/<run-id>/`:
 
 - `summary.json` — rolling status, counts, per-attempt stats
-- `events.jsonl` — structured event log
+- `events.jsonl` — structured event log with call roles such as `classify`,
+  `planning.<step>`, `phase.ready-check`, `phase.execute`, and
+  `phase.validation`
 - `run.log` — human-readable log
 - `attempt-NNN/[retry-NN/]refactor/` — per-attempt agent + test stdout/stderr
+- `baseline/initial/` — baseline validation stdout/stderr before work starts
+- `classify/` — classifier agent stdout/stderr
+- `scope-expansion/` — scope candidates, selection, and bypass reason
+- `attempt-NNN/[retry-NN/]planning/<step>/` — planning agent stdout/stderr for
+  migration planning steps
+- `phase-ready-check/` — phase precondition agent stdout/stderr
+- `attempt-NNN/[retry-NN/]phase-execute/` — phase agent and validation logs
+- `migration-probes/action-NNN/` — migration probe logs during normal `run`
+  actions, including planning, phase ready-checks, and phase execution
 
 Mixed-effort runs are auditable: summaries and call events record the default effort, max allowed effort, requested effort, effective effort, source, and whether the request was capped.
 
-The path prints at startup. Grep it when something goes sideways.
+The path prints at startup. Grep it when something goes sideways. Failed
+non-commit decisions also write durable XDG snapshots under the project failure
+directory, usually
+`~/.local/share/continuous-refactoring/projects/<uuid>/failures/`.
 
 ## Taste files
 
 The taste file is a short bullet list of your refactoring preferences. It gets injected into every agent prompt.
 
-- Project taste: `~/.local/share/continuous-refactoring/projects/<uuid>/taste.md`
+- Project taste: `~/.local/share/continuous-refactoring/projects/<uuid>/taste.md`, or the repo-local path chosen with `init --in-repo-taste [PATH]`
 - Global taste: `~/.local/share/continuous-refactoring/global/taste.md`
 
-Project taste wins over global. Use `taste --interview` to bootstrap one, `taste --refine` to rework it with an agent, or edit the file directly any time.
+Project taste wins over global. Use `taste` to print the active path, `taste --interview` to bootstrap one, `taste --refine` to rework it with an agent, or edit the file directly any time.
 
 ## Larger refactorings
 
@@ -190,7 +267,7 @@ This tells the CLI where to store migration artifacts. The path is repo-relative
 Each `run` / `run-once` tick now checks for eligible migration work before falling back to single-commit cleanups:
 
 1. **Classify** — a classifier agent reads the target and decides: `cohesive-cleanup` (one-shot path) or `needs-plan` (migration path).
-2. **Plan** — for `needs-plan` targets, a six-stage planning workflow runs: generate approaches → pick best → expand into phases → review → revise → final review. Artifacts land under `<live-migrations-dir>/<migration-name>/`.
+2. **Plan** — for `needs-plan` targets, each automation action runs exactly one planning step: approaches, pick-best, expand, review, optional revise/review-2, then final-review. Accepted steps update `.planning/state.json`, store stdout under `.planning/stages/`, and publish through a staged transaction. Failed current-step output stays in run artifacts and is not resume input.
 3. **Execute** — each phase is a self-contained unit of work. The tick picks the oldest eligible migration, checks whether its current phase precondition is satisfied, and executes it on the current branch. Phase completion is judged against the phase file's `## Definition of Done`; commit message identifies the migration as `migration/<name>/<phase-file>.md`.
 
 ### Migration directory layout
@@ -199,14 +276,20 @@ Each `run` / `run-once` tick now checks for eligible migration work before falli
 <live-migrations-dir>/
   <migration-name>/
     manifest.json          # status, phases, wake-up schedule
+    .planning/
+      state.json           # durable planning cursor and accepted step refs
+      stages/              # accepted planning stdout, suffixed on repeats
     plan.md                # the expanded plan
     approaches/            # candidate approaches considered during planning
     phase-1-<name>.md      # per-phase specification
     phase-2-<name>.md
     ...
+  __transactions__/        # internal staged publish state
   __intentional_skips__/   # migrations rejected at final review
 ```
 
+Do not edit `.planning/` or `__transactions__/` by hand. Use `migration doctor` when the shape looks wrong.
+
 ### Wake-up rules
 
 Migrations don't run on every tick. The scheduler now separates **activity** from
@@ -240,7 +323,7 @@ Before executing a phase, a ready-check agent verifies that the current phase pr
 
 - **ready: yes** — phase executes; on green tests, the phase is marked done, any prior deferral markers are cleared, and the migration advances immediately to the next phase.
 - **ready: no** — manifest activity is bumped, a retry cooldown is started, and a future `wake_up_on` is recorded when needed; the tick moves on.
-- **ready: unverifiable** — the migration is flagged `awaiting_human_review` and put on cooldown. Automated migration ticks skip flagged migrations until review clears the flag. Use `review list` to find it and `review perform <migration> --with ... --model ... --effort ...` to resolve it interactively.
+- **ready: unverifiable** — the migration is flagged `awaiting_human_review` and put on cooldown. Automated migration ticks skip flagged migrations until review clears the flag. Use `migration list --awaiting-review` to find it and `migration review <slug-or-path> --with ... --model ... --effort ...` to resolve it interactively.
 
 Human-facing migration references use the relative phase spec path, for example `phase-2-failure-report.md`. The manifest cursor stores the phase `name`, not a numeric index.
 

{continuous_refactoring-0.1.0 → continuous_refactoring-0.3.0}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "continuous-refactoring"
-version = "0.1.0"
+version = "0.3.0"
 description = "Continuous refactoring loop for AI coding agents"
 readme = "README.md"
 requires-python = ">=3.10"