Swap IMG.LY CE.SDK for Orshot Embed

# Migrate this project from IMG.LY CE.SDK to Orshot Embed

You are helping me replace IMG.LY's CreativeEditor SDK (`@cesdk/cesdk-js`, `@cesdk/engine`, `@cesdk/node`) with Orshot (orshot.com). Orshot hosts a template editor that I embed in my app through an iframe or a React/Vue component, and renders images, PDFs and videos from the same templates through an API. It also has native n8n, Make, Zapier, Pipedream and Airtable apps and an MCP server (https://mcp.orshot.com/mcp, setup at https://orshot.com/agents). If you can connect to that MCP server, do it first: it lets you list my Orshot templates, read their parameters and test renders directly. Read the docs linked below before changing anything, then do the work in the order given.

## 1. Find every IMG.LY touchpoint in this project

Search for, and list with file paths:
- imports from `@cesdk/cesdk-js`, `@cesdk/engine`, `@cesdk/node`, `@cesdk/node-native`, and `cdn.img.ly` script tags
- `CreativeEditorSDK.create(`, `CreativeEngine.init(`, the `license` and `baseURL` config, `userId` passed for MAU tracking, `role:`
- `engine.scene.loadFromString`, `saveToString`, `loadFromArchiveURL`, scene and archive files (`.scene`, `.zip`) in storage
- `engine.variable.setString`, `{{variable}}` tokens, placeholder blocks
- `engine.block.export`, `exportVideo`, `onExport`, `onUpload`, custom asset sources, `cesdk.ui.*` and `ly.img.*` component customization, `--ubq-` CSS variables, `i18n.setTranslations`
- the Renderer CLI or any server that runs the headless engine (Dockerfile, CI, cron)

## 2. Templates

Scenes cannot be imported into Orshot. Each template is rebuilt once, one of three ways; do not try to convert scene files in code:
- If the design also exists in Figma, Canva, HTML or Polotno, I import it from there: https://orshot.com/docs/importing-templates
- Otherwise I send Orshot the scene or archive, the assets and one export per template, and they rebuild up to 5 for free: https://orshot.com/migrate/from-imgly
- Or I rebuild it in the Orshot Studio.

After a rebuild, every `{{variable}}` is an Orshot parameter with the same name, and placeholder blocks are editable layers. Imported designs get automatic parameter IDs (like `text_1_1`); I rename those to the old variable names in the Studio. Ask me for the Orshot template IDs, or read the parameters with:
- GET /v1/studio/templates/{id}: https://orshot.com/docs/api-reference/studio-template-get
- List templates: https://orshot.com/docs/api-reference/studio-templates-list

Build a mapping table: scene file → Orshot templateId, and `{{variable}}` → Orshot parameter name. Show it to me before editing code.

## 3. Replace the editor

Reference: https://orshot.com/docs/orshot-embed/integration · React: https://orshot.com/docs/orshot-embed/react-sdk · Vue: https://orshot.com/docs/orshot-embed/vue-sdk

IMG.LY:
```js
const cesdk = await CreativeEditorSDK.create('#cesdk_container', { license: LICENSE, baseURL: ASSETS_CDN, userId: user.id });
await cesdk.engine.scene.loadFromString(scene);
```

Orshot (plain HTML):
```html
<iframe src="https://orshot.com/embeds/EMBED_ID?templateId=12345&userId=USER_ID" title="Editor" allow="clipboard-write" style="width:100%;height:100%;min-height:600px;border:none"></iframe>
```

Orshot (React):
```jsx
import { OrshotEmbed } from "@orshot/embed-react";
<OrshotEmbed embedId="EMBED_ID" templateId={12345} />
// Per-user libraries: use the iframe URL with &userId=… (the SDK props are embedId, templateId, modifications)
```

Rules:
- The embed ID comes from my Orshot workspace (Embed → Embed Code). Store it as `ORSHOT_EMBED_ID`. Remove the license key, the `baseURL` asset hosting and every `@cesdk` package.
- `loadFromString` becomes the `templateId` query parameter. `i18n.setLocale` becomes `?lang=`. Docs: https://orshot.com/docs/orshot-embed/integration
- The `userId` you passed for MAU tracking becomes the `userId` query parameter (plus optional `userName`, `userEmail`); Orshot keeps each user's templates and brand library (images, videos, audio, colors, fonts) apart. Docs: https://orshot.com/docs/orshot-embed/per-user-data
- The Adopter role (users fill a locked layout) becomes template protection (masters open as copies) plus locked layers and `?hide=stylesSidebar`. Docs: https://orshot.com/docs/orshot-embed/template-protection
- `editor.setGlobalScope(…, 'Deny')` and role scopes become per-user permissions: lock actions per user in the dashboard (Your Users → Permissions, needs per-user data) or per session with a `permissions` claim in the signed JWT. Docs: https://orshot.com/docs/orshot-embed/user-permissions
- Theming and component visibility are set in the dashboard (accent color, title, icon, language) and with the `hide` query parameter (`templateBar,pagesBar,metaBar,toolsBar,videoBar,stylesSidebar,smartResize`). Delete the `--ubq-` overrides and `cesdk.ui` calls. Docs: https://orshot.com/docs/orshot-embed/appearance
- If the app runs on Safari or inside webviews, sign a JWT and pass it as `token`. Docs: https://orshot.com/docs/orshot-embed/jwt-authentication

## 4. Replace callbacks and exports

Reference: https://orshot.com/docs/orshot-embed/events · Control: https://orshot.com/docs/orshot-embed/controlling-embed · Custom buttons: https://orshot.com/docs/orshot-embed/custom-buttons · Asset picker: https://orshot.com/docs/orshot-embed/custom-asset-picker

- Your save handler (`saveToString` on change, stored in my database) becomes the `orshot:template:create` / `orshot:template:update` postMessage events plus a webhook URL set in the dashboard. Orshot stores the design; keep only the template ID in my database.
- `onExport` (or the registered `exportDesign` action) and `engine.block.export` in the browser become downloads inside the embed, or a custom toolbar button that emits the PNG/PDF to the parent window (`orshot:custom_action`).
- `onUpload` (or the `uploadFile` action) and custom asset sources become the Custom Asset Picker: answer `orshot:asset:request` with `orshot:asset:response`.
- `engine.variable.setString` at runtime becomes an `orshot:embed:control` message with `modifications`; loading another scene becomes the same message with `templateId`.
- Always check `event.origin` includes `orshot.com`.

## 5. Rewrite the headless exports

Reference: https://orshot.com/docs/api-reference/render-from-studio-template

IMG.LY:
```js
const engine = await CreativeEngine.init({ license: LICENSE });
await engine.scene.loadFromString(scene);
engine.variable.setString('headline', 'Hello');
const blob = await engine.block.export(engine.scene.getPages()[0], { mimeType: 'image/png' });
```

Orshot:
```http
POST https://api.orshot.com/v1/studio/render
Authorization: Bearer ORSHOT_KEY
{ "templateId": 12345, "modifications": { "headline": "Hello", "photo": "https://…" }, "response": { "type": "url", "format": "png" } }
```

Rules:
- `modifications` is keyed by parameter name; a `{{headline}}` variable is the `headline` key.
- Style overrides use dot keys: `"headline.fontSize": 48`, `"headline.color": "#111"`. Docs: https://orshot.com/docs/dynamic-parameters
- Multi-page templates prefix the page: `"page2@headline"`.
- `response.format`: png, jpg, webp, avif, pdf, mp4, webm, gif. `response.type`: url, base64, binary.
- Sync is the default and returns `data.content`. For a webhook use `"mode": "async"` inside `response` plus top-level `webhook_url`; you get `202 { id, status: "queued" }` and can poll GET /v1/studio/render-jobs/{id}. Docs: https://orshot.com/docs/api-reference/async-render-start
- Remove `@cesdk/node`, the Renderer CLI and the WASM/GPU layer from the server, Dockerfile and CI.
- Auth is Bearer. Store the key as `ORSHOT_API_KEY`. Keys: https://orshot.com/docs/quick-start/get-api-key
- Official SDKs (Node, Python, Ruby, PHP): https://orshot.com/docs/sdks · Errors: https://orshot.com/docs/error-reference

## 6. Automations

If a Zapier, Make or n8n step calls the headless engine or a server you run, add the Orshot step next to it with the same parameters, run it once, then remove the old step. Ready-made workflows are in Quick Connect (Copy as n8n workflow / Make blueprint). Docs: https://orshot.com/integrations

## 7. Verify, then switch

Put the Orshot embed behind a feature flag next to the IMG.LY editor. Open the same template in both, save from Orshot, confirm the webhook and postMessage events arrive, render each template once from the API and compare with the engine's output. After a week of matching results, remove the IMG.LY packages and the license. Tell me what you removed.