lemming-cli 0.2.0__tar.gz → 0.3.0__tar.gz

{lemming_cli-0.2.0 → lemming_cli-0.3.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: lemming-cli
-Version: 0.2.0
+Version: 0.3.0
 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
@@ -186,11 +186,17 @@ Lemming comes with several built-in hooks to help manage your project:
   analyzes the results of the finished task and decides if the remaining roadmap
   needs to be adjusted (e.g., adding a missing prerequisite, skipping obsolete
   tasks, or breaking down a broad task).
-- **`readability`**: A code quality hook that reviews changes for adherence to
-  the Google Style Guide and general readability using the
+- **`readability`**: A code quality and simplification hook that challenges
+  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.
+- **`testing`**: Verifies that changed behavior has focused test coverage and
+  that the relevant tests pass.
+- **`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.
 
 ### Custom and Global Hooks
 
@@ -240,13 +246,20 @@ See [docs/EVALS.md](docs/EVALS.md) for details.
 
 ### Roadmap Management
 
-- **`status [<id>]`**: Roadmap overview or deep-dive into a specific task.
+- **`status [<id>]`**: Queue/history overview or deep-dive into a specific
+  task, including supersession lineage and runner/orchestrator-hook execution
+  times. Superseded and failed history stays visible in the default overview;
+  `--verbose` also shows routine completed/cancelled history.
 - **`goal [<text>]`**: Set or view the long-term goal shared by all tasks.
   Supports `-f/--file`.
 - **`add <desc>`**: Append a new task. Supports `--index` and `--runner`.
 - **`edit <id>`**: Modify a task's description, runner, or position.
-- **`delete <id>`**: Remove a task. Supports `--all` and `--completed` for bulk
-  operations.
+- **`delete <id>`**: Remove an unstarted task while retaining its runner log.
+  Tasks with execution history require `--force`; autonomous restructuring
+  should use `supersede`. Supports `--all` and `--completed` for bulk cleanup,
+  including logs.
+- **`supersede <id> --reason <text>`**: Retire a replaced or split task without
+  losing its progress, timings, log, or links to replacement tasks.
 - **`progress`**: Manage progress entries and findings for specific tasks.
   - `list <id>`: List all progress for a task.
   - `add <id> <finding>`: Record a new technical detail.
@@ -277,9 +290,11 @@ See [docs/EVALS.md](docs/EVALS.md) for details.
 - **`fail <id>`**: Mark a task as a terminal failure (will not be retried).
 - **`cancel <id>`**: Stop an in-progress task (kills the runner process).
 - **`reset <id>`**: Clear attempts and progress to start a task fresh.
-- **`logs [<id>]`**: Print a task's execution log to stdout. If no ID is
-  provided, it defaults to the active or most recent task. Orchestrator hook
-  output is automatically appended.
+- Superseded tasks remain visible as non-failing history; replacement tasks
+  link back through their parent task ID.
+- **`logs [<id>]`**: Print a task's execution log to stdout, including retained
+  logs for removed tasks. If no ID is provided, it defaults to the active or
+  most recent task. Orchestrator hook output is automatically appended.
 
 ### Execution
 
@@ -307,10 +322,12 @@ Lemming uses **fuzzy matching** to automatically inject the correct "YOLO"
 - **Antigravity (`agy`)**: Adds `--dangerously-skip-permissions`
 - **Aider**: Adds `--yes --quiet`
 - **Claude**: Adds `--dangerously-skip-permissions`
-- **Codex**: Adds `--yolo`
+- **Codex**: Runs non-interactively via `codex exec`, adds `--json`, and, in
+  YOLO mode, adds `--dangerously-bypass-approvals-and-sandbox`
 
-You can disable this behavior with `--no-defaults`, or use a **template** to
-fully control the command layout:
+You can disable default flag injection with `--no-defaults` (`codex exec`
+remains the Codex execution interface), or use a **template** to fully control
+the command layout:
 
 ```bash
 lemming run --runner "my-tool --input={{prompt}} --json"

{lemming_cli-0.2.0 → lemming_cli-0.3.0}/README.md

@@ -164,11 +164,17 @@ Lemming comes with several built-in hooks to help manage your project:
   analyzes the results of the finished task and decides if the remaining roadmap
   needs to be adjusted (e.g., adding a missing prerequisite, skipping obsolete
   tasks, or breaking down a broad task).
-- **`readability`**: A code quality hook that reviews changes for adherence to
-  the Google Style Guide and general readability using the
+- **`readability`**: A code quality and simplification hook that challenges
+  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.
+- **`testing`**: Verifies that changed behavior has focused test coverage and
+  that the relevant tests pass.
+- **`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.
 
 ### Custom and Global Hooks
 
@@ -218,13 +224,20 @@ See [docs/EVALS.md](docs/EVALS.md) for details.
 
 ### Roadmap Management
 
-- **`status [<id>]`**: Roadmap overview or deep-dive into a specific task.
+- **`status [<id>]`**: Queue/history overview or deep-dive into a specific
+  task, including supersession lineage and runner/orchestrator-hook execution
+  times. Superseded and failed history stays visible in the default overview;
+  `--verbose` also shows routine completed/cancelled history.
 - **`goal [<text>]`**: Set or view the long-term goal shared by all tasks.
   Supports `-f/--file`.
 - **`add <desc>`**: Append a new task. Supports `--index` and `--runner`.
 - **`edit <id>`**: Modify a task's description, runner, or position.
-- **`delete <id>`**: Remove a task. Supports `--all` and `--completed` for bulk
-  operations.
+- **`delete <id>`**: Remove an unstarted task while retaining its runner log.
+  Tasks with execution history require `--force`; autonomous restructuring
+  should use `supersede`. Supports `--all` and `--completed` for bulk cleanup,
+  including logs.
+- **`supersede <id> --reason <text>`**: Retire a replaced or split task without
+  losing its progress, timings, log, or links to replacement tasks.
 - **`progress`**: Manage progress entries and findings for specific tasks.
   - `list <id>`: List all progress for a task.
   - `add <id> <finding>`: Record a new technical detail.
@@ -255,9 +268,11 @@ See [docs/EVALS.md](docs/EVALS.md) for details.
 - **`fail <id>`**: Mark a task as a terminal failure (will not be retried).
 - **`cancel <id>`**: Stop an in-progress task (kills the runner process).
 - **`reset <id>`**: Clear attempts and progress to start a task fresh.
-- **`logs [<id>]`**: Print a task's execution log to stdout. If no ID is
-  provided, it defaults to the active or most recent task. Orchestrator hook
-  output is automatically appended.
+- Superseded tasks remain visible as non-failing history; replacement tasks
+  link back through their parent task ID.
+- **`logs [<id>]`**: Print a task's execution log to stdout, including retained
+  logs for removed tasks. If no ID is provided, it defaults to the active or
+  most recent task. Orchestrator hook output is automatically appended.
 
 ### Execution
 
@@ -285,10 +300,12 @@ Lemming uses **fuzzy matching** to automatically inject the correct "YOLO"
 - **Antigravity (`agy`)**: Adds `--dangerously-skip-permissions`
 - **Aider**: Adds `--yes --quiet`
 - **Claude**: Adds `--dangerously-skip-permissions`
-- **Codex**: Adds `--yolo`
+- **Codex**: Runs non-interactively via `codex exec`, adds `--json`, and, in
+  YOLO mode, adds `--dangerously-bypass-approvals-and-sandbox`
 
-You can disable this behavior with `--no-defaults`, or use a **template** to
-fully control the command layout:
+You can disable default flag injection with `--no-defaults` (`codex exec`
+remains the Codex execution interface), or use a **template** to fully control
+the command layout:
 
 ```bash
 lemming run --runner "my-tool --input={{prompt}} --json"

{lemming_cli-0.2.0 → lemming_cli-0.3.0}/docs/HOOKS.md

@@ -51,15 +51,30 @@ a broad task).
 
 ### `readability`
 
-A code quality hook that reviews 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.
+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.
+
+### `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.
+
+### `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`.
 
 ### Editing Built-in Hook Prompts
 
 The built-in hook prompts are load-bearing: a wording change can regress
 orchestration behavior without any unit test failing. When you edit a prompt
-under `src/lemming/prompts/hooks/`, run its eval suite before shipping:
+under `src/lemming/prompts/hooks/` that has an eval suite, run it before
+shipping:
 
 ```bash
 uv run python -m lemming.evals run --suite roadmap

{lemming_cli-0.2.0 → lemming_cli-0.3.0}/package-lock.json

@@ -12,7 +12,7 @@
         "@biomejs/biome": "1.9.4",
         "@playwright/test": "^1.60.0",
         "jsdom": "latest",
-        "mancha": "^0.22.4",
+        "mancha": "^0.22.7",
         "playwright": "^1.60.0"
       }
     },
@@ -1019,9 +1019,9 @@
       }
     },
     "node_modules/mancha": {
-      "version": "0.22.4",
-      "resolved": "https://registry.npmjs.org/mancha/-/mancha-0.22.4.tgz",
-      "integrity": "sha512-bNurE3cVS3ZoOow3hhkJiJcxRkXCZrWh4NaVVlV1KYFe3iY3wrcAqk/HJKMHw0kglcQjUc2iAtJbemI2oJKIUg==",
+      "version": "0.22.7",
+      "resolved": "https://registry.npmjs.org/mancha/-/mancha-0.22.7.tgz",
+      "integrity": "sha512-ZClxBTYOKSD9f4KqW8lCMYVEUPhxzIRgihw5g20QrD4kzZ9JcQ383LXXkPMVTaCAjLlqYaF3brUMYACwWgQZgA==",
       "dev": true,
       "license": "MIT",
       "dependencies": {

{lemming_cli-0.2.0 → lemming_cli-0.3.0}/package.json

@@ -16,7 +16,7 @@
     "@biomejs/biome": "1.9.4",
     "@playwright/test": "^1.60.0",
     "jsdom": "latest",
-    "mancha": "^0.22.4",
+    "mancha": "^0.22.7",
     "playwright": "^1.60.0"
   }
 }

{lemming_cli-0.2.0 → lemming_cli-0.3.0}/pyproject.toml

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

{lemming_cli-0.2.0 → lemming_cli-0.3.0}/src/lemming/api/hooks_test.py

@@ -15,6 +15,9 @@ def test_list_hooks(client, test_tasks, monkeypatch, tmp_path):
     assert hooks["roadmap"]["masked"] is False
     assert hooks["readability"]["source"] == "built-in"
     assert hooks["readability"]["runs_on_failure"] is False
+    assert hooks["ux"]["priority"] == 70
+    assert hooks["ux"]["source"] == "built-in"
+    assert hooks["ux"]["runs_on_failure"] is False
 
     # Hooks are sorted by ascending priority
     priorities = [h["priority"] for h in payload]

{lemming_cli-0.2.0 → lemming_cli-0.3.0}/src/lemming/api/tasks.py

@@ -76,6 +76,11 @@ def update_task(
     """Update a task's description, runner, position, status, or parent."""
     tasks_file = context.resolve_tasks_file(request.app.state, project)
     status = update.get("status")
+    if status == tasks.TaskStatus.SUPERSEDED:
+        raise fastapi.HTTPException(
+            400,
+            "Use the supersede endpoint so a reason is recorded.",
+        )
 
     # Validation: require progress if completing or failing from the UI,
     # but not if we are just marking a finished task as pending (uncomplete).
@@ -91,6 +96,7 @@ def update_task(
             tasks.TaskStatus.COMPLETED,
             tasks.TaskStatus.FAILED,
             tasks.TaskStatus.CANCELLED,
+            tasks.TaskStatus.SUPERSEDED,
         ):
             require_progress = True
 
@@ -130,11 +136,39 @@ def delete_task(
 ):
     """Delete a single task by ID."""
     tasks.delete_tasks(
-        context.resolve_tasks_file(request.app.state, project), task_id=task_id
+        context.resolve_tasks_file(request.app.state, project),
+        task_id=task_id,
+        force=True,
     )
     return {"status": "ok"}
 
 
+class SupersedeTaskRequest(pydantic.BaseModel):
+    """Request body for superseding a task."""
+
+    reason: str
+
+
+@router.post("/api/tasks/{task_id}/supersede")
+def supersede_task(
+    request: fastapi.Request,
+    task_id: str,
+    body: SupersedeTaskRequest,
+    project: str | None = None,
+):
+    """Supersede a task while retaining its history."""
+    try:
+        return tasks.supersede_task(
+            context.resolve_tasks_file(request.app.state, project),
+            task_id,
+            body.reason,
+        )
+    except ValueError as e:
+        if "not found" in str(e):
+            raise fastapi.HTTPException(404, str(e))
+        raise fastapi.HTTPException(400, str(e))
+
+
 @router.post("/api/tasks/{task_id}/cancel")
 def cancel_task_endpoint(
     request: fastapi.Request, task_id: str, project: str | None = None

{lemming_cli-0.2.0 → lemming_cli-0.3.0}/src/lemming/api/tasks_test.py

@@ -174,6 +174,25 @@ def test_reopen_cancelled_task_via_api(client, test_tasks):
     assert response.json()["attempts"] == 0
 
 
+def test_supersede_and_reopen_task_via_api(client, test_tasks):
+    response = client.post(
+        "/api/tasks/task2/supersede",
+        json={"reason": "split after timeout"},
+    )
+    assert response.status_code == 200
+    assert response.json()["status"] == tasks.TaskStatus.SUPERSEDED
+    assert response.json()["superseded_reason"] == "split after timeout"
+
+    response = client.post(
+        "/api/tasks/task2/update",
+        json={"status": tasks.TaskStatus.PENDING},
+    )
+    assert response.status_code == 200
+    assert response.json()["status"] == tasks.TaskStatus.PENDING
+    assert response.json()["superseded_reason"] is None
+    assert response.json()["superseded_at"] is None
+
+
 def test_has_log_population(client, test_tasks):
     # Initially no logs
     response = client.get("/api/data")
@@ -225,7 +244,7 @@ def test_api_log(client, test_tasks):
     assert response.json() == {"log": ""}
 
 
-def test_api_delete_log_cleanup(client, test_tasks):
+def test_api_delete_retains_log(client, test_tasks):
     test_tasks_file = test_tasks
     # 1. Add a task
     data = tasks.load_tasks(test_tasks_file)
@@ -248,6 +267,20 @@ def test_api_delete_log_cleanup(client, test_tasks):
 
     # 3. Delete via API
     response = client.post(f"/api/tasks/{task_id}/delete")
+    assert response.status_code == 200
+    assert log_file.read_text() == "API delete log"
+
+    response = client.get(f"/api/tasks/{task_id}/log")
+    assert response.status_code == 200
+    assert response.json() == {"log": "API delete log"}
+
+
+def test_api_delete_completed_cleans_up_log(client, test_tasks):
+    log_file = paths.get_log_file(test_tasks, "task1")
+    log_file.write_text("completed task log")
+
+    response = client.post("/api/tasks/delete-completed")
+
     assert response.status_code == 200
     assert not log_file.exists()