Flip docs default to released + support doc-only releases

[clavery]

Summary

• Flip docs URL structure: stable/released docs now live at the root URL, dev docs move to /dev/ (previously dev was at root, released at /release/)
• Add @salesforce/b2c-dx-docs workspace package to enable doc-only releases and changelog tracking
• Update CI workflows for flipped build order, docs tagging, and deployment triggers
• Add docs build to CI to catch broken docs builds before merge

Why a docs workspace package?

Adding a private @salesforce/b2c-dx-docs package to the monorepo with a dependency on @salesforce/b2c-tooling-sdk gives us three benefits via the existing changeset infrastructure:

1. Doc-only releases — Documentation improvements can be released independently by creating a changeset that only bumps @salesforce/b2c-dx-docs. This creates a docs@<version> tag and triggers a docs rebuild without touching CLI/SDK/MCP versions.

2. Automatic cascade on SDK changes — Because the docs package depends on the SDK, the updateInternalDependencies: "patch" setting in changeset config auto-bumps the docs version whenever the SDK is bumped. This is correct behavior since API docs are generated from the SDK and should be rebuilt when it changes.

3. Changelog tracking — Doc changes get their own CHANGELOG.md and appear in GitHub release notes, providing visibility into what changed in the documentation.

Release cascade behavior:

• SDK changeset → SDK bumps → CLI, MCP, Docs all auto-patch → docs tag created → docs rebuilt
• CLI-only changeset → CLI bumps → no cascade to docs (CLI changes don't affect docs build)
• Docs-only changeset → Docs bumps → no cascade to others → docs tag created → docs rebuilt

Changes

File	Change
docs/package.json	New private workspace package
pnpm-workspace.yaml	Add docs to workspace packages
docs/.vitepress/config.mts	Flip IS_RELEASE_BUILD → IS_DEV_BUILD, stable at root, dev at /dev/
.github/workflows/deploy-docs.yml	Flip build order, dual-match tag resolution (@salesforce/* + docs@*), cancel-in-progress: true
.github/workflows/publish.yml	Docs version detection, docs@<version> tag creation, changelog extraction, deploy trigger
.github/workflows/ci.yml	Add docs build step after package builds

Test plan

• pnpm install succeeds with new docs workspace
• pnpm -r run build skips docs package (no build script)
• pnpm run docs:build (default) produces root-path stable docs
• IS_DEV_BUILD=true pnpm run docs:build produces /dev/ base path
• pnpm run lint:agent passes
• pnpm run typecheck:agent passes
• Verify deploy-docs workflow on merge
• Test doc-only changeset with pnpm changeset version

[patricksullivansf]

conceptually this makes sense.

I'm a little confused about how often the dev docs get built by CI

[clavery]

They are built on every change to main. This changes it so the website starts on the last released version instead of the version of the docs from main. You can toggle with a dropdown in the header.