Bump Active Agents extension version on plugin edits#327
Merged
Conversation
added 3 commits
April 22, 2026 16:48
The extension stayed at 0.0.1 across local reinstalls because nothing enforced a version bump when shipped plugin files changed. This bumps the manifests to 0.0.2 and adds a focused base-branch regression so future plugin edits fail without a higher version. Constraint: Installed VS Code folder names come from manifest.version Rejected: Derive a transient install-time version | hides stale source metadata and lets live/template manifests drift Confidence: high Scope-risk: narrow Directive: Bump both live and template Active Agents manifests whenever shipped plugin files change Tested: node --test test/vscode-active-agents-session-state.test.js Tested: openspec validate agent-codex-vscode-extension-version-bump-guard-2026-04-22-16-18 --type change --strict Tested: openspec validate --specs Tested: node scripts/install-vscode-active-agents-extension.js Not-tested: PR merge and sandbox cleanup for agent/codex/always-active-vscode-extension-2026-04-22-16-18
The branch also needed the extension to wake up on startup so the newly versioned install shows live state immediately instead of waiting for a view-open trigger. This adds onStartupFinished to both manifests, keeps the live/template activation contracts aligned, and extends the focused regression to lock that startup behavior in place. Constraint: The shipped live and template manifests must stay identical or local installs and repo scaffolds drift Rejected: Leave activation view-only | delays the companion until the user manually opens the SCM view and weakens the always-active expectation Confidence: high Scope-risk: narrow Directive: Keep the startup activation event and manifest parity covered whenever the Active Agents extension install surface changes Tested: node --test test/vscode-active-agents-session-state.test.js Tested: openspec validate agent-codex-vscode-extension-version-bump-guard-2026-04-22-16-18 --type change --strict Tested: openspec validate --specs Not-tested: PR merge and sandbox cleanup for agent/codex/always-active-vscode-extension-2026-04-22-16-18
The extension now boots on startup, auto-installs a newer workspace build on activate, and offers Reload Window so the newest local companion takes effect without a manual script pass. The focused test suite now locks manifest parity, version bumps, startup activation, and the reload prompt path. Constraint: A running VS Code extension still needs a window reload before newly installed code becomes active Rejected: Silent background install with no reload prompt | leaves the user on stale code with no visible handoff Confidence: high Scope-risk: moderate Reversibility: clean Directive: Keep live/template Active Agents manifests and extension runtime behavior aligned whenever shipped companion files change Tested: node --test test/vscode-active-agents-session-state.test.js; openspec validate agent-codex-vscode-extension-version-bump-guard-2026-04-22-16-18 --type change --strict; openspec validate --specs; node scripts/install-vscode-active-agents-extension.js Not-tested: Real VS Code notification interaction outside the mocked extension harness
NagyVikt
deleted the
agent/codex/always-active-vscode-extension-2026-04-22-16-18
branch
NagyVikt
added a commit
that referenced
this pull request
Apr 22, 2026
* Keep the Active Agents coordinator artifacts aligned with the merged lane The role boards already showed the branding follow-up complete, but the root summary, checkpoint log, and wave prompts still lagged behind. This change records the merged implementation and bookkeeping PRs, fixes the stale repo path in the dormant wave prompts, and adds explicit checkpoint acceptance/evidence blocks so the finished plan can be audited from the coordinator surfaces alone. Constraint: PR #322 and PR #326 already merged, so this follow-up must stay plan-artifact bookkeeping only Rejected: Reopen the implementation or runtime lane | merged execution and the no-op runtime audit made that misleading Confidence: high Scope-risk: narrow Reversibility: clean Directive: When helper cleanup PRs merge, sync the root summary, checkpoints, and wave prompts in the same lane so role boards are not the only truthful source Tested: openspec validate --specs; gh pr view 322 --json number,state,mergedAt,mergeCommit,headRefName,baseRefName,url; gh pr view 326 --json number,state,mergedAt,mergeCommit,headRefName,baseRefName,url; git worktree list --porcelain; git branch -a | rg 'vscode-active-agents-logo-and-runtime-(im|pl)-2026-04-22'; git diff --check Not-tested: Manual VS Code UI render because this lane changes only plan artifacts * Keep merged Active Agents cleanup evidence truthful The runtime branch already merged as PR #327, but its OpenSpec tasks file still showed unchecked cleanup items because the guarded finish hit a worktree-pinned local branch deletion error before the evidence lines were written back. This follow-up only records the actual finish, merge, and cleanup facts. Constraint: The original finish flow merged the branch before the local worktree cleanup failure surfaced Rejected: Leave the stale unchecked cleanup items in place | makes the merged artifact look incomplete and contradicts the verified repo state Confidence: high Scope-risk: narrow Reversibility: clean Directive: When guarded finish partially succeeds, write back the actual PR and cleanup evidence in a tiny follow-up lane instead of leaving stale checkboxes behind Tested: openspec validate agent-codex-vscode-extension-version-bump-guard-2026-04-22-16-18 --type change --strict; openspec validate --specs Not-tested: Runtime suites; no code behavior changed --------- Co-authored-by: NagyVikt <nagy.viktordp@gmail.com>
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
1 participant
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.
Summary
Testing