Two changes:
1. pruneActivityLogs: when retentionDays is 0, skip mtime comparison and
unconditionally remove all files except highest-seq. On Windows, NTFS
timestamp resolution meant freshly-created files could have mtime >=
Date.now() at cutoff calculation, so none were pruned.
2. CI: remove the push-to-main gate on windows-portability so it runs on
PRs too — catches Windows failures before merge instead of after.
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
macOS x64 builds on ARM64 runners also need the target added explicitly.
Use rustup target add for all matrix entries to avoid Blacksmith's
target rewriting in dtolnay/rust-toolchain.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Blacksmith migration (#2414) incorrectly rewrote the Rust target triple
aarch64-unknown-linux-gnu to the runner label blacksmith-4vcpu-ubuntu-2404-arm.
Restore the correct Rust target and split cross-compilation target addition
into an explicit rustup command.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
dtolnay/rust-toolchain resolves Blacksmith runner hostnames as Rust
targets on ARM64 runners. Split target addition into explicit rustup
command for cross-compilation builds.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Adds scripts/base64-scan.sh and a corresponding CI step to detect
prompt injection payloads that are base64-encoded to evade the existing
docs-prompt-injection-scan.sh check.
* chore(contrib): add commit-msg hook, CODEOWNERS, team workflow docs
- Extend install-hooks.sh with commit-msg hook that enforces
Conventional Commits format on every commit
- Add .github/CODEOWNERS mapping packages, CI, scripts, and
security-sensitive files to @gsd-build/maintainers
- CONTRIBUTING.md: add Branching and commits section with naming
convention, commit format, and rebase guidance
- CONTRIBUTING.md: add Working with GSD section covering mode: team,
unique milestone IDs, and worktree isolation for multi-dev workflows
- CONTRIBUTING.md: surface npm run secret-scan:install-hook in Local
development with explanation of both hooks it installs
- CONTRIBUTING.md: align AI disclosure section — no AI tool authorship
in commits, Draft PR requirement for multi-phase agent work
* chore: remove install-hooks.sh — local git hook installation is too intrusive for a contributor PR
A hung unit test on PR #2120 ran for 3+ hours before manual cancellation,
burning ~185 minutes of Actions quota. Add timeouts to cap runaway jobs:
detect-changes (2m), docs-check/lint (5m), build/windows (15m).
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Update pr-risk.yml and ai-triage.yml to match the versions used by all
other CI workflows:
- actions/checkout@v4 → @v6
- actions/setup-node@v4 → @v6
- node-version: '20' → '24'
Also fix unquoted $GITHUB_OUTPUT references in pr-risk.yml shell blocks
to prevent word-splitting issues.
* 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.
CI workflow:
- Replace fetch-depth: 0 with shallow clones (depth 1-2) in lint and
build jobs — saves ~30-60s per job
- Remove fetch-depth: 0 from build and windows-portability (default
depth 1 is sufficient for build/test)
Pipeline workflow:
- Add cache: 'npm' to dev-publish, test-verify, and prod-release
setup-node steps — saves ~1-2 min per job on npm ci
- Move ${{ }} expressions from run: blocks to env: variables in
prod-release and update-builder to prevent command injection vectors
- Use fetch-depth: 2 in update-builder (only needs parent diff)
Build-native workflow:
- Replace hardcoded sleep 30 + single verification with exponential
backoff polling (5s → 10s → 20s → 30s cap, max 5 attempts)
- Replace fixed 15s retry intervals in post-publish smoke test with
exponential backoff (5s → 10s → 20s → 30s cap, 8 attempts)
- Replace fixed 15s dist-tag verification loop with exponential
backoff (6 attempts vs 10 × 15s)
Estimated savings: ~5-10 min per full CI+pipeline run, ~1-3 min per
native build publish.
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-authored-by: TÂCHES <afromanguy@me.com>
Docs-only PRs (only .md files and docs/ changes) now skip the expensive
build, typecheck, and test jobs while still running lint and a new
docs-check job. The docs-check job runs a prompt injection scanner that
detects hidden directives, role overrides, system prompt markers, tool
call injection, and invisible Unicode in markdown prose (excluding
fenced code blocks and inline code spans).
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
- Remove feat/** push trigger (PRs already cover feature branches)
- Add concurrency groups with cancel-in-progress to kill stale runs
- Add paths-ignore for docs/markdown/license/unrelated workflow changes
- Consolidate secret-scan, no-gsd-dir, skill-references into single lint job
- Restrict Windows runner (2x minute multiplier) to main push only
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* fix(gsd): enforce backtick file paths in task plan IO sections
The reactive task graph (ADR-004) derives dependencies from backtick-wrapped
file paths in ## Inputs and ## Expected Output sections. Without concrete
paths, the graph is ambiguous and falls back to sequential execution.
Changes:
- task-plan.md template: add comments explaining paths are machine-parsed
- plan-slice.md prompt: explicitly instruct planner to write backtick file
paths in IO sections, add self-audit check for path presence
- observability-validator.ts: new validation rules missing_output_file_paths
(warning) and missing_input_file_paths (info) catch plans without paths
- plan-quality-validator.test.ts: 4 new test cases for IO path validation
* fix(ci): increase max_tokens and add JSON parse error handling in ai-triage
max_tokens: 300 was too low, causing truncated JSON responses from Claude
that failed to parse. Bumped to 1024 and added try/catch with raw text
logging for easier debugging.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
pull_request events from forks/branches cannot access repo secrets,
causing 401 auth failures on every PR triage. pull_request_target runs
in the base repo context. Safe because the workflow only reads event
payload data and sparse-checks base branch docs — no PR code executes.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Remove the bundled SwiftUI skill which had 13+ broken references to a
non-existent `../macos-apps/references/` directory. Add a CI script
that validates all relative .md file references in bundled skills,
preventing this class of bug from shipping again. Fix 5 additional
pre-existing broken references in other skills.
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Adds a GitHub Actions workflow that automatically triages new issues and
PRs using Claude Haiku 4.5. Classifies with type and priority labels,
and flags items that violate VISION.md or CONTRIBUTING.md guidelines
with a `needs-review` label and explanatory comment. No auto-closing —
maintainer makes all final decisions.
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Establishes contributor guidelines based on maintainer team discussion.
VISION.md defines project identity, principles, and explicit rejection
criteria. CONTRIBUTING.md covers assign-then-PR workflow, RFC process
for architectural changes, AI disclosure policy, and testing standards.
PR template restructured around TL;DR + What/Why/How format.
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
10 tests that run against the installed gsd binary after npm publish:
1. headless query returns valid JSON
2. Empty project → pre-planning phase
3. Milestone with roadmap → planning phase
4. All tasks done → summarizing phase
5. Complete milestone → complete phase
6. Stale auto.lock doesn't block --version
7. Crash recovery query works with stale lock
8. Non-TTY exits quickly with clean error
9. Version skew detected before TTY check
10. --help works (native addon loads or falls back)
Wired into pipeline.yml test-verify job after fixture tests
and before @next promotion.
These catch the state machine / infrastructure bugs from #1308
that unit tests can't reach — they exercise deriveState through
the real gsd binary with real .gsd/ directory structures.
Part of #1308
Two issues in the pipeline:
1. cancel-in-progress: true could cancel a running deployment when a
new push arrives. Deployments should never be interrupted mid-flight.
Changed back to false.
2. The prod-release job bumps the version, commits, and tags — but never
publishes the release version to npm. The dev-publish step publishes
@dev, test-verify promotes to @next, but @latest was never updated.
Users running 'npm install -g gsd-pi' would get stale versions.
Added 'Build release' and 'Publish release to npm @latest' steps after
the git tag push, with idempotent guard for already-published versions.
When the prod environment gate is approved, the pipeline now automatically
determines the semver bump from conventional commits, generates a changelog
entry, bumps all package versions, commits + tags + pushes (triggering
build-native.yml for npm @latest), creates a GitHub Release, and posts
to Discord.
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Dev-stamped versions (2.28.0-dev.xxx) should never be promoted to
@latest on npm. Stable releases are handled by the publish-version
workflow. The pipeline promotes @dev → @next only.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Multiple pipeline runs for the same base version produce identical
release tags, causing E422. Check if release exists before creating.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Multiple CI completions on the same commit trigger duplicate Pipeline
runs. The second run fails with E403 because the version was already
published. Fix by checking npm registry before attempting publish, and
enable cancel-in-progress to avoid redundant runs.
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The local smoke test runs npx gsd-pi which fails in the container
because the gsd bin isn't on PATH. Point GSD_SMOKE_BINARY at the
built dist/loader.js directly with an absolute path so smoke tests
work from any cwd.
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* feat: add pre-commit secret scanner and CI secret detection
Add a comprehensive secret scanning system to prevent accidental
credential leaks in commits and pull requests:
- scripts/secret-scan.sh: ERE-based scanner (macOS/Linux compatible)
that detects AWS keys, API tokens, private keys, database URLs,
GitHub/GitLab/Slack/Stripe/Google/npm tokens, and hardcoded passwords
- scripts/install-hooks.sh: one-command git pre-commit hook installer
- .secretscanignore: allowlist for known false positives (test fixtures,
env var references, placeholder values)
- CI job: secret-scan step in ci.yml scans PR diffs against origin/main
- npm scripts: test:secret-scan, secret-scan, secret-scan:install-hook
- 17 tests covering detection, non-detection, binary skipping, CI mode
* fix: exclude secret-scan test file from CI scanning
The test file contains intentional fake secrets as test inputs.
Add it to .secretscanignore so CI doesn't flag them.
* fix: skip secret-scan tests on Windows (requires bash/POSIX grep)
Two bugs in the Dev Publish job:
1. node -p with escaped double-quotes broke on Node 22's eval mode
(SyntaxError: Invalid or unexpected token). Switched to node -e
with process.stdout.write and unescaped inner quotes.
2. version-stamp updated root package.json but not platform packages.
When npm publish triggered prepublishOnly, sync-platform-versions
dirtied 5 platform package.json files and git diff --exit-code
failed. Added sync-platform-versions to the stamp step so
prepublishOnly finds everything already in sync.
Fixes: https://github.com/gsd-build/gsd-2/actions/runs/23233857718
* feat(S01/T01): Scaffolded the `studio` Electron workspace with a workin…
- package.json
- studio/package.json
- studio/electron.vite.config.ts
- studio/src/main/index.ts
- studio/src/preload/index.ts
- studio/src/renderer/src/styles/index.css
- studio/src/renderer/src/App.tsx
* chore: init gsd
* fix(ci): add safe.directory for containerized pipeline job
The Dev Publish job runs inside a Docker container where the checkout
user differs from the container user (root), causing git's dubious
ownership check to reject git operations in version-stamp.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* fix(ci): remove .gsd/.gitignore from tracking
The no-gsd-dir CI check fails when .gsd/ exists as a directory, even
if only .gitignore is tracked inside it.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* feat(ci): add version stamp script for dev publishes
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* feat(ci): add CLI smoke tests for pipeline test stage
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* feat(ci): add FixtureProvider for LLM conversation recording and replay
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* feat(ci): add fixture test runner and sample recordings
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* feat(ci): add live test stubs and pipeline npm scripts
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* feat(ci): add three-stage promotion pipeline workflow
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* feat(ci): add weekly cleanup workflow for stale dev versions
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* feat(ci): add fixture recording helper stub
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Fixes#882 — npm install -g gsd-pi installing a broken version where
@gsd/pi-coding-agent cannot be resolved, causing ERR_MODULE_NOT_FOUND.
Root causes addressed:
1. On Windows without Developer Mode or admin rights, symlinkSync fails
even for NTFS junctions, leaving node_modules/@gsd/ empty and causing
a cryptic ERR_MODULE_NOT_FOUND instead of a usable error message.
2. If npm latest dist-tag is stale (pointing to an old version that
predates the packages/ directory), users get the same failure.
Changes:
- src/loader.ts: after symlinking, validate @gsd/pi-coding-agent exists;
emit a clear actionable error with reinstall instructions instead of
letting Node throw ERR_MODULE_NOT_FOUND deep inside cli.js. Also adds
cpSync fallback when symlinkSync fails (Windows without elevated perms).
- scripts/link-workspace-packages.cjs: same cpSync fallback — ensures
postinstall succeeds on restricted Windows environments.
- scripts/validate-pack.js: verify @gsd/* packages are resolvable after
the isolated install test, and run `gsd -v` to confirm end-to-end
resolution before declaring the pack valid.
- .github/workflows/build-native.yml: add post-publish dist-tag
verification step that confirms npm dist-tags.latest matches the
published version for stable releases, catching stale-tag regressions
in CI before users encounter them.
* chore: add PR template and bug report issue template
Standardize PR descriptions and bug reports with structured templates
to improve consistency across contributors.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* chore: simplify PR template — replace milestone/slice with target branch
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* chore: rename section to 'Release context'
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
* ci: add extension type-checking to CI pipeline and prepublishOnly
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* fix: resolve remaining extension type errors after merge
- Use cred.type === "api_key" for proper union narrowing in loadToolApiKeys
- Fix optional level parameter in provider-error-pause test
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Detect prerelease versions (containing -next.) and publish npm packages
with --tag next instead of --tag latest, keeping stable users unaffected.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The --version flag outputs a banner with ANSI escape codes. The smoke
test compared the entire multi-line output against the bare version
string, causing false failures on every release.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* fix: remove @gsd/* cross-deps that break npm install (#hotfix)
Workspace packages declared @gsd/* as dependencies in their own
package.json files. npm's bundleDependencies bundles packages into
node_modules/ but still tries to resolve sub-dependencies from the
registry — causing 404s for the unpublished @gsd/* scope.
- Remove @gsd/* from all dependencies (root and workspace packages)
- Add validate-pack.sh: tests tarball installability before publish
- Wire validate-pack into CI (every PR) and publish pipeline
- Bump to v2.10.10
- Update changelog
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* fix: drop bundleDependencies, use postinstall symlinks instead
bundleDependencies with workspace packages causes npm to resolve
@gsd/* from the registry during install — 404 since they're not
published. Replace with a postinstall script that creates
node_modules/@gsd/* symlinks pointing to packages/*.
- Remove @gsd/* from dependencies and bundleDependencies
- Add link-workspace-packages.cjs (CJS, runs before ESM postinstall)
- Update validate-pack to verify symlinks after install
- Include link script in files array
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* fix: robust validate-pack + fallback workspace linking
- Keep @gsd/* in bundleDependencies (for npm pack bundling)
- Remove @gsd/* from root dependencies (prevents 404 registry lookups)
- Add link-workspace-packages.cjs fallback for when bundled symlinks
aren't created
- Simplified validate-pack with better error diagnostics
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* fix: remove bundleDependencies — use postinstall symlinks only
npm 10.x fetches packument metadata for ALL deps including bundled ones.
@gsd/* packages don't exist on npm → 404 → hard install failure.
bundleDependencies is fundamentally broken for unpublished workspace
packages. Replace with:
- packages/ shipped via files array (already was)
- link-workspace-packages.cjs creates node_modules/@gsd/* symlinks in
postinstall, pointing to packages/*
- No @gsd/* in dependencies or bundleDependencies at all
Tarball drops from 40M to 3M (no bundled node_modules).
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* fix: add .npmignore to prevent .gitignore from excluding dist/
.gitignore contains /dist/ and packages/*/dist/ which are needed in
the published tarball. Without .npmignore, npm pack respects .gitignore
and excludes them — even though "files" in package.json should override.
An empty .npmignore causes npm to ignore .gitignore entirely, letting
the "files" field control what's packed.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* fix: avoid SIGPIPE in validate-pack on Linux
tar | grep -q causes SIGPIPE (exit 141) on Linux when grep closes the
pipe early. Write tar listing to a temp file and grep that instead.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* docs: update changelog for v2.10.9
* 2.10.9
* fix(ci): retry smoke test with backoff for npm propagation delay
The post-publish smoke test was failing because npm registry propagation
can take 30-90s. Replaced the fixed 15s sleep with a retry loop (5
attempts, 30s backoff).
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* fix: suppress git credential prompts that freeze TUI (#280)
Set GIT_TERMINAL_PROMPT=0 and GIT_ASKPASS="" on all git subprocess calls
so git fails immediately instead of prompting for credentials when tokens
expire, which deadlocks the TUI's stdin.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* ci: add CI workflow and fix publish to prevent broken releases
Add ci.yml that runs build + test + smoke test on every push/PR to main.
Fix build-native.yml publish job to explicitly build before publishing,
verify dist/loader.js exists, check tarball contents, and smoke test the
published package.
Closes#293
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* feat: add GitHub Workflows skill with CI workflow and ci_monitor tool
- Runs on push to main and feature branches
- Runs on pull requests to main
- Build + test pipeline using Node 22
Cross-platform CI monitoring tool for debugging GitHub Actions:
- `runs` - List recent workflow runs
- `watch` - Monitor running workflow
- `fail-fast` - Exit 1 on first failure (for scripts)
- `log-failed` - Show failed job logs
- `test-summary` - Extract test pass/fail counts
- `check-actions` - GraphQL query for action versions
- `grep` - Search logs with context
- `wait-for` - Block until deployment keyword appears
Pure Node.js - no shell interpolation, works on macOS/Windows/Linux.
Drift-immune skill that:
- Routes all CI operations through ci_monitor.cjs
- Fetches live docs from docs.github.com (no stale training data)
- Provides validation constraints (BEFORE/AFTER/EVIDENCE)
- Split tests into test:unit (141 tests, ~12s) and test:integration (5 tests)
- Fixed idle-recovery.test.ts for current implementation
- Removed AGENTS.md dead code from resource-loader.ts
- Moved npm run build out of tests (fixes ENOBUFS)
When CI fails, you need observable diagnostics:
- `gh run` output is not script-friendly
- ci_monitor.cjs provides structured output for automation
- The skill ensures AI uses the tool, not stale training data
* fix: resolve imports and path for current upstream version
- Updated imports from @mariozechner/pi-coding-agent to @gsd/pi-coding-agent
- Fixed integration test path calculation to use process.cwd()
- Kept test:unit and test:integration scripts
* fix: replace search provider preference instead of accumulating
AuthStorage.set() for api_key credentials appends to the existing list
rather than replacing. When setSearchProviderPreference was called twice
with different values, the second call appended the new value, leaving
the first value at index 0, which get() returned.
Fix: call auth.remove() before auth.set() to ensure only the latest
preference is stored.
https://claude.ai/code/session_01Qx7HRSDb117KzDZzdKk1KB
* fix: address all 10 open PR review comments
- package.json: run build before test:integration so a fresh checkout works
- pack-install.test.ts: replace execSync+shell redirects with execFileSync
argument arrays (portable, no shell parsing, paths with spaces safe)
- ci_monitor.test.ts: remove unconditional passed++ after assert; move
success message after the failed > 0 check so it only prints on success
- setup_gh.cjs: replace unzip/tar shell-outs with platform-specific
execFileSync calls (unzip on macOS, PowerShell Expand-Archive on Windows);
add compareVersions() for correct element-by-element semver comparison
- ci_monitor.cjs: add --repo/-R global option so repo is overrideable;
fix getLogs() to use gh run view --log --job instead of binary REST endpoint
https://claude.ai/code/session_01AT6CgcAB62kWcDsTJg9HZM
* fix: make all changed files fully cross-platform (Windows/macOS/Linux)
- pack-install.test.ts: use tar npm package instead of tar CLI; resolve
gsd binary as gsd.cmd on Windows; skip shebang check on Windows
- setup_gh.cjs: use execFileSync for all binary invocations; replace
which with where on Windows; add Windows PATH guidance; filter preferred
install dirs by platform; unify ZIP extraction to use process.platform
consistently; escape single quotes in PowerShell Expand-Archive args
- ci_monitor.cjs: use path.join for .github/workflows paths; replace
all split('\n') with split(/\r?\n/) to handle Windows CRLF output
https://claude.ai/code/session_01AT6CgcAB62kWcDsTJg9HZM
* refactor: simplify and deduplicate changed files
- ci_monitor.cjs: memoize getRepo() so gh repo view subprocess runs at
most once per invocation instead of once per command call in watch loops
- pack-install.test.ts: extract packTarball() helper to eliminate
duplicate npm pack logic across two tests; remove unused contents variable
https://claude.ai/code/session_01AT6CgcAB62kWcDsTJg9HZM
* refactor: remove redundant existsSync before canWrite() in findInstallDir
canWrite() already returns false for non-existent directories, so the
pre-check was a TOCTOU-style redundancy with no behavioral value.
https://claude.ai/code/session_01AT6CgcAB62kWcDsTJg9HZM
* fix: replace tar npm package with Node built-ins (zlib + manual tar parsing)
tar is not in the dependency tree. listTarEntries() decompresses via
createGunzip() and parses the 512-byte tar block format directly,
reading name/prefix/type/size fields per POSIX ustar spec. No external
dependency required. Also fixes the broken tarball variable reference
left over from the packTarball() refactor.
https://claude.ai/code/session_01AT6CgcAB62kWcDsTJg9HZM
* remove: drop setup_gh scripts in favour of ci_monitor
setup_gh.cjs and setup_gh.py were one-shot gh CLI installers.
ci_monitor.cjs covers the day-to-day CI use case and is the tool
the skill routes through. Environments that need gh installed can
use brew/winget/distro packages directly.
https://claude.ai/code/session_01AT6CgcAB62kWcDsTJg9HZM
* fix: run only unit tests in CI — integration tests cause ENOBUFS
The integration tests (npm pack → npm install → spawn node) exceed
the buffer limits of the CI runner environment. They are documented
as requiring a manual build+run step. CI now runs test:unit only.
https://claude.ai/code/session_01AT6CgcAB62kWcDsTJg9HZM
* fix: run all tests in CI without ENOBUFS
- ci.yml: run unit and integration as separate steps; build is already
its own step so test:integration doesn't need to rebuild
- package.json: remove npm run build from test:integration script
- pack-install.test.ts: npm install uses stdio:'ignore' to avoid
piping large output through Node buffers (root cause of ENOBUFS);
add early dist/ check with clear error message instead of rebuilding
https://claude.ai/code/session_01AT6CgcAB62kWcDsTJg9HZM
* fix: resolve ENOBUFS and clean up setup_gh references
- pack-install.test.ts: derive tarball filename from package.json
instead of piping npm pack --json stdout; use stdio:ignore throughout
to avoid exhausting OS pipe buffers on CI runners
- SKILL.md: remove setup_gh install instructions; assume gh is
pre-installed via system package manager; point to ci_monitor.cjs
- github_project_setup.py: remove setup_gh.py reference from error message
https://claude.ai/code/session_01AT6CgcAB62kWcDsTJg9HZM
* fix: address Copilot review comments on pack-install.test.ts
- listTarEntries: collect chunks in array, Buffer.concat once on end
instead of O(n²) repeated concat in data handler
- listTarEntries: attach error handler to createReadStream so read
errors reject the Promise instead of crashing the process
- npm pack: use stdio:['ignore','ignore','pipe'] to preserve stderr
for diagnostics while still avoiding ENOBUFS on stdout
- npm install: same — pipe stderr so failures include error output
https://claude.ai/code/session_01AT6CgcAB62kWcDsTJg9HZM
---------
Co-authored-by: Claude <noreply@anthropic.com>
