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
13 lines
533 B
YAML
13 lines
533 B
YAML
title: Find one failure in long test output
|
|
check: python -m pytest -q .bench_check
|
|
plan: |
|
|
Milestone 1: fix the one wrong entry in the rate table.
|
|
|
|
1. Run `python -m pytest -v`. Exactly one test fails, and its output names a
|
|
region code.
|
|
2. The tests are correct. In `rates.py`, the rate for region code RNNN must be
|
|
(NNN mod 25) / 100. Correct only the failing region's entry; leave every
|
|
other line as it is.
|
|
3. Run `python -m pytest -q` until every test passes.
|
|
4. Call finish_milestone, with final yes.
|