fix(vscode): honor current configuration and prepare CLI-example releases

[AlexMikhalev]

Atomic autocomplete currently ignores a configured agent on first activation and reuses a Store after endpoint changes. Server requests also ignore enableLocalServer, and the README incorrectly promises Atomic suggestions after two characters. This change uses current credentials/endpoints, refuses configured loopback URLs when local mode is off, and documents the actual space trigger. It also prevents old in-flight responses from replacing results for a newer role, endpoint, agent or query.

Prepare VS Code 0.1.3 preview and Continue 0.1.1 for the existing tag-driven, immutable release workflows. Both packages include the previously merged runnable examples for separately installed terraphim-grep and terraphim-agent. Continue checks its actual MCP version against the manifest, and its source/tag tests follow the versioned package name. No tags, registry-readiness flags, assets or protection settings are changed by this PR.

Validation:

• TypeScript compile and ESLint pass; 63 package tests, 29 existing actual-WASM/protocol/export/link tests and four request-cache race regressions pass.
• Six Continue tests pass against the actual MCP SDK and released terraphim-grep 1.21.20, including graph-drift refusal and retrieval after reviewed restart.
• Actual VS Code 1.141.2 disposable-profile checks pass for configured/cleared/invalid agents, endpoint changes, canonical loopback refusal, explicit remote selection, unavailable local server and role revision changes. Actual save and KG output checks also pass. The latest local run refused native history because its window was unfocused; that failure is retained. The final VSIX still requires the complete Linux/macOS/Windows native CI lifecycle before release.
• No mock service or substitute VS Code/Atomic API is used. This does not claim authenticated remote service access or all-41 UI qualification.

The first CI matrix passed Linux/macOS and failed Windows' local-mode assertion. The native test now binds directly to the already activated helper modules using actual file identity, avoiding another singleton loaded under a differently spelled Windows path. It records requested/loaded filenames, retains the failure and all original assertions, and requires the complete matrix to pass again at the new head.

Refs terraphim/terraphim-ai#3488 (Gitea).