Keep the CI sdk package name so main's preview deploy finds it

ploy previews run pr-deploy.yaml from main, which downloads
build-output-sdk,
so a renamed artifact can never be found from a pull request. Keep the
package
name and point build:sdk:production and build:sdk:development at the
CallViewModel bundle the preview is meant to carry.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

docs/agents/architecture.md

@@ -78,7 +78,9 @@ Code that builds in only one is a bug.
   `pnpm lint:externals`). Interface only so far; the design is `sdk-plan.md`.
 - `build:sdk-target-based-on-call-view-model` — the SDK demo that predates the
   package, one bundle of the `CallViewModel`; entry
-  `sdk-target-based-on-call-view-model/main.ts`.
+  `sdk-target-based-on-call-view-model/main.ts`. CI's `sdk` package
+  (`build:sdk:production` / `build:sdk:development`, the Netlify `-sdk` preview)
+  is still this bundle, not `build:sdk`.
 - `build:component` — `@element-hq/element-call-component`, sources in `component/`
   (its own pnpm project; run pnpm from the repo root). Host API is in the README;
   `pnpm lint:externals` rejects an import of a `react` / `react-dom` /