When a milestone has only CONTEXT-DRAFT.md (no CONTEXT.md), the depends_on
frontmatter was silently ignored because _deriveStateImpl() only read from
CONTEXT.md. This caused dep-blocked milestones to be incorrectly promoted
to active status. Now all three dependency-reading paths fall back to
CONTEXT-DRAFT.md when CONTEXT.md is absent.
Fixes#1724
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
parseProseSliceHeaders() always set done:false regardless of ✓ or
(Complete) markers in the title, causing auto-mode to repeatedly
dispatch complete-slice for already-finished slices.
- Detect ✓ prefix before slice ID ("## ✓ S01: Title")
- Detect ✓ after separator ("## S01: ✓ Title")
- Detect (Complete) suffix ("## S01: Title (Complete)")
- Strip markers from title so downstream consumers get clean names
- Add prose format support to markSliceDoneInRoadmap
Fixes#1803
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Add QUEUE.md and completed-units.json to the durable file whitelist in
both syncGsdStateToWorktree (forward sync) and syncWorktreeStateBack
(reverse sync). These files are written during milestone closeout but
were not being copied back to the project root, causing state loss on
worktree teardown.
Adds regression test verifying both files survive reverse sync.
Fixes#1787
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The @ file autocomplete triggered a synchronous native fuzzyFind call
that walks the entire directory tree. On large repos this blocked the
Node.js event loop and froze the TUI.
Three changes fix this:
1. Skip the fuzzy search when the query is empty (bare "@" with nothing
typed yet) — there is no point walking the full tree with no query.
2. Debounce the initial "@" keystroke instead of firing the search
synchronously, so rapid typing cancels pending walks and the search
only runs once the user pauses.
3. Deduplicate consecutive lookups using lastAutocompleteLookupPrefix
(previously declared but unused) to avoid redundant synchronous
searches when the prefix hasn't changed.
Fixes#1824
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Three bugs caused mergeMilestoneToMain to silently lose all milestone branch
commits when git merge --squash was rejected by dirty/untracked .gsd/ files:
1. nativeMergeSquash catch block returned success:true when git rejected a
merge pre-staging ("local changes would be overwritten") because the
--diff-filter=U conflict check found no markers. Now detects dirty tree
rejections via stderr and returns a __dirty_working_tree__ sentinel.
2. mergeMilestoneToMain deleted the milestone branch unconditionally even
when nothingToCommit was true (empty squash). Now throws with a clear
error and preserves the branch to prevent data loss.
3. clearProjectRootStateFiles only removed STATE.md, auto.lock, and
META.json but left synced milestone dirs and runtime/units from
syncStateToProjectRoot. These untracked files blocked squash merges.
Now cleans all untracked files in synced .gsd/ directories before merge.
Fixes#1738
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* feat(doctor): worktree lifecycle checks, cleanup consolidation, enhanced /worktree list
Phase 1: Worktree lifecycle doctor checks
- worktree_branch_merged: detect worktrees fully merged into main (auto-fixable)
- worktree_stale: warn on worktrees with no commits in 14+ days
- worktree_dirty: warn on stale worktrees with uncommitted changes
- worktree_unpushed: warn on stale worktrees with unpushed commits
- New worktree-health.ts module with shared helpers for status computation
Phase 2: Fold cleanup into doctor
- legacy_slice_branches now fixable (was info-only, doctor fix deletes them)
- snapshot_ref_bloat check added to doctor (was only in /gsd cleanup snapshots)
- /gsd cleanup worktrees wired up as convenience entry point
Phase 3: Enhanced /worktree list
- Shows inline health status per worktree (merge status, dirty files, age, etc)
- Color-coded: green for safe-to-remove, yellow for stale/dirty, dim for active
New git primitives: nativeIsAncestor, nativeLastCommitEpoch, nativeUnpushedCount
* fix: close gaps — rewire cleanup to doctor, add tests
- Rewire handleCleanupBranches to delegate to doctor fix (branch issues)
- Rewire handleCleanupSnapshots to delegate to doctor fix (snapshot issues)
- Remove duplicate cleanup logic from commands-maintenance.ts
- Fix safeToRemove: merged+clean is sufficient (unpushed irrelevant when merged)
- Add 10 new doctor-git tests: worktree_branch_merged detection/fix/no-false-positive, legacy_slice_branches fixable
- Add 21 new worktree-health tests: merged, dirty, unpushed, stale, format
Total: 178 tests pass across 4 suites, 0 failures
* fix(ci): escape glob pattern in JSDoc comment, clean up duplicate comment
* fix: narrow cleanup scope and protect quick branches
* fix(test): trim leading spaces from git branch output assertion
run() calls .trim() so git branch output has no leading spaces.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
---------
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
The tool_result handler early-returned when getDiscussionMilestoneId()
was null, which is always the case in queue mode. This prevented
markDepthVerified() from being called, permanently blocking CONTEXT.md
writes when queuePhaseActive was true.
The handler now also checks isQueuePhaseActive() before returning early,
allowing depth verification to complete in queue mode. A second guard
after depth verification processing ensures the discussion log write
still requires a valid milestoneId.
Fixes#1812
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
When VSCode crashes or the parent process dies, only SIGTERM was handled,
leaving stranded .gsd.lock/ and auto.lock files. Now registers handlers
on SIGTERM, SIGHUP, and SIGINT, and calls both clearLock() and
releaseSessionLock() for complete cleanup.
Fixes#1797
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
When a milestone has a CONTEXT-DRAFT.md (from multi-milestone queue creation)
or no CONTEXT.md at all, auto-mode previously hard-stopped with a message
telling the user to 'Run /gsd to discuss.' This created a dead end because:
1. /gsd (bare) routes to startAuto(step:true), which hits the same stop rule
2. /gsd auto also hits the same stop rule
3. Only /gsd discuss works, but the stop message doesn't mention it
This change replaces both hard-stop rules with discuss-milestone dispatch:
- 'needs-discussion → stop' becomes 'needs-discussion → discuss-milestone'
- 'pre-planning (no context) → stop' becomes 'pre-planning (no context) → discuss-milestone'
The new discuss-milestone unit type:
- Uses the guided-discuss-milestone prompt template
- Inlines CONTEXT-DRAFT.md as seed material when present
- Interviews the user and writes CONTEXT.md
- After CONTEXT.md exists, deriveState() returns 'pre-planning' and the
normal research → plan → execute pipeline continues automatically
Supporting changes:
- auto-prompts.ts: new buildDiscussMilestonePrompt() function
- auto-dashboard.ts: discuss-milestone labels for status display
- complexity-classifier.ts: discuss-milestone classified as 'standard' tier
- auto-recovery.ts: expected artifact = CONTEXT.md for discuss-milestone
Remove all_tasks_done_missing_slice_uat and all_tasks_done_roadmap_not_checked
from COMPLETION_TRANSITION_CODES so they are fixed at task fixLevel. Only
all_tasks_done_missing_slice_summary remains deferred (requires LLM content).
This closes the fragile handoff window where a session crash between last task
and complete-slice left the project inconsistent.
Fixes#1808
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
stopAuto() and pauseAuto() now call resolveAgentEnd() and
_resetPendingResolve() before resetting session state, unblocking
autoLoop's `await unitPromise` so it can see s.active===false and
exit cleanly. Without this, the main interactive loop hangs forever.
Fixes#1799
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
After show-ref fails, fall back to checking if the branch is the current
unborn branch via git branch --show-current. This resolves the asymmetry
where git branch --show-current succeeds on zero-commit repos but
show-ref --verify does not, preventing integration branch verification
from creating an unfixable deadlock.
Fixes#1771
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The doctor's orphaned_completed_units check was running at fixLevel="task"
during every auto-mode post-unit cycle. When artifact files were temporarily
unreachable (worktree sync timing, path resolution), the doctor removed their
completion keys from completed-units.json. This caused deriveState to consider
those tasks incomplete, reverting the user to an earlier slice and discarding
all work past that point.
Add orphaned_completed_units to GLOBAL_STATE_CODES so it is never auto-fixed
at fixLevel="task". Only explicit manual doctor runs (fixLevel="all") can now
remove completion keys.
Fixes#1809
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
realpathSync doesn't resolve Windows 8.3 short names (RUNNER~1),
but realpathSync.native does. This fixes the 3 Windows CI test
failures that block the pipeline from triggering.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
A milestone directory containing only META.json (no CONTEXT, ROADMAP, or
SUMMARY) is an uninitialized "ghost" that causes auto-mode to stall or
falsely report all milestones complete. Add isGhostMilestone() check in
both getActiveMilestoneId() and deriveState() to skip these directories.
Also handle the edge case where all milestones are ghosts by returning
pre-planning instead of complete.
Closes#1662
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* chore(M003/S01): auto-commit after plan-slice
* chore(M003/S01/T02): auto-commit after execute-task
* chore(M003/S01/T03): auto-commit after execute-task
* docs: queue M004 — web mode documentation and CI/CD integration
* chore(M003/S01/T04): auto-commit after execute-task
* chore(M003/S01): auto-commit after complete-slice
* chore(M003/S01): auto-commit after reassess-roadmap
* chore: production polish — real logo, remove scaffold remnants
- Replace placeholder 'G' box in header with real GSD logo icon SVG (currentColor, theme-aware)
- Delete 5 dead placeholder files (placeholder-logo.svg/png, placeholder-user.jpg, placeholder.jpg, placeholder.svg)
- Remove v0.app generator tag from layout metadata
- Remove unused @vercel/analytics dependency
* chore(M003/S02): auto-commit after research-slice
* chore(Q1): auto-commit after quick-task
* fix: remove duplicate parse cache block causing web mode boot failure
The 'Parse Cache' section in files.ts was duplicated (merge artifact),
causing 'Identifier CACHE_MAX has already been declared' when Node's
--experimental-strip-types loaded the file. This made /api/boot return
500, which caused waitForBootReady to time out and web mode launch to
fail with 'boot-ready:http 500'.
Removed the second (older) duplicate block, keeping the first one which
includes the improved mid-sample cache key.
* docs: add quick task summary and update STATE.md
* fix: replace sidebar icon+text with full logo image
Swap the inline SVG G-mark icon and 'GSD 2' text span in the app shell
header with an <img> referencing /logo-white.svg (the full GSD wordmark).
Removes the redundant text label. Sized at h-4 (16px) to fit the header.
* docs(S02): add slice plan
* chore: update state for S02 execution
* chore(M003/S02/T01): auto-commit after execute-task
* chore(M003/S02/T02): auto-commit after execute-task
* chore(M003/S02/T03): auto-commit after execute-task
* chore(M003/S02): auto-commit after complete-slice
* chore(M003/S02): auto-commit after reassess-roadmap
* chore(M003/S03): auto-commit after research-slice
* docs(S03): add slice plan
* chore(M003/S03/T01): auto-commit after execute-task
* chore(M003/S03/T02): auto-commit after execute-task
* chore(M003/S03/T03): auto-commit after execute-task
* chore(M003/S03): auto-commit after complete-slice
* chore(M003/S03): auto-commit after reassess-roadmap
* chore(M003/S04): auto-commit after research-slice
* docs(S04): add slice plan
* chore(M003/S04/T01): auto-commit after execute-task
* chore(M003/S04/T02): auto-commit after execute-task
* chore(M003/S04/T03): auto-commit after execute-task
* chore(M003/S04): auto-commit after complete-slice
* chore(M003/S04): auto-commit after reassess-roadmap
* chore(M003/S05): auto-commit after research-slice
* docs(S05): add slice plan
* chore(M003/S05/T01): auto-commit after execute-task
* chore(M003/S05/T02): auto-commit after execute-task
* chore(M003/S05): auto-commit after complete-slice
* chore(M003/S05): auto-commit after reassess-roadmap
* chore(M003/S06): auto-commit after research-slice
* docs: queue M005
* docs(S06): add slice plan
* chore(M003/S06/T01): auto-commit after execute-task
* chore(M003/S06/T02): auto-commit after execute-task
* chore(M003/S06): auto-commit after complete-slice
* chore(M003/S06): auto-commit after reassess-roadmap
* chore(M003/S07): auto-commit after research-slice
* docs(S07): add slice plan
* chore: update STATE.md for S07 execution
* chore(M003/S07/T01): auto-commit after execute-task
* chore(M003/S07/T02): auto-commit after execute-task
* chore(M003/S07/T03): auto-commit after execute-task
* chore(M003): record integration branch
* chore(M003/S07/T04): auto-commit after execute-task
* chore(M003/S07): auto-commit after complete-slice
* chore(M003/S07): auto-commit after reassess-roadmap
* chore(M003/S08): auto-commit after research-slice
* docs(S08): add slice plan
* chore(M003/S08/T01): auto-commit after execute-task
* chore(M003/S08/T02): auto-commit after execute-task
* chore(M003/S08): auto-commit after complete-slice
* chore(M003/S08): auto-commit after reassess-roadmap
* chore(M003/S09): auto-commit after research-slice
* docs(S09): add slice plan
* chore(M003/S09/T01): auto-commit after execute-task
* chore(M003/S09/T02): auto-commit after execute-task
* chore(M003/S09): auto-commit after complete-slice
* chore(M003): auto-commit after complete-milestone
* chore(M004): record integration branch
* chore: untrack .gsd/ runtime files from git index
* chore(M004): auto-commit after research-milestone
* feat(M006): multi-project workspace
- Bridge registry replacing singleton (Map<string, BridgeService> keyed by project path)
- resolveProjectCwd(request) for ?project= query param with env-var fallback
- All 26 API routes and 16 services threaded with project context
- Project discovery service scanning one directory level with smart detection
- /api/projects and /api/preferences routes
- ProjectStoreManager with per-project SSE lifecycle isolation
- Projects NavRail tab with kind badges and signal chips
- Onboarding dev root step (position 3, skippable)
- Context-aware launch detection (resolveContextAwareCwd)
- BootProjectInitializer for auto-registering boot project
- 25 new contract tests (8 bridge, 10 discovery, 7 launch)
- 1222 tests pass, both builds green
Squash-merged from milestone/M006 work on gsd/quick branch.
Includes M004 and M005 milestone artifacts.
* feat: add dev root setup in Projects view and Settings panel
- Projects view empty state now has inline dev root input with
suggestion chips instead of just a text message
- Settings gear → Workspace tab shows dev root configuration
- /gsd prefs command surface includes dev root section at top
- PUT /api/preferences now merges with existing prefs (read-modify-write)
instead of overwriting — fixes potential data loss of lastActiveProject
- Fixed pre-existing type issue: sectionLabel/sectionIcon Records use
Partial<Record> to handle gsd-* sections that aren't in the map
* feat: native folder picker for dev root selection
- New /api/browse-directories?path= endpoint returns directory listings
from the server filesystem (directories only, excludes dotfiles/node_modules)
- FolderPickerDialog component with directory browser: navigate folders,
go up to parent, select current folder
- Projects view empty state shows 'Browse for Folder' button opening the picker
- Settings Workspace tab shows current path with 'Change' button opening picker
- Replaces text input approach — no more typing paths manually
* fix: move Projects icon to bottom of NavRail, above Git
Projects is a workspace-level navigation action, not a primary view.
Placing it in the bottom section alongside Git and Settings keeps
the top section focused on content views.
* feat: multi-project-aware exit dialog
When multiple projects are open, the exit button shows two options:
- Close current project (disconnects it, switches to another)
- Stop server (shuts down all projects and closes the tab)
With only one project open, shows the original simple 'Stop server' dialog.
Also adds closeProject(), getProjectCount(), and getActiveProjectPaths()
to ProjectStoreManager.
* feat: intercept browser tab close with confirmation and auto-shutdown
beforeunload triggers the browser's native 'Leave site?' confirmation
dialog when the user tries to close the tab. If they confirm, pagehide
fires sendBeacon to /api/shutdown, cleanly stopping all GSD instances.
* feat: remove session card from dashboard, fix beforeunload
- Removed the session card (model, cost, tokens, elapsed, auto mode,
live tool/streaming indicators) from the dashboard right column
- Dashboard current slice section now takes full width
- Removed beforeunload handler (tab close silently shuts down via
pagehide + sendBeacon instead of showing native browser dialog)
- Updated web-state-surfaces-contract test: removed assertion for
activeToolExecution/streamingAssistantText in dashboard
- 1220/1221 tests pass (1 flaky context-store unrelated to changes)
* feat: show loading dialog when switching to a new project
When clicking a project that doesn't have a bridge instance yet,
a shadcn Dialog with a spinner and 'Opening [project]' message
appears instead of navigating to the dashboard with skeleton cards.
The dialog waits for the store's bootStatus to become 'ready' or
'error' (or 30s timeout) before navigating to the dashboard.
Clicking the already-active project navigates directly.
* feat: restore theme toggle and light/dark CSS from M005
M005's theme work was lost during the M006 squash merge (different
branch base). This restores:
- ThemeProvider in layout.tsx with class-based theming and FOIT prevention
- NavRail theme toggle cycling system → light → dark (Monitor/Sun/Moon icons)
- Light-mode :root CSS variables (monochrome oklch, inverted lightness)
- Dark .dark section with custom tokens (--success, --warning, --info,
--terminal, --terminal-foreground, --code-line-number)
- suppressHydrationWarning on <html> for next-themes compatibility
* fix: switch logo between black/white variants based on theme
Uses paired dark:/hidden Tailwind classes — zero JS cost, no flash.
* chore: untrack .gsd/ runtime files from git index
* chore(Q2): auto-commit after quick-task
* feat(web): resizable milestone sidebar + rename tab title to GSD
- Add drag-to-resize handle on left edge of milestone sidebar
(col-resize, 180-480px range, same pattern as terminal resize)
- Change document.title suffix from 'GSD 2' to 'GSD'
- Remove border-l from MilestoneExplorer (drag handle provides separation)
* docs: quick task 2 summary and state update
* feat: spawn GSD instance in right-side terminal, rename browser tab to GSD
- Add command option to PTY manager to spawn pi instead of default shell
- Thread command param through terminal API routes and ShellTerminal component
- DualTerminal right pane now launches a separate pi (GSD) instance
- Update header label to 'Right: Interactive GSD'
- Set browser tab title to 'GSD' instead of project folder name
* fix: use distinct default session ID for GSD terminal to avoid reusing stale zsh session
* fix: make shell terminal respect light/dark theme
- Add light xterm theme alongside existing dark theme
- Detect theme via next-themes useTheme and pass isDark to terminal instances
- Dynamically update xterm theme when user switches themes
- Replace all hardcoded dark bg colors (#0a0a0a, #0c0c0c, zinc-*) with
theme-aware classes (bg-terminal, text-muted-foreground, etc.)
* feat: add loading spinner while terminal session initializes
* feat: replace left-side AutoTerminal with real GSD terminal instance
- Remove custom AutoTerminal React component
- Left side now runs a real pi terminal (sessionPrefix=gsd-main)
- Right side uses sessionPrefix=gsd-interactive for isolation
- Add sessionPrefix prop to ShellTerminal for distinct session IDs
- Update header labels: Left: Primary GSD | Right: Interactive GSD
* feat: auto-select STATE.md on files view initial load
* feat: pre-initialize dual terminal PTY sessions on boot
Keep DualTerminal always mounted (hidden when not active) so PTY
sessions spawn as soon as the bridge connects. Terminals are ready
immediately when the user switches to the power view.
* fix: move STATE.md auto-select effect after handleSelectFile declaration
Fixes TDZ ReferenceError — the useEffect was referencing handleSelectFile
before its useCallback declaration.
* chore(M006): record integration branch
* Squashed commit of the following:
commit e3f495a224f53e954798b6f96a59806db43bfdb0
Author: snowdamiz <yurlovandrew@gmail.com>
Date: Tue Mar 17 16:12:50 2026 -0400
chore: auto-commit before milestone merge
commit d9a0193c9c54fafcaff6bc0de7c169936f41b2df
Author: snowdamiz <yurlovandrew@gmail.com>
Date: Tue Mar 17 08:35:53 2026 -0400
chore: auto-commit before milestone merge
commit 010430059ca50c6b773ee4480e42d2c54a1c0b75
Author: snowdamiz <yurlovandrew@gmail.com>
Date: Tue Mar 17 04:57:49 2026 -0400
chore(M006): record integration branch
commit a6f6d0294c90a253585571a5a9615c7f3e41e7ea
Author: snowdamiz <yurlovandrew@gmail.com>
Date: Tue Mar 17 04:57:36 2026 -0400
docs: queue M006 — Multi-project workspace
commit b2dd57423835d132f6d3963abbb2bfc799e64100
Author: snowdamiz <yurlovandrew@gmail.com>
Date: Tue Mar 17 03:43:52 2026 -0400
chore(M005): record integration branch
# Conflicts:
# .gsd/DECISIONS.md
# .gsd/PROJECT.md
# .gsd/REQUIREMENTS.md
# .gsd/milestones/M006/M006-META.json
# src/web/recovery-diagnostics-service.ts
* chore(M006): record integration branch
* feat(M006): Multi-Project Workspace
Completed slices:
- S01: Bridge registry and project-scoped API surface
- S02: Project discovery, Projects view, and store switching
- S03: Onboarding dev root step, context-aware launch, and final assembly
Branch: milestone/M006
* refactor(visualizer): redesign visualizer-view layout and tab structure
* docs(M007): context, requirements, and roadmap
* chore(M007): record integration branch
* docs(M007): rewrite roadmap and all slice plans to new template format
* chore(M007/S01/T01): auto-commit after execute-task
* chore(M007/S01/T02): auto-commit after execute-task
* chore(M007/S01): auto-commit after complete-slice
* chore(M007/S01): auto-commit after reassess-roadmap
* chore(M007/S02/T01): auto-commit after execute-task
* chore(M007/S02/T02): auto-commit after execute-task
* chore(M007/S02/T03): auto-commit after execute-task
* chore(M007/S02): auto-commit after complete-slice
* chore(M007/S02): auto-commit after reassess-roadmap
* chore(M007/S03/T01): auto-commit after execute-task
* chore(M007/S03/T02): auto-commit after execute-task
* chore(M007/S03): auto-commit after complete-slice
* chore(M007/S03): auto-commit after reassess-roadmap
* chore(M007/S04/T01): auto-commit after execute-task
* chore(M007/S04/T02): auto-commit after execute-task
* chore(M007/S04/T03): auto-commit after execute-task
* chore(M007/S04): auto-commit after complete-slice
* chore(M007): auto-commit after complete-milestone
* feat(M007): Chat Mode — Consumer-Grade GSD Interface
Completed slices:
- S01: PTY output parser and chat message model
- S02: Chat Mode view — main pane
- S03: TUI prompt intercept UI
- S04: Action toolbar and right panel lifecycle
Branch: milestone/M007
* feat(chat-mode): move Discuss to input bar
* fix(web): launch browser PTYs with GSD loader
* chore(M005): record integration branch
* feat(M005): Light Theme with System-Aware Toggle
Completed slices:
- S01: Theme foundation and NavRail toggle
- S02: Component color audit and visual verification
Branch: milestone/M005
* chore(M007): record integration branch
* feat(web): chat mode action bar, smart CTA, project-level status bar, centered visualizer tabs
- Chat input bar: top 3 buttons (Discuss, Next, Auto) + overflow menu with all /gsd subcommands grouped by category, tooltips on hover
- Action routing: main-panel commands (next, auto, stop, pause) vs action-panel commands (discuss, status, visualize, etc.)
- Removed Config, Hooks, Migrate, Inspect from action menu
- Smart placeholder CTA: derives contextual button from workspace state (New Milestone, Start Auto, Resume, Plan, etc.)
- Status bar: project-level totals (duration, tokens, cost) from visualizer API instead of session-scoped auto data
- Visualizer: centered tab bar
* docs(M008): context, requirements, and roadmap
* chore(M008): record integration branch
* chore(M008/S01): auto-commit after research-slice
* docs(S01): add slice plan
* chore(M008/S01/T01): auto-commit after execute-task
* chore(M008/S01/T02): auto-commit after execute-task
* chore(M008/S01): auto-commit after complete-slice
* chore(M008/S01): auto-commit after reassess-roadmap
* chore(M008/S02): auto-commit after research-slice
* docs(S02): add slice plan
* chore(M008/S02/T01): auto-commit after execute-task
* chore(M008/S02/T02): auto-commit after execute-task
* chore(M008/S02): auto-commit after complete-slice
* chore(M008/S02): auto-commit after reassess-roadmap
* chore(M008/S03): auto-commit after research-slice
* docs(S03): add slice plan
* chore(M008/S03/T01): auto-commit after execute-task
* chore(M008/S03/T02): auto-commit after execute-task
* chore(M008/S03/T03): auto-commit after execute-task
* chore(M008/S03): auto-commit after complete-slice
* chore(M008/S03): auto-commit after reassess-roadmap
* chore(M008/S04): auto-commit after research-slice
* docs(S04): add slice plan
* chore(M008/S04/T01): auto-commit after execute-task
* chore(M008/S04/T02): auto-commit after execute-task
* chore(M008/S04): auto-commit after complete-slice
* chore(M008/S04): auto-commit after reassess-roadmap
* chore(M008/S05): auto-commit after research-slice
* docs(S05): add slice plan
* chore(M008/S05/T01): auto-commit after execute-task
* chore(M008/S05/T02): auto-commit after execute-task
* chore(M008/S05): auto-commit after complete-slice
* chore(M008): auto-commit after complete-milestone
* feat(M008): Web Polish
Completed slices:
- S01: Projects Page Redesign
- S02: Browser Update UI
- S03: Theme Defaults & Light Mode Color Audit
- S04: Remote Questions Settings
- S05: Progress Bar Dynamics & Terminal Text Size
Branch: milestone/M008
* docs: project plan — 3 milestones (M009 editor, M010 upstream sync, M011 CI/CD+PWA)
* chore(M009): record integration branch
* chore(M009/S01): auto-commit after research-slice
* docs(S01): add slice plan
* chore(M009/S01/T01): auto-commit after execute-task
* chore(M009/S01/T02): auto-commit after execute-task
* chore(M009/S01): auto-commit after complete-slice
* chore(M009/S01): auto-commit after reassess-roadmap
* chore(M009/S02): auto-commit after research-slice
* docs(S02): add slice plan
* state: S02 executing, next T01
* chore(M009/S02/T01): auto-commit after execute-task
* chore(M009/S02/T02): auto-commit after execute-task
* chore: untrack .gsd/ runtime files from git index
* chore(M009/S04): auto-commit after plan-slice
* docs(S04): add slice plan
* feat(S04/T01): Added dual shiki theme loading (dark + light) driven by…
- web/components/gsd/file-content-viewer.tsx
* chore(M010): record integration branch
* chore(M011): record integration branch
* feat(S02/T01): Added dist/web/standalone/{server.js, public/manifest.js…
- scripts/validate-pack.js
* test(S02/T02): Created .github/workflows/web.yml with full web host CI…
- .github/workflows/web.yml
* fix gitignore
* chore: update .gitignore to match upstream, untrack ignored files
- Updated .gitignore to match upstream/main patterns
- Removed 498 tracked files now covered by .gitignore:
- .gsd/ project state (milestones, plans, summaries, db files)
- Stale lock files (bun.lock, root pnpm-lock.yaml, web/pnpm-lock.yaml)
- Preserved upstream-tracked files:
- pkg/dist/core/export-html/ (negation rules)
- packages/*/pnpm-lock.yaml (tracked upstream)
* feat(M011): PWA support — service worker, install prompt, CI workflow
Squash-merge of milestone/M011 branch.
- Serwist service worker integration with Next.js (sw.ts, sw-register.tsx)
- PWA manifest with standalone display mode and app icons
- Install prompt hook and dismissible banner component
- Web host CI workflow (.github/workflows/web.yml)
- Updated web/.gitignore for Serwist build artifacts
- validate-pack.js script addition
* refine .gitignore: track GSD project artifacts, ignore runtime state
* gitignore: restore full .gsd/ exclusion
* docs(M012): context, requirements, and roadmap
* feat(S01/T01): Squash-merged 443 upstream commits (v2.22→v2.31) into fo…
- .gitignore
- src/cli.ts
- src/resource-loader.ts
- src/resources/extensions/get-secrets-from-user.ts
- src/resources/extensions/gsd/workspace-index.ts
- package-lock.json
* chore: squash merge upstream/main (v2.22→v2.31)
Merges 443 upstream commits from v2.22 to v2.31.0. Resolves 12 conflict files. Preserves fork web-mode additions. Switches web build to webpack mode for NodeNext .js extension import compatibility.
* feat(S02/T01): Added a lowercase "beta" pill badge next to the GSD logo…
- web/components/gsd/app-shell.tsx
* feat(S03/T01): Branch FileContentViewer editable mode: non-markdown fil…
- web/components/gsd/file-content-viewer.tsx
* chore(S04/T01): Added image input pipeline for chat mode: drag-and-drop…
- web/lib/image-utils.ts
- web/components/gsd/chat-mode.tsx
- web/lib/pty-chat-parser.ts
- web/lib/gsd-workspace-store.tsx
* feat(S04/T02): Created /api/terminal/upload endpoint and wired drag-dro…
- web/app/api/terminal/upload/route.ts
- web/components/gsd/shell-terminal.tsx
* chore(S05/T01): Replaced left ShellTerminal with bridge-event Terminal…
- web/components/gsd/dual-terminal.tsx
* feat(S06/T01): Created GuidedDialog component wrapping ChatPane in a fu…
- web/components/gsd/guided-dialog.tsx
- web/components/gsd/project-welcome.tsx
* feat(S06/T02): Wired GuidedDialog into Dashboard with nullable state, o…
- web/components/gsd/dashboard.tsx
* merge upstream/main: sync with v2.31.2, resolve conflicts preserving fork web UI changes
- Version bumps: 2.31.0 → 2.31.2 across all packages
- Upstream refactors adopted: createGitService factory, dispatchUnit helper,
STATE_REBUILD_MIN_INTERVAL_MS constant extraction, KNOWN_UNIT_TYPES centralization
- New upstream features merged: environment health checks, progress score,
doctor providers, health widget, auto-reentrancy guard
- Fork-specific code preserved: web CLI branch, TTY check with --web hint,
workspace index risk/depends/demo fields, dist-redirect web/ extensionless imports
- checkExistingEnvKeys moved inline (upstream deleted env-key-utils.ts)
- Fixed 5 pre-existing test failures: edit-mode slash command parity,
gsd:web script assertion, dual-terminal store contract (moved to terminal.tsx)
* ci: consolidate web workflow into main CI pipeline
Moved web host install and build steps into the CI build job.
Removed the separate web.yml workflow.
* fix(tests): configure onboarding service in bridge/live tests for CI
Tests calling sendBridgeInput via the command route now configure
the onboarding service with in-memory auth storage. Without this,
collectOnboardingState() returns locked (no API key in CI env),
causing all command route calls to return HTTP 423.
* fix: CI and Windows portability for web mode tests
- cli.ts: early TTY check now skips when --web flag is set, allowing
headless web mode launches in CI (fixes 5 runtime harness failures)
- auto-dashboard-service.ts: convert --import path to file:// URL via
pathToFileURL() (fixes ERR_UNSUPPORTED_ESM_URL_SCHEME on Windows)
- web-mode-cli.test.ts: use resolve() for registry key lookups so
Windows-normalized paths match (fixes registerInstance/unregisterInstance)
- web-mode-assembled.test.ts: configure onboarding service with
in-memory auth for settings and slash-command tests (fixes 423 in CI)
* fix: Windows portability for all web service subprocess launchers
All 17 `--import` arguments across web service files now use
pathToFileURL().href instead of raw file paths. Node's --import
flag requires URL scheme on Windows (D:\ paths fail with
ERR_UNSUPPORTED_ESM_URL_SCHEME).
Affected services: auto-dashboard, recovery-diagnostics, hooks,
export, cleanup, forensics, history, settings, doctor, skill-health,
undo, visualizer, bridge, captures, cli-entry.
Also fixes:
- web-session-parity-contract: normalize git rev-parse output with
resolve() for Windows backslash consistency
* fix: repair web recovery diagnostics CI failures
* test: align launched-host integration flows with current web UI
* fix(ci): stabilize packaged web onboarding flow
* feat(web): render main-session native TUI in power user mode
* Update web terminal parity and eslint setup
* Fix web lint and typecheck issues
* Normalize Power User terminal headers
* Restore Geist web font loading
* fix(web): update PWA app name and icon assets
* Remove web PWA functionality
* fix(web): scope terminal surfaces to active project
* feat(web): add project creation flow
* refactor(web): centralize workflow actions and simplify dashboard
* test(web): align packaged runtime integration flows
* fix: route dashboard/sidebar CTA commands through session API and handle RPC lock conflicts
Two bugs prevented the dashboard and sidebar workflow action buttons
(New Milestone, Start Auto, Initialize Project, etc.) from working:
1. Frontend: executeWorkflowActionInPowerMode sent commands via raw
fetch to /api/bridge-terminal/input (PTY keystroke injection) instead
of the session command pipeline (/api/session/command). The agent
never received these commands. Refactored to accept a dispatch
callback that callers wire through sendCommand(buildPromptCommand()).
2. Backend: guardRemoteSession in the /gsd extension called
showNextAction() — an interactive TUI prompt — when it detected
another session's lock. In RPC/web bridge mode this blocks forever
since there is no terminal to answer the prompt. Now detects
GSD_WEB_BRIDGE_TUI=1 and emits an actionable warning notification
instead of blocking.
Files changed:
- web/lib/workflow-action-execution.ts (dispatch callback instead of raw fetch)
- web/components/gsd/dashboard.tsx (pass store-backed dispatch)
- web/components/gsd/sidebar.tsx (MilestoneExplorer + CollapsedMilestoneSidebar)
- src/resources/extensions/gsd/commands.ts (RPC-mode guard in guardRemoteSession)
* fix: terminal drag-drop image upload, Shift+Enter newline, and chat mode unified response bubble
Bug 1 - Power Mode drag-drop: Dropping images on either terminal pane
opened the file in a new tab instead of uploading. Fixed by switching
all drag/drop handlers to native DOM capture-phase listeners (React
synthetic events don't reliably fire through xterm's internal DOM).
Both panes now upload images via /api/terminal/upload and inject
@filepath into the terminal input. DualTerminal wrapper prevents
browser default file-navigation as a safety net.
Bug 2 - Chat Mode dual response: During streaming, the assistant
response and thinking indicator rendered as two separate UI blocks.
Fixed by moving thinking content inline into the assistant ChatBubble
via a new InlineThinking component. Removed the standalone
ThinkingIndicator. Thinking text now appears as a collapsible section
above the response text within the same bubble.
Bug 3 - Shift+Enter newline: xterm.js sends \r for both Enter and
Shift+Enter, but pi's TUI editor expects \n (LF) for newline
insertion. Added native DOM capture-phase keydown listeners on both
MainSessionTerminal and ShellTerminal that intercept Shift+Enter,
preventDefault to block xterm, and send \n through the input channel.
* chore: update lockfile and tsbuildinfo
* refactor: remove right-side action panel, route all commands through main bridge
- Remove ActionPanel, StructuredTerminalActionPane, and all PTY screen-scraping
infrastructure (~700 lines deleted: stripTerminalChrome, isScreenChromeLine,
normalizeScreenLine, beautifyParsedScreenContent, parseStructuredTerminalScreen,
SCREEN_* constants, hidden xterm.js terminal buffer)
- All /gsd subcommands now dispatch through the main bridge session via
sendCommand(buildPromptCommand()). No separate PTY instances.
- Add disabledDuringAuto flag to GSDActionDef. Commands that inject competing
LLM prompts are disabled while auto-mode runs:
- discuss: calls dispatchWorkflow -> pi.sendMessage (would conflict with auto)
- triage: injects triage prompt via pi.sendMessage (same conflict)
- All other commands verified safe: stop/pause control auto, steer explicitly
handles auto with HARD STEER message, capture/knowledge/skip are file IO,
status/queue/history/visualize are read-only, mode/prefs/doctor/export/
cleanup/remote are config/maintenance
- Add inline PendingUiRequest rendering in ChatPane: select (single + multi),
confirm, input, and editor requests appear as interactive chat bubbles in the
message flow with native clickable controls and post-submission confirmation
- Wire FocusedPanel in app-shell.tsx as fallback overlay for pendingUiRequests
in non-chat views (dashboard, power mode, files, etc.)
- Remove unused imports: AnimatePresence, motion, buildProjectAbsoluteUrl,
buildProjectPath, HeadlessTerminal type, compact prop
* chore: gitignore tsbuildinfo files
* onboarding overhaul: add mode, project, and remote steps; refactor existing steps
- Add step-mode.tsx for user/dev mode selection
- Add step-project.tsx for project selection/creation
- Add step-remote.tsx for remote repository configuration
- Add use-user-mode.ts hook for mode state management
- Add /api/dev-mode route for dev mode toggle
- Refactor onboarding-gate.tsx flow and step sequencing
- Refactor step-authenticate, step-dev-root, step-optional,
step-provider, step-ready, step-welcome with updated styling
- Update command-surface, app-shell, dashboard integrations
- Update dev-overrides and workflow-action-execution
* overhaul projects view, simplify boot readiness, add requireProjectCwd
- Redesign projects-view with Sheet/Dialog components and improved styling
- Simplify waitForBootReady: remove bridge phase tracking, return on first successful response
- Boot route returns minimal no-project payload when no project is configured
- Rename resolveProjectCwd → requireProjectCwd across all API routes
- Minor UI adjustments in app-shell, sidebar, terminal
* fix: update tests for upstream merge and UI refactor
Unit tests (7 fixes, 2133/2133 pass):
- smart-entry-complete: match upstream's chooser-based complete flow
- web-bridge-contract: add projectDetection to boot snapshot keys
- web-command-parity: await async registerExtension (upstream decomposition)
- web-mode-cli: update gsd:web script expectation (copy-resources added)
- web-state-surfaces: match refactored editorTextBuffer consumption
- web-workflow-action-execution: match new dispatch-based API, stub localStorage
- web-mode.ts: restore GSD_WEB_PROJECT_CWD in spawn env
Integration tests:
- web-mode-onboarding: simplify to API-only contract (locked→reject→retry→unlocked)
without fragile browser UI assertions that depend on refactored wizard flow
* Clean up dashboard header and redesign project selection gate
- Simplify dashboard header: inline scope badge with title, remove
workflow action buttons and status indicators
- Redesign project selection gate: center logo with subtitle, remove
header bar and side gutters, cleaner layout
- Remove web-mode-runtime integration test
* settings: consolidate tabs, add General panel with font size controls
- Add General tab (terminal font size + code font size) as default settings landing
- Merge Thinking into Model tab (model selection + thinking level in one panel)
- Merge Queue + Compaction + Retry into Session tab (all session behavior knobs)
- Reduce settings nav from 8 tabs to 6 (+ admin when dev mode)
- Legacy section routes (thinking, queue, compaction, retry) still render correctly
- gsd-prefs mega-scroll uses GeneralPanel instead of separate Terminal/Editor panels
* fix: file explorer & visualizer use selected project context, resizable tree panel
- Route all fetch calls in files-view, visualizer-view, and status-bar
through buildProjectUrl() so they respect the active project selection
instead of falling back to GSD_WEB_PROJECT_CWD (server startup project)
- Make file explorer tree panel resizable (180-480px) with drag handle,
matching the milestone sidebar resize pattern
* feat(web): file explorer Agent tab, merged headers, unified chat timeline
- Merge file path display + save button into single header row (3 layers → 2)
- Add Agent tab to file explorer left panel with embedded ChatPane
- Auto-open files in viewer when agent executes edit/write tools
- Show inline diff (red/green lines) for agent-edited files with auto-dismiss
- MD files default to Edit tab when agent-opened so raw changes are visible
- Unified chat timeline: tool executions render inline where they happen,
not stacked at the bottom
- Persist user messages in workspace store so they survive tab switches
- Shorten chat input placeholder to 'Message…', remove hint text
* feat(chat): persist thinking blocks and render in chronological order
- Add TurnSegment type to track thinking/text/tool events in order
- Finalize streaming content into segments at phase transitions
(thinking→text, text→thinking, tool start/end, turn boundary)
- Store completedTurnSegments parallel to liveTranscript for history
- Rebuild chat timeline from segments so thinking blocks render
in their correct position between text and tool calls
- Thinking blocks now persist after streaming ends (collapsible)
- Restyle InlineThinking to monochrome (muted-foreground) — removes
amber/warning colors for consistency with dark theme
* feat(web): add Integrations tab to settings panel for remote channel config
* feat(web): bot token input in settings and onboarding, card-based integrations panel
- Add PATCH endpoint to /api/remote-questions for saving bot tokens
to ~/.gsd/agent/auth.json (same storage as TUI key manager)
- Redesign RemoteQuestionsPanel: card-based channel picker, inline
token input with show/hide toggle, collapsible advanced settings,
connected state banner with disconnect
- Add bot token input to onboarding StepRemote with same PATCH flow
- Remove 'configure via TUI or environment' messaging — web UI now
handles the full setup end-to-end
* fix(web): address PR #1717 security review feedback
Security (blocking):
- Add bearer token auth to all API routes via Next.js middleware
- Generate random token at launch, pass to browser via URL fragment
- Add Origin/CORS validation rejecting cross-origin API requests
- Whitelist PTY commands (gsd, user shell, /bin/bash, /bin/zsh, /bin/sh)
- Restrict /api/browse-directories to devRoot scope
Cleanup:
- Move shiki, react-markdown, remark-gfm from root to web/package.json
- Remove as-any casts in input-controller.ts (extend host type properly)
- Add extensions_ready signal to RPC mode (fixes void bindExtensions race)
- Add test fixture dummy keys to .secretscanignore (fixes CI lint)
* fix(web): resolve Next.js 16 build warnings
- Rename middleware.ts → proxy.ts with proxy() export (Next.js 16 convention)
- Add @gsd/native to webpack externals (fixes package path resolution warning)
- Hide require fallback from webpack static analysis in pty-manager (fixes
critical dependency warning)
* fix(web): pass auth token to boot readiness probe
The readiness probe hits /api/boot to check server startup, but the
proxy now requires a bearer token. Thread the authToken through
waitForBootReady → requestLocalJson so the probe authenticates.
* chore: sync lockfiles after moving deps to web/package.json
* fix(test): update web-mode-cli test for auth token in browser URL
The test asserted the exact opened URL, which now includes a random
auth token fragment. Updated to pattern-match the token and verify
GSD_WEB_AUTH_TOKEN is passed consistently in the spawn env.
* fix(test): pass auth token in web-mode-onboarding integration test
The runtime harness now extracts the auth token from the browser-open
stub log and exposes it on RuntimeLaunchResult.authToken. Added
runtimeAuthHeaders() helper. Updated the onboarding test to pass
Authorization headers on all fetch calls and waitForHttpOk.
* fix(test): match renamed nextMilestoneIdReserved in smart-entry-complete test
Upstream #1569 renamed nextMilestoneId → nextMilestoneIdReserved.
Updated the regex assertion to accept both names.
* feat(web): support GSD_WEB_ALLOWED_ORIGINS for secure tunnel setups
Adds a comma-separated GSD_WEB_ALLOWED_ORIGINS env var that merges
additional origins into the CORS allowlist. Defaults to localhost-only
when unset. Enables Tailscale Serve, Cloudflare Tunnel, ngrok, etc.
createRequire() in shared/ui.ts uses CJS resolution which needs a
"require" condition in package.json exports. Without it, Node throws
ERR_PACKAGE_PATH_NOT_EXPORTED.
Verified locally: build, typecheck:extensions, test:unit (0 fail),
test:integration (0 fail), validate-pack all pass.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Slices with declared depends:[S01] now get "dependency slice" message
instead of "earlier slice" from the dispatch guard (PR #1770).
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
ESM modules don't have require(). Use createRequire(import.meta.url)
which works in both jiti-loaded and native ESM contexts.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
integration_branch_missing is now auto-fixable (fallback to main branch
detection) with warning severity, not error. Test expectations updated.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The test creates a worktree path 11 levels deep, exceeding the 10-level
walk-up limit. In CI, the deep resolved path through a symlinked .gsd
fails to find the .git file and returns the raw path instead of the
project root.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The postinstall script references this file but it wasn't listed in
the package.json files array, causing npm install to fail in CI's
validate-pack step.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
- Remove duplicate `selfHealRuntimeRecords` import in auto.ts (PRs #1772 and #1773 both added it)
- Add missing `model?: string` to runPreDispatchHooks return type in loop-deps.ts (PR #1781 referenced it)
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
When verifyExpectedArtifact returns false for a unit type with a known
expected artifact, postUnitPreVerification now returns "retry" instead
of "continue". This sets pendingVerificationRetry on the session so the
next loop iteration re-dispatches with failure context, preventing
13+ blind re-dispatches of the same failed unit before the stuck-loop
detector kicks in.
Closes#1571
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
dispatchHookUnit() previously used a simplistic lookup that only matched
exact model IDs or "provider/id" against ctx.modelRegistry.getAvailable().
Non-Claude models (e.g. openrouter/openai/gpt-5.4-codex) silently fell
back to the session model with no warning.
- Replace simplistic lookup in dispatchHookUnit with resolveModelId() which
handles provider/model, bare-id, and OpenRouter org/model formats
- Add warning notification when a hook model can't be resolved instead of
silent fallback
- Wire sidecar hook model override through runUnitPhase so post-unit hook
model fields are applied after standard model selection
- Consume pre-dispatch hook model field (hookModelOverride) in IterationData
so it reaches the dispatch phase
- Export resolveModelId from auto-model-selection.ts for reuse
- Add resolveModelId to LoopDeps interface for testability
Closes#1720
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The blanket catch in auto/loop.ts treated all errors as transient and retried
up to 3 times, burning ~$20 per retry on guaranteed failures like disk-full.
Infrastructure errors (ENOSPC, ENOMEM, EROFS, EDQUOT, EMFILE, ENFILE) are now
detected before the retry logic and trigger an immediate stop with a clear
error message. Also adds a pre-dispatch disk space check to the health gate
so low-disk conditions are caught before dispatching a unit.
Closes#1694
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
resolveHookArtifactPath() built paths as .gsd/<MID>/slices/... instead
of .gsd/milestones/<MID>/slices/..., causing artifact idempotency checks,
retry_on detection, and skip_if in pre-dispatch hooks to all fail silently.
Closes#1721
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
When a milestone has only CONTEXT-DRAFT.md, the survivor branch check
sets hasSurvivorBranch=true and skips all showSmartEntry calls. Auto-mode
then dispatches needs-discussion->stop, creating an infinite loop on
every /gsd run. Add a pre-check: when hasSurvivorBranch is true AND
phase is needs-discussion, route to the interactive discussion handler.
Closes#1726
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Auto-mode launches Playwright/Chrome for browser-based verification but
never closes browsers between units or during stopAuto teardown. Over
retries and re-dispatches, Chrome processes accumulate and spike RAM.
Add closeBrowser() calls in two locations:
- stopAuto() finally block: ensures browser cleanup on any exit path
- postUnitPreVerification(): tears down browser between unit completions
Both use a getBrowser() guard to skip the import when no browser is active,
keeping the lazy-load pattern intact.
Closes#1733
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
After milestone transitions in auto-mode, STATE.md remained stale because
rebuildState() was never called. Additionally, completed-units.json retained
entries from the previous milestone, causing dispatch to skip units in the
new milestone context. This adds rebuildState() to the milestone transition
block (bypassing the 30-second throttle) and resets completed-units tracking
when the active milestone changes.
Closes#1576
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
handleAgentEnd, pauseAuto, and supervision timer catch blocks could
leave the unitPromise unresolved, causing autoLoop to hang permanently
on `await unitPromise`. Add resolveAgentEndCancelled() and call it on
every exit path that previously skipped resolution.
Closes#1666
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
pauseAuto now calls closeoutUnit() and clearUnitRuntimeRecord() for the
current unit before setting s.active = false, preventing stale
"dispatched" runtime records from accumulating on disk.
The resume path in startAuto now calls selfHealRuntimeRecords() before
entering autoLoop to clean any stale records that survived from prior
sessions (e.g. if clearUnitRuntimeRecord failed silently during pause).
Closes#1625
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
