fix(release): correct VSIX tombstone identity + staging verify hygiene (v0.3.0 hotfix)

[Dongbumlee]

Pre-tag-push hotfixes for v0.3.0

PR #187 was merged before two issues were caught:

1. P0 — VSIX tombstone shipped with the wrong extension identity. The tombstone scaffolded in 2f128d9 published as AgentOpsToolkit.agentops-skills (a brand-new extension that has never existed on the VS Code Marketplace) and pointed migrating users to AgentOpsAccelerator.agentops-skills (also wrong — the canonical new identity per plugins/agentops/package.json is AgentOpsAccelerator.agentops-accelerator).

   Without this fix, publishing v0.3.0 would create a brand-new extension nobody has installed, and the ~5 versions of the legacy AgentOpsToolkit.agentops-toolkit extension already in users' VS Code installs would never receive a deprecation prompt.

   018cf74 rewrites the tombstone to identify itself as AgentOpsToolkit.agentops-toolkit (republishes onto the existing Marketplace listing, triggers in-place update for current users) and corrects all references to the new extension across package.json, src/extension.ts, the tombstone README/CHANGELOG/CDN deprecation request, the repo-root CHANGELOG.md (flows into the GitHub release body and PyPI tombstone long description), and docs/verifying-tombstones.md (verification commands users will copy-paste).

2. CI hygiene — staging verify-tombstone-testpypi flaked when only dev versions of accelerator existed on TestPyPI. 5af6936 splits the verification into two install steps (tombstone with --no-deps, then accelerator with --pre) so staging stays green between full releases. No effect on release.yml (PyPI prod always has both packages at the tagged version when the verify step runs).

Verification

Staging on release/v0.3.0 is fully green at 018cf74 (8/8 jobs, run #26615257593):

• build-pypi-tombstone ✅
• build / build ✅
• publish-vsix-prerelease ✅
• publish-testpypi ✅
• verify-testpypi ✅
• publish-tombstone-testpypi ✅
• publish-tombstone-vsix-prerelease ✅ — confirms AgentOpsToolkit.agentops-toolkit v0.3.0-pre publishes cleanly under the existing publisher
• verify-tombstone-testpypi ✅ — confirms the redirect (agentops-toolkit==0.3.0 → agentops-accelerator>=0.3.0) installs cleanly from TestPyPI

Critic review (tombstone-identity-critic, Correctness lens)

• Identity coherence ✅ — publisher+name yield AgentOpsToolkit.agentops-toolkit
• Version monotonicity ✅ — 0.3.0 > 0.1.8 (highest existing) and > 0.2.2 (highest in git history)
• NEW_EXTENSION_ID consistency ✅ — all 4 use sites + DEPRECATION_MESSAGE interpolation
• Storage key namespace preservation ✅ — agentops-toolkit.deprecation-prompt-shown unchanged
• Backward compatibility ✅ — legacy versions 0.1.7 and 0.2.2 verified declarative-only (contributes.chatSkills only, no main/commands/keybindings/settings), so zero state-collision risk
• Workflow cross-references ✅ — release.yml publish-tombstone-vsix and staging.yml publish-tombstone-vsix-prerelease consume the renamed manifest cleanly

Plan after merge

1. Tag v0.3.0 at this merge commit
2. release.yml triggers — publishes agentops-accelerator==0.3.0 + agentops-toolkit==0.3.0 tombstone to PyPI; publishes accelerator + tombstone VSIX to VS Code Marketplace; creates GitHub release
3. Verify all three tombstones live (PyPI, VSCode Marketplace, TestPyPI)
4. File the Microsoft CDN deprecation request per tombstones/vscode/CDN_DEPRECATION_REQUEST.md

Closes part of #181.

[Dongbumlee]

🔍 Discovery during VSCode Marketplace verification — additional commit added

While verifying the staging publish-tombstone-vsix-prerelease run actually pushed a new pre-release to the Marketplace (no new versions appeared on the AgentOpsToolkit.agentops-toolkit listing after 018cf74), I pulled the job log and found:

Publishing 'AgentOpsToolkit.agentops-toolkit v0.3.0'...
Error: Access Denied: The Personal Access Token used has expired.
You're using an expired Personal Access Token, please get a new PAT.
Error: Process completed with exit code 1.

The job reported success because both staging VSIX publish steps carry continue-on-error: true. The expired VSCE_PAT has been silently failing every staging publish for an extended period — which is why the new accelerator extension (AgentOpsAccelerator.agentops-accelerator) doesn't exist on the Marketplace yet, and why no 0.3.0 pre-release ever landed on the legacy tombstone target.

New commit de0bf8a — replace blanket tolerance with conditional tolerance

de0bf8a fix(ci): staging vsce publish must surface auth/network failures ports the same pattern release.yml lines 469–489 already uses:

• Capture combined stdout+stderr from vsce publish
• Swallow exit code ONLY when output contains already exists (re-run of an already-published pre-release version — the only benign failure mode)
• Propagate every other exit code (auth, network, validation, 5xx)
• Move PAT to env: block (matches release.yml; avoids leaking into shell interpolation)

Applied to both:

• staging.yml:348 — main extension agentops-accelerator publish
• staging.yml:425 — tombstone agentops-toolkit publish

Required actions before pushing v0.3.0 tag

• @donlee regenerates VSCE_PAT at https://aka.ms/vscodepat with scope covering BOTH publishers (AgentOpsToolkit + AgentOpsAccelerator)
• Updates the VSCE_PAT GitHub repo secret
• Re-trigger staging on this branch — must show all 8 jobs ✅ for the first time
• Then merge this PR and tag v0.3.0

Without the PAT renewal, release.yml's publish-vsix and publish-tombstone-vsix jobs will fail outright on tag push (no continue-on-error there) and abort the release.