fix(webapp): make SDK bundle-docs build step work in pruned Docker image

The webapp Docker build runs the SDK build as a dependency. The SDK's new
bundle-docs step was not runnable in the pruned image: the script was not
copied into the builder, and the repo docs/ tree it reads is pruned away.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: d-cs

.server-changes/fix-webapp-docker-sdk-bundle-docs.md

@@ -0,0 +1,6 @@
+---
+area: webapp
+type: fix
+---
+
+Fix webapp Docker build failing because the SDK's bundle-docs build step was not runnable in the pruned image

docker/Dockerfile

@@ -68,6 +68,7 @@ RUN chmod +x ./scripts/wait-for-it.sh
 RUN chmod +x ./scripts/entrypoint.sh
 COPY --chown=node:node .configs/tsconfig.base.json .configs/tsconfig.base.json
 COPY --chown=node:node scripts/updateVersion.ts scripts/updateVersion.ts
+COPY --chown=node:node scripts/bundleSdkDocs.ts scripts/bundleSdkDocs.ts
 RUN pnpm run generate
 RUN --mount=type=secret,id=sentry_auth_token \
     SENTRY_AUTH_TOKEN=$(cat /run/secrets/sentry_auth_token) \

scripts/bundleSdkDocs.ts

@@ -65,6 +65,19 @@ async function collectManifest(): Promise<string[]> {
 }
 
 async function bundleSdkDocs() {
+  // When the SDK is built as a dependency inside a pruned workspace (e.g. the webapp Docker
+  // image), the repo-level docs/ tree is a separate workspace package that isn't part of that
+  // build's dependency graph, so it isn't present. The SDK isn't being published there, so
+  // there's nothing to bundle: skip rather than fail. Publishing always runs from the full
+  // monorepo where docs/ exists, so the missing-docs guard below still protects releases.
+  const docsRoot = path.join(repoRoot, "docs");
+  try {
+    await fs.access(docsRoot);
+  } catch {
+    console.log(`[bundleSdkDocs] docs/ not present at ${docsRoot}; skipping (pruned build)`);
+    return;
+  }
+
   const manifest = await collectManifest();
 
   if (manifest.length === 0) {