Shell and pages, runs on their own profile, the Visual check, side-by-side spec tests (#311 #314 #318 #313 #312 #315 #268 #306) #319

Merged
cmoriarty merged 6 commits from claude/batch-311 into main 2026-10-29 21:37:23 -04:00
Owner

Four OpenSpec changes, as planned with the operator on 2026-10-29:

shell-and-pages

  • #311: once its shell exits, the agent shell's wrapper returns, even while a process left in the background holds the output pipe. Run 145's step had wedged there.
  • #314: the run bar's breadcrumb gives way, so at half width the run's time no longer covers the state chip.
  • #318: a project writing its plan shows "Writing the plan", not "No plan is left on disk".

runs-use-their-own-profile

  • #313: a run's context per agent, mediation, Repair's limits and default auto-approve come from its own recorded profile. The run limit is counted per backend, and each backend a going run uses is probed, so its steps wait only on their own backend.
  • #312: with Free in use, settings save.

the-visual-check

  • The step agent.judge becomes agent.visual-check, "Visual check". Internal names stay: the judge agent, judge.json and the Free tier.
  • #315: its chip opens its report: verdict, play-through, failed criteria with evidence and screenshots, console errors, and the next round's verdict.
  • #268: a scenario only a browser shows is listed in .osf/test/visual.json instead of mock-tested. It no longer counts as missing a test, and the Visual check judges it by name.

side-by-side-spec-tests

  • #306, first slice: on a backend with several sessions, each capability's scenario-test step works in its own worktree, three at once, and is merged back. On trogdor that should take run 147's 32 minutes to about 17.

Checks

  • ./tools/test.sh: 247 backend, 63 UI, 21 browser.
  • ./tools/sim.sh: 73 of 73. New: shell-background, which hangs on the old wrapper. spec-tests-per-capability now expects its steps to overlap, and fails with side by side off.

Verification after the deploy: a planned project on vLLM with the Breakout brief and its five Could-add ideas, and #269's seeded faults.

🤖 Generated with Claude Code

Four OpenSpec changes, as planned with the operator on 2026-10-29: **`shell-and-pages`** - #311: once its shell exits, the agent shell's wrapper returns, even while a process left in the background holds the output pipe. Run 145's step had wedged there. - #314: the run bar's breadcrumb gives way, so at half width the run's time no longer covers the state chip. - #318: a project writing its plan shows "Writing the plan", not "No plan is left on disk". **`runs-use-their-own-profile`** - #313: a run's context per agent, mediation, Repair's limits and default auto-approve come from its own recorded profile. The run limit is counted per backend, and each backend a going run uses is probed, so its steps wait only on their own backend. - #312: with Free in use, settings save. **`the-visual-check`** - The step `agent.judge` becomes `agent.visual-check`, "Visual check". Internal names stay: the `judge` agent, `judge.json` and the Free tier. - #315: its chip opens its report: verdict, play-through, failed criteria with evidence and screenshots, console errors, and the next round's verdict. - #268: a scenario only a browser shows is listed in `.osf/test/visual.json` instead of mock-tested. It no longer counts as missing a test, and the Visual check judges it by name. **`side-by-side-spec-tests`** - #306, first slice: on a backend with several sessions, each capability's scenario-test step works in its own worktree, three at once, and is merged back. On trogdor that should take run 147's 32 minutes to about 17. **Checks** - `./tools/test.sh`: 247 backend, 63 UI, 21 browser. - `./tools/sim.sh`: 73 of 73. New: `shell-background`, which hangs on the old wrapper. `spec-tests-per-capability` now expects its steps to overlap, and fails with side by side off. **Verification after the deploy:** a planned project on vLLM with the Breakout brief and its five Could-add ideas, and #269's seeded faults. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
cmoriarty deleted branch claude/batch-311 2026-10-29 21:37:23 -04:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
cmoriarty/braid!319
No description provided.