lemming-cli 0.5.0__tar.gz → 0.5.1__tar.gz

{lemming_cli-0.5.0 → lemming_cli-0.5.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: lemming-cli
-Version: 0.5.0
+Version: 0.5.1
 Summary: An autonomous, iterative task runner for AI coding agents.
 Project-URL: Homepage, https://github.com/owahltinez/lemming
 Project-URL: Repository, https://github.com/owahltinez/lemming
@@ -144,6 +144,14 @@ lemming exec "Add pagination to the tasks API" --review all
 which is resolved to the files it changed. It defaults to uncommitted work, or
 to the whole tree outside a git repository.
 
+Reviews may edit the working directory. The built-in readability review
+intentionally applies fixes, and testing may repair production code or tests.
+UX is instructed to remain advisory, but its prompt and `--no-yolo` do not
+enforce filesystem isolation. A global review override may perform any actions
+its prompt requests. When isolation is required, follow the working-copy
+guidance below and pass a separate VCS-managed working copy with
+`lemming -C <working-copy> exec --review ...`.
+
 Each run is self-contained: nothing is read from the project's roadmap or its
 local hooks, it runs only the requested task and reviews, and its state
 directory is removed unless it failed — in which case it is kept, and its path
@@ -284,13 +292,15 @@ Lemming comes with several built-in hooks to help manage your project:
   unnecessary complexity and duplicate implementations, then reviews changes for
   adherence to the Google Style Guide and general readability using the
   [readability](https://github.com/owahltinez/readability) tool (exposed as
-  `lemming readability`). It can record findings as task progress or suggest
-  follow-up refactoring tasks.
+  `lemming readability`). It intentionally applies automated and targeted fixes
+  in the working directory and records broader findings as task progress.
 - **`testing`**: Verifies that changed behavior has focused test coverage and
-  that the relevant tests pass.
+  that the relevant tests pass. It may repair small, targeted problems in
+  production code or tests and may add, merge, or remove tests.
 - **`ux`**: Reviews at most one critical user journey affected by a user-visible
   change. It reports only concrete, reproducible continuity gaps and exits
-  immediately for non-user-facing tasks.
+  immediately for non-user-facing tasks. Its prompt instructs the agent to stay
+  advisory, but this is not sandbox-enforced.
 
 ### Custom and Global Hooks
 
@@ -432,7 +442,8 @@ These come before the subcommand and apply to all of them.
     `add`, there is no length cap.
   - `--review <names>`: Reviews to run after the task, comma-separated or
     repeated; `all` selects every one. With no description, only the reviews
-    run. Hooks that revise the roadmap cannot be selected.
+    run. Reviews may edit the working directory. Hooks that revise the roadmap
+    cannot be selected.
   - `--scope <path|range>`: What the reviews look at. Paths pass through; a git
     revision range is resolved to the files it changed. Defaults to uncommitted
     work, or the whole tree outside a repository.

{lemming_cli-0.5.0 → lemming_cli-0.5.1}/README.md

@@ -121,6 +121,14 @@ lemming exec "Add pagination to the tasks API" --review all
 which is resolved to the files it changed. It defaults to uncommitted work, or
 to the whole tree outside a git repository.
 
+Reviews may edit the working directory. The built-in readability review
+intentionally applies fixes, and testing may repair production code or tests.
+UX is instructed to remain advisory, but its prompt and `--no-yolo` do not
+enforce filesystem isolation. A global review override may perform any actions
+its prompt requests. When isolation is required, follow the working-copy
+guidance below and pass a separate VCS-managed working copy with
+`lemming -C <working-copy> exec --review ...`.
+
 Each run is self-contained: nothing is read from the project's roadmap or its
 local hooks, it runs only the requested task and reviews, and its state
 directory is removed unless it failed — in which case it is kept, and its path
@@ -261,13 +269,15 @@ Lemming comes with several built-in hooks to help manage your project:
   unnecessary complexity and duplicate implementations, then reviews changes for
   adherence to the Google Style Guide and general readability using the
   [readability](https://github.com/owahltinez/readability) tool (exposed as
-  `lemming readability`). It can record findings as task progress or suggest
-  follow-up refactoring tasks.
+  `lemming readability`). It intentionally applies automated and targeted fixes
+  in the working directory and records broader findings as task progress.
 - **`testing`**: Verifies that changed behavior has focused test coverage and
-  that the relevant tests pass.
+  that the relevant tests pass. It may repair small, targeted problems in
+  production code or tests and may add, merge, or remove tests.
 - **`ux`**: Reviews at most one critical user journey affected by a user-visible
   change. It reports only concrete, reproducible continuity gaps and exits
-  immediately for non-user-facing tasks.
+  immediately for non-user-facing tasks. Its prompt instructs the agent to stay
+  advisory, but this is not sandbox-enforced.
 
 ### Custom and Global Hooks
 
@@ -409,7 +419,8 @@ These come before the subcommand and apply to all of them.
     `add`, there is no length cap.
   - `--review <names>`: Reviews to run after the task, comma-separated or
     repeated; `all` selects every one. With no description, only the reviews
-    run. Hooks that revise the roadmap cannot be selected.
+    run. Reviews may edit the working directory. Hooks that revise the roadmap
+    cannot be selected.
   - `--scope <path|range>`: What the reviews look at. Paths pass through; a git
     revision range is resolved to the files it changed. Defaults to uncommitted
     work, or the whole tree outside a repository.

{lemming_cli-0.5.0 → lemming_cli-0.5.1}/SKILL.md

@@ -136,8 +136,12 @@ lemming -C /tmp/pr-123 exec --review testing --scope main...HEAD
 which is resolved to the files it changed. It defaults to uncommitted work, and
 a clean tree stops the run rather than reviewing everything.
 
-Reviews **edit the workspace** — readability applies fixes and reruns checks.
-That is the point, but it means a review is not read-only.
+Reviews may edit the working directory. Readability intentionally applies fixes,
+and testing may repair production code or tests. UX is instructed to remain
+advisory, but its prompt and `--no-yolo` do not enforce filesystem isolation. A
+global review override may perform any actions its prompt requests. When
+isolation is required, use a separate VCS-managed working copy and pass it with
+the global `-C` option, as in the example above.
 
 ## Drive a roadmap
 

{lemming_cli-0.5.0 → lemming_cli-0.5.1}/docs/HOOKS.md

@@ -54,20 +54,34 @@ a broad task).
 A code quality and simplification hook that challenges unnecessary complexity,
 indirection, and duplicated implementations before reviewing changes for
 adherence to the Google Style Guide and general readability using the bundled
-`lemming readability` tool. It provides feedback via task progress or suggests
-follow-up refactoring tasks.
+`lemming readability` tool. It intentionally applies automated and targeted
+fixes in the working directory and records broader findings as task progress.
 
 ### `testing`
 
 Checks that changed behavior has focused test coverage and runs the relevant
-tests. It records larger testing gaps as task progress for the roadmap hook.
+tests. It may repair small, targeted problems in production code or tests and
+may add, merge, or remove tests. It records larger testing gaps as task progress
+for the roadmap hook.
 
 ### `ux`
 
 A lightweight journey-continuity review for user-visible changes. It considers
 at most one affected critical journey, reports only concrete and reproducible
 gaps, and exits immediately when the task did not change user-facing behavior.
-It runs after `testing` and before `roadmap`.
+Its prompt instructs the agent to stay advisory, but this is not
+sandbox-enforced. It runs after `testing` and before `roadmap`.
+
+### Reviews Are Not Read-Only
+
+When selected with `lemming exec --review`, the hooks above may edit the working
+directory. Prompt instructions and `--no-yolo` do not enforce filesystem
+isolation. When isolation is required, create a separate VCS-managed working
+copy and pass it through the global option:
+
+```bash
+lemming -C <working-copy> exec --review <name>
+```
 
 ### Editing Built-in Hook Prompts
 
@@ -104,7 +118,8 @@ Because of this precedence order, overriding a built-in hook only requires
 creating a Markdown file with the same logical name in the project or global
 directory (e.g. `~/.local/lemming/hooks/90-roadmap.md`); delete the file to
 restore the built-in version. Global hooks are available to all Lemming projects
-on the system.
+on the system. A global review override selected by `lemming exec --review` may
+perform any actions its prompt requests.
 
 ### Example: `lint` hook
 

{lemming_cli-0.5.0 → lemming_cli-0.5.1}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "lemming-cli"
-version = "0.5.0"
+version = "0.5.1"
 description = "An autonomous, iterative task runner for AI coding agents."
 readme = "README.md"
 authors = [

{lemming_cli-0.5.0 → lemming_cli-0.5.1}/src/lemming/cli/exec_cli.py

@@ -223,7 +223,7 @@ def _task_status(
     help=(
         "Reviews to run after the task, comma-separated or repeated. "
         "Use 'all' for every review. With no description, only the "
-        "reviews run."
+        "reviews run. Reviews may edit the working directory."
     ),
 )
 @click.option(

{lemming_cli-0.5.0 → lemming_cli-0.5.1}/uv.lock

@@ -307,7 +307,7 @@ wheels = [
 
 [[package]]
 name = "lemming-cli"
-version = "0.5.0"
+version = "0.5.1"
 source = { editable = "." }
 dependencies = [
     { name = "beautifulsoup4" },