dongarandClaude Opus 5.5
6ae2375194
nisse-dev now runs only the conversational loop. The gated state machine it was built alongside is gone: - Removed control.py, planner.py, executor.py, approvals.py, gates.py (command_form moves to loop/reader.py), publish.py and poller.py, the old assembly in agent.py (its shared helpers move to loop/build.py), the store's state-machine view (get_state, transition), their tests, the old end-to-end and live planning/milestone/gate tests, and specs/orchestrator.qnt with its scenarios. - Roles are driver, helper, expert and classifier; driver is required. loop:, roles.planner, roles.executor and tuning.executor are refused with what to use instead; tuning.driver takes the turn cap and failure limit. - The benchmark and the capability matrix measure the driver: the loop's own system prompt and tools, the task's plan as the agreed restatement. Task plans end with finish_milestone, so earlier runs show as (old); stored runs' executor tuning reads as the driver's. - A delegation on the loop records what its helper's alias resolved to (L9), as the old path's did. - The dump shows a work item's revision and what it waits for. - Behaviour the old tests covered and the loop shares stays covered: driver runs that fail on a model call, stop mid-turn, reset the failure count; go-aheads ignoring case and punctuation; a request too big to fit is never sent; the assembly tests, now on build_loop_agent. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PPQ14L3LikyefCMFBqEbKE
41 lines
2.4 KiB
YAML
41 lines
2.4 KiB
YAML
title: Carry out a long milestone whose steps build on each other
|
|
check: python -m pytest -q .bench_check
|
|
plan: |
|
|
Milestone 1: add due dates to the task tracker.
|
|
|
|
Run `python -m pytest -q` after each step; every test must still pass
|
|
before you start the next one. Use `datetime.date` for dates throughout.
|
|
|
|
1. `tracker/models.py`: add a field `due: date | None = None` to `Task`,
|
|
after `done`.
|
|
2. `tracker/storage.py`: `save` writes `"version": 2`, and each task's
|
|
`"due"` as an ISO string ("2026-10-01") or null. `load` reads version 1
|
|
files (their tasks have no "due"; use None) and version 2 files. Any
|
|
other version raises `ValueError("unsupported tasks file version: N")`,
|
|
with N the version found.
|
|
3. `tracker/core.py`: `add_task` takes a keyword argument
|
|
`due: date | None = None` and stores it on the new task.
|
|
4. `tracker/core.py`: change `sort_tasks` so that tasks not done come
|
|
before tasks done; within each of those two groups, tasks with a due
|
|
date come first, earliest due date first, then tasks without one; ties
|
|
are broken by id.
|
|
5. `tracker/core.py`: add `overdue(tasks: list[Task], today: date) -> list[Task]`:
|
|
tasks not done whose due date is before `today`, in `sort_tasks` order.
|
|
6. `tracker/formatting.py`: `format_task` takes a second argument
|
|
`today: date`. A task with a due date gets " (due 2026-10-01)" after its
|
|
title. An overdue task (as in step 5) shows `[!]` instead of `[ ]`.
|
|
Examples: "[ ] 3 Buy milk", "[x] 4 Call Bob (due 2026-10-01)",
|
|
"[!] 5 Pay rent (due 2026-09-01)".
|
|
7. `tracker/cli.py`: pass today's date to `format_task`. Today is the
|
|
`TRACKER_TODAY` environment variable (YYYY-MM-DD) when it is set, else
|
|
`date.today()`. `add` gains an option `--due YYYY-MM-DD`; an invalid date
|
|
must call `parser.error("invalid --due date: VALUE")`, which exits with
|
|
status 2. `list` gains a flag `--overdue` that lists only overdue tasks.
|
|
8. Add tests under `tests/` for each of steps 1-7, run `python -m pytest -q`
|
|
until everything passes, then check the whole flow by running:
|
|
`TRACKER_FILE=/tmp/tracker-check.json TRACKER_TODAY=2026-10-05 python -m tracker add "Pay rent" --due 2026-10-01`
|
|
then the same with `list --overdue`, which must print
|
|
`[!] 1 Pay rent (due 2026-10-01)`. Delete /tmp/tracker-check.json
|
|
before and after.
|
|
9. Call finish_milestone, with final yes.
|