Skip to content

feat(workspace): add fix-with-agent, checks tab, and fleet lanes - #50

Merged
astykyj merged 3 commits into
mainfrom
feat/ref-svc-parity
Jun 23, 2026
Merged

feat(workspace): add fix-with-agent, checks tab, and fleet lanes#50
astykyj merged 3 commits into
mainfrom
feat/ref-svc-parity

Conversation

@astyfx

@astyfx astyfx commented Jun 23, 2026

Copy link
Copy Markdown
Member

Summary

Three workflow features for the local single-user experience, building on the verification/turn-journal foundation (PR #48).

Key changes

  • feat(verification): forward failing checks to the agent (one-click fix) — when a pre-merge check fails, hand the failure straight to the agent to fix in one click. (verification.ts, app.store.ts)
  • feat(checks): add pre-merge Checks tab to the Changes panel — surface check results in a dedicated tab inside the Changes panel, the permanent home for verification UX. (WorkspaceChangesPanel.tsx, EditorPanel.tsx)
  • feat(fleet): group workspaces into lifecycle lanes — derive a lifecycle dimension (In progress / In review / Backlog / Done) orthogonal to runtime status; PR state is the strongest signal, falling back to activity. No schema change. (FleetView.tsx, task-status.ts)

Verification

  • bun run typecheck — clean
  • bun test tests/fleet-task-status.test.ts tests/turn-verification.test.ts — 34 pass / 0 fail

🤖 Generated with Claude Code

astyfx and others added 3 commits June 23, 2026 12:36
Turn a turn's failing verification checks into a follow-up turn. Adds a
"Fix with agent" action to the Changes-panel verification popover (header
fixes all; a per-failure "Fix" narrows to one check). Builds a
provider-agnostic prompt from each failure's scriptId + bounded output and
submits it via sendUserMessage for the verifying task — queued if a turn is
in flight, started otherwise. Never auto-submits.

- buildVerificationFixPrompt: pure, bounded-output prompt builder (+ tests)
- requestVerificationFix store action wires the popover to sendUserMessage

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
A read-only "ready to merge?" roll-up beside Changes/History that
consolidates the scattered pre-merge signals into one surface:

- Pull request readiness (cached PR status + title)
- Verification (reuses the failure list; hosts the "Fix with agent"
  action from the one-click fix loop)
- Intent guard findings (click to open the file)
- Working-tree summary (branch, staged/working/conflicts)
- Open todos

PR status is refreshed only while the Changes tab is active so it never
double-fetches alongside the Information panel. The tab trigger shows a
count of merge-blocking signals. Reuses existing semantic + PR-tone
tokens; no new theme colors.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Adds a *lifecycle* dimension (In progress / In review / Backlog / Done)
orthogonal to the existing per-task runtime status, so the Fleet view
reads as an at-a-glance multi-agent overview.

Lifecycle is derived (no schema change): a linked PR is the strongest
signal (open → in review, merged/closed → done), else live/recent task
activity → in progress, else backlog. Each workspace section reports its
lane up to FleetView (same pattern as attention targets); the parent
groups workspaces into lanes and renders labeled separators only when a
project actually spans more than one lane. Sections stay keyed siblings
in one list so regrouping never remounts them.

Pure deriveFleetLifecycleStatus + groupFleetWorkspacesByLane (+ tests).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@astykyj
astykyj merged commit 5e55970 into main Jun 23, 2026
3 checks passed
@astykyj
astykyj deleted the feat/ref-svc-parity branch June 23, 2026 11:04
@astyfx astyfx changed the title feat(workspace): reference-product parity — fix-with-agent, checks tab, fleet lanes feat(workspace): add fix-with-agent, checks tab, and fleet lanes Aug 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants