lemming-cli 0.1.1__tar.gz → 0.1.2__tar.gz

lemming_cli-0.1.2/.github/workflows/screenshots.yml

@@ -0,0 +1,51 @@
+name: Screenshots
+
+# Regenerates the dashboard screenshots in docs/ whenever the web UI changes,
+# so they can never go stale. Generation is deterministic (frozen clock and
+# animations disabled), so this only commits when the UI actually changed.
+# The commit touches only docs/screenshots, which is outside the paths filter
+# below, so it cannot re-trigger this workflow.
+on:
+  push:
+    branches: [main]
+    paths:
+      - 'src/lemming/web/**'
+      - 'playwright.config.js'
+      - '.github/workflows/screenshots.yml'
+
+permissions:
+  contents: write
+
+jobs:
+  regenerate:
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v6
+
+      - name: Set up Node.js
+        uses: actions/setup-node@v6
+        with:
+          node-version: '20'
+
+      - name: Install Node.js dependencies
+        run: npm install
+
+      - name: Install Playwright browser
+        run: npx playwright install --with-deps chromium
+
+      - name: Regenerate screenshots
+        run: npm run screenshots
+
+      - name: Commit updated screenshots
+        run: |
+          if git diff --quiet docs/screenshots; then
+            echo "Screenshots are up to date."
+            exit 0
+          fi
+          git config user.name "github-actions[bot]"
+          git config user.email "41898282+github-actions[bot]@users.noreply.github.com"
+          git add docs/screenshots
+          git commit -m "Regenerate dashboard screenshots"
+          git pull --rebase --autostash origin main
+          git push

{lemming_cli-0.1.1 → lemming_cli-0.1.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: lemming-cli
-Version: 0.1.1
+Version: 0.1.2
 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
@@ -32,7 +32,7 @@ human-readable `tasks.yml` file.
 ## Why Lemming?
 
 - **Zero Context Drift**: By breaking projects into discrete tasks, Lemming
-  ensures agents stay focused. They only see the project context, relevant
+  ensures agents stay focused. They only see the long-term goal, relevant
   history, and the specific task at hand.
 - **Transparency & Control**: Every decision, technical finding, and progress
   update is recorded in a human-readable `tasks.yml` file. You can step in,
@@ -61,11 +61,11 @@ uv tool install lemming-cli
 
 ### 1. Scaffold the Roadmap
 
-Initialize your project context and define your goals.
+Set the long-term goal and define the first tasks.
 
 ```bash
-# Set project-wide rules (e.g. tech stack, style guides)
-lemming context "Use React, TypeScript, and Tailwind. Follow TDD."
+# Set the long-term goal that every task works toward
+lemming goal "Build a habit-tracking web app with auth, offline support, and tests"
 
 # Add tasks to the queue
 lemming add "Initialize the project with Vite"
@@ -73,6 +73,11 @@ lemming add "Create the Button component"
 lemming add "Implement the authentication flow"
 ```
 
+The goal is the one piece of state every task sees, no matter how far into the
+roadmap it runs — describe what "done" looks like for the project. Durable
+coding rules (tech stack, style guides) belong in your repo's agent files (e.g.
+`AGENTS.md`, `CLAUDE.md`), which your agent already reads on its own.
+
 ### 2. Review and Refine
 
 See exactly what's pending and what the agent will see.
@@ -114,19 +119,19 @@ lemming serve --tunnel cloudflare
   folders directly from the UI.
 - **Browse Files**: Quickly open your workspace in a separate window to inspect
   files and directory structure alongside the roadmap.
-- **Interactive Controls**: Add tasks, edit context, and manage the execution
+- **Interactive Controls**: Add tasks, edit the goal, and manage the execution
   loop from your browser.
 
 ---
 
 ## How it Works
 
-Lemming maintains a human-readable `tasks.yml` file containing your project
-context, a queue of tasks, and recorded progress. When you run `lemming run`, it
+Lemming maintains a human-readable `tasks.yml` file containing your long-term
+goal, a queue of tasks, and recorded progress. When you run `lemming run`, it
 loops through each pending task:
 
 1.  **Build a scoped prompt**: Lemming assembles a prompt containing only the
-    project context, a summary of completed tasks and their progress, and the
+    long-term goal, a summary of completed tasks and their progress, and the
     current task description.
 2.  **Invoke the agent**: It launches your chosen agent CLI with that prompt,
     monitors it with heartbeats, and streams output to a log file.
@@ -195,7 +200,7 @@ by replacing its symlink with a file, or **disable** a global override by
 deleting the symlink.
 
 Hooks follow a specific discovery precedence: **Project > Global > Built-in**.
-See [DOCS/HOOKS.md](docs/HOOKS.md) for more details.
+See [docs/HOOKS.md](docs/HOOKS.md) for more details.
 
 ### Managing Hooks and Configuration
 
@@ -216,6 +221,18 @@ lemming config set runner aider
 lemming hooks set roadmap lint
 ```
 
+### Evaluating Prompt Changes
+
+Editing a hook prompt can regress behavior without any test failing. The
+containerized eval harness replays realistic scenarios against the real hook
+execution path and grades the outcome mechanically:
+
+```bash
+uv run python -m lemming.evals run --suite roadmap
+```
+
+See [docs/EVALS.md](docs/EVALS.md) for details.
+
 ---
 
 ## Command Reference
@@ -223,8 +240,8 @@ lemming hooks set roadmap lint
 ### Roadmap Management
 
 - **`status [<id>]`**: Roadmap overview or deep-dive into a specific task.
-- **`context [<text>]`**: Set or view project-wide instructions. Supports
-  `-f/--file`.
+- **`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
@@ -321,6 +338,10 @@ git push origin v0.1.1
 
 ## Screenshots
 
+These are regenerated automatically by CI whenever the web UI changes (see
+`.github/workflows/screenshots.yml`); run `npm run screenshots` to preview them
+locally.
+
 ### Dashboard
 
 ![Dashboard](docs/screenshots/dashboard-desktop.png)

{lemming_cli-0.1.1 → lemming_cli-0.1.2}/README.md

@@ -10,7 +10,7 @@ human-readable `tasks.yml` file.
 ## Why Lemming?
 
 - **Zero Context Drift**: By breaking projects into discrete tasks, Lemming
-  ensures agents stay focused. They only see the project context, relevant
+  ensures agents stay focused. They only see the long-term goal, relevant
   history, and the specific task at hand.
 - **Transparency & Control**: Every decision, technical finding, and progress
   update is recorded in a human-readable `tasks.yml` file. You can step in,
@@ -39,11 +39,11 @@ uv tool install lemming-cli
 
 ### 1. Scaffold the Roadmap
 
-Initialize your project context and define your goals.
+Set the long-term goal and define the first tasks.
 
 ```bash
-# Set project-wide rules (e.g. tech stack, style guides)
-lemming context "Use React, TypeScript, and Tailwind. Follow TDD."
+# Set the long-term goal that every task works toward
+lemming goal "Build a habit-tracking web app with auth, offline support, and tests"
 
 # Add tasks to the queue
 lemming add "Initialize the project with Vite"
@@ -51,6 +51,11 @@ lemming add "Create the Button component"
 lemming add "Implement the authentication flow"
 ```
 
+The goal is the one piece of state every task sees, no matter how far into the
+roadmap it runs — describe what "done" looks like for the project. Durable
+coding rules (tech stack, style guides) belong in your repo's agent files (e.g.
+`AGENTS.md`, `CLAUDE.md`), which your agent already reads on its own.
+
 ### 2. Review and Refine
 
 See exactly what's pending and what the agent will see.
@@ -92,19 +97,19 @@ lemming serve --tunnel cloudflare
   folders directly from the UI.
 - **Browse Files**: Quickly open your workspace in a separate window to inspect
   files and directory structure alongside the roadmap.
-- **Interactive Controls**: Add tasks, edit context, and manage the execution
+- **Interactive Controls**: Add tasks, edit the goal, and manage the execution
   loop from your browser.
 
 ---
 
 ## How it Works
 
-Lemming maintains a human-readable `tasks.yml` file containing your project
-context, a queue of tasks, and recorded progress. When you run `lemming run`, it
+Lemming maintains a human-readable `tasks.yml` file containing your long-term
+goal, a queue of tasks, and recorded progress. When you run `lemming run`, it
 loops through each pending task:
 
 1.  **Build a scoped prompt**: Lemming assembles a prompt containing only the
-    project context, a summary of completed tasks and their progress, and the
+    long-term goal, a summary of completed tasks and their progress, and the
     current task description.
 2.  **Invoke the agent**: It launches your chosen agent CLI with that prompt,
     monitors it with heartbeats, and streams output to a log file.
@@ -173,7 +178,7 @@ by replacing its symlink with a file, or **disable** a global override by
 deleting the symlink.
 
 Hooks follow a specific discovery precedence: **Project > Global > Built-in**.
-See [DOCS/HOOKS.md](docs/HOOKS.md) for more details.
+See [docs/HOOKS.md](docs/HOOKS.md) for more details.
 
 ### Managing Hooks and Configuration
 
@@ -194,6 +199,18 @@ lemming config set runner aider
 lemming hooks set roadmap lint
 ```
 
+### Evaluating Prompt Changes
+
+Editing a hook prompt can regress behavior without any test failing. The
+containerized eval harness replays realistic scenarios against the real hook
+execution path and grades the outcome mechanically:
+
+```bash
+uv run python -m lemming.evals run --suite roadmap
+```
+
+See [docs/EVALS.md](docs/EVALS.md) for details.
+
 ---
 
 ## Command Reference
@@ -201,8 +218,8 @@ lemming hooks set roadmap lint
 ### Roadmap Management
 
 - **`status [<id>]`**: Roadmap overview or deep-dive into a specific task.
-- **`context [<text>]`**: Set or view project-wide instructions. Supports
-  `-f/--file`.
+- **`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
@@ -299,6 +316,10 @@ git push origin v0.1.1
 
 ## Screenshots
 
+These are regenerated automatically by CI whenever the web UI changes (see
+`.github/workflows/screenshots.yml`); run `npm run screenshots` to preview them
+locally.
+
 ### Dashboard
 
 ![Dashboard](docs/screenshots/dashboard-desktop.png)

lemming_cli-0.1.2/docs/EVALS.md

@@ -0,0 +1,89 @@
+# Prompt Evals 🧪
+
+Lemming's behavior is driven by prompts (the task runner and the orchestrator
+hooks), so a prompt edit can regress the system without any test failing. The
+eval harness in `lemming.evals` catches that: it replays realistic "a task just
+finished" situations against the real hook execution path and grades the outcome
+with mechanical checks — no LLM judging involved.
+
+## How it Works
+
+Each **scenario** seeds a hermetic fixture: a tiny git repository plus a
+`tasks.yml` mid-flight (e.g. a task that just failed for the third time). A
+**trial** runs the hook under eval against that fixture using the same code path
+as the orchestrator, then a **grader** inspects the aftermath:
+
+- Did the roadmap hook repair a task that failed at max attempts, or did it
+  naively reset it?
+- Did it leave a healthy roadmap untouched?
+- Did it keep its hands off source files (`git status` must stay clean)?
+
+Every trial runs in its own container built from the repo `Dockerfile`, with
+only the fixture workspace and a per-trial `LEMMING_HOME` mounted. The agent
+under eval cannot touch the host, and concurrent trials share no state, so
+trials run in parallel safely.
+
+## Running
+
+Evals invoke real agents: expect minutes of wall clock and real token spend.
+They are a manual gate for prompt changes, not part of the unit test suite.
+
+```bash
+# List available suites and scenarios
+uv run python -m lemming.evals list
+
+# Run a suite (roadmap or readability): scenarios x 3 trials in parallel
+uv run python -m lemming.evals run --suite roadmap
+uv run python -m lemming.evals run --suite readability
+
+# Iterate on a single scenario with fewer trials
+uv run python -m lemming.evals run \
+    --scenario repair-exhausted-failure --trials 1 --skip-build
+
+# Machine-readable results and a non-default pass threshold
+uv run python -m lemming.evals run --json-report report.json --min-pass-rate 0.67
+```
+
+The command prints per-scenario pass rates (agents are stochastic, so think in
+rates, not booleans) and, for each failed trial, the failing checks plus the
+kept workspace path so you can inspect exactly what the agent did. Runner logs
+land in the trial's `home/` directory next to the workspace. The exit code is
+non-zero when any scenario's pass rate drops below `--min-pass-rate`.
+
+### Required vs Advisory Checks
+
+Most checks encode the prompt's hard contract mechanically (no source changes,
+no naive task resets, tests stay green) — a red there is a defect, and the right
+response is to improve the prompt. A few checks grade a semantic property
+through a keyword proxy (e.g. "the added task mentions multiply") and are marked
+**advisory**: they never fail a trial and print as yellow `inspect:` lines
+instead. An advisory red means read the workspace and adjudicate — if the
+agent's output was genuinely fine, widen the proxy; if it was vague, tighten the
+prompt. Keeping proxies out of the pass/fail gate is what keeps hard reds
+trustworthy.
+
+### Credentials
+
+The default runner is `agy`. Each trial automatically receives a private,
+disposable copy of the host's `~/.gemini` config (caches, history, and the
+bundled CLI excluded) mounted at `/root/.gemini`, so containers can refresh
+tokens and write state without ever touching the real agy home — and concurrent
+trials stay fully isolated from each other.
+
+For API-key runners, `ANTHROPIC_API_KEY`, `CLAUDE_CODE_OAUTH_TOKEN`,
+`GEMINI_API_KEY`, and `GOOGLE_API_KEY` are forwarded into the container when set
+on the host. Any other credential files can be mounted with `--volume`.
+
+## Adding Scenarios
+
+Scenarios live in `src/lemming/evals/` (see `roadmap.py`):
+
+1. Write a `build` function that seeds the workspace via `fixtures.init_repo`
+   and `fixtures.save_roadmap`.
+2. Write a `grade` function returning `scenarios.Check` results. Prefer checks
+   that are mechanically verifiable: roadmap diffs, `fixtures.dirty_paths` for
+   source drift, task statuses.
+3. Register the scenario in the module's `SCENARIOS` list, and new suites in
+   `suites.all_suites`.
+4. Add unit tests that grade simulated good and bad agent behavior; the graders
+   themselves must stay fast and offline.

{lemming_cli-0.1.1 → lemming_cli-0.1.2}/docs/HOOKS.md

@@ -34,6 +34,19 @@ 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.
 
+### 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:
+
+```bash
+uv run python -m lemming.evals run --suite roadmap
+uv run python -m lemming.evals run --suite readability
+```
+
+See [EVALS.md](EVALS.md) for how the suites work and how to interpret results.
+
 ## Custom Hooks
 
 You can define your own hooks by creating Markdown files in the following
@@ -122,8 +135,7 @@ is running, and the next task execution will respect the updated settings.
 
 Your hook template can use the following placeholders:
 
-- `{{roadmap}}`: A structured summary of the entire project context and all
-  tasks.
+- `{{roadmap}}`: A structured summary of the long-term goal and all tasks.
 - `{{finished_task}}`: Details about the task that just finished (ID,
   description, progress, and the last 100 lines of its execution log).
 - `{{finished_task_id}}`: The ID of the task that just finished.

{lemming_cli-0.1.1 → lemming_cli-0.1.2}/package-lock.json

@@ -10,10 +10,10 @@
       "hasInstallScript": true,
       "devDependencies": {
         "@biomejs/biome": "1.9.4",
-        "@playwright/test": "^1.58.2",
+        "@playwright/test": "^1.60.0",
         "jsdom": "latest",
         "mancha": "^0.22.4",
-        "playwright": "^1.58.2"
+        "playwright": "^1.60.0"
       }
     },
     "node_modules/@acemir/cssom": {
@@ -430,13 +430,13 @@
       }
     },
     "node_modules/@playwright/test": {
-      "version": "1.58.2",
-      "resolved": "https://registry.npmjs.org/@playwright/test/-/test-1.58.2.tgz",
-      "integrity": "sha512-akea+6bHYBBfA9uQqSYmlJXn61cTa+jbO87xVLCWbTqbWadRVmhxlXATaOjOgcBaWU4ePo0wB41KMFv3o35IXA==",
+      "version": "1.60.0",
+      "resolved": "https://registry.npmjs.org/@playwright/test/-/test-1.60.0.tgz",
+      "integrity": "sha512-O71yZIbAh/PxDMNGns37GHBIfrVkEVyn+AXyIa5dOTfb4/xNvRWV+Vv/NMbNCtODB/pO7vLlF2OTmMVLhmr7Ag==",
       "dev": true,
       "license": "Apache-2.0",
       "dependencies": {
-        "playwright": "1.58.2"
+        "playwright": "1.60.0"
       },
       "bin": {
         "playwright": "cli.js"
@@ -1253,13 +1253,13 @@
       "license": "ISC"
     },
     "node_modules/playwright": {
-      "version": "1.58.2",
-      "resolved": "https://registry.npmjs.org/playwright/-/playwright-1.58.2.tgz",
-      "integrity": "sha512-vA30H8Nvkq/cPBnNw4Q8TWz1EJyqgpuinBcHET0YVJVFldr8JDNiU9LaWAE1KqSkRYazuaBhTpB5ZzShOezQ6A==",
+      "version": "1.60.0",
+      "resolved": "https://registry.npmjs.org/playwright/-/playwright-1.60.0.tgz",
+      "integrity": "sha512-hheHdokM8cdqCb0lcE3s+zT4t4W+vvjpGxsZlDnikarzx8tSzMebh3UiFtgqwFwnTnjYQcsyMF8ei2mCO/tpeA==",
       "dev": true,
       "license": "Apache-2.0",
       "dependencies": {
-        "playwright-core": "1.58.2"
+        "playwright-core": "1.60.0"
       },
       "bin": {
         "playwright": "cli.js"
@@ -1272,9 +1272,9 @@
       }
     },
     "node_modules/playwright-core": {
-      "version": "1.58.2",
-      "resolved": "https://registry.npmjs.org/playwright-core/-/playwright-core-1.58.2.tgz",
-      "integrity": "sha512-yZkEtftgwS8CsfYo7nm0KE8jsvm6i/PTgVtB8DL726wNf6H2IMsDuxCpJj59KDaxCtSnrWan2AeDqM7JBaultg==",
+      "version": "1.60.0",
+      "resolved": "https://registry.npmjs.org/playwright-core/-/playwright-core-1.60.0.tgz",
+      "integrity": "sha512-9bW6zvX/m0lEbgTKJ6YppOKx8H3VOPBMOCFh2irXFOT4BbHgrx5hPjwJYLT40Lu+4qtD36qKc/Hn56StUW57IA==",
       "dev": true,
       "license": "Apache-2.0",
       "bin": {

{lemming_cli-0.1.1 → lemming_cli-0.1.2}/package.json

@@ -5,7 +5,8 @@
   "type": "module",
   "scripts": {
     "postinstall": "npm run vendor",
-    "test": "node --test src/lemming/web/*.test.js && playwright test",
+    "test": "node --test src/lemming/web/*.test.js && playwright test --project=chromium",
+    "screenshots": "playwright test --project=screenshots",
     "lint": "biome check .",
     "format": "biome format --write .",
     "check": "mancha check src/lemming/web/*.html",
@@ -13,9 +14,9 @@
   },
   "devDependencies": {
     "@biomejs/biome": "1.9.4",
-    "@playwright/test": "^1.58.2",
+    "@playwright/test": "^1.60.0",
     "jsdom": "latest",
     "mancha": "^0.22.4",
-    "playwright": "^1.58.2"
+    "playwright": "^1.60.0"
   }
 }

{lemming_cli-0.1.1 → lemming_cli-0.1.2}/playwright.config.js

@@ -10,6 +10,13 @@ export default defineConfig({
     {
       name: 'chromium',
       use: { ...devices['Desktop Chrome'] },
+      testIgnore: /screenshots\.spec\.js/,
+    },
+    // Regenerates docs/screenshots; run via `npm run screenshots`.
+    {
+      name: 'screenshots',
+      use: { ...devices['Desktop Chrome'] },
+      testMatch: /screenshots\.spec\.js/,
     },
   ],
 });

{lemming_cli-0.1.1 → lemming_cli-0.1.2}/pyproject.toml

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

{lemming_cli-0.1.1 → lemming_cli-0.1.2}/src/lemming/api/config.py

@@ -19,13 +19,13 @@ def get_runners():
     return list(models.KNOWN_RUNNERS)
 
 
-@router.post("/api/context")
-def update_context(
+@router.post("/api/goal")
+def update_goal(
     request: fastapi.Request, update: dict, project: str | None = None
 ):
-    """Update the shared project context passed to task runners."""
+    """Update the long-term goal shared with all task runners."""
     tasks_file = context.resolve_tasks_file(request.app.state, project)
-    tasks.update_context(tasks_file, update.get("context", ""))
+    tasks.update_goal(tasks_file, update.get("goal", ""))
     return {"status": "ok"}
 
 

{lemming_cli-0.1.1 → lemming_cli-0.1.2}/src/lemming/api/config_test.py

@@ -23,29 +23,29 @@ def test_get_runners(client):
     assert response.json() == ["agy", "aider", "claude", "codex"]
 
 
-def test_project_context_isolation(client, test_tasks):
-    """Context is isolated per project."""
+def test_project_goal_isolation(client, test_tasks):
+    """The goal is isolated per project."""
     root = api.app.state.root
-    subdir = root / "ctx_test"
+    subdir = root / "goal_test"
     subdir.mkdir(exist_ok=True)
 
-    # Set context for sub-project
+    # Set the goal for the sub-project
     response = client.post(
-        "/api/context",
-        json={"context": "Sub-project context"},
-        params={"project": "ctx_test"},
+        "/api/goal",
+        json={"goal": "Sub-project goal"},
+        params={"project": "goal_test"},
     )
     assert response.status_code == 200
 
-    # Root context should be unchanged
+    # Root goal should be unchanged
     res = client.get("/api/data")
     assert res.status_code == 200
-    assert res.json()["context"] == "Initial context"
+    assert res.json()["goal"] == "Initial goal"
 
-    # Sub-project context should be set
-    res = client.get("/api/data", params={"project": "ctx_test"})
+    # Sub-project goal should be set
+    res = client.get("/api/data", params={"project": "goal_test"})
     assert res.status_code == 200
-    assert res.json()["context"] == "Sub-project context"
+    assert res.json()["goal"] == "Sub-project goal"
 
 
 def test_run_loop_with_project(client, test_tasks):

{lemming_cli-0.1.1 → lemming_cli-0.1.2}/src/lemming/api/conftest.py

@@ -28,7 +28,7 @@ def test_tasks():
 
     # Scaffold a valid file
     data = tasks.Roadmap(
-        context="Initial context",
+        goal="Initial goal",
         tasks=[
             tasks.Task(
                 id="task1",
@@ -175,7 +175,7 @@ def test_workspace():
     # Set up some tasks in the subproject
     sub_tasks_file = subproject_dir / "tasks.yml"
     data = tasks.Roadmap(
-        context="Subproject context",
+        goal="Subproject goal",
         tasks=[
             tasks.Task(
                 id="sub1",

{lemming_cli-0.1.1 → lemming_cli-0.1.2}/src/lemming/api/main.py

@@ -11,7 +11,7 @@ from .. import paths
 from . import auth, config, directories, files, hooks, tasks
 from . import logging as lemming_logging
 
-# Re-export for backward compatibility and tests
+# Re-exported so logging configs can reference lemming.api.QuietPollFilter
 QuietPollFilter = lemming_logging.QuietPollFilter
 
 

{lemming_cli-0.1.1 → lemming_cli-0.1.2}/src/lemming/api/tasks.py

@@ -11,7 +11,7 @@ router = fastapi.APIRouter()
 
 @router.get("/api/data", response_model=tasks.ProjectData)
 def get_data(request: fastapi.Request, project: str | None = None):
-    """Get the full project data: context, config, tasks, and status."""
+    """Get the full project data: goal, config, tasks, and status."""
     tasks_file = context.resolve_tasks_file(request.app.state, project)
     data = tasks.get_project_data(tasks_file)
     data.cwd = str(context.resolve_project_dir(request.app.state, project))

{lemming_cli-0.1.1 → lemming_cli-0.1.2}/src/lemming/api/tasks_test.py

@@ -7,7 +7,7 @@ def test_get_data(client, test_tasks):
     response = client.get("/api/data")
     assert response.status_code == 200
     data = response.json()
-    assert data["context"] == "Initial context"
+    assert data["goal"] == "Initial goal"
     assert len(data["tasks"]) == 3
     # Check that task1 is in the list
     task1 = next(t for t in data["tasks"] if t["id"] == "task1")

{lemming_cli-0.1.1 → lemming_cli-0.1.2}/src/lemming/cli/__init__.py

@@ -1,7 +1,7 @@
 """Lemming CLI package; importing the submodules registers all commands."""
 
 from . import config as _config_cmds  # noqa: F401
-from . import context as _context_cmds  # noqa: F401
+from . import goal as _goal_cmds  # noqa: F401
 from . import hooks as _hooks_cmds  # noqa: F401
 from . import operations as _ops_cmds  # noqa: F401
 from . import progress as _progress_cmds  # noqa: F401

{lemming_cli-0.1.1 → lemming_cli-0.1.2}/src/lemming/cli/config_test.py

@@ -21,7 +21,7 @@ class TestCLIConfig(unittest.TestCase):
 
         # Scaffold a valid file
         data = tasks.Roadmap(
-            context="Initial context",
+            goal="Initial goal",
             tasks=[],
         )
         tasks.save_tasks(self.test_tasks_file, data)