@opside-cloud/cli

The local authoring tool for Opside automations. It finds the enclosing Opside workspace Git repository, validates its strict YAML definition graph, and writes the disposable @opside-cloud/generated package used by TypeScript and editors:

npx @opside-cloud/cli generate
npx @opside-cloud/cli generate --watch
npx @opside-cloud/cli generate --check
npx @opside-cloud/cli mini-app scaffold --template blank --name appointment_request --label "Appointment request"

The generated package lives at node_modules/@opside-cloud/generated/{client,common,server}.ts plus one mini-apps/<name>.ts facade per authored mini app. It is derived output, not source: do not commit or edit it. --check performs no writes and exits with status 2 when output is missing or stale. Invalid definitions exit with status 1 and preserve the previous generated package. Usage errors exit with status 64.

The scaffold command copies a public E9.4 starter into repository YAML and React/TypeScript source without overwriting existing files or following a symbolic link in either destination chain. Exclusive no-follow file creation and exact-handle verification make the two-file operation roll back if its second path becomes unsafe. It invokes the same public SDK scaffold planner used by Cell's New mini app route; neither owns a private source builder. Build, preview, publish and repair remain in the validated repository/Cell management flow described in docs/mini-app-authoring.md.

Publication status

The package is publish-ready under Opside Cloud's proprietary UNLICENSED terms. The exact-ref release workflow builds, verifies, packs, clean-installs, hashes, and uploads the SDK and CLI tarballs without npm credentials. Public publication remains the standalone P9.E12.8 tail after npm access returns.