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>

sdk-target-based-on-call-view-model/README.md

@@ -23,8 +23,11 @@ pnpm build:sdk-target-based-on-call-view-model
 
 in the repository root. (`pnpm build:sdk` builds the `sdk/` package instead.)
 
-It will create `sdk-target-based-on-call-view-model/dist` containing the compiled js
-file, `matrixrtc-sdk.js`.
+CI's `sdk` package (`build:sdk:production`, `build:sdk:development`, the
+`build-output-sdk` artifact and the `pr<N>-sdk` Netlify preview) is still this
+bundle, not the `sdk/` package, until its consumers have moved over.
+
+It will create `dist` containing the compiled js file, `matrixrtc-sdk.js`.
 
 This file needs to be hosted. Locally (via `npx serve -l 81234 --cors`) or on a remote server.
 

sdk-target-based-on-call-view-model/main.ts

@@ -8,7 +8,8 @@ Please see LICENSE in the repository root for full details.
 /**
  * EXPERIMENTAL
  *
- * This file is the entrypoint for the sdk build of element call: `pnpm build:sdk`
+ * This file is the entrypoint for the sdk build of element call:
+ * `pnpm build:sdk-target-based-on-call-view-model`
  * use in widgets.
  * It exposes the `createMatrixRTCSdk` which creates the `MatrixRTCSdk` interface (see below) that
  * can be used to join a rtc session and exchange realtime data.