[Eduardo Villalpando Mello (edvilme)]

Summary

Fixes #138.

• Prevent a rejected in-flight restart from re-registering the formatter placeholder after context disposal.
• Guard the same lifetime boundary when missing-interpreter shutdown or per-project initialization finishes after disposal.
• Add four deferred-barrier regression tests, including preservation of fallback recovery on a live context.

Restart scheduling, shutdown waiting semantics, and normal formatter recovery are unchanged.

Validation

• Before the fix, the reported reproduction left two provider registrations and one live provider after disposal, rather than one registration and no live providers. Two analogous disposal regressions also failed.
• Full TypeScript suite: 156 passing on Node 24.17.0, Windows x64.
• TypeScript build, production lint, changed-test ESLint, and git diff --check: passed; existing nonblocking lint warnings remain.
• Independently reran all four new regression cases before committing: 4 passing on Node 26.13.0.

[Copilot]

🟢 Approval recommended

No active review issues are reported for the changes preventing formatter-placeholder restoration after disposal.

No open issues 🎉

What changed in this PR

Addresses #138 by preventing asynchronous server operations from restoring the formatter placeholder after the extension context is disposed, while preserving fallback recovery for live contexts.

Changes:

• Add disposal guards after per-project initialization, missing-interpreter shutdown, and restart failure.
• Add four regression tests covering disposal races and live-context fallback recovery.
• Clarify that disposal removes the placeholder without waiting for in-flight restarts.

File	Description
typescript/​tests/​activation.test.ts	Add deferred-barrier tests for disposal safety and fallback recovery.
typescript/​src/​activation.ts	Guard formatter registration after disposal and clarify the lifecycle contract.

_{Review effort: Balanced}

[Rich Chiodo (rchiodo)]

🔒 Automated review in progress — Rich Chiodo (@rchiodo) is auto-reviewing this PR.

[Rich Chiodo (rchiodo)]

Reviewed commit: 611209ffddb5d263785b93c051727ee8bef84b9c

Result: 🔴 could-not-verify

Verification details

Verification: Automated verification is best effort. The PR author remains responsible for testing.

Summary: [unavailable] Container verification could not start and local execution was not authorized for this PR HEAD: Podman machine 'pyrx-automation' is not running.

Test runs: none recorded.

[Rich Chiodo (rchiodo)]

Approved via Review Center.