Friendlier docs voice; restructure highlights; add real screenshots

- Soften the intro and per-feature copy on index.md / installation.md;
  remove dw.json/SFCC_* jargon from outward-facing prose.
- Reorder highlights and add screenshots for the three biggest ones
  (Sandbox Realm Explorer, Library Explorer, Script Debugger). Make
  highlight images clickable so the inline thumbnail can be expanded
  to the full-resolution capture.
- Rename Cartridge Code Sync -> "Cartridge Management and Code Watch/
  Upload"; add SCAPI API Explorer as a dedicated highlight.
- Drop the Page Designer Assistant highlight; promote Scaffolding to a
  highlight in its place (covers cartridges, controllers, hooks, jobs).
- Expand the Script Debugger blurb to call out controllers, jobs,
  custom scripts, SCAPI hooks, Custom APIs, breakpoints, and log points.
- Delete features.md; fold Log Tailing, Active Instance Status Bar, and
  B2C CLI Plugin Support onto index.md and update sidebar / cross-links.
- Drop Project Root Pinning from configuration.md (uncommon use case).
- Mention the VS Code Extension on docs/guide/index.md with a quick-
  install block parallel to the CLI/MCP installs, using the existing
  release.data.ts loader.

Author: clavery

docs/.vitepress/config.mts

@@ -82,7 +82,6 @@ const guidesSidebar = [
       {text: 'Overview', link: '/vscode-extension/'},
       {text: 'Installation', link: '/vscode-extension/installation'},
       {text: 'Configuration', link: '/vscode-extension/configuration'},
-      {text: 'Features', link: '/vscode-extension/features'},
     ],
   },
   {

docs/guide/index.md

@@ -1,14 +1,19 @@
 ---
-description: Introduction to the Agentic B2C Developer Toolkit — CLI, Agent Skills, MCP Server, and SDK for Salesforce Agentforce Commerce.
+description: Introduction to the Agentic B2C Developer Toolkit — CLI, Agent Skills, MCP Server, VS Code extension, and SDK for Salesforce Agentforce Commerce.
 ---
 
+<script setup>
+import {data as vsxRelease} from '../vscode-extension/release.data.ts';
+</script>
+
 # Introduction
 
 The Agentic B2C Developer Toolkit exposes the B2C Commerce platform as commands, MCP tools, and coding skills — so you and your AI agents can build, deploy, and operate storefronts from the terminal or directly inside your IDE. No clicking through Business Manager to deploy, no context-switching to run a job, no manual copy-paste when your agent needs to touch a live sandbox.
 
 - **B2C CLI** — a single command for every workflow: cartridge deploys, jobs, ODS/MRT, WebDAV, site archives, SLAS, eCDN, Account Manager, CI/CD.
 - **Agent Skills** — 30+ preconfigured skills that teach your coding agent (Claude Code, Cursor, Agentforce Vibes, Copilot, Codex) how B2C Commerce works — SCAPI Custom APIs, SLAS, SFRA controllers and forms, ISML, Page Designer, hooks, custom objects — and which CLI commands to run when.
 - **MCP Server** — a focused set of MCP tools that complement the CLI for agent-driven workflows.
+- **VS Code Extension** *(Developer Preview)* — sandbox management, cartridge code sync, content libraries, SCAPI explorer, and a server-side script debugger right inside VS Code.
 - **Tooling SDK** — everything the CLI does, available as a typed TypeScript SDK for custom integrations.
 
 ## Quick CLI Install
@@ -74,13 +79,37 @@ claude plugin install b2c-dx-mcp --scope project
 
 See the [MCP Server Installation Guide](/mcp/installation) for full setup steps and troubleshooting.
 
+## Quick VS Code Extension Install <Badge type="warning" text="Developer Preview" />
+
+The B2C DX VS Code Extension brings sandbox management, code sync, content libraries, the SCAPI explorer, and a server-side debugger into VS Code. It isn't on the Marketplace yet — install the latest pre-built `.vsix` from GitHub.
+
+<div v-if="!vsxRelease.unavailable">
+
+Latest version: <strong>{{ vsxRelease.version }}</strong> · <a :href="vsxRelease.vsixDownloadUrl">Download {{ vsxRelease.vsixAssetName }}</a> · <a :href="vsxRelease.releasePageUrl">Release notes</a>
+
+```bash
+code --install-extension {{ vsxRelease.vsixAssetName }}
+# or, in Cursor:
+cursor --install-extension {{ vsxRelease.vsixAssetName }}
+```
+
+</div>
+<div v-else>
+
+The extension hasn't shipped a release yet. Browse the <a :href="vsxRelease.fallbackUrl">GitHub releases page</a> for `b2c-vs-extension@*` tags.
+
+</div>
+
+See the [VS Code Extension](/vscode-extension/) section for the full overview, [installation](/vscode-extension/installation), and [configuration](/vscode-extension/configuration).
+
 ## Next Steps
 
 - [Authentication Setup](./authentication) - Set up Account Manager, OCAPI, and WebDAV
 - [Analytics Reports (CIP/CCAC)](./analytics-reports-cip-ccac) - Run curated analytics reports and SQL queries
 - [Configuration](./configuration) - Configure instances and credentials
 - [IDE Integration](./ide-integration) - Connect Prophet VS Code to B2C CLI configuration
 - [MCP Server](/mcp/) - AI-assisted development with Model Context Protocol
+- [VS Code Extension](/vscode-extension/) - Sandbox management, code sync, and the script debugger inside VS Code
 - [CLI Reference](/cli/) - Browse available commands
 - [MCP Tools](/mcp/toolsets) - Explore MCP tools for cartridges, MRT, SCAPI, and so on
 - [SDK Reference](/api/) - Explore the SDK

docs/index.md

@@ -152,5 +152,5 @@ Browse the [GitHub releases page]({{ vsxRelease.fallbackUrl }}) for `b2c-vs-exte
 
 </div>
 
-Detailed setup: [Installation](/vscode-extension/installation) · [Configuration](/vscode-extension/configuration) · [Features](/vscode-extension/features)
+Detailed setup: [Installation](/vscode-extension/installation) · [Configuration](/vscode-extension/configuration)
 

docs/vscode-extension/configuration.md

@@ -10,7 +10,6 @@ This page covers:
 
 - [Connecting to a B2C Instance](#connecting-to-a-b2c-instance) — credentials per feature.
 - [Switching the Active Instance](#switching-the-active-instance) — single-workspace, multi-instance.
-- [Project Root Pinning](#project-root-pinning) — multi-root workspaces.
 - [Settings Reference](#settings-reference) — the `b2c-dx.*` toggles and verbosity controls.
 
 ## Connecting to a B2C Instance
@@ -19,7 +18,7 @@ The extension needs different credentials depending on which feature you use. **
 
 ### Per-feature requirements
 
-Each feature documents its own requirements in [Features](./features). The summary:
+A summary by feature:
 
 | Feature | Required `dw.json` fields |
 | ------- | ------------------------- |
@@ -66,15 +65,6 @@ When `dw.json` defines multiple named instances (the recommended pattern for wor
 
 The same pointer is shared with the CLI: switching here is equivalent to running `b2c setup instance set-active <name>`.
 
-## Project Root Pinning
-
-In a multi-root workspace, the extension auto-detects the project root by walking up from the active editor (or the first workspace folder) looking for `dw.json` / `package.json` markers. Two commands let you override the auto-detected root:
-
-- **B2C DX: Use as B2C Commerce Root** — only available on a workspace-root folder when more than one folder is open in the workspace. Right-click that folder in the Explorer and select the command to pin it. While a pin is active, the status bar shows a `$(pinned)` indicator.
-- **B2C DX: Reset B2C Commerce Root to Auto-Detect** — clears the pin and returns to auto-detection. Run from the Command Palette (this command has no Explorer context-menu entry).
-
-The pin is workspace-scoped (stored in workspace state).
-
 ## Settings Reference
 
 These VS Code settings live under the `b2c-dx.*` namespace. **You usually don't need to change any of them** — they exist for niche cases like disabling a feature you don't use, or quieting the log channel for a bug report. To browse: **Settings** (Cmd+,) → search for `b2c-dx`.
@@ -125,6 +115,6 @@ The B2C Script Debugger registers regardless of these toggles — it activates o
 
 ## Next Steps
 
-- [Features](./features) — full feature tour with per-feature credential callouts.
+- [Overview](./) — what the extension can do.
 - [Authentication Setup](../guide/authentication) — Account Manager API clients, WebDAV access keys, OAuth scopes.
 - [CLI Configuration](../guide/configuration) — full `dw.json` reference and precedence rules.