fix(workers): deploy native Cloudflare workspace projects

[dxiongya]

Cloudflare-native applications could fail at three different stages: Wrangler imports rejected valid initial SQLite Durable Object migrations, monorepo packages were initialized with npm commands even when the repository declared Yarn or pnpm, and complete static applications above the legacy 12 MiB JSON limit could not reach the control plane. This change preserves the native project shape while mapping only the provider state xAPI actually manages.

The importer now accepts only an initial new_sqlite_classes migration whose class set exactly matches the imported Durable Object bindings; rename/delete/regular/partial migrations remain blocked. Complete bundles use the backend multipart Artifact contract with exact binary bytes, 10,000 assets, 25 MiB per asset, and 100 MiB total content. Existing framework initialization inherits the repository package manager, and a 413 now identifies a stale or misconfigured 128 MiB control-plane ingress instead of returning an opaque upload failure.

Validation:

• bun install --frozen-lockfile
• bun run typecheck
• bun run build
• bun run test (493 passed)
• npm pack --dry-run --ignore-scripts
• Real Excalidraw workspace build through generated Corepack Yarn commands
• Real 62.9 MiB Excalidraw plan succeeds locally; production push correctly exposed that backend #250 has not yet been promoted beyond dev

The live Excalidraw deployment must be retried only after the backend multipart endpoint and scoped 128 MiB ingress from xapi-backend #250 reach the target control plane. No static assets were removed or split to bypass that release dependency.

[dxiongya]

按本轮 Workers 统一整理要求，由 Draft #38（feature/workers-refactor）接替，整合原生部署、Container、CLI 与 Skill。原改动和来源已保留并去重，placement deployment identity P1 继续在统一清单跟踪，不视为已解决。原分支不删除；没有 npm 发布或版本改动。