Keep Active Agents workspace builds versioned above main#334
Merged
Conversation
added 2 commits
April 22, 2026 17:30
The Active Agents companion still had a merge-scarred provider duplicate, a full clean-worktree mtime walk, and extension-local stop/diff implementations that drifted from gx. This change bounds and caches clean-worktree activity probes, adds a narrow gx agents stop --pid route, switches diff opening to VS Code's Git change UI, and points the regressions at the live vscode source so the shipped surface stays covered. Constraint: Active Agents refreshes inside the VS Code extension host, so clean-worktree scans and diff/stop actions must stay cheap and non-blocking Rejected: Keep raw process.kill and git diff dumps in the extension | would keep drifting from gx and block on large diffs Confidence: high Scope-risk: moderate Directive: Keep vscode/guardex-active-agents/* and templates/vscode/guardex-active-agents/* in sync; install fallback still depends on parity even though tests now target the live vscode copy Tested: node --test test/vscode-active-agents-session-state.test.js test/agents.test.js Not-tested: Manual VS Code UI smoke in a real extension host
The new Active Agents parity guard exposed a release-contract hole: the extension bundle changed, but both live and template manifests still reported 0.0.3 while main already shipped 0.0.4. Bumping both copies to 0.0.5 keeps the auto-install/update flow aligned with the real bundle. Constraint: Active Agents extension edits must version above the base branch Rejected: Leave the manifest at 0.0.3 | test/vscode-active-agents-session-state.test.js rejects changed extension files without a higher version Confidence: high Scope-risk: narrow Directive: Bump both live and template Active Agents manifests whenever the extension bundle changes Tested: node --test test/metadata.test.js Tested: node --test test/agents.test.js Tested: node --test --test-force-exit test/vscode-active-agents-session-state.test.js Not-tested: Combined multi-file node --test run without --test-force-exit still leaves lingering mock-handle processes in this environment
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automated by gx branch finish (PR flow).