Loading…
Reference in a new issue
No description provided.
Delete branch "claude/console-fixes-and-session-cap"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Batch A from the 2026-11-15 issue review: six issues in one change,
console-fixes-and-session-cap(proposal, specs, design and tasks underopenspec/changes/).What changed
only. A gate names the decision ("Approve the merge"), so auto-approve needs no rewrite. A task group is named by its plan's heading in the transcript and the Stop dialog too, not "Implement group N", and the tasks rules ask for each heading in about three words. A run with no plan keeps the number. At 1440 px no name or condition wraps, half-width boxes included (measured on every box of a seeded thorough run).started_at, which is new in/api/status.osf.repair.openednames its agent. An Ask period closes when its run is no longer live, and Ask going on as Repair closes Ask's period first. The spine's entry and the helper tab read "Ask" for a conversation that was only Ask's. Records from before this change read "Repair".POST /api/runs/deleteanswers 202 and deletes in a background job, one job at a time.GET /api/runs/delete/{id}gives the progress and, once the job ends, the results. The dialog sends the whole selection and follows the job. A timed-out request names what was asked and no longer blames other tabs.POST /api/runs/{run}/helper-place) and gives it back when it ends. A helper its step waits for works in the step's place, one at a time per step. If osfd does not answer within 2 s, the guard falls back to its old gate.stoptakes an optionalidand stops only that helper. Eachstopcall is handled once, so a secondstop testworks.Checked
./tools/test.shpasses in 51 s on the laptop../tools/sim.sh --smokepasses all 7 scenarios, andhelpers-wait-for-a-place,helpers-queue-in-the-backgroundandapply-writes-ignored-sourcepass.stopby id.The graph at 1440 px
From a seeded test server. The apply groups' titles come from the run's plan; the other step names are the new ones.
Not done
🤖 Generated with Claude Code
`POST /api/runs/delete` answers 202 at once and deletes its runs in a job, one job at a time; `GET /api/runs/delete/{id}` says how far it has got and, once ended, each run's result. The dialog sends the whole selection and follows the job. A request osfd does not answer in time now names what was asked and no longer blames other tabs. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>The ceiling is read for each run from the backend it was started on, and counts the agent steps on that backend with the places granted to their helpers. A helper started in the background asks osfd for a place (`POST /api/runs/{run}/helper-place`) and gives it back when its session ends; one its step waits for works in the step's place, one at a time per step. When osfd does not answer, the guard falls back to its own gate. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>