@superblocksteam/vite-plugin-file-sync 2.0.170 → 2.0.171-next.0

package/dist/ai-service/skills/system/superblocks-migration/skill.generated.d.ts

@@ -1,2 +1,2 @@
-export declare const content = "---\nname: superblocks-migration\ndescription: |\n  Convert legacy Superblocks 2.0 YAML APIs (\"block-chain\" format) to the new 3.0 sdk-api TypeScript format.\n  Load when executing a v2\u2192v3 migration turn \u2014 the runtime prompt will tell you to.\nreadOnly: true\nmetadata:\n  author: superblocks\n  version: \"1.0\"\n---\n\n# v2 \u2192 v3 API Translation\n\nYou are converting **legacy Superblocks \"block-chain\" YAML APIs** into the **new code-mode `@superblocksteam/sdk-api` TypeScript format**. Each YAML file under `scratch/v2-backup/apis/<ApiName>/api.yaml` must be emitted as a single TypeScript file at `server/apis/<ApiName>/api.ts` that compiles, typechecks, and preserves behavior exactly.\n\n## Meta-rule: ZERO judgment calls\n\nIf any situation below is not resolved deterministically by this document, **STOP** for that API. Do **not** pick a default. Do **not** guess a factory, a shape, or an import. Skip it, continue with other APIs, and mark the checklist item as `failed` via `build_manageChecklist` with a short `failureReason` describing the exact ambiguity (failing rule, block name if any, what would be needed to proceed). This rule overrides everything else.\n\nCorollary: do not add `// TODO` comments that silently ship. Unresolved items live only as `failed` checklist entries.\n\nCorollary for `migration_page_route_verification_*`: see the _Page route verification_ section below \u2014 screenshot timeout/error \u2192 `failed`, never `completed`, never \"verified via router/source inspection.\" The full rule (including the hard-rule restatements) lives there to avoid drift.\n\n## Inputs and outputs\n\n- **Source tree:** `scratch/v2-backup/apis/<ApiName>/api.yaml`. Discover the actual set by listing the directory \u2014 do not hardcode a count or list.\n- **Target tree:** `server/apis/<ApiName>/api.ts`. Do not create scaffolding trees that do not already exist (see \"Registry registration\" below).\n- **Checklist:** the migration checklist has already been seeded with one item per API (id `api_<ApiName>`, origin `2.0-upgrade`, status `pending`, `clearOnFinalize: false`). Legacy in-flight runs may still have `origin: \"seed_api\"` for these API items. Pull the live set by calling `build_manageChecklist` with `action: \"get\"` and filtering to `status: \"pending\"` plus API-migration origins (`origin: \"2.0-upgrade\"` or legacy `origin: \"seed_api\"`) \u2014 that is your authoritative API list and count for this turn.\n\n## Required reading (read these BEFORE writing any output)\n\nAuthoritative. If a rule here conflicts with your priors, these win.\n\n1. The installed SDK root documentation through `getSdkApiDocs` \u2014 call it with no arguments for the current section index, then retrieve every top-level section (following every `root.continuation`) so the full api() contract, execution model, `ctx.*`, exports, error classes, performance best practices, `useApi` frontend hook, and integration method table are covered without loading the whole README at once.\n2. `node_modules/@superblocksteam/sdk-api/src/index.ts` (the **barrel**) \u2014 the authoritative list of exported factory names. Integration factory names are whatever this file exports, not whatever the directory name is. Never invent or case-fold a factory name without confirming it here.\n3. Version-aware documentation for **every integration** referenced by the YAMLs you convert:\n   - Call `getSdkApiDocs` with that integration's ID (or plugin ID when no integration ID is available).\n   - If a vendor-specific factory exists for the target service (e.g., a dedicated one for a given LLM provider), prefer it over a generic HTTP one.\n4. `skills/system/superblocks-migration/references/yaml-block-mapping.md` \u2014 full YAML \u2192 TS mapping for each legacy block type.\n\nThere is **no `javascript` integration** in sdk-api \u2014 inline JS/TS lives directly inside `run(ctx, input)`. Any block whose YAML key is `javascript:` becomes plain TypeScript in `run()`. The same applies to **`python:` blocks**: there is no `python` integration in sdk-api, so port the body to inline TypeScript inside `run(ctx, input)` (see \"Substituting unsupported integrations\" below and the Python section in `yaml-block-mapping.md`).\n\n## Substituting unsupported integrations\n\nThe pre-migration UI warns the user when an app references integrations whose v2 plugin is not present in sdk-api. The migration is **not** aborted on those APIs \u2014 they are still in your `seed_api` checklist and you are expected to make a best-effort port rather than immediately marking them `failed`.\n\nSubstitution rules (apply in order; first match wins):\n\n1. **`python:` step \u2192 inline TypeScript.** Re-write the Python body as equivalent TypeScript inside `run(ctx, input)`, exactly the way `javascript:` blocks are inlined. Translate Python idioms to JS/TS (e.g. `requests.get(...)` \u2192 `fetch(...)`, list comprehensions \u2192 `array.map`/`filter`, `len(x)` \u2192 `x.length`, dict access \u2192 object property access, `os.environ[...]` \u2192 `process.env[...]`, raise/except \u2192 `throw`/`try\u2026catch`). If the Python relied on a third-party PyPI package with no obvious JS equivalent, mark that one API `failed` with a `failureReason` naming the package \u2014 do not ship a guess.\n2. **HTTP-shaped vendor plugin \u2192 REST.** If an unsupported integration was effectively making REST calls (e.g. a thin wrapper around an HTTP API) and you can read the request shape from the YAML, port it to the `restApi` factory from sdk-api (or the dedicated vendor factory if one exists in the barrel \u2014 check `node_modules/@superblocksteam/sdk-api/src/index.ts`).\n3. **Otherwise, mark `failed`.** Per the meta-rule, do not invent a factory or fabricate behavior. Use `build_manageChecklist` with `status: \"failed\"` and a concrete `failureReason` (e.g. `\"unsupported integration <pluginId> with no JS-equivalent path\"`).\n\nDo **not** silently skip a step or replace it with a `// TODO` \u2014 every API still needs a deterministic outcome (`completed` or `failed`) on the checklist.\n\n## Preflight gate (MUST pass before any file edits)\n\nComplete this orientation sequence before writing or modifying any API file:\n\n0. **Install recommended user dependencies (before API work).** The platform restructure already computed exactly which v2 user-added packages the migrated client/server code imports, and persisted them at `scratch/migration-state.json` \u2192 `recommendedUserDeps` (each entry has `name`, `version`, and `dev`). Your job is to install that list \u2014 not to recompute it.\n   - Mark `migration_dependency_verification` as `in_progress` via `build_manageChecklist`.\n   - Read `scratch/migration-state.json` and extract `recommendedUserDeps`.\n   - If `recommendedUserDeps` is missing or empty, mark `migration_dependency_verification` as `completed` and continue to step 1.\n   - Otherwise, call `build_installPackages` **once** with every entry from `recommendedUserDeps` (passing `name`, `version`, and `dev` through unchanged). Do **not** skip because `node_modules` exists on disk; the platform never wrote these packages into `package.json`.\n   - **Failure semantics (covers every non-success outcome \u2014 no judgment calls):**\n     - On full success \u2192 mark `migration_dependency_verification` as `completed`.\n     - On **any** failure \u2014 full, partial (some packages installed, others did not), structured registry error (`not_in_registry`, `registry_auth_failed`, `registry_unreachable`), or unstructured error \u2014 mark `migration_dependency_verification` as `failed` with a `failureReason` that lists the affected package names and the tool's verbatim error code or message. Treat partial success the same as full failure for checklist purposes; do not split into multiple checklist items. Then continue to step 1 so API translation can still proceed. The user/operator will repair the registry/packages and re-trigger the migration turn.\n   - If `scratch/migration-state.json` also contains `recommendedUserDepsPinnedToLatest` (a string array of package names), include those names in the `failureReason` of `migration_dependency_verification` even on full success \u2014 phrased as \"pinned to latest, may need user confirmation: <names>\" \u2014 so the user can downgrade them before runtime if the latest major is incompatible. Use status `completed` in this case (the install succeeded), but the surfaced reason gives the user a checkpoint to act on.\n   - Do **not** scan imports yourself, edit `package.json`, or add packages outside `recommendedUserDeps`. If you believe a package is missing from the list, that is a platform bug: mark `migration_dependency_verification` as `failed` with `failureReason: \"platform bug: <pkg> imported by <file> but absent from recommendedUserDeps\"` and continue with API work using the packages that did install. (`build_manageChecklist` has no `note` action \u2014 `failed` with a structured `failureReason` is the only way to record this.)\n1. Call `build_manageChecklist` with `action: \"get\"` and filter to `status: \"pending\"` and API-migration origins (`origin: \"2.0-upgrade\"` or legacy `origin: \"seed_api\"`) \u2014 this is your authoritative API list and count for this turn.\n2. Read `node_modules/@superblocksteam/sdk-api/src/index.ts` and treat it as the **only** source of truth for sdk-api export/factory names.\n3. Call `getSdkApiDocs()` for the installed root README index, then retrieve every top-level section and follow every continuation before editing. This is the progressive equivalent of reading the whole root README.\n4. For each API, call `getSdkApiDocs` only for the integration(s) needed by that API right before migrating it (just-in-time). Do **not** preload every integration's documentation for the entire app.\n\nHard constraints:\n\n- Do **not** rely on prior conversation memory, \"knowledge\" summaries, or inferred export names.\n- Do **not** start editing API files until preflight steps 0\u20133 are complete.\n- If required documentation cannot be retrieved, mark that API's checklist item `failed` with a concrete `failureReason` that names the failed `getSdkApiDocs` selector or integration ID.\n\n## File layout & exports\n\n- One API per file, default export: `export default api({ ... });`.\n- Use ESM-style relative `.js` specifiers in imports.\n- File path: `server/apis/<ApiName>/api.ts` where `<ApiName>` is the YAML `metadata.name` (for example, `GetFloors` \u2192 `server/apis/GetFloors/api.ts`).\n- The `api({ name })` string and the registry key must both equal the YAML `metadata.name` verbatim \u2014 frontends call `useApi(\"<metadata.name>\")`.\n\n### Registry registration (conditional)\n\n- If `server/apis/index.ts` exists in the target tree: add an import + entry for each new module. Do not reorder existing entries.\n- If it does **not** exist: do **not** create it, do not create scaffolding. Mark the checklist item `failed` with a `failureReason` noting the missing registry.\n\n## Critical rules\n\n1. **Integration IDs are opaque per-YAML.** Extract each distinct `step.integration` UUID to a named `const` at the top of the file. Never carry UUIDs across files.\n2. **SQL: parameterize always.** Zero `${\u2026}` interpolations may remain inside any SQL string. Dynamic lists use `= ANY($N::<type>[])` \u2014 never string-building `IN (\u2026)`.\n3. **`query` vs `execute`.** Rows returned \u2192 `query` with Zod schema. Nothing actionable \u2192 `execute`.\n4. **Output shape preservation.** Mirror the legacy API's externally-visible response exactly \u2014 shape, nullability, cardinality. Do not wrap in envelopes.\n5. **Default is sequential.** `TYPE_FOREACH` \u2192 `for ... of` with sequential `await`. `Promise.all` only when YAML explicitly used a `parallel:` block.\n6. **Determinism, no slop.** No retries, no caching, no extra logging beyond a single `ctx.log.info(\"<ApiName> start\", {...})` at the top of `run`. No narrative code comments.\n7. **Never invent client methods.** If the integration README only documents `apiRequest`, use `apiRequest`.\n\n## Security / user identity\n\n- `authorization.type: AUTHORIZATION_TYPE_APP_USERS` is enforced by the server; rely on `ctx.user` in TS.\n- If the YAML accepts `userId` / `email` / etc. as API input, remove that input and read from `ctx.user` instead.\n\n## Observability\n\n- One `ctx.log.info(\"<ApiName> start\", { <safe-ids> })` at the top of `run` is allowed. Never log secrets, tokens, or PII.\n\n## Verification before you hand off\n\nRuntime verification (required):\n\n1. `build_debug` passing is required but not sufficient. Do not treat compile/typecheck success as proof that runtime behavior is correct.\n2. Use risk-based runtime checks: run `testApi` for APIs with integrations (REST/vendor/SQL), multi-step control flow, transformed outputs, or any uncertainty. For obviously simple APIs, you may skip `testApi`.\n3. If `testApi` output appears stale or mismatched, run `build_reloadFile` once and re-test. If runtime still fails after documented-method verification + one reload/retest cycle, record a concrete `failureReason` and continue.\n\nPage route verification (required once per migration run):\n\n**Hard rule:** A route is verified only with **runtime visual evidence on that exact path**. Reading `client/router.tsx`, page source, or backup artifacts is orientation only \u2014 it **never** satisfies verification.\n\n**Hard rule:** `build_debug` passing and `get_runtime_errors` returning `count: 0` are **not sufficient** for route verification. Do not mark routes `completed` because \"only APIs changed\" or \"the frontend files are unchanged.\"\n\n**Hard rule:** If `build_captureScreenshot` errors or times out for a route, mark that `migration_page_route_verification_*` item `failed` with `failureReason` naming the path and outcome (prefix `page_route_screenshot_timeout:` or `page_route_screenshot_error:`). Do **not** mark `completed`. Do **not** substitute router/source inspection.\n\n### Evidence required per route\n\nMark `completed` only when **all** are true:\n\n1. The app preview is on **that route's path** (not merely the default route).\n2. `build_captureScreenshot` **succeeds** and returns an image you inspect.\n3. You **describe** what you see and confirm it is not a loading-only view (follow the screenshot tool's skeleton/spinner retry procedure first).\n4. Any route-specific runtime errors are resolved (re-check after fixes).\n\n### Procedure (one route at a time)\n\n1. Enumerate checklist items whose IDs start with `migration_page_route_verification_`.\n2. Enumerate paths from `scratch/v2-backup/router.tsx` (fallback: `scratch/v2-backup/pages/**/index.tsx` confirmed against `client/router.tsx`).\n3. For each route: set the matching item `in_progress` \u2192 `build_navigatePreview` with that path \u2192 `build_captureScreenshot` \u2192 on success, `completed`.\n4. If the preview looks stale, `build_reloadFile` **once**, then retry screenshot. If capture still fails, `failed` with `failureReason` as above.\n5. Fix import/lazy-load/runtime failures, then repeat from step 3 for that route.\n\n### Forbidden shortcuts\n\n- Marking `completed` because `client/router.tsx` lists the path\n- Marking `completed` because the page module exists under `client/pages/`\n- Marking `completed` after screenshot timeout/error\n- Batch-marking all route items without per-route screenshot evidence\n\nFor each converted API, self-check:\n\n1. File default-exports exactly one `api({...})`; `name` matches `metadata.name`.\n2. Zero `${\u2026}` interpolations remain in any SQL string.\n3. No SQL `IN (\u2026)` built by concatenation; dynamic lists use `= ANY($N::<type>[])`.\n4. Every prior block's `.output` read is replaced by an actual result `const`.\n5. Input is the minimal union of identifiers the YAML references that are not produced by earlier blocks or `Variables`.\n6. Output shape exactly mirrors the legacy API's external response.\n7. If `server/apis/index.ts` exists, it registers the new module under `metadata.name`.\n8. **sdk-api integration wiring:** declare each integration in an `integrations: { \u2026 }` block and call it via `ctx.integrations.<key>` \u2014 never call `postgres(ID)` / `github(ID)` / etc. inside `run()` as if they were clients.\n9. **`input` / `output` schemas:** both are Zod schemas (`input: z.object({\u2026})`, `output: z.\u2026`). Do not use plain `{ field: { type: \"string\" } }` objects.\n10. **`run` signature:** `async run(ctx, input)` (or destructured input fields as the second argument). Never import `ctx` from the module scope.\n\n## Parallelization policy\n\nCount pending APIs from the checklist (`build_manageChecklist` `action: \"get\"`, filter `status: \"pending\"` and API-migration origins: `origin: \"2.0-upgrade\"` or legacy `origin: \"seed_api\"`).\n\n- **If the pending count is `< 8`:** migrate the APIs yourself, sequentially. Do NOT call `spawnCodingSubagents`. Work through each API using the per-API procedure below.\n- **If the pending count is `>= 8`:** you **MUST spawn sub-agents** to migrate these APIs in parallel. There are too many APIs to migrate sequentially yourself. Do NOT attempt to migrate APIs yourself in this run \u2014 use `spawnCodingSubagents`.\n  - Split pending APIs into batches of ~5 (aim for 4\u20135 per batch; 4 workers \u00D7 5 APIs = 20, the hard cap), with a hard cap of **4 sub-agents** and **20 APIs** in this spawn. If more APIs remain pending, leave them for a **later spawn round** after this one returns \u2014 never enlarge a worker's share.\n  - The spawn tool will reject oversized batches and will refuse to fan out under heap pressure. If it errors because the batch is too large, shrink the batch and retry. If it refuses because of heap pressure, do not retry spawn in this turn \u2014 wait for a later turn after memory has dropped. Do not fall back to migrating remaining APIs yourself while the pending count is still \u2265 8.\n  - For each batch, craft an `instructions` string that:\n    - Names the exact `<ApiName>` values that sub-agent owns, verbatim, as a bulleted list.\n    - **Directs the sub-agent to `build_readFile` `skills/system/superblocks-migration/SKILL.md` (and the integration README(s) for the APIs it owns) before writing any files.** Do not inline a shortened sdk-api contract \u2014 keep a single source of truth.\n    - Restates the per-API procedure below so the sub-agent is self-contained.\n    - Reminds the sub-agent to update the shared checklist (id `api_<ApiName>`) for every item it owns.\n    - **Restates the vacuous-pass rule and the sentinel explicitly**: the sub-agent must apply the `passed` outcome's vacuous-pass check itself (source real inputs before accepting a sad-path-only pass), and when it marks an API `completed` on an exhausted sourcing attempt it MUST set `failureReason` to `vacuous_pass_accepted: <reason>`. This is the only signal that reaches you \u2014 you run the final sweep without the sub-agents' chat context, so an unflagged vacuous pass is invisible to you.\n  - **Also pass `apiNames: [\"<ApiName1>\", \"<ApiName2>\", \u2026]` for every sub-agent**, listing the same names that appear in its `instructions`. The spawn tool stamps each `api_<ApiName>` checklist item with that sub-agent's `id` as `workerId` BEFORE fan-out, which lets the migration UI render one batch row per sub-agent in the chat sidebar. Forgetting `apiNames` is non-fatal (the sub-agents still run) but the sidebar checklist will fall back to one row per API instead of one per batch.\n  - **Call `spawnCodingSubagents` as the ONLY tool call in that turn.** Do not emit any other tool calls alongside it \u2014 no reads, no writes, no checklist updates. The tool blocks until every sub-agent finishes; you cannot do migration work \"while waiting\" because there is no waiting from your perspective \u2014 your next turn only begins after the tool returns. If you emit other tool calls in the same turn, you and the sub-agents will race on the shared checklist and corrupt state.\n  - **After `spawnCodingSubagents` returns** \u2014 only in a subsequent turn \u2014 read the checklist via `build_manageChecklist` with `action: \"get\"`. For any `failed` items, review the `failureReason`. Retry small numbers of recoverable failures yourself (sequentially, using the per-API procedure below). Leave deterministic failures as `failed`. Then re-count pending APIs; if any remain, repeat this batching step with another `spawnCodingSubagents` call. Do not proceed to the final sweep until every API item is `completed` or `failed`.\n\n## Per-API procedure\n\nFor APIs you migrate yourself, or that you embed in a sub-agent's `instructions`:\n\n1. Call `build_manageChecklist` with `action: \"update\"`, `itemId: \"api_<ApiName>\"`, `status: \"in_progress\"`.\n2. Read `scratch/v2-backup/apis/<ApiName>/api.yaml` and any sibling files the blocks reference.\n3. Produce the TypeScript module at `server/apis/<ApiName>/api.ts`, overwriting the stub. Use the YAML block \u2192 TS mapping in `skills/system/superblocks-migration/references/yaml-block-mapping.md`.\n4. If `server/apis/index.ts` exists, update it to register the new module.\n5. Call `build_debug`. If it fails, fix and repeat until it passes. Do not proceed to step 6 until `build_debug` succeeds.\n6. **Call `runMigrationVerification({ apiName: \"<ApiName>\", inputs: <inputs> })` and resolve every divergence in this same chat.** The tool's response includes `attempt` and `maxAttempts` so you don't need to track an attempt counter yourself \u2014 the server reads it from on-disk history per API.\n\n   Your job is to make v3 produce the same response as v2 \u2014 not to \"try a few times and punt to the user\". The user already lived with this API working on v2 with their real data; if v3 doesn't match, that's a regression you introduced, and you fix it here. NEVER leave a `diverged` API for the user to \"Accept divergence\" or \"Try one more attempt\" via the API calls panel \u2014 those buttons exist as escape hatches for situations the policy gate requires (mutations, denied integrations), not as a way for you to skip work.\n\n   Synthesize `inputs` the same way you would for `testApi`. Inspect the v2 YAML from step 2 (`apiInputs` / externally-declared parameters) and the v3 TS from step 3 (`input` schema on `run(ctx, input)`). Every name the caller must supply must appear as a top-level key in `inputs` with a realistic value \u2014 a mock, or a real value harvested per the \"Sourcing input values\" rules below \u2014 matching its expected type. This includes two categories \u2014 do not conflate them:\n   - **API parameters** \u2014 names declared in `apiInputs` (v2) or the v3 `input` shape (e.g. `sourceContext`, `currentDocument`, `messages`). Pass each parameter name directly as a key in `inputs`. These are what the frontend passes when it invokes the API; they are not unavailable \"runtime bindings.\"\n   - **UI bindings and caller context** \u2014 values the API reads from the app that are not API parameters (component values like `Input1.value`/`Select1.selectedItem.id`, table selections like `Table1.selectedRow`, state variables, workflow `body`/`params` not declared as `apiInputs`). Mock each binding the API references that isn't produced by an earlier block.\n\n   Both v2 and v3 receive the same `inputs`, so this is what makes the diff meaningful \u2014 `{}` for an API that expects parameters or bindings produces a vacuous `both_failed` that tells you nothing. Errors like `'sourceContext' is not defined` (v2) or v3 input-validation failures for missing required fields mean you omitted keys from `inputs`; synthesize mocks and retry. That is not an environmental failure.\n\n   **Sourcing input values \u2014 real app data over invented data.** A value is only \"realistic\" if the system the API talks to actually accepts it. Invented values are fine for self-contained inputs (a search string, a page size, a boolean flag). But when an input must reference something that already exists \u2014 any key the target system looks up, such as a row/record ID, a resource name, or an uploaded-file reference \u2014 do NOT invent it: an invented identifier either fails on both sides or exercises only the not-found/guard-clause path, and neither proves the API works. Source a real value instead, in this order:\n   1. **Harvest from the app's own APIs.** Find a read-only API in this app (prefer zero-input \"list\"/\"get all\" APIs) whose output contains the identifier you need, run it via `testApi`, and take a value from its real response. Chain as needed: a list API yields a real ID \u2192 pass it to the detail API \u2192 its response yields the next identifier. Prefer migrating and verifying zero-input read-only APIs first so their outputs become your pool of real test data.\n   2. **Follow the client code.** The `useApi`/`useApiData`/`executeApi` call sites under `client/` (and the v2 pages under `scratch/v2-backup/`) show where the app gets each input \u2014 a table's selected row, a route param, a select populated by another API. Trace that source to a concrete real value.\n   3. Only if neither path yields a value, fall back to an invented mock \u2014 and treat any resulting not-found/empty output as unverified (see the vacuous-pass rule under `passed` below).\n\n   Outcomes and how to resolve them:\n   - **`passed`**: `passed` only proves v2 and v3 agree on the inputs you supplied. Before accepting it, check what actually ran: if the shared output is a sad-path/guard-clause result \u2014 a not-found or error object from a caught exception, a validity flag that came back false, an empty result from a lookup that should have matched \u2014 the API's core logic never executed and the pass is vacuous. In that case source real inputs (per the sourcing rules above) and re-run `runMigrationVerification`; only accept a sad-path-only pass after the sourcing steps genuinely produced no usable value. Once a non-vacuous `passed` is in hand, call `build_manageChecklist` with `status: \"completed\"`. Done. If instead you are marking `completed` on an exhausted sourcing attempt (the pass stayed vacuous), you MUST also set `failureReason` to a string beginning `vacuous_pass_accepted:` followed by a one-line reason \u2014 this sentinel is the only durable signal that survives into the final sweep (and across sub-agents, whose chat context the orchestrator cannot see).\n\n   **Platform gate:** the checklist store rejects `status: \"completed\"` on `api_<ApiName>` items until verification has run at least once (`lastVerificationAt` is set \u2014 normally via this tool). You cannot bulk-mark APIs complete without calling `runMigrationVerification` per API.\n   - **`skipped_mutation`**: the runtime marks the checklist item `completed` with `verificationSkippedReason: \"mutation\"` automatically. Do **NOT** keep it `in_progress` or ask the user a grouped decision. Continue translating each API as well as you can from the code; the user will verify mutation-skipped APIs manually at finalize time.\n\n   - **`v2_unrunnable`**: the v2 backup itself couldn't execute, so there is no baseline to match. Call `build_manageChecklist` with `status: \"completed\"` and continue.\n\n   - **`timeout`**: a pipeline stalled past the reporting timeout (`side` says which one). This is transient environment noise \u2014 a dropped editor connection or a backgrounded browser tab \u2014 NOT evidence about the API. Do **NOT** mark the item `completed`. Retry `runMigrationVerification` after finishing your current API. If it times out repeatedly, tell the user verification is stalling (likely tab backgrounded / connection dropped), ask them to keep the app tab focused, and retry \u2014 never convert repeated timeouts into `completed`.\n\n   - **`disconnected`**: the editor connection was down when the pipeline tried to run (`side` says which one) \u2014 the app tab is closed, backgrounded, or reconnecting. Unlike `timeout` this diagnosis is certain, and it says nothing about the API. Do **NOT** mark the item `completed`. Tell the user the app tab must stay open and focused during verification, then retry `runMigrationVerification` \u2014 never convert `disconnected` into `completed`.\n\n   - **`both_failed`**:\n     - If you passed `inputs: {}` or omitted declared API parameters / bindings: synthesize real `inputs` (per the bullet above) and retry. Do NOT mark completed here \u2014 missing inputs caused this, not a real failure.\n     - If the error names a symbol that appears in `apiInputs` or the v3 `input` schema: add that key to `inputs` with a realistic mock and retry. Do NOT classify this as environmental \u2014 the parameter is available; you did not supply it.\n     - If you passed real inputs and v2 still failed: read v2's error. If it is environmental (auth/credentials/integration-unavailable: \"no integration configured\", \"401\", \"ECONNREFUSED\", \"missing API key\"), v2 cannot run in this verification context regardless of what you do \u2014 call `build_manageChecklist` with `status: \"completed\"` and continue; the user will verify manually. If it's a v2 runtime error that v3 also reproduces, treat as `diverged` (your inputs are wrong, or the API expects state that isn't reproducible here \u2014 revise inputs and retry).\n\n   - **`error`**: a system error in the verification flow itself (cannot read v3 source, etc.). Fix what you can; if it persists across one retry, mark the item `failed` with `failureReason: \"<error detail>\"` and continue.\n\n- **`diverged`**: the API ran on both sides and the outputs differ. **Iterate until v3 matches v2 byte-for-byte (modulo the normalizations api-comparator already applies: identical ISO timestamps, near-now ISO timestamps within \u00B160s of each other and \u00B15min of \"now\", UUIDs, monotonic integer IDs differing by \u22641 on fields whose leaf ends with \"id\", floats within 1e-9 relative tolerance, and per-request opaque identifiers at leaves named `requestId`/`traceId`/`spanId`/`correlationId`/`sessionId`/`nonce`/`csrfToken`/`_id` \u2014 note: a bare leaf named `token` is intentionally NOT normalized, since auth/access-token divergence is a security-relevant signal we want to surface).**\n\n  There is one bounded judgment exception: if both v2 and v3 executions succeeded, the output shape/types are equivalent, and the remaining diffs are value-level fields you reasonably infer are inherently non-deterministic outputs for this API, treat the migration as semantically complete for this run. In that case, mark the checklist item `completed` and continue.\n\n  Use this exception only when all of the following are true:\n  - The divergence is not structural (no missing/extra fields, no type mismatch, no changed nesting/cardinality, no changed error/status behavior).\n  - The differing fields are expected to vary per invocation and do not change control flow decisions.\n  - The API's functional contract remains intact for downstream consumers.\n\n  If any of those conditions are not met, the divergence is semantic and must be fixed \u2014 do NOT add code purely to mask values the comparator already tolerates.\n\n  For each `summaryForAgent` entry \u2014 every entry names the JSON path that diverged and the v2/v3 values \u2014 find the block in `server/apis/<ApiName>/api.ts` that produces that path and fix the discrepancy. Common causes, in rough order of frequency:\n  - wrong column projection or missing field in a SELECT\n  - missing transform / output shape mismatch (array vs object wrapper, single vs list)\n  - off-by-one or wrong placeholder in a SQL parameter\n  - mistyped binding key (case, plural, dotted path)\n  - type coercion (string vs number, null vs undefined, boolean vs \"true\")\n  - missing default value when the binding is undefined\n  - wrong join order or implicit ordering of rows\n  - filter/where condition different from v2\n  - missing `LIMIT`, `OFFSET`, or pagination handling\n\n  If a divergence stems from the `inputs` you passed (e.g. v2 echoes the input one way and v3 a different way because they normalize it differently), revise the inputs alongside the source.\n\n  Then call `build_debug` (fix any failures), then `runMigrationVerification` again with the revised source/inputs.\n\n  **There is no fixed retry budget \u2014 iterate until `passed` or until you have firm structural evidence that no v3 source change can reconcile v2 and v3.** Acceptable evidence for stopping: v2 references a YAML construct with no v3 SDK equivalent and the divergence is in that construct; v2 derives a value from runtime state v3 cannot observe (e.g. an env var that differs by environment). When you stop on structural grounds, mark the item `failed` with `failureReason: \"verification_diverged_irreconcilable: <one-paragraph reason naming the specific summaryForAgent entry and the structural reason> | summary: <JSON.stringify(summaryForAgent)>\"`.\n\n  Guardrail against infinite loops (NOT a retry budget): if you have iterated 8 times on the same API and the set of divergences has not materially changed across the last 3 attempts (i.e. you are flailing, not converging), stop and mark `failed` with the same `failureReason` shape. If you ARE converging \u2014 fewer divergences each attempt, or the remaining ones look smaller \u2014 keep going past 8.\n\n## Run-level rules\n\n- Do NOT emit a free-text UNRESOLVED report \u2014 every unresolved item must be a `failed` checklist entry with a `failureReason`.\n- Do NOT stop the run because one API failed. Only stop once every API is either `completed` or `failed`.\n\n## Updating integration write policy (Clark-only, with user consent)\n\nDuring migration, integration write policy (`allow` / `deny` per integration UUID) lives in `scratch/migration-state.json` \u2192 `integrationWritePolicy`. The pre-migration modal sets it once; **there is no mid-migration UI for the user to change it.**\n\n- **Only Clark can update write policy mid-migration**, and only when the user **explicitly asks** (e.g. \"test this API even though I set Don't test\", \"go ahead and run writes against Postgres\").\n- **Never** tell the user to update write policy in the UI \u2014 they cannot.\n- **Never** hand-edit `scratch/migration-state.json` with `build_writeFile` / `build_editFile` to change write policy. Use `updateMigrationWritePolicy` instead; it validates input and shows a permission card when granting `allow`.\n- To find integration ids: read the `const` UUID at the top of `server/apis/<ApiName>/api.ts`, or read existing keys from `scratch/migration-state.json` \u2192 `integrationWritePolicy`.\n- After updating policy to `allow` (with user approval), call `testApi` or `runMigrationVerification` again for the affected APIs.\n\nIf `testApi` is blocked by access control because an integration is still `deny`, explain that the user previously chose \"Don't test\" for that integration and ask whether they want you to update the policy and retry \u2014 do not suggest they change settings in the UI.\n\n## User-reported manual verification\n\nSome APIs are marked `completed` without automatic testing \u2014 write-policy \"Don't test\" (`verificationSkippedReason: \"mutation\"`) or a `testApi` permission denial (`verificationSkippedReason: \"testing_denied\"`). The user is expected to verify these by using the app themselves.\n\n### When the user asks how to test a skipped API\n\nIf the user requests manual test instructions for a specific API (including when the UI sends a prompt referencing `skills/system/migration-api-verification/SKILL.md`):\n\n1. Read `skills/system/migration-api-verification/SKILL.md` and follow it.\n2. Produce UI click-through steps for that API \u2014 do **NOT** call `testApi` or `runMigrationVerification`.\n\n### When the user confirms they verified an API\n\nIf the user tells you they have checked such an API and it works (e.g. \"I clicked through the app and GetOrders works, mark it complete\"), call `markApiManuallyVerified({ apiName })`. Do **NOT** call `testApi` or `runMigrationVerification` for it \u2014 the user opted out of automatic testing. This records the API as user-verified so it no longer appears in the list of APIs needing manual verification.\n\nIf the user instead asks you to **test** a denied or skipped API (not merely confirm they tested it manually), call `updateMigrationWritePolicy` first to grant `allow` for the relevant integration ids, then run `testApi` or `runMigrationVerification`.\n\n## Post-batch re-verification\n\nAfter `spawnCodingSubagents` returns (or after all sequential APIs are settled), before updating the checklist overall status:\n\n1. Call `build_manageChecklist` with `action: \"get\"` and read all items.\n2. For any item where `verificationOutcome === \"auto_passed\"` and `lastVerificationAt` is older than any sibling item's `updatedAt` minus 60 seconds: this item may have drifted due to registry edits made by later sub-agents. Re-run `runMigrationVerification({ apiName, inputs: <inputs> })` for each such item \u2014 synthesize `inputs` the same way as in step 6 of the per-API procedure, including the \"Sourcing input values\" rule (harvest real IDs from the app's read-only APIs; do not invent identifiers).\n3. If any re-verification produces `diverged`, apply the normal per-API diverge\u2192retry loop (no fixed retry budget; iterate until `passed` or firm structural-irreconcilability evidence, with the anti-flail guardrail at 8 iterations without convergence).\n4. Proceed to mark overall checklist completed/failed only after all re-verifications settle and the final sweep below is done.\n\n## Final sweep: retry unverified happy paths with real app data (required once per run)\n\nIf your closing summary would say \"I could not verify the happy path for X\" \u2014 that sentence is a trigger to do more work, not a conclusion to hand the user. Before marking the overall checklist completed/failed, do one last pass:\n\n1. From the checklist, collect every API that (a) is `failed` or unresolved because its test never succeeded, or (b) was marked `completed` but carries the `vacuous_pass_accepted:` sentinel in `failureReason` (set by you or by a sub-agent when a sad-path-only pass was accepted after exhausting sourcing).\n\n   Note on the parallel path: for APIs a sub-agent migrated, you cannot see its chat context or reconstruct its verification outputs \u2014 `verificationOutcome` records only the outcome type (`auto_passed`), not whether the pass was vacuous. The `vacuous_pass_accepted:` sentinel is therefore the ONLY way a sub-agent's vacuous pass surfaces here; APIs a sub-agent completed without it are treated as genuinely verified. This is why the sub-agent `instructions` MUST restate the vacuous-pass rule and the sentinel (see Parallelization policy). If you have specific reason to distrust a sub-agent's `completed` items (e.g. its batch reported many `both_failed` retries), re-verify them here with harvested real inputs rather than trusting the bare `completed`.\n\n2. For each, harvest real inputs from the app itself per the \"Sourcing input values\" rule in the per-API procedure: run the app's read-only APIs via `testApi` (zero-input list APIs first) and chain their real outputs into the inputs of the API under test.\n3. Re-run `runMigrationVerification` with those real inputs and resolve the outcome per the normal per-API rules.\n4. Only APIs whose sourcing steps genuinely produced no usable value (or whose failures are environmental per the `both_failed` rules) may finish the run without a happy-path verification \u2014 and each needs a `failureReason` or verification record saying so.\n";
+export declare const content = "---\nname: superblocks-migration\ndescription: |\n  Convert legacy Superblocks 2.0 YAML APIs (\"block-chain\" format) to the new 3.0 sdk-api TypeScript format.\n  Load when executing a v2\u2192v3 migration turn \u2014 the runtime prompt will tell you to.\nreadOnly: true\nmetadata:\n  author: superblocks\n  version: \"1.0\"\n---\n\n# v2 \u2192 v3 API Translation\n\nYou are converting **legacy Superblocks \"block-chain\" YAML APIs** into the **new code-mode `@superblocksteam/sdk-api` TypeScript format**. Each YAML file under `scratch/v2-backup/apis/<ApiName>/api.yaml` must be emitted as a single TypeScript file at `server/apis/<ApiName>/api.ts` that compiles, typechecks, and preserves behavior exactly.\n\n## Meta-rule: ZERO judgment calls\n\nIf any situation below is not resolved deterministically by this document, **STOP** for that API. Do **not** pick a default. Do **not** guess a factory, a shape, or an import. Skip it, continue with other APIs, and mark the checklist item as `failed` via `build_manageChecklist` with a short `failureReason` describing the exact ambiguity (failing rule, block name if any, what would be needed to proceed). This rule overrides everything else.\n\nCorollary: do not add `// TODO` comments that silently ship. Unresolved items live only as `failed` checklist entries.\n\nCorollary for `migration_page_route_verification_*`: see the _Page route verification_ section below \u2014 screenshot timeout/error \u2192 `failed`, never `completed`, never \"verified via router/source inspection.\" The full rule (including the hard-rule restatements) lives there to avoid drift.\n\n## Inputs and outputs\n\n- **Source tree:** `scratch/v2-backup/apis/<ApiName>/api.yaml`. Discover the actual set by listing the directory \u2014 do not hardcode a count or list.\n- **Target tree:** `server/apis/<ApiName>/api.ts`. Do not create scaffolding trees that do not already exist (see \"Registry registration\" below).\n- **Checklist:** the migration checklist has already been seeded with one item per API (id `api_<ApiName>`, origin `2.0-upgrade`, status `pending`, `clearOnFinalize: false`). Legacy in-flight runs may still have `origin: \"seed_api\"` for these API items. Pull the live set by calling `build_manageChecklist` with `action: \"get\"` and filtering to `status: \"pending\"` plus API-migration origins (`origin: \"2.0-upgrade\"` or legacy `origin: \"seed_api\"`) \u2014 that is your authoritative API list and count for this turn.\n\n## Required reading (read these BEFORE writing any output)\n\nAuthoritative. If a rule here conflicts with your priors, these win.\n\n1. The installed SDK root documentation through `getSdkApiDocs`. The first call of the session (preflight step 3) returns the complete shared README. Read all of it so the full api() contract, execution model, `ctx.*`, exports, error classes, performance best practices, `useApi` frontend hook, and integration method table are covered.\n2. `node_modules/@superblocksteam/sdk-api/src/index.ts` (the **barrel**) \u2014 the authoritative list of exported factory names. Integration factory names are whatever this file exports, not whatever the directory name is. Never invent or case-fold a factory name without confirming it here.\n3. Version-aware documentation for **every integration** referenced by the YAMLs you convert:\n   - Call `getSdkApiDocs` with that integration's ID (or plugin ID when no integration ID is available).\n   - If a vendor-specific factory exists for the target service (e.g., a dedicated one for a given LLM provider), prefer it over a generic HTTP one.\n4. `skills/system/superblocks-migration/references/yaml-block-mapping.md` \u2014 full YAML \u2192 TS mapping for each legacy block type.\n\nThere is **no `javascript` integration** in sdk-api \u2014 inline JS/TS lives directly inside `run(ctx, input)`. Any block whose YAML key is `javascript:` becomes plain TypeScript in `run()`. The same applies to **`python:` blocks**: there is no `python` integration in sdk-api, so port the body to inline TypeScript inside `run(ctx, input)` (see \"Substituting unsupported integrations\" below and the Python section in `yaml-block-mapping.md`).\n\n## Substituting unsupported integrations\n\nThe pre-migration UI warns the user when an app references integrations whose v2 plugin is not present in sdk-api. The migration is **not** aborted on those APIs \u2014 they are still in your `seed_api` checklist and you are expected to make a best-effort port rather than immediately marking them `failed`.\n\nSubstitution rules (apply in order; first match wins):\n\n1. **`python:` step \u2192 inline TypeScript.** Re-write the Python body as equivalent TypeScript inside `run(ctx, input)`, exactly the way `javascript:` blocks are inlined. Translate Python idioms to JS/TS (e.g. `requests.get(...)` \u2192 `fetch(...)`, list comprehensions \u2192 `array.map`/`filter`, `len(x)` \u2192 `x.length`, dict access \u2192 object property access, `os.environ[...]` \u2192 `process.env[...]`, raise/except \u2192 `throw`/`try\u2026catch`). If the Python relied on a third-party PyPI package with no obvious JS equivalent, mark that one API `failed` with a `failureReason` naming the package \u2014 do not ship a guess.\n2. **HTTP-shaped vendor plugin \u2192 REST.** If an unsupported integration was effectively making REST calls (e.g. a thin wrapper around an HTTP API) and you can read the request shape from the YAML, port it to the `restApi` factory from sdk-api (or the dedicated vendor factory if one exists in the barrel \u2014 check `node_modules/@superblocksteam/sdk-api/src/index.ts`).\n3. **Otherwise, mark `failed`.** Per the meta-rule, do not invent a factory or fabricate behavior. Use `build_manageChecklist` with `status: \"failed\"` and a concrete `failureReason` (e.g. `\"unsupported integration <pluginId> with no JS-equivalent path\"`).\n\nDo **not** silently skip a step or replace it with a `// TODO` \u2014 every API still needs a deterministic outcome (`completed` or `failed`) on the checklist.\n\n## Preflight gate (MUST pass before any file edits)\n\nComplete this orientation sequence before writing or modifying any API file:\n\n0. **Install recommended user dependencies (before API work).** The platform restructure already computed exactly which v2 user-added packages the migrated client/server code imports, and persisted them at `scratch/migration-state.json` \u2192 `recommendedUserDeps` (each entry has `name`, `version`, and `dev`). Your job is to install that list \u2014 not to recompute it.\n   - Mark `migration_dependency_verification` as `in_progress` via `build_manageChecklist`.\n   - Read `scratch/migration-state.json` and extract `recommendedUserDeps`.\n   - If `recommendedUserDeps` is missing or empty, mark `migration_dependency_verification` as `completed` and continue to step 1.\n   - Otherwise, call `build_managePackages` **once** with `action` `install` and every entry from `recommendedUserDeps` in `packages` (passing `name`, `version`, and `dev` through unchanged). Do **not** skip because `node_modules` exists on disk; the platform never wrote these packages into `package.json`.\n   - **Failure semantics (covers every non-success outcome \u2014 no judgment calls):**\n     - On full success \u2192 mark `migration_dependency_verification` as `completed`.\n     - On **any** failure \u2014 full, partial (some packages installed, others did not), structured registry error (`not_in_registry`, `registry_auth_failed`, `registry_unreachable`), or unstructured error \u2014 mark `migration_dependency_verification` as `failed` with a `failureReason` that lists the affected package names and the tool's verbatim error code or message. Treat partial success the same as full failure for checklist purposes; do not split into multiple checklist items. Then continue to step 1 so API translation can still proceed. The user/operator will repair the registry/packages and re-trigger the migration turn.\n   - If `scratch/migration-state.json` also contains `recommendedUserDepsPinnedToLatest` (a string array of package names), include those names in the `failureReason` of `migration_dependency_verification` even on full success \u2014 phrased as \"pinned to latest, may need user confirmation: <names>\" \u2014 so the user can downgrade them before runtime if the latest major is incompatible. Use status `completed` in this case (the install succeeded), but the surfaced reason gives the user a checkpoint to act on.\n   - Do **not** scan imports yourself, edit `package.json`, or add packages outside `recommendedUserDeps`. If you believe a package is missing from the list, that is a platform bug: mark `migration_dependency_verification` as `failed` with `failureReason: \"platform bug: <pkg> imported by <file> but absent from recommendedUserDeps\"` and continue with API work using the packages that did install. (`build_manageChecklist` has no `note` action \u2014 `failed` with a structured `failureReason` is the only way to record this.)\n1. Call `build_manageChecklist` with `action: \"get\"` and filter to `status: \"pending\"` and API-migration origins (`origin: \"2.0-upgrade\"` or legacy `origin: \"seed_api\"`) \u2014 this is your authoritative API list and count for this turn.\n2. Read `node_modules/@superblocksteam/sdk-api/src/index.ts` and treat it as the **only** source of truth for sdk-api export/factory names.\n3. Before editing the first API file, call `getSdkApiDocs` with that API's integration ID (or plugin ID when no integration ID is available). The first call of the session returns the complete shared root README together with that API's plugin docs. Read all of the README before editing any API file. Later calls, including the per-API calls in step 4, return plugin docs only.\n4. For each API, call `getSdkApiDocs` only for the integration(s) needed by that API right before migrating it (just-in-time). Do **not** preload every integration's documentation for the entire app.\n\nHard constraints:\n\n- Do **not** rely on prior conversation memory, \"knowledge\" summaries, or inferred export names.\n- Do **not** start editing API files until preflight steps 0\u20133 are complete.\n- If required documentation cannot be retrieved, mark that API's checklist item `failed` with a concrete `failureReason` that names the failed `getSdkApiDocs` integration ID or plugin ID.\n\n## File layout & exports\n\n- One API per file, default export: `export default api({ ... });`.\n- Use ESM-style relative `.js` specifiers in imports.\n- File path: `server/apis/<ApiName>/api.ts` where `<ApiName>` is the YAML `metadata.name` (for example, `GetFloors` \u2192 `server/apis/GetFloors/api.ts`).\n- The `api({ name })` string and the registry key must both equal the YAML `metadata.name` verbatim \u2014 frontends call `useApi(\"<metadata.name>\")`.\n\n### Registry registration (conditional)\n\n- If `server/apis/index.ts` exists in the target tree: add an import + entry for each new module. Do not reorder existing entries.\n- If it does **not** exist: do **not** create it, do not create scaffolding. Mark the checklist item `failed` with a `failureReason` noting the missing registry.\n\n## Critical rules\n\n1. **Integration IDs are opaque per-YAML.** Extract each distinct `step.integration` UUID to a named `const` at the top of the file. Never carry UUIDs across files.\n2. **SQL: parameterize always.** Zero `${\u2026}` interpolations may remain inside any SQL string. Dynamic lists use `= ANY($N::<type>[])` \u2014 never string-building `IN (\u2026)`.\n3. **`query` vs `execute`.** Rows returned \u2192 `query` with Zod schema. Nothing actionable \u2192 `execute`.\n4. **Output shape preservation.** Mirror the legacy API's externally-visible response exactly \u2014 shape, nullability, cardinality. Do not wrap in envelopes.\n5. **Default is sequential.** `TYPE_FOREACH` \u2192 `for ... of` with sequential `await`. `Promise.all` only when YAML explicitly used a `parallel:` block.\n6. **Determinism, no slop.** No retries, no caching, no extra logging beyond a single `ctx.log.info(\"<ApiName> start\", {...})` at the top of `run`. No narrative code comments.\n7. **Never invent client methods.** If the integration README only documents `apiRequest`, use `apiRequest`.\n\n## Security / user identity\n\n- `authorization.type: AUTHORIZATION_TYPE_APP_USERS` is enforced by the server; rely on `ctx.user` in TS.\n- If the YAML accepts `userId` / `email` / etc. as API input, remove that input and read from `ctx.user` instead.\n\n## Observability\n\n- One `ctx.log.info(\"<ApiName> start\", { <safe-ids> })` at the top of `run` is allowed. Never log secrets, tokens, or PII.\n\n## Verification before you hand off\n\nRuntime verification (required):\n\n1. `build_debug` passing is required but not sufficient. Do not treat compile/typecheck success as proof that runtime behavior is correct.\n2. Use risk-based runtime checks: run `testApi` for APIs with integrations (REST/vendor/SQL), multi-step control flow, transformed outputs, or any uncertainty. For obviously simple APIs, you may skip `testApi`.\n3. If `testApi` output appears stale or mismatched, run `build_reloadFile` once and re-test. If runtime still fails after documented-method verification + one reload/retest cycle, record a concrete `failureReason` and continue.\n\nPage route verification (required once per migration run):\n\n**Hard rule:** A route is verified only with **runtime visual evidence on that exact path**. Reading `client/router.tsx`, page source, or backup artifacts is orientation only \u2014 it **never** satisfies verification.\n\n**Hard rule:** `build_debug` passing and `get_runtime_errors` returning `count: 0` are **not sufficient** for route verification. Do not mark routes `completed` because \"only APIs changed\" or \"the frontend files are unchanged.\"\n\n**Hard rule:** If `build_captureScreenshot` errors or times out for a route, mark that `migration_page_route_verification_*` item `failed` with `failureReason` naming the path and outcome (prefix `page_route_screenshot_timeout:` or `page_route_screenshot_error:`). Do **not** mark `completed`. Do **not** substitute router/source inspection.\n\n### Evidence required per route\n\nMark `completed` only when **all** are true:\n\n1. The app preview is on **that route's path** (not merely the default route).\n2. `build_captureScreenshot` **succeeds** and returns an image you inspect.\n3. You **describe** what you see and confirm it is not a loading-only view (follow the screenshot tool's skeleton/spinner retry procedure first).\n4. Any route-specific runtime errors are resolved (re-check after fixes).\n\n### Procedure (one route at a time)\n\n1. Enumerate checklist items whose IDs start with `migration_page_route_verification_`.\n2. Enumerate paths from `scratch/v2-backup/router.tsx` (fallback: `scratch/v2-backup/pages/**/index.tsx` confirmed against `client/router.tsx`).\n3. For each route: set the matching item `in_progress` \u2192 `build_navigatePreview` with that path \u2192 `build_captureScreenshot` \u2192 on success, `completed`.\n4. If the preview looks stale, `build_reloadFile` **once**, then retry screenshot. If capture still fails, `failed` with `failureReason` as above.\n5. Fix import/lazy-load/runtime failures, then repeat from step 3 for that route.\n\n### Forbidden shortcuts\n\n- Marking `completed` because `client/router.tsx` lists the path\n- Marking `completed` because the page module exists under `client/pages/`\n- Marking `completed` after screenshot timeout/error\n- Batch-marking all route items without per-route screenshot evidence\n\nFor each converted API, self-check:\n\n1. File default-exports exactly one `api({...})`; `name` matches `metadata.name`.\n2. Zero `${\u2026}` interpolations remain in any SQL string.\n3. No SQL `IN (\u2026)` built by concatenation; dynamic lists use `= ANY($N::<type>[])`.\n4. Every prior block's `.output` read is replaced by an actual result `const`.\n5. Input is the minimal union of identifiers the YAML references that are not produced by earlier blocks or `Variables`.\n6. Output shape exactly mirrors the legacy API's external response.\n7. If `server/apis/index.ts` exists, it registers the new module under `metadata.name`.\n8. **sdk-api integration wiring:** declare each integration in an `integrations: { \u2026 }` block and call it via `ctx.integrations.<key>` \u2014 never call `postgres(ID)` / `github(ID)` / etc. inside `run()` as if they were clients.\n9. **`input` / `output` schemas:** both are Zod schemas (`input: z.object({\u2026})`, `output: z.\u2026`). Do not use plain `{ field: { type: \"string\" } }` objects.\n10. **`run` signature:** `async run(ctx, input)` (or destructured input fields as the second argument). Never import `ctx` from the module scope.\n\n## Parallelization policy\n\nCount pending APIs from the checklist (`build_manageChecklist` `action: \"get\"`, filter `status: \"pending\"` and API-migration origins: `origin: \"2.0-upgrade\"` or legacy `origin: \"seed_api\"`).\n\n- **If the pending count is `< 8`:** migrate the APIs yourself, sequentially. Do NOT call `spawnCodingSubagents`. Work through each API using the per-API procedure below.\n- **If the pending count is `>= 8`:** you **MUST spawn sub-agents** to migrate these APIs in parallel. There are too many APIs to migrate sequentially yourself. Do NOT attempt to migrate APIs yourself in this run \u2014 use `spawnCodingSubagents`.\n  - Split pending APIs into batches of ~5 (aim for 4\u20135 per batch; 4 workers \u00D7 5 APIs = 20, the hard cap), with a hard cap of **4 sub-agents** and **20 APIs** in this spawn. If more APIs remain pending, leave them for a **later spawn round** after this one returns \u2014 never enlarge a worker's share.\n  - The spawn tool will reject oversized batches and will refuse to fan out under heap pressure. If it errors because the batch is too large, shrink the batch and retry. If it refuses because of heap pressure, do not retry spawn in this turn \u2014 wait for a later turn after memory has dropped. Do not fall back to migrating remaining APIs yourself while the pending count is still \u2265 8.\n  - For each batch, craft an `instructions` string that:\n    - Names the exact `<ApiName>` values that sub-agent owns, verbatim, as a bulleted list.\n    - **Directs the sub-agent to `build_readFile` `skills/system/superblocks-migration/SKILL.md` (and the integration README(s) for the APIs it owns) before writing any files.** Do not inline a shortened sdk-api contract \u2014 keep a single source of truth.\n    - Restates the per-API procedure below so the sub-agent is self-contained.\n    - Reminds the sub-agent to update the shared checklist (id `api_<ApiName>`) for every item it owns.\n    - **Restates the vacuous-pass rule and the sentinel explicitly**: the sub-agent must apply the `passed` outcome's vacuous-pass check itself (source real inputs before accepting a sad-path-only pass), and when it marks an API `completed` on an exhausted sourcing attempt it MUST set `failureReason` to `vacuous_pass_accepted: <reason>`. This is the only signal that reaches you \u2014 you run the final sweep without the sub-agents' chat context, so an unflagged vacuous pass is invisible to you.\n  - **Also pass `apiNames: [\"<ApiName1>\", \"<ApiName2>\", \u2026]` for every sub-agent**, listing the same names that appear in its `instructions`. The spawn tool stamps each `api_<ApiName>` checklist item with that sub-agent's `id` as `workerId` BEFORE fan-out, which lets the migration UI render one batch row per sub-agent in the chat sidebar. Forgetting `apiNames` is non-fatal (the sub-agents still run) but the sidebar checklist will fall back to one row per API instead of one per batch.\n  - **Call `spawnCodingSubagents` as the ONLY tool call in that turn.** Do not emit any other tool calls alongside it \u2014 no reads, no writes, no checklist updates. The tool blocks until every sub-agent finishes; you cannot do migration work \"while waiting\" because there is no waiting from your perspective \u2014 your next turn only begins after the tool returns. If you emit other tool calls in the same turn, you and the sub-agents will race on the shared checklist and corrupt state.\n  - **After `spawnCodingSubagents` returns** \u2014 only in a subsequent turn \u2014 read the checklist via `build_manageChecklist` with `action: \"get\"`. For any `failed` items, review the `failureReason`. Retry small numbers of recoverable failures yourself (sequentially, using the per-API procedure below). Leave deterministic failures as `failed`. Then re-count pending APIs; if any remain, repeat this batching step with another `spawnCodingSubagents` call. Do not proceed to the final sweep until every API item is `completed` or `failed`.\n\n## Per-API procedure\n\nFor APIs you migrate yourself, or that you embed in a sub-agent's `instructions`:\n\n1. Call `build_manageChecklist` with `action: \"update\"`, `itemId: \"api_<ApiName>\"`, `status: \"in_progress\"`.\n2. Read `scratch/v2-backup/apis/<ApiName>/api.yaml` and any sibling files the blocks reference.\n3. Produce the TypeScript module at `server/apis/<ApiName>/api.ts`, overwriting the stub. Use the YAML block \u2192 TS mapping in `skills/system/superblocks-migration/references/yaml-block-mapping.md`.\n4. If `server/apis/index.ts` exists, update it to register the new module.\n5. Call `build_debug`. If it fails, fix and repeat until it passes. Do not proceed to step 6 until `build_debug` succeeds.\n6. **Call `runMigrationVerification({ apiName: \"<ApiName>\", inputs: <inputs> })` and resolve every divergence in this same chat.** The tool's response includes `attempt` and `maxAttempts` so you don't need to track an attempt counter yourself \u2014 the server reads it from on-disk history per API.\n\n   Your job is to make v3 produce the same response as v2 \u2014 not to \"try a few times and punt to the user\". The user already lived with this API working on v2 with their real data; if v3 doesn't match, that's a regression you introduced, and you fix it here. NEVER leave a `diverged` API for the user to \"Accept divergence\" or \"Try one more attempt\" via the API calls panel \u2014 those buttons exist as escape hatches for situations the policy gate requires (mutations, denied integrations), not as a way for you to skip work.\n\n   Synthesize `inputs` the same way you would for `testApi`. Inspect the v2 YAML from step 2 (`apiInputs` / externally-declared parameters) and the v3 TS from step 3 (`input` schema on `run(ctx, input)`). Every name the caller must supply must appear as a top-level key in `inputs` with a realistic value \u2014 a mock, or a real value harvested per the \"Sourcing input values\" rules below \u2014 matching its expected type. This includes two categories \u2014 do not conflate them:\n   - **API parameters** \u2014 names declared in `apiInputs` (v2) or the v3 `input` shape (e.g. `sourceContext`, `currentDocument`, `messages`). Pass each parameter name directly as a key in `inputs`. These are what the frontend passes when it invokes the API; they are not unavailable \"runtime bindings.\"\n   - **UI bindings and caller context** \u2014 values the API reads from the app that are not API parameters (component values like `Input1.value`/`Select1.selectedItem.id`, table selections like `Table1.selectedRow`, state variables, workflow `body`/`params` not declared as `apiInputs`). Mock each binding the API references that isn't produced by an earlier block.\n\n   Both v2 and v3 receive the same `inputs`, so this is what makes the diff meaningful \u2014 `{}` for an API that expects parameters or bindings produces a vacuous `both_failed` that tells you nothing. Errors like `'sourceContext' is not defined` (v2) or v3 input-validation failures for missing required fields mean you omitted keys from `inputs`; synthesize mocks and retry. That is not an environmental failure.\n\n   **Sourcing input values \u2014 real app data over invented data.** A value is only \"realistic\" if the system the API talks to actually accepts it. Invented values are fine for self-contained inputs (a search string, a page size, a boolean flag). But when an input must reference something that already exists \u2014 any key the target system looks up, such as a row/record ID, a resource name, or an uploaded-file reference \u2014 do NOT invent it: an invented identifier either fails on both sides or exercises only the not-found/guard-clause path, and neither proves the API works. Source a real value instead, in this order:\n   1. **Harvest from the app's own APIs.** Find a read-only API in this app (prefer zero-input \"list\"/\"get all\" APIs) whose output contains the identifier you need, run it via `testApi`, and take a value from its real response. Chain as needed: a list API yields a real ID \u2192 pass it to the detail API \u2192 its response yields the next identifier. Prefer migrating and verifying zero-input read-only APIs first so their outputs become your pool of real test data.\n   2. **Follow the client code.** The `useApi`/`useApiData`/`executeApi` call sites under `client/` (and the v2 pages under `scratch/v2-backup/`) show where the app gets each input \u2014 a table's selected row, a route param, a select populated by another API. Trace that source to a concrete real value.\n   3. Only if neither path yields a value, fall back to an invented mock \u2014 and treat any resulting not-found/empty output as unverified (see the vacuous-pass rule under `passed` below).\n\n   Outcomes and how to resolve them:\n   - **`passed`**: `passed` only proves v2 and v3 agree on the inputs you supplied. Before accepting it, check what actually ran: if the shared output is a sad-path/guard-clause result \u2014 a not-found or error object from a caught exception, a validity flag that came back false, an empty result from a lookup that should have matched \u2014 the API's core logic never executed and the pass is vacuous. In that case source real inputs (per the sourcing rules above) and re-run `runMigrationVerification`; only accept a sad-path-only pass after the sourcing steps genuinely produced no usable value. Once a non-vacuous `passed` is in hand, call `build_manageChecklist` with `status: \"completed\"`. Done. If instead you are marking `completed` on an exhausted sourcing attempt (the pass stayed vacuous), you MUST also set `failureReason` to a string beginning `vacuous_pass_accepted:` followed by a one-line reason \u2014 this sentinel is the only durable signal that survives into the final sweep (and across sub-agents, whose chat context the orchestrator cannot see).\n\n   **Platform gate:** the checklist store rejects `status: \"completed\"` on `api_<ApiName>` items until verification has run at least once (`lastVerificationAt` is set \u2014 normally via this tool). You cannot bulk-mark APIs complete without calling `runMigrationVerification` per API.\n   - **`skipped_mutation`**: the runtime marks the checklist item `completed` with `verificationSkippedReason: \"mutation\"` automatically. Do **NOT** keep it `in_progress` or ask the user a grouped decision. Continue translating each API as well as you can from the code; the user will verify mutation-skipped APIs manually at finalize time.\n\n   - **`v2_unrunnable`**: the v2 backup itself couldn't execute, so there is no baseline to match. Call `build_manageChecklist` with `status: \"completed\"` and continue.\n\n   - **`timeout`**: a pipeline stalled past the reporting timeout (`side` says which one). This is transient environment noise \u2014 a dropped editor connection or a backgrounded browser tab \u2014 NOT evidence about the API. Do **NOT** mark the item `completed`. Retry `runMigrationVerification` after finishing your current API. If it times out repeatedly, tell the user verification is stalling (likely tab backgrounded / connection dropped), ask them to keep the app tab focused, and retry \u2014 never convert repeated timeouts into `completed`.\n\n   - **`disconnected`**: the editor connection was down when the pipeline tried to run (`side` says which one) \u2014 the app tab is closed, backgrounded, or reconnecting. Unlike `timeout` this diagnosis is certain, and it says nothing about the API. Do **NOT** mark the item `completed`. Tell the user the app tab must stay open and focused during verification, then retry `runMigrationVerification` \u2014 never convert `disconnected` into `completed`.\n\n   - **`both_failed`**:\n     - If you passed `inputs: {}` or omitted declared API parameters / bindings: synthesize real `inputs` (per the bullet above) and retry. Do NOT mark completed here \u2014 missing inputs caused this, not a real failure.\n     - If the error names a symbol that appears in `apiInputs` or the v3 `input` schema: add that key to `inputs` with a realistic mock and retry. Do NOT classify this as environmental \u2014 the parameter is available; you did not supply it.\n     - If you passed real inputs and v2 still failed: read v2's error. If it is environmental (auth/credentials/integration-unavailable: \"no integration configured\", \"401\", \"ECONNREFUSED\", \"missing API key\"), v2 cannot run in this verification context regardless of what you do \u2014 call `build_manageChecklist` with `status: \"completed\"` and continue; the user will verify manually. If it's a v2 runtime error that v3 also reproduces, treat as `diverged` (your inputs are wrong, or the API expects state that isn't reproducible here \u2014 revise inputs and retry).\n\n   - **`error`**: a system error in the verification flow itself (cannot read v3 source, etc.). Fix what you can; if it persists across one retry, mark the item `failed` with `failureReason: \"<error detail>\"` and continue.\n\n- **`diverged`**: the API ran on both sides and the outputs differ. **Iterate until v3 matches v2 byte-for-byte (modulo the normalizations api-comparator already applies: identical ISO timestamps, near-now ISO timestamps within \u00B160s of each other and \u00B15min of \"now\", UUIDs, monotonic integer IDs differing by \u22641 on fields whose leaf ends with \"id\", floats within 1e-9 relative tolerance, and per-request opaque identifiers at leaves named `requestId`/`traceId`/`spanId`/`correlationId`/`sessionId`/`nonce`/`csrfToken`/`_id` \u2014 note: a bare leaf named `token` is intentionally NOT normalized, since auth/access-token divergence is a security-relevant signal we want to surface).**\n\n  There is one bounded judgment exception: if both v2 and v3 executions succeeded, the output shape/types are equivalent, and the remaining diffs are value-level fields you reasonably infer are inherently non-deterministic outputs for this API, treat the migration as semantically complete for this run. In that case, mark the checklist item `completed` and continue.\n\n  Use this exception only when all of the following are true:\n  - The divergence is not structural (no missing/extra fields, no type mismatch, no changed nesting/cardinality, no changed error/status behavior).\n  - The differing fields are expected to vary per invocation and do not change control flow decisions.\n  - The API's functional contract remains intact for downstream consumers.\n\n  If any of those conditions are not met, the divergence is semantic and must be fixed \u2014 do NOT add code purely to mask values the comparator already tolerates.\n\n  For each `summaryForAgent` entry \u2014 every entry names the JSON path that diverged and the v2/v3 values \u2014 find the block in `server/apis/<ApiName>/api.ts` that produces that path and fix the discrepancy. Common causes, in rough order of frequency:\n  - wrong column projection or missing field in a SELECT\n  - missing transform / output shape mismatch (array vs object wrapper, single vs list)\n  - off-by-one or wrong placeholder in a SQL parameter\n  - mistyped binding key (case, plural, dotted path)\n  - type coercion (string vs number, null vs undefined, boolean vs \"true\")\n  - missing default value when the binding is undefined\n  - wrong join order or implicit ordering of rows\n  - filter/where condition different from v2\n  - missing `LIMIT`, `OFFSET`, or pagination handling\n\n  If a divergence stems from the `inputs` you passed (e.g. v2 echoes the input one way and v3 a different way because they normalize it differently), revise the inputs alongside the source.\n\n  Then call `build_debug` (fix any failures), then `runMigrationVerification` again with the revised source/inputs.\n\n  **There is no fixed retry budget \u2014 iterate until `passed` or until you have firm structural evidence that no v3 source change can reconcile v2 and v3.** Acceptable evidence for stopping: v2 references a YAML construct with no v3 SDK equivalent and the divergence is in that construct; v2 derives a value from runtime state v3 cannot observe (e.g. an env var that differs by environment). When you stop on structural grounds, mark the item `failed` with `failureReason: \"verification_diverged_irreconcilable: <one-paragraph reason naming the specific summaryForAgent entry and the structural reason> | summary: <JSON.stringify(summaryForAgent)>\"`.\n\n  Guardrail against infinite loops (NOT a retry budget): if you have iterated 8 times on the same API and the set of divergences has not materially changed across the last 3 attempts (i.e. you are flailing, not converging), stop and mark `failed` with the same `failureReason` shape. If you ARE converging \u2014 fewer divergences each attempt, or the remaining ones look smaller \u2014 keep going past 8.\n\n## Run-level rules\n\n- Do NOT emit a free-text UNRESOLVED report \u2014 every unresolved item must be a `failed` checklist entry with a `failureReason`.\n- Do NOT stop the run because one API failed. Only stop once every API is either `completed` or `failed`.\n\n## Updating integration write policy (Clark-only, with user consent)\n\nDuring migration, integration write policy (`allow` / `deny` per integration UUID) lives in `scratch/migration-state.json` \u2192 `integrationWritePolicy`. The pre-migration modal sets it once; **there is no mid-migration UI for the user to change it.**\n\n- **Only Clark can update write policy mid-migration**, and only when the user **explicitly asks** (e.g. \"test this API even though I set Don't test\", \"go ahead and run writes against Postgres\").\n- **Never** tell the user to update write policy in the UI \u2014 they cannot.\n- **Never** hand-edit `scratch/migration-state.json` with `build_writeFile` / `build_editFile` to change write policy. Use `updateMigrationWritePolicy` instead; it validates input and shows a permission card when granting `allow`.\n- To find integration ids: read the `const` UUID at the top of `server/apis/<ApiName>/api.ts`, or read existing keys from `scratch/migration-state.json` \u2192 `integrationWritePolicy`.\n- After updating policy to `allow` (with user approval), call `testApi` or `runMigrationVerification` again for the affected APIs.\n\nIf `testApi` is blocked by access control because an integration is still `deny`, explain that the user previously chose \"Don't test\" for that integration and ask whether they want you to update the policy and retry \u2014 do not suggest they change settings in the UI.\n\n## User-reported manual verification\n\nSome APIs are marked `completed` without automatic testing \u2014 write-policy \"Don't test\" (`verificationSkippedReason: \"mutation\"`) or a `testApi` permission denial (`verificationSkippedReason: \"testing_denied\"`). The user is expected to verify these by using the app themselves.\n\n### When the user asks how to test a skipped API\n\nIf the user requests manual test instructions for a specific API (including when the UI sends a prompt referencing `skills/system/migration-api-verification/SKILL.md`):\n\n1. Read `skills/system/migration-api-verification/SKILL.md` and follow it.\n2. Produce UI click-through steps for that API \u2014 do **NOT** call `testApi` or `runMigrationVerification`.\n\n### When the user confirms they verified an API\n\nIf the user tells you they have checked such an API and it works (e.g. \"I clicked through the app and GetOrders works, mark it complete\"), call `markApiManuallyVerified({ apiName })`. Do **NOT** call `testApi` or `runMigrationVerification` for it \u2014 the user opted out of automatic testing. This records the API as user-verified so it no longer appears in the list of APIs needing manual verification.\n\nIf the user instead asks you to **test** a denied or skipped API (not merely confirm they tested it manually), call `updateMigrationWritePolicy` first to grant `allow` for the relevant integration ids, then run `testApi` or `runMigrationVerification`.\n\n## Post-batch re-verification\n\nAfter `spawnCodingSubagents` returns (or after all sequential APIs are settled), before updating the checklist overall status:\n\n1. Call `build_manageChecklist` with `action: \"get\"` and read all items.\n2. For any item where `verificationOutcome === \"auto_passed\"` and `lastVerificationAt` is older than any sibling item's `updatedAt` minus 60 seconds: this item may have drifted due to registry edits made by later sub-agents. Re-run `runMigrationVerification({ apiName, inputs: <inputs> })` for each such item \u2014 synthesize `inputs` the same way as in step 6 of the per-API procedure, including the \"Sourcing input values\" rule (harvest real IDs from the app's read-only APIs; do not invent identifiers).\n3. If any re-verification produces `diverged`, apply the normal per-API diverge\u2192retry loop (no fixed retry budget; iterate until `passed` or firm structural-irreconcilability evidence, with the anti-flail guardrail at 8 iterations without convergence).\n4. Proceed to mark overall checklist completed/failed only after all re-verifications settle and the final sweep below is done.\n\n## Final sweep: retry unverified happy paths with real app data (required once per run)\n\nIf your closing summary would say \"I could not verify the happy path for X\" \u2014 that sentence is a trigger to do more work, not a conclusion to hand the user. Before marking the overall checklist completed/failed, do one last pass:\n\n1. From the checklist, collect every API that (a) is `failed` or unresolved because its test never succeeded, or (b) was marked `completed` but carries the `vacuous_pass_accepted:` sentinel in `failureReason` (set by you or by a sub-agent when a sad-path-only pass was accepted after exhausting sourcing).\n\n   Note on the parallel path: for APIs a sub-agent migrated, you cannot see its chat context or reconstruct its verification outputs \u2014 `verificationOutcome` records only the outcome type (`auto_passed`), not whether the pass was vacuous. The `vacuous_pass_accepted:` sentinel is therefore the ONLY way a sub-agent's vacuous pass surfaces here; APIs a sub-agent completed without it are treated as genuinely verified. This is why the sub-agent `instructions` MUST restate the vacuous-pass rule and the sentinel (see Parallelization policy). If you have specific reason to distrust a sub-agent's `completed` items (e.g. its batch reported many `both_failed` retries), re-verify them here with harvested real inputs rather than trusting the bare `completed`.\n\n2. For each, harvest real inputs from the app itself per the \"Sourcing input values\" rule in the per-API procedure: run the app's read-only APIs via `testApi` (zero-input list APIs first) and chain their real outputs into the inputs of the API under test.\n3. Re-run `runMigrationVerification` with those real inputs and resolve the outcome per the normal per-API rules.\n4. Only APIs whose sourcing steps genuinely produced no usable value (or whose failures are environmental per the `both_failed` rules) may finish the run without a happy-path verification \u2014 and each needs a `failureReason` or verification record saying so.\n";
 //# sourceMappingURL=skill.generated.d.ts.map

package/dist/ai-service/skills/system/superblocks-migration/skill.generated.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"skill.generated.d.ts","sourceRoot":"","sources":["../../../../../src/ai-service/skills/system/superblocks-migration/skill.generated.ts"],"names":[],"mappings":"AAGA,eAAO,MAAM,OAAO,m+tCAoTnB,CAAC"}
+{"version":3,"file":"skill.generated.d.ts","sourceRoot":"","sources":["../../../../../src/ai-service/skills/system/superblocks-migration/skill.generated.ts"],"names":[],"mappings":"AAGA,eAAO,MAAM,OAAO,2luCAoTnB,CAAC"}

package/dist/ai-service/skills/system/superblocks-migration/skill.generated.js

@@ -33,7 +33,7 @@ Corollary for \`migration_page_route_verification_*\`: see the _Page route verif
 
 Authoritative. If a rule here conflicts with your priors, these win.
 
-1. The installed SDK root documentation through \`getSdkApiDocs\` — call it with no arguments for the current section index, then retrieve every top-level section (following every \`root.continuation\`) so the full api() contract, execution model, \`ctx.*\`, exports, error classes, performance best practices, \`useApi\` frontend hook, and integration method table are covered without loading the whole README at once.
+1. The installed SDK root documentation through \`getSdkApiDocs\`. The first call of the session (preflight step 3) returns the complete shared README. Read all of it so the full api() contract, execution model, \`ctx.*\`, exports, error classes, performance best practices, \`useApi\` frontend hook, and integration method table are covered.
 2. \`node_modules/@superblocksteam/sdk-api/src/index.ts\` (the **barrel**) — the authoritative list of exported factory names. Integration factory names are whatever this file exports, not whatever the directory name is. Never invent or case-fold a factory name without confirming it here.
 3. Version-aware documentation for **every integration** referenced by the YAMLs you convert:
    - Call \`getSdkApiDocs\` with that integration's ID (or plugin ID when no integration ID is available).
@@ -62,7 +62,7 @@ Complete this orientation sequence before writing or modifying any API file:
    - Mark \`migration_dependency_verification\` as \`in_progress\` via \`build_manageChecklist\`.
    - Read \`scratch/migration-state.json\` and extract \`recommendedUserDeps\`.
    - If \`recommendedUserDeps\` is missing or empty, mark \`migration_dependency_verification\` as \`completed\` and continue to step 1.
-   - Otherwise, call \`build_installPackages\` **once** with every entry from \`recommendedUserDeps\` (passing \`name\`, \`version\`, and \`dev\` through unchanged). Do **not** skip because \`node_modules\` exists on disk; the platform never wrote these packages into \`package.json\`.
+   - Otherwise, call \`build_managePackages\` **once** with \`action\` \`install\` and every entry from \`recommendedUserDeps\` in \`packages\` (passing \`name\`, \`version\`, and \`dev\` through unchanged). Do **not** skip because \`node_modules\` exists on disk; the platform never wrote these packages into \`package.json\`.
    - **Failure semantics (covers every non-success outcome — no judgment calls):**
      - On full success → mark \`migration_dependency_verification\` as \`completed\`.
      - On **any** failure — full, partial (some packages installed, others did not), structured registry error (\`not_in_registry\`, \`registry_auth_failed\`, \`registry_unreachable\`), or unstructured error — mark \`migration_dependency_verification\` as \`failed\` with a \`failureReason\` that lists the affected package names and the tool's verbatim error code or message. Treat partial success the same as full failure for checklist purposes; do not split into multiple checklist items. Then continue to step 1 so API translation can still proceed. The user/operator will repair the registry/packages and re-trigger the migration turn.
@@ -70,14 +70,14 @@ Complete this orientation sequence before writing or modifying any API file:
    - Do **not** scan imports yourself, edit \`package.json\`, or add packages outside \`recommendedUserDeps\`. If you believe a package is missing from the list, that is a platform bug: mark \`migration_dependency_verification\` as \`failed\` with \`failureReason: "platform bug: <pkg> imported by <file> but absent from recommendedUserDeps"\` and continue with API work using the packages that did install. (\`build_manageChecklist\` has no \`note\` action — \`failed\` with a structured \`failureReason\` is the only way to record this.)
 1. Call \`build_manageChecklist\` with \`action: "get"\` and filter to \`status: "pending"\` and API-migration origins (\`origin: "2.0-upgrade"\` or legacy \`origin: "seed_api"\`) — this is your authoritative API list and count for this turn.
 2. Read \`node_modules/@superblocksteam/sdk-api/src/index.ts\` and treat it as the **only** source of truth for sdk-api export/factory names.
-3. Call \`getSdkApiDocs()\` for the installed root README index, then retrieve every top-level section and follow every continuation before editing. This is the progressive equivalent of reading the whole root README.
+3. Before editing the first API file, call \`getSdkApiDocs\` with that API's integration ID (or plugin ID when no integration ID is available). The first call of the session returns the complete shared root README together with that API's plugin docs. Read all of the README before editing any API file. Later calls, including the per-API calls in step 4, return plugin docs only.
 4. For each API, call \`getSdkApiDocs\` only for the integration(s) needed by that API right before migrating it (just-in-time). Do **not** preload every integration's documentation for the entire app.
 
 Hard constraints:
 
 - Do **not** rely on prior conversation memory, "knowledge" summaries, or inferred export names.
 - Do **not** start editing API files until preflight steps 0–3 are complete.
-- If required documentation cannot be retrieved, mark that API's checklist item \`failed\` with a concrete \`failureReason\` that names the failed \`getSdkApiDocs\` selector or integration ID.
+- If required documentation cannot be retrieved, mark that API's checklist item \`failed\` with a concrete \`failureReason\` that names the failed \`getSdkApiDocs\` integration ID or plugin ID.
 
 ## File layout & exports
 

package/dist/ai-service/skills/system/superblocks-sdk-api/skill.generated.d.ts

@@ -1,2 +1,2 @@
-export declare const content = "---\nname: superblocks-sdk-api\ndescription: |\n  Retrieve authoritative SDK API and integration guidance progressively before creating or editing SDK APIs.\nreadOnly: true\nmetadata:\n  author: superblocks\n  version: \"1.0\"\n---\n\n# SDK API documentation workflow\n\nUse `getSdkApiDocs` as the authoritative SDK documentation interface. Do not read SDK README files directly and do not fetch newer documentation from the internet: the tool reads the installed `@superblocksteam/sdk-api` package and applies plugin/orchestrator version overlays.\n\nThe root README reflects that installed package and is not proof that every statement matches a customer's execution runtime. Plugin documentation remains compatibility-aware: the tool resolves overlays using both the integration execution version and the orchestrator's `javascriptsdkapi` version.\n\n## Before writing or modifying an SDK API\n\n1. Call `getSdkApiDocs` with the app's integration IDs whenever available. Use the returned version-aware plugin guidance for integration methods and signatures.\n2. For shared SDK rules, call `getSdkApiDocs()` with no arguments. This returns a compact index derived from the installed root README, not the full document.\n3. Request only the relevant root entry with `getSdkApiDocs({ section: \"<id>\" })`.\n4. If the result contains `root.continuation`, retrieve the rest with `getSdkApiDocs({ continuation: \"<exact token>\" })`. Continue until no token is returned. Never repeat the original section call to get the next chunk.\n5. If a section or continuation is stale or unknown, use the refreshed index in the response and restart from the current section ID.\n\nKeep exact `section`, `continuation`, integration ID, and plugin ID arguments when refetching after compaction. SDK signatures, examples, and detailed implementation rules remain in `getSdkApiDocs`; do not infer or duplicate them from this skill.\n";
+export declare const content = "---\nname: superblocks-sdk-api\ndescription: |\n  Retrieve authoritative SDK API and integration guidance before creating or editing SDK APIs.\nreadOnly: true\nmetadata:\n  author: superblocks\n  version: \"1.0\"\n---\n\n# SDK API documentation workflow\n\nUse `getSdkApiDocs` as the authoritative SDK documentation interface. Do not read SDK README files directly and do not fetch newer documentation from the internet: the tool reads the installed `@superblocksteam/sdk-api` package and applies plugin/orchestrator version overlays.\n\nThe root README reflects that installed package and is not proof that every statement matches a customer's execution runtime. Plugin documentation remains compatibility-aware: the tool resolves overlays using both the integration execution version and the orchestrator's `javascriptsdkapi` version.\n\n## Before writing or modifying an SDK API\n\n1. Call `getSdkApiDocs({ integrationIds })` with the app's integration IDs whenever available, or `getSdkApiDocs({ pluginIds })` when the integration does not exist yet. The first call in a session returns the complete shared SDK README plus the plugin docs. Read it before writing or modifying any `server/apis/**` file.\n2. Repeat calls with IDs return plugin docs only; the README is not repeated while it is still in context.\n3. If neither integration IDs nor plugin IDs are known, call `getSdkApiDocs()` with no arguments. It returns the same complete shared SDK README on the first call in a session and the shared guidance alone afterwards.\n\nSDK signatures, examples, and detailed implementation rules remain in `getSdkApiDocs`; do not infer or duplicate them from this skill.\n\n`testApi` returns `timing`. `roundTripMs` runs from sending the request until the editor answered or the call failed, including file sync and authentication. `executionMs` is how long the API ran, as measured by the orchestrator, when it reports one. `integrationCallCount` and `integrationTotalMs` are the number and summed duration of its integration calls.\n";
 //# sourceMappingURL=skill.generated.d.ts.map

package/dist/ai-service/skills/system/superblocks-sdk-api/skill.generated.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"skill.generated.d.ts","sourceRoot":"","sources":["../../../../../src/ai-service/skills/system/superblocks-sdk-api/skill.generated.ts"],"names":[],"mappings":"AAGA,eAAO,MAAM,OAAO,k4DAyBnB,CAAC"}
+{"version":3,"file":"skill.generated.d.ts","sourceRoot":"","sources":["../../../../../src/ai-service/skills/system/superblocks-sdk-api/skill.generated.ts"],"names":[],"mappings":"AAGA,eAAO,MAAM,OAAO,y/DAyBnB,CAAC"}

package/dist/ai-service/skills/system/superblocks-sdk-api/skill.generated.js

@@ -3,7 +3,7 @@
 export const content = `---
 name: superblocks-sdk-api
 description: |
-  Retrieve authoritative SDK API and integration guidance progressively before creating or editing SDK APIs.
+  Retrieve authoritative SDK API and integration guidance before creating or editing SDK APIs.
 readOnly: true
 metadata:
   author: superblocks
@@ -18,12 +18,12 @@ The root README reflects that installed package and is not proof that every stat
 
 ## Before writing or modifying an SDK API
 
-1. Call \`getSdkApiDocs\` with the app's integration IDs whenever available. Use the returned version-aware plugin guidance for integration methods and signatures.
-2. For shared SDK rules, call \`getSdkApiDocs()\` with no arguments. This returns a compact index derived from the installed root README, not the full document.
-3. Request only the relevant root entry with \`getSdkApiDocs({ section: "<id>" })\`.
-4. If the result contains \`root.continuation\`, retrieve the rest with \`getSdkApiDocs({ continuation: "<exact token>" })\`. Continue until no token is returned. Never repeat the original section call to get the next chunk.
-5. If a section or continuation is stale or unknown, use the refreshed index in the response and restart from the current section ID.
+1. Call \`getSdkApiDocs({ integrationIds })\` with the app's integration IDs whenever available, or \`getSdkApiDocs({ pluginIds })\` when the integration does not exist yet. The first call in a session returns the complete shared SDK README plus the plugin docs. Read it before writing or modifying any \`server/apis/**\` file.
+2. Repeat calls with IDs return plugin docs only; the README is not repeated while it is still in context.
+3. If neither integration IDs nor plugin IDs are known, call \`getSdkApiDocs()\` with no arguments. It returns the same complete shared SDK README on the first call in a session and the shared guidance alone afterwards.
 
-Keep exact \`section\`, \`continuation\`, integration ID, and plugin ID arguments when refetching after compaction. SDK signatures, examples, and detailed implementation rules remain in \`getSdkApiDocs\`; do not infer or duplicate them from this skill.
+SDK signatures, examples, and detailed implementation rules remain in \`getSdkApiDocs\`; do not infer or duplicate them from this skill.
+
+\`testApi\` returns \`timing\`. \`roundTripMs\` runs from sending the request until the editor answered or the call failed, including file sync and authentication. \`executionMs\` is how long the API ran, as measured by the orchestrator, when it reports one. \`integrationCallCount\` and \`integrationTotalMs\` are the number and summed duration of its integration calls.
 `;
 //# sourceMappingURL=skill.generated.js.map

package/dist/ai-service/skills/system/third-party-migration/skill.generated.d.ts

@@ -1,2 +1,2 @@
-export declare const content = "---\nname: third-party-migration\ndescription: |\n  Migrate a third-party app (Replit, Streamlit, Lovable, v0, or similar) into a Superblocks 3.0 full-stack app.\n  Load when the user asks to migrate, import, or port an external app \u2014 or when the source tree contains hallmarks of a supported platform (`replit.md` / `.replit`, `streamlit_app.py`, `.streamlit/config.toml`, `import streamlit as st`, `src/integrations/supabase/`, `supabase/functions/`, `lovable-tagger`, an `app/` directory with `next.config.*` and `\"use client\"` / `\"use server\"` directives, etc.) and the user wants it turned into a Superblocks app.\nreadOnly: true\nmetadata:\n  author: superblocks\n  version: \"1.0\"\n---\n\n# Third-Party App \u2192 Superblocks 3.0 Migration\n\nPort a user-provided external app into the Superblocks fullstack app you are running inside (template: `app-fullstack`). The source tree is **read-only material**. All edits land in the target app under `server/` and `client/`.\n\nThis file is the migration framework. **Per-platform mapping rules live in sibling files** \u2014 load the right one before you start mapping.\n\n## Checklist is mandatory\n\nChecklist discipline is required for every migration run:\n\n- Before any file edits, ensure migration checklist items are seeded via `build_manageChecklist`.\n- Before editing an item, mark it `in_progress`.\n- After the edit lands, mark it `completed`, or `failed` with a concrete `failureReason` if deterministic completion is impossible.\n- When you need an item to survive `build_finalize`, set `clearOnFinalize: false` on add/update. Use this only for migration-tracking items that must persist until explicit migration completion.\n- Do not continue implementation if checklist state is missing, stale, or inconsistent with the work you are doing. Fix checklist state first.\n- Free-text progress updates are never a substitute for checklist updates.\n\n## Identify the source platform\n\nMatch the source tree against these signals, then read the matching reference file in this folder. Read it once, up-front \u2014 it tells you what shapes to look for and how each maps to Superblocks.\n\n- **Replit** \u2014 `replit.md`, `.replit`, `artifacts/`, an Express server with an Orval-generated client. \u2192 load `replit.md`.\n- **Streamlit** \u2014 `streamlit_app.py`, `.streamlit/config.toml`, dependency files containing `streamlit`, Python files with `import streamlit as st`, or a Python `pages/` multipage app structure. Follow the general guidelines in this document.\n- **Lovable** \u2014 `src/integrations/supabase/client.ts`, `supabase/config.toml`, `supabase/functions/`, `supabase/migrations/`, `lovable-tagger` in `vite.config.ts`. \u2192 load `lovable.md`.\n- **v0** \u2014 `app/<segment>/page.tsx` (Next.js App Router) plus `next.config.{js,mjs,ts}` and `next` in `package.json`, files with `\"use client\"` / `\"use server\"` directives, `next/link` / `next/navigation` imports, `components/ui/` with shadcn primitives. \u2192 load `v0.md`.\n- **Claude Design** \u2014 a frontend-only prototype (no `package.json`, no `node_modules`, no build config) whose durable hallmarks are: React + ReactDOM + `@babel/standalone` loaded from a CDN; `<script type=\"text/babel\" src=\"...\">` for JSX files; `/*EDITMODE-BEGIN*/ ... /*EDITMODE-END*/` markers in defaults blocks; `useTweaks` / `TweaksPanel` / `TweakSection` / `TweakToggle` window globals; `<html data-theme=\"...\">` with CSS variables such as `var(--accent)` / `var(--ink)`. A **common** layout is a flat archive with one top-level `<Name>.html` plus sibling `app.jsx`, `data.js` (or `data.jsx`), and `tweaks-panel.jsx` \u2014 but exports may nest modules under a project directory, include a large bundler-style standalone HTML at the archive root, ship an embedded design-system bundle (e.g. `_ds/`), or duplicate stale files at the root vs a nested folder. When layout deviates, rely on the durable hallmarks and the actual tree \u2014 do not force the flat-archive shape. \u2192 load `claude-design.md`.\n- **Ambiguous or neither** \u2014 stop and ask the user which platform the source came from. Do not guess. It is possible that it is No Platform. In this case, follow the general guidelines in this document and ask user questions for any ambiguity.\n\nWhen a source only **partially** matches a platform's hallmarks, do not abandon identification or reshape the tree to fit the canonical checklist. Explore the actual archive, confirm via durable signals, use best judgment to find the real entry point and module layout, and `askMultiChoice` on genuine ambiguity rather than forcing a textbook export shape.\n\nThe framework below applies to every platform; the platform file fills in the source-specific mapping.\n\n## Target layout\n\nThe app you are running inside looks like this. Do not invent new top-level directories.\n\n```\nclient/\n  App.tsx           \u2014 root with <AppProvider> + <Outlet />\n  router.tsx        \u2014 react-router v7 data mode (`createBrowserRouter`); see Router shape below\n  index.css         \u2014 Tailwind v4 + theme tokens\n  hooks/\n    useApi.ts       \u2014 typed wrapper around useTypedApi<ApiRegistry>\n    useApiData.ts   \u2014 typed wrapper around useTypedApiData<ApiRegistry>\n  lib/executeApi.ts \u2014 non-React typed executeApi\n  pages/<Name>/index.tsx\n  components/ui/    \u2014 shadcn primitives (do not modify)\nserver/\n  apis/\n    index.ts        \u2014 registry: `const apis = { ApiName: ... } as const;`\n    <ApiName>/api.ts\n```\n\n## Universal mapping (applies to every source)\n\nThese hold regardless of source platform. Per-platform specifics layer on top.\n\n- APIs are addressed by `name` via the registry \u2014 there is no URL path. Within `api()`:\n  - All inputs (whatever shape the source had \u2014 body, query, params, function args) \u2192 one unified `input` Zod schema; destructure inside `run(ctx, { ... })`.\n  - The handler's response \u2192 `return { ... }` from `run`. The `output` schema validates it automatically; do not `safeParse` by hand.\n  - Auth \u2192 `ctx.user` (`userId`, `email`, `name`, `groups`, `customClaims`). Auth is platform-managed; drop the source's auth flows entirely.\n  - Errors \u2192 throw the `SdkError` subtypes the sdk-api README documents (`InputValidationError`, `OutputValidationError`, `IntegrationError`, `ExecutionError`). Never invent error classes or return HTTP status codes.\n  - DB clients (`pg`, `knex`, `prisma`, Drizzle, `supabase.from(...)`) \u2192 declare in `integrations: { db: postgres(DB_INTEGRATION_ID) }` and call `ctx.integrations.db.query(sql, ZodSchema, params, { label: \"...\" })` / `.execute(...)`. Parameterized SQL only. Hold integration UUIDs in module-level `const`s, not literals scattered through `run`.\n  - External HTTP (`axios`, `fetch`, third-party SDKs) \u2192 declared integration + `ctx.integrations.<name>.apiRequest({ method, path, body }, { response: ZodSchema })`.\n  - `process.env.*` / `import.meta.env.*` / `Deno.env.get(...)` \u2192 `ctx.env`. Logging \u2192 `ctx.log.info/warn/error/debug(msg, data?)`.\n  - Server bootstrapping (`app.listen`, CORS, route grouping, middleware setup, `Deno.serve`) \u2192 drop entirely. The platform handles it.\n- **Each frontend page \u2192 one Superblocks page** at `client/pages/<Name>/index.tsx`, wired into `client/router.tsx`.\n- **Each backend data source (DB, REST client, S3, ...) \u2192 one Superblocks integration** referenced by UUID. Credentials live on the integration, never in code.\n\n### Router shape (`client/router.tsx`)\n\nThe editor parses this file statically to build the page list and route table. **Use one of the supported page-component bindings \u2014 anything else silently drops every route and the editor shows a \"404 / route has been deleted\" overlay.**\n\nSupported page bindings (mix freely):\n\n```tsx\n// 1. Inline lazy on the route object (preferred \u2014 matches the template):\n{ path: \"about\", lazy: () => import(\"./pages/About/index.tsx\").then(m => ({ Component: m.default })) }\n\n// 2. Static default import + Component / element:\nimport About from \"./pages/About/index.tsx\";\n{ path: \"about\", Component: About }\n{ path: \"about\", element: <About /> }\n\n// 3. Top-level `const` bound to React.lazy + Component / element:\nconst About = lazy(() => import(\"./pages/About/index.tsx\"));\n{ path: \"about\", Component: About }\n```\n\nDo **not**: assign `Component` / `element` to identifiers bound by anything other than a static import or `lazy(() => import(\"...\"))` (no IIFEs, no helper wrappers, no conditional `lazy(...)`, no objects whose keys are computed from a loop). The parser only resolves the shapes above.\n\n## Authoritative references (read just-in-time, not up front)\n\n- `getSdkApiDocs` and `node_modules/@superblocksteam/sdk-api/src/index.ts` \u2014 use the tool's root section index for the server `api()` contract and the barrel for the full list of factory names. Follow `root.continuation` exactly. **Never invent factory names.** If required documentation or the barrel is unavailable, mark the affected checklist item `failed` with the failed selector or missing path as the reason.\n- Version-aware per-integration documentation from `getSdkApiDocs` \u2014 retrieve once, with an integration ID when possible, when you first emit an API that uses that integration.\n- `skills/system/superblocks-frontend/SKILL.md` - the target client's API-hook behavior and loading-state contract.\n\n> \u26A0\uFE0F **Never** load `skills/system/superblocks-api/SKILL.md`. It describes a different, block-based API pattern that is incompatible with the fullstack template's `sdk-api`. Mixing them produces code that does not compile.\n\n## Non-negotiables\n\n1. **Track everything in the checklist.** The **first tool call after exiting plan mode** or **during build mode, before building** is `build_manageChecklist` to seed. Before every per-item edit, `update <itemId> in_progress`; after, `update <itemId> completed` (or `failed` with a concrete `failureReason`). If you are about to write code and the checklist is empty, stale, or missing the item you are working on, **stop and fix the checklist first** \u2014 the orchestration depends on it. Free-text status reports are not a substitute.\n2. **Discover before you edit.** Read the user's prompt and any in-archive instructional files (README, spec, guidance docs \u2014 the platform guide lists artifact patterns for that source) **before** mapping. Summarize inferred product purpose, primary personas, and explicit non-goals in the discovery summary. Then inventory routes, pages, data sources, env vars, _and visual surface_ (theme tokens, `index.css`, custom CSS, font setup, layout shells) across the entire source tree before writing any code. The platform file tells you what shapes to look for.\n3. **Ask before guessing.** Multiple integrations of the same kind, missing integrations, unsupported data sources, or any platform-specific ambiguity \u2192 stop and `askMultiChoice`. Never pick for the user. Non-canonical export layout (nested dirs, duplicate entry files, bundler HTML decoys) does **not** automatically trigger `askMultiChoice`. First explore the archive and use the durable hallmarks in the platform guide to identify the true entry. If the layout is still genuinely ambiguous after exploration, `askMultiChoice`. Do not force the textbook layout, and do not ask before making a reasonable exploration attempt. The platform file lists ambiguities specific to that source.\n4. **Preserve visual identity.** The migrated app must be pixel-faithful to the source. Transfer these source details verbatim: copy strings (every label, heading, placeholder, helper text, button, empty state, error, alt text, tooltip, and aria-label), Tailwind class lists, CSS custom properties with original units and color space (no HSL\u2194OKLCH conversion), border-radius, spacing / padding / margin / gap, width / height literals including arbitrary values such as `w-[280px]` and `rounded-[14px]`, shadow tokens and values, typography (family, weight, size, line-height, and letter-spacing), icon identity (same lucide name or same inline SVG), inline SVG and image assets, breakpoints and responsive prefixes, animations and transitions, component breakdown, and JSX nesting. shadcn/ui components stay as-is. Do **not** redesign, restyle, or \"clean up\" while porting. A diff that goes beyond data hooks + auth + routing + framework directives is a regression \u2014 back it out.\n5. **Never copy secrets.** DSN strings, API keys, anon/service-role keys, JWT secrets, env-var lookups for credentials \u2014 none move into the target tree. Integration UUIDs replace them. Surface every leaked secret you find (especially client-side `VITE_*` / `NEXT_PUBLIC_*` keys) in the discovery summary so the user can rotate them.\n6. **No `// TODO`s.** Anything you can't finish deterministically becomes a `failed` checklist item with a concrete `failureReason`.\n7. **Don't scaffold.** If `server/apis/index.ts` or `client/router.tsx` doesn't already exist, you're in the wrong app \u2014 stop and surface this.\n8. **Don't fabricate a backend.** If the source is genuinely frontend-only, the migrated app should also be frontend-only. Don't invent APIs to \"complete\" the architecture.\n\n## Workflow\n\n1. **Locate the source.** If the user gave a path, use it. Otherwise look in the working tree for the platform signals listed above. If ambiguous, ask.\n2. **Load the platform guide.** Read `replit.md`, `lovable.md`, `v0.md`, or `claude-design.md` based on what you found. Do not start mapping before you've read it \u2014 it documents the source's shape and how each piece translates.\n3. **Read guidance and inventory.** First, read the user's prompt and any in-archive instructional files per the platform guide. State inferred product intent and non-goals before mapping. Then, following the platform guide's discovery checklist, enumerate every route/handler, page, data source, env var, secret, and visual asset in the source tree. When the export layout is non-canonical, identify the true runtime entry (not bundler decoys or stale duplicates) and reconcile nested module directories. Surface a one-paragraph summary plus an itemized list of integrations and unsupported features before writing anything. If the source has bespoke styling, seed a `setup_theme` checklist item to port it.\n4. **Resolve integrations.** For each data source kind: call `searchIntegrations` (filter by `type`). One match \u2192 bind it. Multiple \u2192 ask the user which. Zero \u2192 ask whether to create one; if yes, use `listAvailableIntegrationTypes` (if needed) and `openIntegrationSetup`, then ask the user explicitly whether they saved or cancelled before re-searching. Resolution is **blocking** \u2014 the checklist cannot be seeded until every kind maps to a UUID, is explicitly deferred, or has been confirmed unsupported.\n5. **Seed the checklist** via `build_manageChecklist`. One `api_<ApiName>` per backend interaction, one `frontend_<PageName>` per page, plus `setup_router`, `setup_registry`, `setup_cleanup`, and any `setup_theme` / `setup_storage` / `unsupported_<feature>` items the platform guide tells you to add. Print the count as a sanity check; if it looks wrong, re-check discovery.\n6. **Execute.** Every item follows the same ritual \u2014 no exceptions:\n   - **Before touching files:** `build_manageChecklist update <itemId> in_progress`.\n   - **Classify the work** per _Before emitting code_ below \u2014 pick the right tool (copy / copy+edit / write) before you start typing.\n   - **Emit / edit the files** for that item using the tool the classification selected.\n   - File edits change the live app immediately. Create a page before adding its router reference. Remove router references before deleting a page. For a rename, create the new page, repoint the router, then delete the old page. Wait for each dependent tool call to return without an error. Batch only independent tool calls.\n   - **After the edit lands:** `build_manageChecklist update <itemId> completed` (or `failed` with a concrete `failureReason`).\n   - You are not done with an item until its checklist entry has moved to a terminal state. Do not batch updates at the end; update as you go.\n   - **For parallelizable work:** call `spawnCodingSubagents` with batches of tasks. Each batch's `instructions` must direct the sub-agent to `build_readFile` `skills/system/third-party-migration/SKILL.md` and the matching platform file (for example, `v0.md`) before touching any files. Do not inline the fidelity contract; keep a single source of truth. The instructions also name exact `itemId`s, include the integration-UUID map and source path, include any platform-specific context the sub-agent needs (e.g. RLS-replacement clauses for Lovable), and tell the sub-agent to follow the same `in_progress` \u2192 `completed`/`failed` ritual for every item it owns.\n   - `spawnCodingSubagents` **must be the only tool call in that turn.** It blocks until every sub-agent finishes; there is no \"while waiting\" from your perspective. Other tool calls in the same turn race on the shared checklist and corrupt state. After it returns, read the checklist and handle `failed` items sequentially. If the tool itself errors, surface it and fall back to sequential \u2014 or fail the affected items with `sub-agent orchestration failed: <error>`.\n\n## Before emitting code\n\nPick the right tool **before** you start typing. The source tree is the source of truth; preserve it byte-for-byte wherever you can. `build_writeFile` is an escalation, not the primary tool \u2014 a rewritten file is only as faithful as the model's attention, while a copied file is faithful by construction.\n\nFor each checklist item, classify the target file(s) into the **lowest bucket that fits** and use the tool for that bucket:\n\n| Source vs. target needs                                                                                        | Tool                                            | Examples                                                                                                                                       |\n| -------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |\n| **Directory** of non-source files                                                                              | `build_copyDirectory` \u2014 never per-file          | `public/`, `static/`, `assets/`, `src/assets/`, fonts, image bundles                                                                           |\n| **Identical** \u2014 byte-for-byte                                                                                  | `build_copyFile`                                | data modules, type files, JSON, fixtures, vendored utils, content/copy modules, shadcn primitives the source has already customized            |\n| **Trivial edits only** \u2014 \u2264 3 distinct edit sites                                                               | `build_copyFile` then `build_editFile` per site | import-path swaps (`react-router-dom` \u2192 `react-router`), single hook rename, one-line constant fix, removing a single `\"use client\"` directive |\n| **Structural changes** \u2014 different component APIs, framework wrappers, routing overhaul, data-hook replacement | `build_writeFile`                               | page components whose data layer is being rewritten, server handlers being reshaped to `api(...)`, router file being regenerated               |\n\n**Heuristic:** if you cannot name the specific lines that need to change before reading the file, you have not earned `build_writeFile` yet \u2014 `build_readFile` first, then re-classify.\n\n**Asset directories never get a per-file ruling.** If `public/` (or the platform's equivalent \u2014 see the per-platform guide) exists in the source, it ships as a single `build_copyDirectory` regardless of contents. Do not enumerate, do not skip, do not selectively copy \"the ones you think you'll need.\"\n\n## When emitting code\n\n- **Server.** Default-export one `api({ name, integrations, input, output, run })` from `@superblocksteam/sdk-api`. The `name` and the registry key in `server/apis/index.ts` must equal `<ApiName>` verbatim \u2014 the client calls `useApi(\"<ApiName>\")` by that exact string. Preserve the external response shape exactly so the migrated frontend keeps working. Use parameterized SQL only (`$N`); zero string interpolations. Throw the error classes the sdk-api README documents instead of returning HTTP status codes.\n- **Client.** Replace the source's data hooks with `useApiData` (reads) or `useApi` (mutations) keyed by `<ApiName>`. **Import the typed wrappers from the template, not the library directly:** `import { useApi } from \"@/hooks/useApi.js\"`, `import { useApiData } from \"@/hooks/useApiData.js\"`, `import { executeApi } from \"@/lib/executeApi.js\"`. They give compile-time inference from `ApiRegistry`. Drop the source's generated client packages, `QueryClientProvider`, base-URL or auth-token getters, and any auth-context plumbing \u2014 Superblocks handles all of that. shadcn/form + react-hook-form + zod stays. Follow the loading-state guidance in `superblocks-frontend/SKILL.md`.\n- **ESM imports.** Every relative import in emitted code uses an explicit `.js` extension (`./api.js`, `../hooks/useApi.js`) \u2014 even though the source is `.ts`. The template is ESM; bare specifiers fail at runtime.\n- **Theme port.** When carrying over the source's theme, copy the existing color values **as-is** into `client/index.css`'s `:root` block. HSL values written `hsl(222 47% 11%)` (CSS Color Level 4 space-separated form) work directly with the `@theme inline` mapping in Tailwind v4. **Do not convert to OKLCH** unless the source already uses OKLCH \u2014 converting introduces drift and is a common visual-regression source.\n- **Visual fidelity.** JSX structure, Tailwind classes, shadcn variants, custom CSS, theme tokens, fonts, and layout containers must transfer over **unchanged** from the source page. The only things that change in a page port are the data hooks, the auth touchpoints, and the router primitives. Do not \"improve\" markup, swap class names, or substitute components. If the diff between source and target page goes beyond data + auth + routing, you are over-editing \u2014 back out the cosmetic changes.\n- **Sub-agents must not** call `searchIntegrations`, `openIntegrationSetup`, or any integration-resolution tool. If they hit a kind missing from the map, fail the item with `unresolved integration kind: <kind>` and let the main agent handle it on return.\n\n## Done\n\nStop only when every checklist item is `completed` or `failed`. Report the counts plus any platform-specific findings the per-platform guide asks you to surface (e.g. leaked secrets, replaced RLS policies, unsupported realtime features). Do not claim success \u2014 defer verification to the user running the app.\n";
+export declare const content = "---\nname: third-party-migration\ndescription: |\n  Migrate a third-party app (Replit, Streamlit, Lovable, v0, or similar) into a Superblocks 3.0 full-stack app.\n  Load when the user asks to migrate, import, or port an external app \u2014 or when the source tree contains hallmarks of a supported platform (`replit.md` / `.replit`, `streamlit_app.py`, `.streamlit/config.toml`, `import streamlit as st`, `src/integrations/supabase/`, `supabase/functions/`, `lovable-tagger`, an `app/` directory with `next.config.*` and `\"use client\"` / `\"use server\"` directives, etc.) and the user wants it turned into a Superblocks app.\nreadOnly: true\nmetadata:\n  author: superblocks\n  version: \"1.0\"\n---\n\n# Third-Party App \u2192 Superblocks 3.0 Migration\n\nPort a user-provided external app into the Superblocks fullstack app you are running inside (template: `app-fullstack`). The source tree is **read-only material**. All edits land in the target app under `server/` and `client/`.\n\nThis file is the migration framework. **Per-platform mapping rules live in sibling files** \u2014 load the right one before you start mapping.\n\n## Checklist is mandatory\n\nChecklist discipline is required for every migration run:\n\n- Before any file edits, ensure migration checklist items are seeded via `build_manageChecklist`.\n- Before editing an item, mark it `in_progress`.\n- After the edit lands, mark it `completed`, or `failed` with a concrete `failureReason` if deterministic completion is impossible.\n- When you need an item to survive `build_finalize`, set `clearOnFinalize: false` on add/update. Use this only for migration-tracking items that must persist until explicit migration completion.\n- Do not continue implementation if checklist state is missing, stale, or inconsistent with the work you are doing. Fix checklist state first.\n- Free-text progress updates are never a substitute for checklist updates.\n\n## Identify the source platform\n\nMatch the source tree against these signals, then read the matching reference file in this folder. Read it once, up-front \u2014 it tells you what shapes to look for and how each maps to Superblocks.\n\n- **Replit** \u2014 `replit.md`, `.replit`, `artifacts/`, an Express server with an Orval-generated client. \u2192 load `replit.md`.\n- **Streamlit** \u2014 `streamlit_app.py`, `.streamlit/config.toml`, dependency files containing `streamlit`, Python files with `import streamlit as st`, or a Python `pages/` multipage app structure. Follow the general guidelines in this document.\n- **Lovable** \u2014 `src/integrations/supabase/client.ts`, `supabase/config.toml`, `supabase/functions/`, `supabase/migrations/`, `lovable-tagger` in `vite.config.ts`. \u2192 load `lovable.md`.\n- **v0** \u2014 `app/<segment>/page.tsx` (Next.js App Router) plus `next.config.{js,mjs,ts}` and `next` in `package.json`, files with `\"use client\"` / `\"use server\"` directives, `next/link` / `next/navigation` imports, `components/ui/` with shadcn primitives. \u2192 load `v0.md`.\n- **Claude Design** \u2014 a frontend-only prototype (no `package.json`, no `node_modules`, no build config) whose durable hallmarks are: React + ReactDOM + `@babel/standalone` loaded from a CDN; `<script type=\"text/babel\" src=\"...\">` for JSX files; `/*EDITMODE-BEGIN*/ ... /*EDITMODE-END*/` markers in defaults blocks; `useTweaks` / `TweaksPanel` / `TweakSection` / `TweakToggle` window globals; `<html data-theme=\"...\">` with CSS variables such as `var(--accent)` / `var(--ink)`. A **common** layout is a flat archive with one top-level `<Name>.html` plus sibling `app.jsx`, `data.js` (or `data.jsx`), and `tweaks-panel.jsx` \u2014 but exports may nest modules under a project directory, include a large bundler-style standalone HTML at the archive root, ship an embedded design-system bundle (e.g. `_ds/`), or duplicate stale files at the root vs a nested folder. When layout deviates, rely on the durable hallmarks and the actual tree \u2014 do not force the flat-archive shape. \u2192 load `claude-design.md`.\n- **Ambiguous or neither** \u2014 stop and ask the user which platform the source came from. Do not guess. It is possible that it is No Platform. In this case, follow the general guidelines in this document and ask user questions for any ambiguity.\n\nWhen a source only **partially** matches a platform's hallmarks, do not abandon identification or reshape the tree to fit the canonical checklist. Explore the actual archive, confirm via durable signals, use best judgment to find the real entry point and module layout, and `askMultiChoice` on genuine ambiguity rather than forcing a textbook export shape.\n\nThe framework below applies to every platform; the platform file fills in the source-specific mapping.\n\n## Target layout\n\nThe app you are running inside looks like this. Do not invent new top-level directories.\n\n```\nclient/\n  App.tsx           \u2014 root with <AppProvider> + <Outlet />\n  router.tsx        \u2014 react-router v7 data mode (`createBrowserRouter`); see Router shape below\n  index.css         \u2014 Tailwind v4 + theme tokens\n  hooks/\n    useApi.ts       \u2014 typed wrapper around useTypedApi<ApiRegistry>\n    useApiData.ts   \u2014 typed wrapper around useTypedApiData<ApiRegistry>\n  lib/executeApi.ts \u2014 non-React typed executeApi\n  pages/<Name>/index.tsx\n  components/ui/    \u2014 shadcn primitives (do not modify)\nserver/\n  apis/\n    index.ts        \u2014 registry: `const apis = { ApiName: ... } as const;`\n    <ApiName>/api.ts\n```\n\n## Universal mapping (applies to every source)\n\nThese hold regardless of source platform. Per-platform specifics layer on top.\n\n- APIs are addressed by `name` via the registry \u2014 there is no URL path. Within `api()`:\n  - All inputs (whatever shape the source had \u2014 body, query, params, function args) \u2192 one unified `input` Zod schema; destructure inside `run(ctx, { ... })`.\n  - The handler's response \u2192 `return { ... }` from `run`. The `output` schema validates it automatically; do not `safeParse` by hand.\n  - Auth \u2192 `ctx.user` (`userId`, `email`, `name`, `groups`, `customClaims`). Auth is platform-managed; drop the source's auth flows entirely.\n  - Errors \u2192 throw the `SdkError` subtypes the sdk-api README documents (`InputValidationError`, `OutputValidationError`, `IntegrationError`, `ExecutionError`). Never invent error classes or return HTTP status codes.\n  - DB clients (`pg`, `knex`, `prisma`, Drizzle, `supabase.from(...)`) \u2192 declare in `integrations: { db: postgres(DB_INTEGRATION_ID) }` and call `ctx.integrations.db.query(sql, ZodSchema, params, { label: \"...\" })` / `.execute(...)`. Parameterized SQL only. Hold integration UUIDs in module-level `const`s, not literals scattered through `run`.\n  - External HTTP (`axios`, `fetch`, third-party SDKs) \u2192 declared integration + `ctx.integrations.<name>.apiRequest({ method, path, body }, { response: ZodSchema })`.\n  - `process.env.*` / `import.meta.env.*` / `Deno.env.get(...)` \u2192 `ctx.env`. Logging \u2192 `ctx.log.info/warn/error/debug(msg, data?)`.\n  - Server bootstrapping (`app.listen`, CORS, route grouping, middleware setup, `Deno.serve`) \u2192 drop entirely. The platform handles it.\n- **Each frontend page \u2192 one Superblocks page** at `client/pages/<Name>/index.tsx`, wired into `client/router.tsx`.\n- **Each backend data source (DB, REST client, S3, ...) \u2192 one Superblocks integration** referenced by UUID. Credentials live on the integration, never in code.\n\n### Router shape (`client/router.tsx`)\n\nThe editor parses this file statically to build the page list and route table. **Use one of the supported page-component bindings \u2014 anything else silently drops every route and the editor shows a \"404 / route has been deleted\" overlay.**\n\nSupported page bindings (mix freely):\n\n```tsx\n// 1. Inline lazy on the route object (preferred \u2014 matches the template):\n{ path: \"about\", lazy: () => import(\"./pages/About/index.tsx\").then(m => ({ Component: m.default })) }\n\n// 2. Static default import + Component / element:\nimport About from \"./pages/About/index.tsx\";\n{ path: \"about\", Component: About }\n{ path: \"about\", element: <About /> }\n\n// 3. Top-level `const` bound to React.lazy + Component / element:\nconst About = lazy(() => import(\"./pages/About/index.tsx\"));\n{ path: \"about\", Component: About }\n```\n\nDo **not**: assign `Component` / `element` to identifiers bound by anything other than a static import or `lazy(() => import(\"...\"))` (no IIFEs, no helper wrappers, no conditional `lazy(...)`, no objects whose keys are computed from a loop). The parser only resolves the shapes above.\n\n## Authoritative references (read just-in-time, not up front)\n\n- `getSdkApiDocs` and `node_modules/@superblocksteam/sdk-api/src/index.ts`: use the complete shared README returned by `getSdkApiDocs` with the target integration's ID or plugin ID for the server `api()` contract, and the barrel for the full list of factory names. **Never invent factory names.** If required documentation or the barrel is unavailable, mark the affected checklist item `failed` with the failed call or missing path as the reason.\n- Version-aware per-integration documentation from `getSdkApiDocs` \u2014 retrieve once, with an integration ID when possible, when you first emit an API that uses that integration.\n- `skills/system/superblocks-frontend/SKILL.md` - the target client's API-hook behavior and loading-state contract.\n\n> \u26A0\uFE0F **Never** load `skills/system/superblocks-api/SKILL.md`. It describes a different, block-based API pattern that is incompatible with the fullstack template's `sdk-api`. Mixing them produces code that does not compile.\n\n## Non-negotiables\n\n1. **Track everything in the checklist.** The **first tool call after exiting plan mode** or **during build mode, before building** is `build_manageChecklist` to seed. Before every per-item edit, `update <itemId> in_progress`; after, `update <itemId> completed` (or `failed` with a concrete `failureReason`). If you are about to write code and the checklist is empty, stale, or missing the item you are working on, **stop and fix the checklist first** \u2014 the orchestration depends on it. Free-text status reports are not a substitute.\n2. **Discover before you edit.** Read the user's prompt and any in-archive instructional files (README, spec, guidance docs \u2014 the platform guide lists artifact patterns for that source) **before** mapping. Summarize inferred product purpose, primary personas, and explicit non-goals in the discovery summary. Then inventory routes, pages, data sources, env vars, _and visual surface_ (theme tokens, `index.css`, custom CSS, font setup, layout shells) across the entire source tree before writing any code. The platform file tells you what shapes to look for.\n3. **Ask before guessing.** Multiple integrations of the same kind, missing integrations, unsupported data sources, or any platform-specific ambiguity \u2192 stop and `askMultiChoice`. Never pick for the user. Non-canonical export layout (nested dirs, duplicate entry files, bundler HTML decoys) does **not** automatically trigger `askMultiChoice`. First explore the archive and use the durable hallmarks in the platform guide to identify the true entry. If the layout is still genuinely ambiguous after exploration, `askMultiChoice`. Do not force the textbook layout, and do not ask before making a reasonable exploration attempt. The platform file lists ambiguities specific to that source.\n4. **Preserve visual identity.** The migrated app must be pixel-faithful to the source. Transfer these source details verbatim: copy strings (every label, heading, placeholder, helper text, button, empty state, error, alt text, tooltip, and aria-label), Tailwind class lists, CSS custom properties with original units and color space (no HSL\u2194OKLCH conversion), border-radius, spacing / padding / margin / gap, width / height literals including arbitrary values such as `w-[280px]` and `rounded-[14px]`, shadow tokens and values, typography (family, weight, size, line-height, and letter-spacing), icon identity (same lucide name or same inline SVG), inline SVG and image assets, breakpoints and responsive prefixes, animations and transitions, component breakdown, and JSX nesting. shadcn/ui components stay as-is. Do **not** redesign, restyle, or \"clean up\" while porting. A diff that goes beyond data hooks + auth + routing + framework directives is a regression \u2014 back it out.\n5. **Never copy secrets.** DSN strings, API keys, anon/service-role keys, JWT secrets, env-var lookups for credentials \u2014 none move into the target tree. Integration UUIDs replace them. Surface every leaked secret you find (especially client-side `VITE_*` / `NEXT_PUBLIC_*` keys) in the discovery summary so the user can rotate them.\n6. **No `// TODO`s.** Anything you can't finish deterministically becomes a `failed` checklist item with a concrete `failureReason`.\n7. **Don't scaffold.** If `server/apis/index.ts` or `client/router.tsx` doesn't already exist, you're in the wrong app \u2014 stop and surface this.\n8. **Don't fabricate a backend.** If the source is genuinely frontend-only, the migrated app should also be frontend-only. Don't invent APIs to \"complete\" the architecture.\n\n## Workflow\n\n1. **Locate the source.** If the user gave a path, use it. Otherwise look in the working tree for the platform signals listed above. If ambiguous, ask.\n2. **Load the platform guide.** Read `replit.md`, `lovable.md`, `v0.md`, or `claude-design.md` based on what you found. Do not start mapping before you've read it \u2014 it documents the source's shape and how each piece translates.\n3. **Read guidance and inventory.** First, read the user's prompt and any in-archive instructional files per the platform guide. State inferred product intent and non-goals before mapping. Then, following the platform guide's discovery checklist, enumerate every route/handler, page, data source, env var, secret, and visual asset in the source tree. When the export layout is non-canonical, identify the true runtime entry (not bundler decoys or stale duplicates) and reconcile nested module directories. Surface a one-paragraph summary plus an itemized list of integrations and unsupported features before writing anything. If the source has bespoke styling, seed a `setup_theme` checklist item to port it.\n4. **Resolve integrations.** For each data source kind: call `searchIntegrations` (filter by `type`). One match \u2192 bind it. Multiple \u2192 ask the user which. Zero \u2192 ask whether to create one; if yes, use `listAvailableIntegrationTypes` (if needed) and `openIntegrationSetup`, then ask the user explicitly whether they saved or cancelled before re-searching. Resolution is **blocking** \u2014 the checklist cannot be seeded until every kind maps to a UUID, is explicitly deferred, or has been confirmed unsupported.\n5. **Seed the checklist** via `build_manageChecklist`. One `api_<ApiName>` per backend interaction, one `frontend_<PageName>` per page, plus `setup_router`, `setup_registry`, `setup_cleanup`, and any `setup_theme` / `setup_storage` / `unsupported_<feature>` items the platform guide tells you to add. Print the count as a sanity check; if it looks wrong, re-check discovery.\n6. **Execute.** Every item follows the same ritual \u2014 no exceptions:\n   - **Before touching files:** `build_manageChecklist update <itemId> in_progress`.\n   - **Classify the work** per _Before emitting code_ below \u2014 pick the right tool (copy / copy+edit / write) before you start typing.\n   - **Emit / edit the files** for that item using the tool the classification selected.\n   - File edits change the live app immediately. Create a page before adding its router reference. Remove router references before deleting a page. For a rename, create the new page, repoint the router, then delete the old page. Wait for each dependent tool call to return without an error. Batch only independent tool calls.\n   - **After the edit lands:** `build_manageChecklist update <itemId> completed` (or `failed` with a concrete `failureReason`).\n   - You are not done with an item until its checklist entry has moved to a terminal state. Do not batch updates at the end; update as you go.\n   - **For parallelizable work:** call `spawnCodingSubagents` with batches of tasks. Each batch's `instructions` must direct the sub-agent to `build_readFile` `skills/system/third-party-migration/SKILL.md` and the matching platform file (for example, `v0.md`) before touching any files. Do not inline the fidelity contract; keep a single source of truth. The instructions also name exact `itemId`s, include the integration-UUID map and source path, include any platform-specific context the sub-agent needs (e.g. RLS-replacement clauses for Lovable), and tell the sub-agent to follow the same `in_progress` \u2192 `completed`/`failed` ritual for every item it owns.\n   - `spawnCodingSubagents` **must be the only tool call in that turn.** It blocks until every sub-agent finishes; there is no \"while waiting\" from your perspective. Other tool calls in the same turn race on the shared checklist and corrupt state. After it returns, read the checklist and handle `failed` items sequentially. If the tool itself errors, surface it and fall back to sequential \u2014 or fail the affected items with `sub-agent orchestration failed: <error>`.\n\n## Before emitting code\n\nPick the right tool **before** you start typing. The source tree is the source of truth; preserve it byte-for-byte wherever you can. `build_writeFile` is an escalation, not the primary tool \u2014 a rewritten file is only as faithful as the model's attention, while a copied file is faithful by construction.\n\nFor each checklist item, classify the target file(s) into the **lowest bucket that fits** and use the tool for that bucket:\n\n| Source vs. target needs                                                                                        | Tool                                            | Examples                                                                                                                                       |\n| -------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |\n| **Directory** of non-source files                                                                              | `build_copyDirectory` \u2014 never per-file          | `public/`, `static/`, `assets/`, `src/assets/`, fonts, image bundles                                                                           |\n| **Identical** \u2014 byte-for-byte                                                                                  | `build_copyFile`                                | data modules, type files, JSON, fixtures, vendored utils, content/copy modules, shadcn primitives the source has already customized            |\n| **Trivial edits only** \u2014 \u2264 3 distinct edit sites                                                               | `build_copyFile` then `build_editFile` per site | import-path swaps (`react-router-dom` \u2192 `react-router`), single hook rename, one-line constant fix, removing a single `\"use client\"` directive |\n| **Structural changes** \u2014 different component APIs, framework wrappers, routing overhaul, data-hook replacement | `build_writeFile`                               | page components whose data layer is being rewritten, server handlers being reshaped to `api(...)`, router file being regenerated               |\n\n**Heuristic:** if you cannot name the specific lines that need to change before reading the file, you have not earned `build_writeFile` yet \u2014 `build_readFile` first, then re-classify.\n\n**Asset directories never get a per-file ruling.** If `public/` (or the platform's equivalent \u2014 see the per-platform guide) exists in the source, it ships as a single `build_copyDirectory` regardless of contents. Do not enumerate, do not skip, do not selectively copy \"the ones you think you'll need.\"\n\n## When emitting code\n\n- **Server.** Default-export one `api({ name, integrations, input, output, run })` from `@superblocksteam/sdk-api`. The `name` and the registry key in `server/apis/index.ts` must equal `<ApiName>` verbatim \u2014 the client calls `useApi(\"<ApiName>\")` by that exact string. Preserve the external response shape exactly so the migrated frontend keeps working. Use parameterized SQL only (`$N`); zero string interpolations. Throw the error classes the sdk-api README documents instead of returning HTTP status codes.\n- **Client.** Replace the source's data hooks with `useApiData` (reads) or `useApi` (mutations) keyed by `<ApiName>`. **Import the typed wrappers from the template, not the library directly:** `import { useApi } from \"@/hooks/useApi.js\"`, `import { useApiData } from \"@/hooks/useApiData.js\"`, `import { executeApi } from \"@/lib/executeApi.js\"`. They give compile-time inference from `ApiRegistry`. Drop the source's generated client packages, `QueryClientProvider`, base-URL or auth-token getters, and any auth-context plumbing \u2014 Superblocks handles all of that. shadcn/form + react-hook-form + zod stays. Follow the loading-state guidance in `superblocks-frontend/SKILL.md`.\n- **ESM imports.** Every relative import in emitted code uses an explicit `.js` extension (`./api.js`, `../hooks/useApi.js`) \u2014 even though the source is `.ts`. The template is ESM; bare specifiers fail at runtime.\n- **Theme port.** When carrying over the source's theme, copy the existing color values **as-is** into `client/index.css`'s `:root` block. HSL values written `hsl(222 47% 11%)` (CSS Color Level 4 space-separated form) work directly with the `@theme inline` mapping in Tailwind v4. **Do not convert to OKLCH** unless the source already uses OKLCH \u2014 converting introduces drift and is a common visual-regression source.\n- **Visual fidelity.** JSX structure, Tailwind classes, shadcn variants, custom CSS, theme tokens, fonts, and layout containers must transfer over **unchanged** from the source page. The only things that change in a page port are the data hooks, the auth touchpoints, and the router primitives. Do not \"improve\" markup, swap class names, or substitute components. If the diff between source and target page goes beyond data + auth + routing, you are over-editing \u2014 back out the cosmetic changes.\n- **Sub-agents must not** call `searchIntegrations`, `openIntegrationSetup`, or any integration-resolution tool. If they hit a kind missing from the map, fail the item with `unresolved integration kind: <kind>` and let the main agent handle it on return.\n\n## Done\n\nStop only when every checklist item is `completed` or `failed`. Report the counts plus any platform-specific findings the per-platform guide asks you to surface (e.g. leaked secrets, replaced RLS policies, unsupported realtime features). Do not claim success \u2014 defer verification to the user running the app.\n";
 //# sourceMappingURL=skill.generated.d.ts.map

package/dist/ai-service/skills/system/third-party-migration/skill.generated.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"skill.generated.d.ts","sourceRoot":"","sources":["../../../../../src/ai-service/skills/system/third-party-migration/skill.generated.ts"],"names":[],"mappings":"AAGA,eAAO,MAAM,OAAO,o0tBAuKnB,CAAC"}
+{"version":3,"file":"skill.generated.d.ts","sourceRoot":"","sources":["../../../../../src/ai-service/skills/system/third-party-migration/skill.generated.ts"],"names":[],"mappings":"AAGA,eAAO,MAAM,OAAO,81tBAuKnB,CAAC"}

package/dist/ai-service/skills/system/third-party-migration/skill.generated.js

@@ -104,7 +104,7 @@ Do **not**: assign \`Component\` / \`element\` to identifiers bound by anything
 
 ## Authoritative references (read just-in-time, not up front)
 
-- \`getSdkApiDocs\` and \`node_modules/@superblocksteam/sdk-api/src/index.ts\` — use the tool's root section index for the server \`api()\` contract and the barrel for the full list of factory names. Follow \`root.continuation\` exactly. **Never invent factory names.** If required documentation or the barrel is unavailable, mark the affected checklist item \`failed\` with the failed selector or missing path as the reason.
+- \`getSdkApiDocs\` and \`node_modules/@superblocksteam/sdk-api/src/index.ts\`: use the complete shared README returned by \`getSdkApiDocs\` with the target integration's ID or plugin ID for the server \`api()\` contract, and the barrel for the full list of factory names. **Never invent factory names.** If required documentation or the barrel is unavailable, mark the affected checklist item \`failed\` with the failed call or missing path as the reason.
 - Version-aware per-integration documentation from \`getSdkApiDocs\` — retrieve once, with an integration ID when possible, when you first emit an API that uses that integration.
 - \`skills/system/superblocks-frontend/SKILL.md\` - the target client's API-hook behavior and loading-state contract.
 

package/dist/ai-service/state-machine/clark-fsm.d.ts

@@ -64,7 +64,7 @@ export declare const AGENT_REPORTED_ERROR_TO_USER = "agentReportedErrorToUser";
 export declare const AGENT_NEEDS_USER_INPUT = "agentNeedsUserInput";
 export declare const AGENT_GAVE_UP = "agentGaveUp";
 export declare const AGENT_CANCELED = "agentCanceled";
-export declare const LLM_REQUESTED_CONTEXT = "llmRequestedContext";
+declare const LLM_REQUESTED_CONTEXT = "llmRequestedContext";
 export declare const LLM_FINISHED_UNEXPECTEDLY = "llmFinishedUnexpectedly";
 export declare const LLM_ERRORED = "llmErrored";
 export declare const LLM_FINISHED = "llmFinished";
@@ -314,7 +314,7 @@ export declare class Clark extends TracedFSM<ClarkState, ClarkEvent, ClarkContex
     private sendContextUsage;
 }
 export type ClarkTransition = FSMOnTransitionParams<ClarkState, ClarkEvent>;
-export type ClarkStateHandlerFactory = (clark: Clark, params: ClarkStateHandlerParams) => (transition: ClarkTransition) => Promise<void>;
+type ClarkStateHandlerFactory = (clark: Clark, params: ClarkStateHandlerParams) => (transition: ClarkTransition) => Promise<void>;
 export type ClarkStateHandlerFactories = {
     [K in ClarkState]: ClarkStateHandlerFactory;
 };
@@ -444,7 +444,6 @@ export type ClarkContext = {
         content: string;
     }[];
     abortController?: AbortController;
-    initialElementIds?: string[];
     initialFilePaths?: {
         apis: string[];
         components: string[];

package/dist/ai-service/state-machine/clark-fsm.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"clark-fsm.d.ts","sourceRoot":"","sources":["../../../src/ai-service/state-machine/clark-fsm.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,eAAe,EAAE,MAAM,kBAAkB,CAAC;AAExD,OAAO,KAAK,EAAE,YAAY,EAAoC,MAAM,IAAI,CAAC;AACzE,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,MAAM,CAAC;AAE1C,OAAO,KAAK,EACV,iBAAiB,EACjB,iBAAiB,EACjB,wBAAwB,EACxB,aAAa,EACb,mBAAmB,EACnB,8BAA8B,EAC9B,0BAA0B,EAC1B,gBAAgB,EAChB,MAAM,EACN,WAAW,EAGX,aAAa,EACb,yBAAyB,EACzB,gBAAgB,EAChB,oBAAoB,EACpB,cAAc,EACd,eAAe,EACf,YAAY,EACZ,oBAAoB,EACpB,oBAAoB,EACrB,MAAM,uCAAuC,CAAC;AAC/C,OAAO,KAAK,EACV,sBAAsB,EACtB,oBAAoB,EACpB,kBAAkB,EACnB,MAAM,yBAAyB,CAAC;AAEjC,OAAO,KAAK,EAAE,UAAU,EAAE,MAAM,4BAA4B,CAAC;AAG7D,OAAO,KAAK,EAAE,cAAc,EAAE,MAAM,+BAA+B,CAAC;AACpE,OAAO,KAAK,EAAE,qBAAqB,EAAE,MAAM,uCAAuC,CAAC;AACnF,OAAO,KAAK,EAAE,YAAY,EAAE,MAAM,6BAA6B,CAAC;AAChE,OAAO,KAAK,EAAE,kBAAkB,EAAE,MAAM,8BAA8B,CAAC;AACvE,OAAO,KAAK,EAAE,oBAAoB,EAAE,IAAI,EAAE,MAAM,0BAA0B,CAAC;AAC3E,OAAO,KAAK,EAAE,mBAAmB,EAAE,MAAM,2CAA2C,CAAC;AACrF,OAAO,KAAK,EAAE,gBAAgB,EAAE,MAAM,wCAAwC,CAAC;AAC/E,OAAO,KAAK,EAAE,QAAQ,EAAE,MAAM,2BAA2B,CAAC;AAC1D,OAAO,KAAK,EAAE,gBAAgB,EAAE,MAAM,+BAA+B,CAAC;AACtE,OAAO,KAAK,EAAE,eAAe,EAAE,MAAM,2BAA2B,CAAC;AACjE,OAAO,KAAK,EAAE,qBAAqB,EAAE,MAAM,gBAAgB,CAAC;AAC5D,OAAO,KAAK,EAAE,gBAAgB,EAAE,MAAM,0BAA0B,CAAC;AACjE,OAAO,KAAK,EAAE,gBAAgB,EAAE,MAAM,mCAAmC,CAAC;AAC1E,OAAO,KAAK,EAAE,YAAY,EAAE,MAAM,uBAAuB,CAAC;AAC1D,OAAO,KAAK,EAAE,SAAS,EAAE,0BAA0B,EAAE,MAAM,kBAAkB,CAAC;AAO9E,OAAO,KAAK,EAAE,gBAAgB,EAAE,MAAM,8BAA8B,CAAC;AAOrE,OAAO,KAAK,EAAE,gBAAgB,EAAE,MAAM,iBAAiB,CAAC;AACxD,OAAO,KAAK,EAAE,gBAAgB,EAAE,MAAM,gCAAgC,CAAC;AAEvE,OAAO,KAAK,EAAE,WAAW,EAAE,MAAM,iBAAiB,CAAC;AACnD,OAAO,KAAK,EACV,sBAAsB,EAEvB,MAAM,oBAAoB,CAAC;AAC5B,OAAO,KAAK,EAAE,0BAA0B,EAAE,MAAM,6BAA6B,CAAC;AAC9E,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,+BAA+B,CAAC;AACnE,OAAO,KAAK,EAAE,mBAAmB,EAAE,MAAM,gEAAgE,CAAC;AAC1G,OAAO,KAAK,EAAE,gBAAgB,EAAE,MAAM,uBAAuB,CAAC;AAC9D,OAAO,KAAK,EAAE,SAAS,EAAE,MAAM,wBAAwB,CAAC;AACxD,OAAO,KAAK,EAAE,gBAAgB,EAAE,MAAM,yBAAyB,CAAC;AAChE,OAAO,KAAK,EACV,eAAe,EACf,eAAe,EACf,aAAa,EACb,UAAU,EACV,YAAY,EACZ,YAAY,EACZ,UAAU,EACX,MAAM,aAAa,CAAC;AACrB,OAAO,KAAK,EAAE,YAAY,EAAE,MAAM,sBAAsB,CAAC;AAGzD,OAAO,KAAK,EACV,qBAAqB,EACrB,2BAA2B,EAC5B,MAAM,UAAU,CAAC;AAElB,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,6BAA6B,CAAC;AAKjE,OAAO,KAAK,EAAE,iBAAiB,EAAE,MAAM,0BAA0B,CAAC;AAClE,OAAO,EACL,SAAS,EACT,KAAK,IAAI,EACT,KAAK,yBAAyB,EAC9B,KAAK,2BAA2B,EACjC,MAAM,iBAAiB,CAAC;AAEzB,QAAA,MAAM,CAAC;;;;;;;;CAQG,CAAC;AAEX,eAAO,MAAM,eAAe;;;;;;;;CAAI,CAAC;AACjC,MAAM,MAAM,UAAU,GAAG,MAAM,OAAO,CAAC,CAAC;AAExC,eAAO,MAAM,gBAAgB,mBAAmB,CAAC;AACjD,eAAO,MAAM,mBAAmB,sBAAsB,CAAC;AACvD,eAAO,MAAM,mBAAmB,sBAAsB,CAAC;AACvD,eAAO,MAAM,aAAa,iBAAiB,CAAC;AAC5C,eAAO,MAAM,aAAa,iBAAiB,CAAC;AAC5C,eAAO,MAAM,4BAA4B,6BAA6B,CAAC;AACvE,eAAO,MAAM,sBAAsB,wBAAwB,CAAC;AAC5D,eAAO,MAAM,aAAa,gBAAgB,CAAC;AAC3C,eAAO,MAAM,cAAc,kBAAkB,CAAC;AAC9C,eAAO,MAAM,qBAAqB,wBAAwB,CAAC;AAC3D,eAAO,MAAM,yBAAyB,4BAA4B,CAAC;AACnE,eAAO,MAAM,WAAW,eAAe,CAAC;AACxC,eAAO,MAAM,YAAY,gBAAgB,CAAC;AAC1C,eAAO,MAAM,uBAAuB,0BAA0B,CAAC;AAC/D,eAAO,MAAM,wBAAwB,2BAA2B,CAAC;AACjE,eAAO,MAAM,uBAAuB,0BAA0B,CAAC;AAC/D,eAAO,MAAM,iCAAiC,kCACb,CAAC;AAClC,eAAO,MAAM,sBAAsB,yBAAyB,CAAC;AAC7D,eAAO,MAAM,oBAAoB,uBAAuB,CAAC;AACzD,eAAO,MAAM,0BAA0B,4BAA4B,CAAC;AACpE,eAAO,MAAM,iBAAiB,oBAAoB,CAAC;AAEnD,MAAM,MAAM,UAAU,GAClB;IACE,IAAI,EAAE,OAAO,gBAAgB,CAAC;IAC9B,OAAO,EAAE,iBAAiB,CAAC;IAC3B,WAAW,CAAC,EAAE,aAAa,CAAC;IAC5B,6BAA6B,CAAC,EAAE,OAAO,CAAC;IACxC;;;;;;OAMG;IACH,QAAQ,CAAC,EAAE,OAAO,CAAC;IACnB;;;;OAIG;IACH,oBAAoB,CAAC,EAAE,OAAO,CAAC;CAChC,GACD;IAAE,IAAI,EAAE,OAAO,mBAAmB,CAAC;IAAC,QAAQ,CAAC,EAAE,OAAO,CAAA;CAAE,GACxD;IAAE,IAAI,EAAE,OAAO,mBAAmB,CAAC;IAAC,QAAQ,CAAC,EAAE,OAAO,CAAA;CAAE,GACxD;IAAE,IAAI,EAAE,OAAO,aAAa,CAAC;IAAC,OAAO,CAAC,EAAE,aAAa,CAAA;CAAE,GACvD;IACE,IAAI,EAAE,OAAO,aAAa,CAAC;IAC3B,UAAU,EAAE,MAAM,CAAC;IACnB,aAAa,CAAC,EAAE,aAAa,CAAC;IAC9B,SAAS,CAAC,EAAE,OAAO,CAAC;IACpB,yGAAyG;IACzG,YAAY,CAAC,EAAE,OAAO,CAAC;IACvB;;;;OAIG;IACH,yBAAyB,CAAC,EAAE,MAAM,CAAC;IACnC,kBAAkB,CAAC,EAAE,MAAM,CAAC;CAC7B,GACD;IAAE,IAAI,EAAE,OAAO,4BAA4B,CAAC;IAAC,KAAK,EAAE,KAAK,CAAA;CAAE,GAC3D;IACE,IAAI,EAAE,OAAO,sBAAsB,CAAC;IACpC,MAAM,CAAC,EAAE,MAAM,CAAC;IAChB,mGAAmG;IACnG,qBAAqB,CAAC,EAAE,OAAO,CAAC;IAChC;;;;OAIG;IACH,mBAAmB,CAAC,EAAE,OAAO,CAAC;CAC/B,GACD;IAAE,IAAI,EAAE,OAAO,aAAa,CAAA;CAAE,GAC9B;IACE,IAAI,EAAE,OAAO,cAAc,CAAC;IAC5B,MAAM,CAAC,EAAE,MAAM,CAAC;IAChB,OAAO,EAAE,aAAa,CAAC;IACvB,aAAa,CAAC,EAAE,oBAAoB,CAAC;CACtC,GACD;IAAE,IAAI,EAAE,OAAO,qBAAqB,CAAC;IAAC,MAAM,EAAE,MAAM,CAAA;CAAE,GACtD;IACE,IAAI,EAAE,OAAO,yBAAyB,CAAC;IACvC,YAAY,EAAE,YAAY,CAAC;CAC5B,GACD;IAAE,IAAI,EAAE,OAAO,WAAW,CAAC;IAAC,KAAK,EAAE,gBAAgB,CAAA;CAAE,GACrD;IACE,IAAI,EAAE,OAAO,YAAY,CAAC;IAC1B,KAAK,EAAE,YAAY,EAAE,CAAC;CACvB,GACD;IAAE,IAAI,EAAE,OAAO,uBAAuB,CAAC;IAAC,KAAK,EAAE,KAAK,CAAA;CAAE,GACtD;IACE,IAAI,EAAE,OAAO,wBAAwB,CAAC;IACtC,KAAK,EAAE,YAAY,EAAE,CAAC;CACvB,GACD;IAAE,IAAI,EAAE,OAAO,uBAAuB,CAAA;CAAE,GACxC;IAAE,IAAI,EAAE,OAAO,iCAAiC,CAAA;CAAE,GAClD;IACE,IAAI,EAAE,OAAO,sBAAsB,CAAC;IACpC,cAAc,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,EAAE,CAAC,CAAC;IACzC,gBAAgB,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,EAAE,CAAC,CAAC;IAC3C,uBAAuB,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,EAAE,CAAC,CAAC;CACnD,GACD;IAAE,IAAI,EAAE,OAAO,oBAAoB,CAAC;IAAC,KAAK,EAAE,KAAK,CAAA;CAAE,GACnD;IAAE,IAAI,EAAE,OAAO,0BAA0B,CAAA;CAAE,GAC3C;IAAE,IAAI,EAAE,OAAO,iBAAiB,CAAC;IAAC,aAAa,CAAC,EAAE,OAAO,CAAA;CAAE,CAAC;AAGhE,eAAO,MAAM,WAAW;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAiDd,CAAC;AAEX,MAAM,MAAM,KAAK,GAAG,OAAO,CAAC,CAAC,IAAI,CAAC;AAClC,MAAM,MAAM,cAAc,GAAG,OAAO,CAAC,CAAC,aAAa,CAAC;AACpD,MAAM,MAAM,cAAc,GAAG,OAAO,CAAC,CAAC,aAAa,CAAC;AACpD,MAAM,MAAM,aAAa,GAAG,OAAO,CAAC,CAAC,YAAY,CAAC;AAClD,MAAM,MAAM,eAAe,GAAG,OAAO,CAAC,CAAC,cAAc,CAAC;AACtD,MAAM,MAAM,iBAAiB,GAAG,OAAO,CAAC,CAAC,gBAAgB,CAAC;AAE1D,MAAM,MAAM,6BAA6B,GAAG,2BAA2B,CACrE,UAAU,EACV,UAAU,CACX,CAAC;AAEF,MAAM,MAAM,uBAAuB,GAAG,2BAA2B,CAC/D,UAAU,EACV,UAAU,EACV,YAAY,CACb,CAAC;AAEF,qBAAa,KAAM,SAAQ,SAAS,CAAC,UAAU,EAAE,UAAU,EAAE,YAAY,CAAC;IACxE,OAAO,CAAC,wBAAwB,CAAqC;IACrE,OAAO,CAAC,sBAAsB,CAAK;gBAEvB,MAAM,EAAE;QAClB,cAAc,EAAE,YAAY,CAAC;QAC7B,uBAAuB,EAAE,6BAA6B,CAAC;QACvD,YAAY,CAAC,EAAE,MAAM,MAAM,GAAG,SAAS,CAAC;QACxC,iBAAiB,CAAC,EAAE,uBAAuB,CAAC;KAC7C;IAQM,gBAAgB,CAAC,KAAK,EAAE,qBAAqB,GAAG,oBAAoB;IA0BpE,YAAY,IAAI,IAAI;cAyFR,kBAAkB,CACnC,aAAa,EAAE,UAAU,GACxB,sBAAsB;cASN,mBAAmB,CACpC,KAAK,EAAE,UAAU,GAChB,yBAAyB;cAiBT,aAAa,CAAC,KAAK,EAAE,UAAU,GAAG,OAAO,CAAC,UAAU,CAAC;cAerD,qBAAqB,CACtC,MAAM,EAAE,qBAAqB,CAAC,UAAU,EAAE,UAAU,CAAC,GACpD,IAAI;IAIP;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;OA+BG;IACG,UAAU,CAAC,KAAK,SAAS,MAAM,CAAC,MAAM,EAAE,IAAI,CAAC,EACjD,QAAQ,EAAE,uBAAuB,EACjC,OAAO,EAAE,sBAAsB,CAAC,KAAK,CAAC,GACrC,OAAO,CAAC,gBAAgB,CAAC,KAAK,CAAC,CAAC;IA0OnC,OAAO,CAAC,MAAM,CAAC,QAAQ,CAAC,iBAAiB,CAa9B;IAEX;;;;;;;;;;;;;;;;OAgBG;IACG,mBAAmB,CACvB,QAAQ,EAAE,IAAI,CACZ,uBAAuB,EACvB,kBAAkB,GAAG,kBAAkB,GAAG,eAAe,CAC1D,EACD,KAAK,EAAE,MAAM,EACb,OAAO,EAAE,MAAM,GACd,OAAO,CAAC,IAAI,CAAC;IAsBhB,OAAO,CAAC,eAAe;IA2CvB;;;;OAIG;IACH,sBAAsB,IAAI,OAAO;IAQjC,oBAAoB,CAAC,QAAQ,EAAE,oBAAoB,GAAG,IAAI;IAI1D,qBAAqB,IAAI,IAAI;IAK7B,mFAAmF;IACnF,yBAAyB,IAAI,MAAM;IAInC,OAAO,CAAC,gBAAgB;CAUzB;AAED,MAAM,MAAM,eAAe,GAAG,qBAAqB,CAAC,UAAU,EAAE,UAAU,CAAC,CAAC;AAE5E,MAAM,MAAM,wBAAwB,GAAG,CACrC,KAAK,EAAE,KAAK,EACZ,MAAM,EAAE,uBAAuB,KAC5B,CAAC,UAAU,EAAE,eAAe,KAAK,OAAO,CAAC,IAAI,CAAC,CAAC;AAEpD,MAAM,MAAM,0BAA0B,GAAG;KACtC,CAAC,IAAI,UAAU,GAAG,wBAAwB;CAC5C,CAAC;AAEF,MAAM,MAAM,mBAAmB,CAAC,CAAC,SAAS,UAAU,IAClD,MAAM,CAAC,OAAO,WAAW,CAAC,CAAC,CAAC,CAAC,SAAS,KAAK,GACvC,KAAK,GACL;KACG,CAAC,IAAI,MAAM,CAAC,OAAO,WAAW,CAAC,CAAC,CAAC,CAAC,GAAG,OAAO,CAAC,UAAU,EAAE;QAAE,IAAI,EAAE,CAAC,CAAA;KAAE,CAAC;CACvE,CAAC,MAAM,CAAC,OAAO,WAAW,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC;AAEvC;;;;;;;;;GASG;AACH,MAAM,WAAW,eAAe;IAC9B,oEAAoE;IACpE,QAAQ,EAAE,GAAG,CAAC,MAAM,CAAC,CAAC;IACtB,iDAAiD;IACjD,MAAM,EAAE,GAAG,CAAC,MAAM,CAAC,CAAC;IACpB,0CAA0C;IAC1C,MAAM,EAAE,GAAG,CAAC,MAAM,CAAC,CAAC;IACpB;;;;;;;;uEAQmE;IACnE,MAAM,EAAE,GAAG,CAAC,MAAM,CAAC,CAAC;CACrB;AAED;;;;;;;GAOG;AACH,MAAM,MAAM,eAAe,GAAG,WAAW,GAAG,SAAS,GAAG,QAAQ,CAAC;AAEjE,4DAA4D;AAC5D,MAAM,MAAM,gBAAgB,GAAG,KAAK,GAAG;IACrC,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB,KAAK,CAAC,EAAE,eAAe,CAAC;IACxB,oFAAoF;IACpF,MAAM,CAAC,EAAE,MAAM,CAAC;CACjB,CAAC;AAEF,MAAM,MAAM,YAAY,GAAG;IACzB;;;;;;;;;;;;;;;OAeG;IACH,IAAI,EAAE,YAAY,GAChB,YAAY,GACZ,iBAAiB,GAAG;QAClB,sBAAsB,CACpB,OAAO,EAAE,aAAa,EACtB,WAAW,EAAE,aAAa,GAAG,SAAS,EACtC,OAAO,CAAC,EAAE;YAAE,gBAAgB,CAAC,EAAE,OAAO,CAAA;SAAE,GACvC,IAAI,CAAC;KACT,CAAC;IACJ,cAAc,CAAC,EAAE,OAAO,CAAC;IACzB;;;;;;;OAOG;IACH,sBAAsB,CAAC,EAAE,oBAAoB,CAAC;IAC9C;;;;;;;;;OASG;IACH,kCAAkC,CAAC,EAAE;QACnC,2DAA2D;QAC3D,QAAQ,EAAE,MAAM,CAAC;QACjB,wEAAwE;QACxE,mBAAmB,EAAE,MAAM,EAAE,CAAC;QAC9B,kEAAkE;QAClE,QAAQ,CAAC,EAAE,MAAM,CAAC;KACnB,CAAC;IACF;;;;;;;OAOG;IACH,sBAAsB,CAAC,EAAE,OAAO,CAAC;IACjC;;;;;;OAMG;IACH,0BAA0B,CAAC,EAAE;QAC3B,QAAQ,EAAE,MAAM,CAAC;QACjB,mBAAmB,EAAE,MAAM,EAAE,CAAC;QAC9B,QAAQ,CAAC,EAAE,MAAM,CAAC;KACnB,CAAC;IACF,eAAe,CAAC,EAAE;QAChB,IAAI,EAAE,MAAM,GAAG,WAAW,CAAC;QAC3B,WAAW,EAAE,OAAO,CAAC;QACrB,OAAO,EAAE,MAAM,CAAC;KACjB,EAAE,CAAC;IACJ,eAAe,CAAC,EAAE,eAAe,CAAC;IAClC,iBAAiB,CAAC,EAAE,MAAM,EAAE,CAAC;IAC7B,gBAAgB,CAAC,EAAE;QACjB,IAAI,EAAE,MAAM,EAAE,CAAC;QACf,UAAU,EAAE,MAAM,EAAE,CAAC;KACtB,CAAC;IACF,mBAAmB,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,UAAU,CAAC,CAAC;IACjD,gBAAgB,CAAC,EAAE,cAAc,CAAC;IAClC,aAAa,CAAC,EAAE,OAAO,CAAC;IACxB,YAAY,CAAC,EAAE,MAAM,CAAC;IACtB,GAAG,CAAC,EAAE,MAAM,CAAC;IACb,QAAQ,CAAC,EAAE,MAAM,CAAC;IAClB,yEAAyE;IACzE,sBAAsB,CAAC,EAAE,MAAM,CAAC;IAChC;;;;OAIG;IACH,2BAA2B,CAAC,EAAE,OAAO,CAAC;IACtC,8EAA8E;IAC9E,2BAA2B,CAAC,EAAE,MAAM,CAAC;IAGrC,aAAa,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAC;IACxC,aAAa,CAAC,EAAE,MAAM,CAAC;IACvB;;;;;;;OAOG;IACH,YAAY,CAAC,EAAE,MAAM,CAAC;IACtB,qBAAqB,CAAC,EAAE,wBAAwB,EAAE,CAAC;IACnD,8BAA8B,CAAC,EAAE,8BAA8B,CAAC;IAChE,mBAAmB,CAAC,EAAE,mBAAmB,CAAC;IAC1C,eAAe,CAAC,EAAE,OAAO,CAAC;IAC1B,kBAAkB,CAAC,EAAE,MAAM,CAAC;IAC5B,sBAAsB,CAAC,EAAE,OAAO,CAAC;IACjC,wBAAwB,CAAC,EAAE,MAAM,CAAC;IAClC,iBAAiB,CAAC,EAAE,MAAM,CAAC;IAC3B,iBAAiB,CAAC,EAAE,OAAO,CAAC;IAC5B,iBAAiB,CAAC,EAAE,gBAAgB,EAAE,CAAC;IACvC,aAAa,CAAC,EAAE,gBAAgB,EAAE,CAAC;IACnC,WAAW,CAAC,EAAE,eAAe,EAAE,CAAC;IAChC,aAAa,CAAC,EAAE,KAAK,CAAC,YAAY,GAAG;QAAE,KAAK,EAAE,MAAM,CAAC;QAAC,KAAK,CAAC,EAAE,MAAM,CAAA;KAAE,CAAC,CAAC;IACxE,iBAAiB,CAAC,EAAE,GAAG,CAAC,MAAM,CAAC,CAAC;IAChC,SAAS,CAAC,EAAE;QACV,KAAK,EAAE;YACL,EAAE,EAAE,MAAM,CAAC;YACX,OAAO,EAAE,MAAM,CAAC;YAChB,MAAM,EAAE,SAAS,GAAG,aAAa,GAAG,WAAW,GAAG,WAAW,GAAG,QAAQ,CAAC;YACzE,SAAS,EAAE,MAAM,CAAC;YAClB,SAAS,CAAC,EAAE,MAAM,CAAC;YACnB,+CAA+C;YAC/C,aAAa,CAAC,EAAE,MAAM,CAAC;SACxB,EAAE,CAAC;QACJ,WAAW,EAAE,MAAM,CAAC;KACrB,CAAC;IACF,SAAS,CAAC,EAAE,iBAAiB,CAAC;IAC9B,YAAY,CAAC,EAAE;QAAE,WAAW,CAAC,EAAE,MAAM,CAAC;QAAC,UAAU,CAAC,EAAE,MAAM,CAAA;KAAE,CAAC;IAC7D,oBAAoB,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;IAC9C,WAAW,CAAC,EAAE,MAAM,CAAC;IACrB,WAAW,CAAC,EAAE,WAAW,CAAC;IAC1B;;;;;;OAMG;IACH,0BAA0B,CAAC,EAAE,MAAM,CAAC;IACpC,cAAc,CAAC,EAAE,mBAAmB,EAAE,CAAC;IACvC,YAAY,CAAC,EAAE,YAAY,CAAC;IAC5B,UAAU,CAAC,EAAE,MAAM,CAAC;IACpB,cAAc,CAAC,EAAE,OAAO,CAAC;IACzB,eAAe,CAAC,EAAE;QAChB,aAAa,EAAE,MAAM,CAAC;QACtB,SAAS,EAAE,MAAM,CAAC;QAClB,UAAU,EAAE,MAAM,CAAC;QACnB,WAAW,EAAE,MAAM,CAAC;QACpB,YAAY,EAAE,MAAM,CAAC;QACrB,QAAQ,EAAE,sBAAsB,EAAE,CAAC;QACnC,YAAY,EAAE,MAAM,CAAC;QACrB,iBAAiB,CAAC,EAAE,MAAM,CAAC;QAC3B,mBAAmB,CAAC,EAAE,OAAO,CAAC;QAC9B,eAAe,CAAC,EAAE,MAAM,CAAC;QACzB,iBAAiB,CAAC,EAAE,MAAM,CAAC;KAC5B,CAAC;IACF,QAAQ,CAAC,EAAE,OAAO,GAAG,QAAQ,GAAG,OAAO,GAAG,aAAa,CAAC;IACxD;;;;;;;;OAQG;IACH,mBAAmB,CAAC,EAAE,yBAAyB,CAAC;IAChD,wBAAwB,CAAC,EAAE;QACzB,EAAE,EAAE,MAAM,CAAC;QACX,OAAO,EAAE,aAAa,CAAC;QACvB;;;;;;;WAOG;QACH,mBAAmB,CAAC,EAAE,OAAO,CAAC;KAC/B,CAAC;IACF;;;;;OAKG;IACH,eAAe,CAAC,EAAE,OAAO,CAAC,oBAAoB,CAAC,CAAC;IAChD,0BAA0B,CAAC,EAAE;QAC3B,OAAO,EAAE,aAAa,CAAC;KACxB,CAAC;IACF,kCAAkC,CAAC,EAAE,MAAM,CAAC;IAC5C,8GAA8G;IAC9G,8BAA8B,CAAC,EAAE;QAC/B,SAAS,EAAE,MAAM,CAAC;KACnB,CAAC;IACF;;;;;;;OAOG;IACH,yBAAyB,CAAC,EAAE,MAAM,EAAE,CAAC;IACrC,4BAA4B,CAAC,EAAE;QAC7B,SAAS,EAAE,MAAM,CAAC;QAClB,QAAQ,EAAE,MAAM,CAAC;QACjB,QAAQ,EACJ;YAAE,MAAM,EAAE,cAAc,CAAC;YAAC,UAAU,EAAE,MAAM,CAAA;SAAE,GAC9C;YACE,MAAM,EAAE,QAAQ,CAAC;YACjB,WAAW,EAAE,MAAM,CAAC;YACpB,UAAU,EAAE,MAAM,CAAC;YACnB,OAAO,EACH;gBAAE,IAAI,EAAE,SAAS,CAAA;aAAE,GACnB;gBAAE,IAAI,EAAE,kBAAkB,CAAC;gBAAC,OAAO,EAAE,MAAM,CAAA;aAAE,GAC7C;gBAAE,IAAI,EAAE,WAAW,CAAC;gBAAC,OAAO,EAAE,MAAM,CAAA;aAAE,CAAC;SAC5C,GACD;YAAE,MAAM,EAAE,OAAO,CAAC;YAAC,UAAU,EAAE,MAAM,CAAA;SAAE,CAAC;QAC5C,UAAU,CAAC,EAAE;YAAE,MAAM,EAAE,MAAM,CAAC;YAAC,OAAO,EAAE,MAAM,CAAC;YAAC,IAAI,EAAE,MAAM,CAAA;SAAE,CAAC;QAC/D,cAAc,CAAC,EAAE;YAAE,OAAO,EAAE,MAAM,EAAE,CAAC;YAAC,OAAO,CAAC,EAAE,MAAM,CAAC;YAAC,OAAO,CAAC,EAAE,MAAM,CAAA;SAAE,CAAC;QAC3E,QAAQ,EAAE,GAAG,CAAC;QACd,WAAW,CAAC,EAAE,gBAAgB,EAAE,CAAC;QACjC,UAAU,CAAC,EAAE,MAAM,CAAC;QACpB,SAAS,CAAC,EAAE,MAAM,CAAC;QACnB,6GAA6G;QAC7G,iBAAiB,CAAC,EAAE,MAAM,CAAC;KAC5B,CAAC;IACF,6BAA6B,CAAC,EAAE,GAAG,CAAC,MAAM,CAAC,CAAC;IAC5C,WAAW,CAAC,EAAE,UAAU,EAAE,CAAC;IAC3B,8CAA8C;IAC9C,eAAe,CAAC,EAAE,eAAe,CAAC;IAClC,8FAA8F;IAC9F,yBAAyB,CAAC,EAAE,GAAG,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;IAChD,oHAAoH;IACpH,yBAAyB,CAAC,EAAE,GAAG,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;IAChD,8EAA8E;IAC9E,eAAe,CAAC,EAAE,GAAG,CAAC,MAAM,CAAC,CAAC;IAC9B,8FAA8F;IAC9F,cAAc,CAAC,EAAE,cAAc,CAAC;IAChC,0BAA0B;IAC1B,gBAAgB,CAAC,EAAE,MAAM,CAAC;IAC1B,iDAAiD;IACjD,gBAAgB,CAAC,EAAE,KAAK,CAAC;QAAE,EAAE,EAAE,MAAM,CAAC;QAAC,IAAI,EAAE,MAAM,CAAC;QAAC,WAAW,CAAC,EAAE,MAAM,CAAA;KAAE,CAAC,CAAC;IAC7E,0EAA0E;IAC1E,gBAAgB,CAAC,EAAE,GAAG,CACpB,MAAM,EACN,aAAa,GAAG,SAAS,GAAG,QAAQ,GAAG,QAAQ,GAAG,SAAS,CAC5D,CAAC;IACF,qEAAqE;IACrE,wBAAwB,CAAC,EAAE,MAAM,CAAC;IAElC,eAAe,CAAC,EAAE;QAChB,IAAI,EAAE,MAAM,CAAC;QACb,aAAa,EAAE,MAAM,CAAC;KACvB,CAAC;IACF,6BAA6B,CAAC,EAAE,OAAO,CAAC;IACxC,uBAAuB,CAAC,EAAE,MAAM,CAAC;IACjC,gBAAgB,CAAC,EAAE,OAAO,CAAC;IAC3B,yEAAyE;IACzE,wBAAwB,CAAC,EAAE,OAAO,CAAC;IAGnC,kFAAkF;IAClF,sCAAsC,CAAC,EAAE,OAAO,CAAC;IACjD,sFAAsF;IACtF,kCAAkC,CAAC,EAAE,0BAA0B,EAAE,CAAC;IAClE,0FAA0F;IAC1F,4BAA4B,CAAC,EAAE,OAAO,CAAC;IACvC,0FAA0F;IAC1F,mBAAmB,CAAC,EAAE;QACpB,SAAS,EAAE,MAAM,CAAC;QAClB,gBAAgB,EAAE,0BAA0B,EAAE,CAAC;KAChD,CAAC;IACF,gGAAgG;IAChG,2BAA2B,CAAC,EAAE,oBAAoB,EAAE,CAAC;IACrD;;;;;;;;;OASG;IACH,uBAAuB,CAAC,EAAE,MAAM,CAAC;CAClC,CAAC;AAEF,MAAM,MAAM,uBAAuB,GAAG,eAAe,GAAG;IACtD,gBAAgB,EAAE,gBAAgB,CAAC;IACnC,QAAQ,EAAE,QAAQ,CAAC;IACnB;;;OAGG;IACH,UAAU,CAAC,EAAE,UAAU,CAAC;IACxB;;;;;;;;;;OAUG;IACH,WAAW,CAAC,EAAE,kBAAkB,CAAC;IACjC;;;;;;OAMG;IACH,gBAAgB,EAAE,gBAAgB,CAAC;IACnC,OAAO,EAAE,kBAAkB,CAAC,eAAe,CAAC,CAAC;IAC7C,mBAAmB,EAAE,mBAAmB,CAAC;IACzC,gBAAgB,EAAE,gBAAgB,CAAC;IACnC,gBAAgB,EAAE,gBAAgB,CAAC;IACnC,eAAe,EAAE,eAAe,CAAC;IACjC,WAAW,EAAE,WAAW,CAAC;IACzB,gBAAgB,EAAE,gBAAgB,CAAC;IACnC,aAAa,EAAE,aAAa,CAAC;IAC7B,gBAAgB,EAAE,gBAAgB,CAAC;IACnC,YAAY,EAAE,YAAY,CAAC;IAC3B,qBAAqB,EAAE,qBAAqB,CAAC;IAC7C,SAAS,EAAE,SAAS,CAAC;IACrB,gBAAgB,EAAE,0BAA0B,CAAC;IAC7C,sBAAsB,EAAE,CAAC,SAAS,EAAE,MAAM,KAAK,IAAI,CAAC;IACpD,6BAA6B,EAAE,CAC7B,OAAO,EAAE,iBAAiB,KACvB,OAAO,CAAC,iBAAiB,GAAG,SAAS,CAAC,CAAC;IAC5C,UAAU,CAAC,EAAE,aAAa,CAAC;IAC3B,gBAAgB,CAAC,EAAE,gBAAgB,CAAC;IACpC;;;;;;OAMG;IACH,SAAS,CAAC,EAAE,SAAS,CAAC;IACtB;;;;;;;;;;OAUG;IACH,iBAAiB,CAAC,EAAE,MAAM,MAAM,GAAG,SAAS,CAAC;CAC9C,CAAC;AAEF;;;;;;GAMG;AACH,UAAU,sBAAsB,CAC9B,KAAK,SAAS,MAAM,CAAC,MAAM,EAAE,IAAI,CAAC,CAClC,SAAQ,IAAI,CAAC,0BAA0B,CAAC,KAAK,CAAC,EAAE,OAAO,GAAG,gBAAgB,CAAC;IAC3E,iGAAiG;IACjG,KAAK,CAAC,EAAE,eAAe,CAAC;CACzB"}
+{"version":3,"file":"clark-fsm.d.ts","sourceRoot":"","sources":["../../../src/ai-service/state-machine/clark-fsm.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,eAAe,EAAE,MAAM,kBAAkB,CAAC;AAExD,OAAO,KAAK,EAAE,YAAY,EAAoC,MAAM,IAAI,CAAC;AACzE,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,MAAM,CAAC;AAE1C,OAAO,KAAK,EACV,iBAAiB,EACjB,iBAAiB,EACjB,wBAAwB,EACxB,aAAa,EACb,mBAAmB,EACnB,8BAA8B,EAC9B,0BAA0B,EAC1B,gBAAgB,EAChB,MAAM,EACN,WAAW,EAGX,aAAa,EACb,yBAAyB,EACzB,gBAAgB,EAChB,oBAAoB,EACpB,cAAc,EACd,eAAe,EACf,YAAY,EACZ,oBAAoB,EACpB,oBAAoB,EACrB,MAAM,uCAAuC,CAAC;AAC/C,OAAO,KAAK,EACV,sBAAsB,EACtB,oBAAoB,EACpB,kBAAkB,EACnB,MAAM,yBAAyB,CAAC;AAEjC,OAAO,KAAK,EAAE,UAAU,EAAE,MAAM,4BAA4B,CAAC;AAG7D,OAAO,KAAK,EAAE,cAAc,EAAE,MAAM,+BAA+B,CAAC;AACpE,OAAO,KAAK,EAAE,qBAAqB,EAAE,MAAM,uCAAuC,CAAC;AACnF,OAAO,KAAK,EAAE,YAAY,EAAE,MAAM,6BAA6B,CAAC;AAChE,OAAO,KAAK,EAAE,kBAAkB,EAAE,MAAM,8BAA8B,CAAC;AACvE,OAAO,KAAK,EAAE,oBAAoB,EAAE,IAAI,EAAE,MAAM,0BAA0B,CAAC;AAC3E,OAAO,KAAK,EAAE,mBAAmB,EAAE,MAAM,2CAA2C,CAAC;AACrF,OAAO,KAAK,EAAE,gBAAgB,EAAE,MAAM,wCAAwC,CAAC;AAC/E,OAAO,KAAK,EAAE,QAAQ,EAAE,MAAM,2BAA2B,CAAC;AAC1D,OAAO,KAAK,EAAE,gBAAgB,EAAE,MAAM,+BAA+B,CAAC;AACtE,OAAO,KAAK,EAAE,eAAe,EAAE,MAAM,2BAA2B,CAAC;AACjE,OAAO,KAAK,EAAE,qBAAqB,EAAE,MAAM,gBAAgB,CAAC;AAC5D,OAAO,KAAK,EAAE,gBAAgB,EAAE,MAAM,0BAA0B,CAAC;AACjE,OAAO,KAAK,EAAE,gBAAgB,EAAE,MAAM,mCAAmC,CAAC;AAC1E,OAAO,KAAK,EAAE,YAAY,EAAE,MAAM,uBAAuB,CAAC;AAC1D,OAAO,KAAK,EAAE,SAAS,EAAE,0BAA0B,EAAE,MAAM,kBAAkB,CAAC;AAO9E,OAAO,KAAK,EAAE,gBAAgB,EAAE,MAAM,8BAA8B,CAAC;AAOrE,OAAO,KAAK,EAAE,gBAAgB,EAAE,MAAM,iBAAiB,CAAC;AACxD,OAAO,KAAK,EAAE,gBAAgB,EAAE,MAAM,gCAAgC,CAAC;AAEvE,OAAO,KAAK,EAAE,WAAW,EAAE,MAAM,iBAAiB,CAAC;AACnD,OAAO,KAAK,EACV,sBAAsB,EAEvB,MAAM,oBAAoB,CAAC;AAC5B,OAAO,KAAK,EAAE,0BAA0B,EAAE,MAAM,6BAA6B,CAAC;AAC9E,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,+BAA+B,CAAC;AACnE,OAAO,KAAK,EAAE,mBAAmB,EAAE,MAAM,gEAAgE,CAAC;AAC1G,OAAO,KAAK,EAAE,gBAAgB,EAAE,MAAM,uBAAuB,CAAC;AAC9D,OAAO,KAAK,EAAE,SAAS,EAAE,MAAM,wBAAwB,CAAC;AACxD,OAAO,KAAK,EAAE,gBAAgB,EAAE,MAAM,yBAAyB,CAAC;AAChE,OAAO,KAAK,EACV,eAAe,EACf,eAAe,EACf,aAAa,EACb,UAAU,EACV,YAAY,EACZ,YAAY,EACZ,UAAU,EACX,MAAM,aAAa,CAAC;AACrB,OAAO,KAAK,EAAE,YAAY,EAAE,MAAM,sBAAsB,CAAC;AAGzD,OAAO,KAAK,EACV,qBAAqB,EACrB,2BAA2B,EAC5B,MAAM,UAAU,CAAC;AAElB,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,6BAA6B,CAAC;AAKjE,OAAO,KAAK,EAAE,iBAAiB,EAAE,MAAM,0BAA0B,CAAC;AAClE,OAAO,EACL,SAAS,EACT,KAAK,IAAI,EACT,KAAK,yBAAyB,EAC9B,KAAK,2BAA2B,EACjC,MAAM,iBAAiB,CAAC;AAEzB,QAAA,MAAM,CAAC;;;;;;;;CAQG,CAAC;AAEX,eAAO,MAAM,eAAe;;;;;;;;CAAI,CAAC;AACjC,MAAM,MAAM,UAAU,GAAG,MAAM,OAAO,CAAC,CAAC;AAExC,eAAO,MAAM,gBAAgB,mBAAmB,CAAC;AACjD,eAAO,MAAM,mBAAmB,sBAAsB,CAAC;AACvD,eAAO,MAAM,mBAAmB,sBAAsB,CAAC;AACvD,eAAO,MAAM,aAAa,iBAAiB,CAAC;AAC5C,eAAO,MAAM,aAAa,iBAAiB,CAAC;AAC5C,eAAO,MAAM,4BAA4B,6BAA6B,CAAC;AACvE,eAAO,MAAM,sBAAsB,wBAAwB,CAAC;AAC5D,eAAO,MAAM,aAAa,gBAAgB,CAAC;AAC3C,eAAO,MAAM,cAAc,kBAAkB,CAAC;AAC9C,QAAA,MAAM,qBAAqB,wBAAwB,CAAC;AACpD,eAAO,MAAM,yBAAyB,4BAA4B,CAAC;AACnE,eAAO,MAAM,WAAW,eAAe,CAAC;AACxC,eAAO,MAAM,YAAY,gBAAgB,CAAC;AAC1C,eAAO,MAAM,uBAAuB,0BAA0B,CAAC;AAC/D,eAAO,MAAM,wBAAwB,2BAA2B,CAAC;AACjE,eAAO,MAAM,uBAAuB,0BAA0B,CAAC;AAC/D,eAAO,MAAM,iCAAiC,kCACb,CAAC;AAClC,eAAO,MAAM,sBAAsB,yBAAyB,CAAC;AAC7D,eAAO,MAAM,oBAAoB,uBAAuB,CAAC;AACzD,eAAO,MAAM,0BAA0B,4BAA4B,CAAC;AACpE,eAAO,MAAM,iBAAiB,oBAAoB,CAAC;AAEnD,MAAM,MAAM,UAAU,GAClB;IACE,IAAI,EAAE,OAAO,gBAAgB,CAAC;IAC9B,OAAO,EAAE,iBAAiB,CAAC;IAC3B,WAAW,CAAC,EAAE,aAAa,CAAC;IAC5B,6BAA6B,CAAC,EAAE,OAAO,CAAC;IACxC;;;;;;OAMG;IACH,QAAQ,CAAC,EAAE,OAAO,CAAC;IACnB;;;;OAIG;IACH,oBAAoB,CAAC,EAAE,OAAO,CAAC;CAChC,GACD;IAAE,IAAI,EAAE,OAAO,mBAAmB,CAAC;IAAC,QAAQ,CAAC,EAAE,OAAO,CAAA;CAAE,GACxD;IAAE,IAAI,EAAE,OAAO,mBAAmB,CAAC;IAAC,QAAQ,CAAC,EAAE,OAAO,CAAA;CAAE,GACxD;IAAE,IAAI,EAAE,OAAO,aAAa,CAAC;IAAC,OAAO,CAAC,EAAE,aAAa,CAAA;CAAE,GACvD;IACE,IAAI,EAAE,OAAO,aAAa,CAAC;IAC3B,UAAU,EAAE,MAAM,CAAC;IACnB,aAAa,CAAC,EAAE,aAAa,CAAC;IAC9B,SAAS,CAAC,EAAE,OAAO,CAAC;IACpB,yGAAyG;IACzG,YAAY,CAAC,EAAE,OAAO,CAAC;IACvB;;;;OAIG;IACH,yBAAyB,CAAC,EAAE,MAAM,CAAC;IACnC,kBAAkB,CAAC,EAAE,MAAM,CAAC;CAC7B,GACD;IAAE,IAAI,EAAE,OAAO,4BAA4B,CAAC;IAAC,KAAK,EAAE,KAAK,CAAA;CAAE,GAC3D;IACE,IAAI,EAAE,OAAO,sBAAsB,CAAC;IACpC,MAAM,CAAC,EAAE,MAAM,CAAC;IAChB,mGAAmG;IACnG,qBAAqB,CAAC,EAAE,OAAO,CAAC;IAChC;;;;OAIG;IACH,mBAAmB,CAAC,EAAE,OAAO,CAAC;CAC/B,GACD;IAAE,IAAI,EAAE,OAAO,aAAa,CAAA;CAAE,GAC9B;IACE,IAAI,EAAE,OAAO,cAAc,CAAC;IAC5B,MAAM,CAAC,EAAE,MAAM,CAAC;IAChB,OAAO,EAAE,aAAa,CAAC;IACvB,aAAa,CAAC,EAAE,oBAAoB,CAAC;CACtC,GACD;IAAE,IAAI,EAAE,OAAO,qBAAqB,CAAC;IAAC,MAAM,EAAE,MAAM,CAAA;CAAE,GACtD;IACE,IAAI,EAAE,OAAO,yBAAyB,CAAC;IACvC,YAAY,EAAE,YAAY,CAAC;CAC5B,GACD;IAAE,IAAI,EAAE,OAAO,WAAW,CAAC;IAAC,KAAK,EAAE,gBAAgB,CAAA;CAAE,GACrD;IACE,IAAI,EAAE,OAAO,YAAY,CAAC;IAC1B,KAAK,EAAE,YAAY,EAAE,CAAC;CACvB,GACD;IAAE,IAAI,EAAE,OAAO,uBAAuB,CAAC;IAAC,KAAK,EAAE,KAAK,CAAA;CAAE,GACtD;IACE,IAAI,EAAE,OAAO,wBAAwB,CAAC;IACtC,KAAK,EAAE,YAAY,EAAE,CAAC;CACvB,GACD;IAAE,IAAI,EAAE,OAAO,uBAAuB,CAAA;CAAE,GACxC;IAAE,IAAI,EAAE,OAAO,iCAAiC,CAAA;CAAE,GAClD;IACE,IAAI,EAAE,OAAO,sBAAsB,CAAC;IACpC,cAAc,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,EAAE,CAAC,CAAC;IACzC,gBAAgB,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,EAAE,CAAC,CAAC;IAC3C,uBAAuB,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,EAAE,CAAC,CAAC;CACnD,GACD;IAAE,IAAI,EAAE,OAAO,oBAAoB,CAAC;IAAC,KAAK,EAAE,KAAK,CAAA;CAAE,GACnD;IAAE,IAAI,EAAE,OAAO,0BAA0B,CAAA;CAAE,GAC3C;IAAE,IAAI,EAAE,OAAO,iBAAiB,CAAC;IAAC,aAAa,CAAC,EAAE,OAAO,CAAA;CAAE,CAAC;AAGhE,eAAO,MAAM,WAAW;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAiDd,CAAC;AAEX,MAAM,MAAM,KAAK,GAAG,OAAO,CAAC,CAAC,IAAI,CAAC;AAClC,MAAM,MAAM,cAAc,GAAG,OAAO,CAAC,CAAC,aAAa,CAAC;AACpD,MAAM,MAAM,cAAc,GAAG,OAAO,CAAC,CAAC,aAAa,CAAC;AACpD,MAAM,MAAM,aAAa,GAAG,OAAO,CAAC,CAAC,YAAY,CAAC;AAClD,MAAM,MAAM,eAAe,GAAG,OAAO,CAAC,CAAC,cAAc,CAAC;AACtD,MAAM,MAAM,iBAAiB,GAAG,OAAO,CAAC,CAAC,gBAAgB,CAAC;AAE1D,MAAM,MAAM,6BAA6B,GAAG,2BAA2B,CACrE,UAAU,EACV,UAAU,CACX,CAAC;AAEF,MAAM,MAAM,uBAAuB,GAAG,2BAA2B,CAC/D,UAAU,EACV,UAAU,EACV,YAAY,CACb,CAAC;AAEF,qBAAa,KAAM,SAAQ,SAAS,CAAC,UAAU,EAAE,UAAU,EAAE,YAAY,CAAC;IACxE,OAAO,CAAC,wBAAwB,CAAqC;IACrE,OAAO,CAAC,sBAAsB,CAAK;gBAEvB,MAAM,EAAE;QAClB,cAAc,EAAE,YAAY,CAAC;QAC7B,uBAAuB,EAAE,6BAA6B,CAAC;QACvD,YAAY,CAAC,EAAE,MAAM,MAAM,GAAG,SAAS,CAAC;QACxC,iBAAiB,CAAC,EAAE,uBAAuB,CAAC;KAC7C;IAQM,gBAAgB,CAAC,KAAK,EAAE,qBAAqB,GAAG,oBAAoB;IA0BpE,YAAY,IAAI,IAAI;cAyFR,kBAAkB,CACnC,aAAa,EAAE,UAAU,GACxB,sBAAsB;cASN,mBAAmB,CACpC,KAAK,EAAE,UAAU,GAChB,yBAAyB;cAiBT,aAAa,CAAC,KAAK,EAAE,UAAU,GAAG,OAAO,CAAC,UAAU,CAAC;cAerD,qBAAqB,CACtC,MAAM,EAAE,qBAAqB,CAAC,UAAU,EAAE,UAAU,CAAC,GACpD,IAAI;IAIP;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;OA+BG;IACG,UAAU,CAAC,KAAK,SAAS,MAAM,CAAC,MAAM,EAAE,IAAI,CAAC,EACjD,QAAQ,EAAE,uBAAuB,EACjC,OAAO,EAAE,sBAAsB,CAAC,KAAK,CAAC,GACrC,OAAO,CAAC,gBAAgB,CAAC,KAAK,CAAC,CAAC;IA0OnC,OAAO,CAAC,MAAM,CAAC,QAAQ,CAAC,iBAAiB,CAa9B;IAEX;;;;;;;;;;;;;;;;OAgBG;IACG,mBAAmB,CACvB,QAAQ,EAAE,IAAI,CACZ,uBAAuB,EACvB,kBAAkB,GAAG,kBAAkB,GAAG,eAAe,CAC1D,EACD,KAAK,EAAE,MAAM,EACb,OAAO,EAAE,MAAM,GACd,OAAO,CAAC,IAAI,CAAC;IAsBhB,OAAO,CAAC,eAAe;IA2CvB;;;;OAIG;IACH,sBAAsB,IAAI,OAAO;IAQjC,oBAAoB,CAAC,QAAQ,EAAE,oBAAoB,GAAG,IAAI;IAI1D,qBAAqB,IAAI,IAAI;IAK7B,mFAAmF;IACnF,yBAAyB,IAAI,MAAM;IAInC,OAAO,CAAC,gBAAgB;CAUzB;AAED,MAAM,MAAM,eAAe,GAAG,qBAAqB,CAAC,UAAU,EAAE,UAAU,CAAC,CAAC;AAE5E,KAAK,wBAAwB,GAAG,CAC9B,KAAK,EAAE,KAAK,EACZ,MAAM,EAAE,uBAAuB,KAC5B,CAAC,UAAU,EAAE,eAAe,KAAK,OAAO,CAAC,IAAI,CAAC,CAAC;AAEpD,MAAM,MAAM,0BAA0B,GAAG;KACtC,CAAC,IAAI,UAAU,GAAG,wBAAwB;CAC5C,CAAC;AAEF,MAAM,MAAM,mBAAmB,CAAC,CAAC,SAAS,UAAU,IAClD,MAAM,CAAC,OAAO,WAAW,CAAC,CAAC,CAAC,CAAC,SAAS,KAAK,GACvC,KAAK,GACL;KACG,CAAC,IAAI,MAAM,CAAC,OAAO,WAAW,CAAC,CAAC,CAAC,CAAC,GAAG,OAAO,CAAC,UAAU,EAAE;QAAE,IAAI,EAAE,CAAC,CAAA;KAAE,CAAC;CACvE,CAAC,MAAM,CAAC,OAAO,WAAW,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC;AAEvC;;;;;;;;;GASG;AACH,MAAM,WAAW,eAAe;IAC9B,oEAAoE;IACpE,QAAQ,EAAE,GAAG,CAAC,MAAM,CAAC,CAAC;IACtB,iDAAiD;IACjD,MAAM,EAAE,GAAG,CAAC,MAAM,CAAC,CAAC;IACpB,0CAA0C;IAC1C,MAAM,EAAE,GAAG,CAAC,MAAM,CAAC,CAAC;IACpB;;;;;;;;uEAQmE;IACnE,MAAM,EAAE,GAAG,CAAC,MAAM,CAAC,CAAC;CACrB;AAED;;;;;;;GAOG;AACH,MAAM,MAAM,eAAe,GAAG,WAAW,GAAG,SAAS,GAAG,QAAQ,CAAC;AAEjE,4DAA4D;AAC5D,MAAM,MAAM,gBAAgB,GAAG,KAAK,GAAG;IACrC,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB,KAAK,CAAC,EAAE,eAAe,CAAC;IACxB,oFAAoF;IACpF,MAAM,CAAC,EAAE,MAAM,CAAC;CACjB,CAAC;AAEF,MAAM,MAAM,YAAY,GAAG;IACzB;;;;;;;;;;;;;;;OAeG;IACH,IAAI,EAAE,YAAY,GAChB,YAAY,GACZ,iBAAiB,GAAG;QAClB,sBAAsB,CACpB,OAAO,EAAE,aAAa,EACtB,WAAW,EAAE,aAAa,GAAG,SAAS,EACtC,OAAO,CAAC,EAAE;YAAE,gBAAgB,CAAC,EAAE,OAAO,CAAA;SAAE,GACvC,IAAI,CAAC;KACT,CAAC;IACJ,cAAc,CAAC,EAAE,OAAO,CAAC;IACzB;;;;;;;OAOG;IACH,sBAAsB,CAAC,EAAE,oBAAoB,CAAC;IAC9C;;;;;;;;;OASG;IACH,kCAAkC,CAAC,EAAE;QACnC,2DAA2D;QAC3D,QAAQ,EAAE,MAAM,CAAC;QACjB,wEAAwE;QACxE,mBAAmB,EAAE,MAAM,EAAE,CAAC;QAC9B,kEAAkE;QAClE,QAAQ,CAAC,EAAE,MAAM,CAAC;KACnB,CAAC;IACF;;;;;;;OAOG;IACH,sBAAsB,CAAC,EAAE,OAAO,CAAC;IACjC;;;;;;OAMG;IACH,0BAA0B,CAAC,EAAE;QAC3B,QAAQ,EAAE,MAAM,CAAC;QACjB,mBAAmB,EAAE,MAAM,EAAE,CAAC;QAC9B,QAAQ,CAAC,EAAE,MAAM,CAAC;KACnB,CAAC;IACF,eAAe,CAAC,EAAE;QAChB,IAAI,EAAE,MAAM,GAAG,WAAW,CAAC;QAC3B,WAAW,EAAE,OAAO,CAAC;QACrB,OAAO,EAAE,MAAM,CAAC;KACjB,EAAE,CAAC;IACJ,eAAe,CAAC,EAAE,eAAe,CAAC;IAClC,gBAAgB,CAAC,EAAE;QACjB,IAAI,EAAE,MAAM,EAAE,CAAC;QACf,UAAU,EAAE,MAAM,EAAE,CAAC;KACtB,CAAC;IACF,mBAAmB,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,UAAU,CAAC,CAAC;IACjD,gBAAgB,CAAC,EAAE,cAAc,CAAC;IAClC,aAAa,CAAC,EAAE,OAAO,CAAC;IACxB,YAAY,CAAC,EAAE,MAAM,CAAC;IACtB,GAAG,CAAC,EAAE,MAAM,CAAC;IACb,QAAQ,CAAC,EAAE,MAAM,CAAC;IAClB,yEAAyE;IACzE,sBAAsB,CAAC,EAAE,MAAM,CAAC;IAChC;;;;OAIG;IACH,2BAA2B,CAAC,EAAE,OAAO,CAAC;IACtC,8EAA8E;IAC9E,2BAA2B,CAAC,EAAE,MAAM,CAAC;IAGrC,aAAa,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAC;IACxC,aAAa,CAAC,EAAE,MAAM,CAAC;IACvB;;;;;;;OAOG;IACH,YAAY,CAAC,EAAE,MAAM,CAAC;IACtB,qBAAqB,CAAC,EAAE,wBAAwB,EAAE,CAAC;IACnD,8BAA8B,CAAC,EAAE,8BAA8B,CAAC;IAChE,mBAAmB,CAAC,EAAE,mBAAmB,CAAC;IAC1C,eAAe,CAAC,EAAE,OAAO,CAAC;IAC1B,kBAAkB,CAAC,EAAE,MAAM,CAAC;IAC5B,sBAAsB,CAAC,EAAE,OAAO,CAAC;IACjC,wBAAwB,CAAC,EAAE,MAAM,CAAC;IAClC,iBAAiB,CAAC,EAAE,MAAM,CAAC;IAC3B,iBAAiB,CAAC,EAAE,OAAO,CAAC;IAC5B,iBAAiB,CAAC,EAAE,gBAAgB,EAAE,CAAC;IACvC,aAAa,CAAC,EAAE,gBAAgB,EAAE,CAAC;IACnC,WAAW,CAAC,EAAE,eAAe,EAAE,CAAC;IAChC,aAAa,CAAC,EAAE,KAAK,CAAC,YAAY,GAAG;QAAE,KAAK,EAAE,MAAM,CAAC;QAAC,KAAK,CAAC,EAAE,MAAM,CAAA;KAAE,CAAC,CAAC;IACxE,iBAAiB,CAAC,EAAE,GAAG,CAAC,MAAM,CAAC,CAAC;IAChC,SAAS,CAAC,EAAE;QACV,KAAK,EAAE;YACL,EAAE,EAAE,MAAM,CAAC;YACX,OAAO,EAAE,MAAM,CAAC;YAChB,MAAM,EAAE,SAAS,GAAG,aAAa,GAAG,WAAW,GAAG,WAAW,GAAG,QAAQ,CAAC;YACzE,SAAS,EAAE,MAAM,CAAC;YAClB,SAAS,CAAC,EAAE,MAAM,CAAC;YACnB,+CAA+C;YAC/C,aAAa,CAAC,EAAE,MAAM,CAAC;SACxB,EAAE,CAAC;QACJ,WAAW,EAAE,MAAM,CAAC;KACrB,CAAC;IACF,SAAS,CAAC,EAAE,iBAAiB,CAAC;IAC9B,YAAY,CAAC,EAAE;QAAE,WAAW,CAAC,EAAE,MAAM,CAAC;QAAC,UAAU,CAAC,EAAE,MAAM,CAAA;KAAE,CAAC;IAC7D,oBAAoB,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;IAC9C,WAAW,CAAC,EAAE,MAAM,CAAC;IACrB,WAAW,CAAC,EAAE,WAAW,CAAC;IAC1B;;;;;;OAMG;IACH,0BAA0B,CAAC,EAAE,MAAM,CAAC;IACpC,cAAc,CAAC,EAAE,mBAAmB,EAAE,CAAC;IACvC,YAAY,CAAC,EAAE,YAAY,CAAC;IAC5B,UAAU,CAAC,EAAE,MAAM,CAAC;IACpB,cAAc,CAAC,EAAE,OAAO,CAAC;IACzB,eAAe,CAAC,EAAE;QAChB,aAAa,EAAE,MAAM,CAAC;QACtB,SAAS,EAAE,MAAM,CAAC;QAClB,UAAU,EAAE,MAAM,CAAC;QACnB,WAAW,EAAE,MAAM,CAAC;QACpB,YAAY,EAAE,MAAM,CAAC;QACrB,QAAQ,EAAE,sBAAsB,EAAE,CAAC;QACnC,YAAY,EAAE,MAAM,CAAC;QACrB,iBAAiB,CAAC,EAAE,MAAM,CAAC;QAC3B,mBAAmB,CAAC,EAAE,OAAO,CAAC;QAC9B,eAAe,CAAC,EAAE,MAAM,CAAC;QACzB,iBAAiB,CAAC,EAAE,MAAM,CAAC;KAC5B,CAAC;IACF,QAAQ,CAAC,EAAE,OAAO,GAAG,QAAQ,GAAG,OAAO,GAAG,aAAa,CAAC;IACxD;;;;;;;;OAQG;IACH,mBAAmB,CAAC,EAAE,yBAAyB,CAAC;IAChD,wBAAwB,CAAC,EAAE;QACzB,EAAE,EAAE,MAAM,CAAC;QACX,OAAO,EAAE,aAAa,CAAC;QACvB;;;;;;;WAOG;QACH,mBAAmB,CAAC,EAAE,OAAO,CAAC;KAC/B,CAAC;IACF;;;;;OAKG;IACH,eAAe,CAAC,EAAE,OAAO,CAAC,oBAAoB,CAAC,CAAC;IAChD,0BAA0B,CAAC,EAAE;QAC3B,OAAO,EAAE,aAAa,CAAC;KACxB,CAAC;IACF,kCAAkC,CAAC,EAAE,MAAM,CAAC;IAC5C,8GAA8G;IAC9G,8BAA8B,CAAC,EAAE;QAC/B,SAAS,EAAE,MAAM,CAAC;KACnB,CAAC;IACF;;;;;;;OAOG;IACH,yBAAyB,CAAC,EAAE,MAAM,EAAE,CAAC;IACrC,4BAA4B,CAAC,EAAE;QAC7B,SAAS,EAAE,MAAM,CAAC;QAClB,QAAQ,EAAE,MAAM,CAAC;QACjB,QAAQ,EACJ;YAAE,MAAM,EAAE,cAAc,CAAC;YAAC,UAAU,EAAE,MAAM,CAAA;SAAE,GAC9C;YACE,MAAM,EAAE,QAAQ,CAAC;YACjB,WAAW,EAAE,MAAM,CAAC;YACpB,UAAU,EAAE,MAAM,CAAC;YACnB,OAAO,EACH;gBAAE,IAAI,EAAE,SAAS,CAAA;aAAE,GACnB;gBAAE,IAAI,EAAE,kBAAkB,CAAC;gBAAC,OAAO,EAAE,MAAM,CAAA;aAAE,GAC7C;gBAAE,IAAI,EAAE,WAAW,CAAC;gBAAC,OAAO,EAAE,MAAM,CAAA;aAAE,CAAC;SAC5C,GACD;YAAE,MAAM,EAAE,OAAO,CAAC;YAAC,UAAU,EAAE,MAAM,CAAA;SAAE,CAAC;QAC5C,UAAU,CAAC,EAAE;YAAE,MAAM,EAAE,MAAM,CAAC;YAAC,OAAO,EAAE,MAAM,CAAC;YAAC,IAAI,EAAE,MAAM,CAAA;SAAE,CAAC;QAC/D,cAAc,CAAC,EAAE;YAAE,OAAO,EAAE,MAAM,EAAE,CAAC;YAAC,OAAO,CAAC,EAAE,MAAM,CAAC;YAAC,OAAO,CAAC,EAAE,MAAM,CAAA;SAAE,CAAC;QAC3E,QAAQ,EAAE,GAAG,CAAC;QACd,WAAW,CAAC,EAAE,gBAAgB,EAAE,CAAC;QACjC,UAAU,CAAC,EAAE,MAAM,CAAC;QACpB,SAAS,CAAC,EAAE,MAAM,CAAC;QACnB,6GAA6G;QAC7G,iBAAiB,CAAC,EAAE,MAAM,CAAC;KAC5B,CAAC;IACF,6BAA6B,CAAC,EAAE,GAAG,CAAC,MAAM,CAAC,CAAC;IAC5C,WAAW,CAAC,EAAE,UAAU,EAAE,CAAC;IAC3B,8CAA8C;IAC9C,eAAe,CAAC,EAAE,eAAe,CAAC;IAClC,8FAA8F;IAC9F,yBAAyB,CAAC,EAAE,GAAG,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;IAChD,oHAAoH;IACpH,yBAAyB,CAAC,EAAE,GAAG,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;IAChD,8EAA8E;IAC9E,eAAe,CAAC,EAAE,GAAG,CAAC,MAAM,CAAC,CAAC;IAC9B,8FAA8F;IAC9F,cAAc,CAAC,EAAE,cAAc,CAAC;IAChC,0BAA0B;IAC1B,gBAAgB,CAAC,EAAE,MAAM,CAAC;IAC1B,iDAAiD;IACjD,gBAAgB,CAAC,EAAE,KAAK,CAAC;QAAE,EAAE,EAAE,MAAM,CAAC;QAAC,IAAI,EAAE,MAAM,CAAC;QAAC,WAAW,CAAC,EAAE,MAAM,CAAA;KAAE,CAAC,CAAC;IAC7E,0EAA0E;IAC1E,gBAAgB,CAAC,EAAE,GAAG,CACpB,MAAM,EACN,aAAa,GAAG,SAAS,GAAG,QAAQ,GAAG,QAAQ,GAAG,SAAS,CAC5D,CAAC;IACF,qEAAqE;IACrE,wBAAwB,CAAC,EAAE,MAAM,CAAC;IAElC,eAAe,CAAC,EAAE;QAChB,IAAI,EAAE,MAAM,CAAC;QACb,aAAa,EAAE,MAAM,CAAC;KACvB,CAAC;IACF,6BAA6B,CAAC,EAAE,OAAO,CAAC;IACxC,uBAAuB,CAAC,EAAE,MAAM,CAAC;IACjC,gBAAgB,CAAC,EAAE,OAAO,CAAC;IAC3B,yEAAyE;IACzE,wBAAwB,CAAC,EAAE,OAAO,CAAC;IAGnC,kFAAkF;IAClF,sCAAsC,CAAC,EAAE,OAAO,CAAC;IACjD,sFAAsF;IACtF,kCAAkC,CAAC,EAAE,0BAA0B,EAAE,CAAC;IAClE,0FAA0F;IAC1F,4BAA4B,CAAC,EAAE,OAAO,CAAC;IACvC,0FAA0F;IAC1F,mBAAmB,CAAC,EAAE;QACpB,SAAS,EAAE,MAAM,CAAC;QAClB,gBAAgB,EAAE,0BAA0B,EAAE,CAAC;KAChD,CAAC;IACF,gGAAgG;IAChG,2BAA2B,CAAC,EAAE,oBAAoB,EAAE,CAAC;IACrD;;;;;;;;;OASG;IACH,uBAAuB,CAAC,EAAE,MAAM,CAAC;CAClC,CAAC;AAEF,MAAM,MAAM,uBAAuB,GAAG,eAAe,GAAG;IACtD,gBAAgB,EAAE,gBAAgB,CAAC;IACnC,QAAQ,EAAE,QAAQ,CAAC;IACnB;;;OAGG;IACH,UAAU,CAAC,EAAE,UAAU,CAAC;IACxB;;;;;;;;;;OAUG;IACH,WAAW,CAAC,EAAE,kBAAkB,CAAC;IACjC;;;;;;OAMG;IACH,gBAAgB,EAAE,gBAAgB,CAAC;IACnC,OAAO,EAAE,kBAAkB,CAAC,eAAe,CAAC,CAAC;IAC7C,mBAAmB,EAAE,mBAAmB,CAAC;IACzC,gBAAgB,EAAE,gBAAgB,CAAC;IACnC,gBAAgB,EAAE,gBAAgB,CAAC;IACnC,eAAe,EAAE,eAAe,CAAC;IACjC,WAAW,EAAE,WAAW,CAAC;IACzB,gBAAgB,EAAE,gBAAgB,CAAC;IACnC,aAAa,EAAE,aAAa,CAAC;IAC7B,gBAAgB,EAAE,gBAAgB,CAAC;IACnC,YAAY,EAAE,YAAY,CAAC;IAC3B,qBAAqB,EAAE,qBAAqB,CAAC;IAC7C,SAAS,EAAE,SAAS,CAAC;IACrB,gBAAgB,EAAE,0BAA0B,CAAC;IAC7C,sBAAsB,EAAE,CAAC,SAAS,EAAE,MAAM,KAAK,IAAI,CAAC;IACpD,6BAA6B,EAAE,CAC7B,OAAO,EAAE,iBAAiB,KACvB,OAAO,CAAC,iBAAiB,GAAG,SAAS,CAAC,CAAC;IAC5C,UAAU,CAAC,EAAE,aAAa,CAAC;IAC3B,gBAAgB,CAAC,EAAE,gBAAgB,CAAC;IACpC;;;;;;OAMG;IACH,SAAS,CAAC,EAAE,SAAS,CAAC;IACtB;;;;;;;;;;OAUG;IACH,iBAAiB,CAAC,EAAE,MAAM,MAAM,GAAG,SAAS,CAAC;CAC9C,CAAC;AAEF;;;;;;GAMG;AACH,UAAU,sBAAsB,CAC9B,KAAK,SAAS,MAAM,CAAC,MAAM,EAAE,IAAI,CAAC,CAClC,SAAQ,IAAI,CAAC,0BAA0B,CAAC,KAAK,CAAC,EAAE,OAAO,GAAG,gBAAgB,CAAC;IAC3E,iGAAiG;IACjG,KAAK,CAAC,EAAE,eAAe,CAAC;CACzB"}

package/dist/ai-service/state-machine/clark-fsm.js

@@ -31,7 +31,7 @@ export const AGENT_REPORTED_ERROR_TO_USER = "agentReportedErrorToUser";
 export const AGENT_NEEDS_USER_INPUT = "agentNeedsUserInput";
 export const AGENT_GAVE_UP = "agentGaveUp";
 export const AGENT_CANCELED = "agentCanceled";
-export const LLM_REQUESTED_CONTEXT = "llmRequestedContext";
+const LLM_REQUESTED_CONTEXT = "llmRequestedContext";
 export const LLM_FINISHED_UNEXPECTEDLY = "llmFinishedUnexpectedly";
 export const LLM_ERRORED = "llmErrored";
 export const LLM_FINISHED = "llmFinished";