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
16 lines
795 B
YAML
16 lines
795 B
YAML
title: Implement a parser from a written specification
|
|
check: python -m pytest -q .bench_check
|
|
plan: |
|
|
Milestone 1: implement `parse_duration` as `SPEC.md` specifies.
|
|
|
|
1. Read all of `SPEC.md`. It has eight numbered rules; every one applies.
|
|
2. In `durations.py`, replace the body of `parse_duration(text: str) -> int`
|
|
so that it follows every rule in `SPEC.md`, including the inputs each
|
|
rule says are invalid and the error message for them. Examples:
|
|
"1h30m" -> 5400; "90" -> 90; "1:02:03" -> 3723.
|
|
3. Create `test_durations.py` with pytest tests: at least one valid and one
|
|
invalid input for each of the eight rules.
|
|
4. Run `python -m pytest -q test_durations.py`, and fix `durations.py`
|
|
until every test passes.
|
|
5. Call finish_milestone, with final yes.
|