> ## Documentation Index
> Fetch the complete documentation index at: https://docs.budscollab.com/llms.txt
> Use this file to discover all available pages before exploring further.

# CLI surface contract

> Which BudsCollab CLI commands are public SDK artifact commands, hosted service commands, or legacy builder commands.

The public SDK package sells the artifact lane first. The checked contract is
`public-cli-surface-contract.json`, which separates commands that are ready for
developer-owned repos from commands that still depend on hosted BudsCollab
services or legacy builder packages.

The selected public CLI cut is declared in `artifact-cli-cut-contract.json`.
The `@budscollab/cli` package `main` and `budsui` bin point at `dist/sdk.js`,
which is built from `packages/budsui-cli/src/sdk.ts` with
`pnpm --filter @budscollab/cli build:sdk`.

## Public artifact lane

These commands are the core public SDK path:

```bash theme={null}
budsui app init
budsui app blueprint
budsui app widget
budsui app project
budsui app from-blueprint
budsui app validate
budsui app inspect
budsui app showcase
budsui app skill
budsui app pack
budsui app registry
budsui app registry-validate
budsui app registry-acceptance
budsui app registry-acceptance-validate
budsui app registry-publisher-verification
budsui app registry-publisher-verification-validate
budsui app registry-review-evidence
budsui app registry-review-evidence-validate
budsui app registry-signing-request
budsui app registry-signing-request-validate
budsui app registry-install-policy
budsui app registry-install-policy-validate
```

They create the standard artifacts:

* `budscollab.blueprint.json`
* `budscollab.package.json`
* `budscollab-showcase.json`
* `SHOWCASE.md`
* `budscollab-app-review.json`
* `budscollab-registry-submission.json`
* `budscollab-registry-index.json`
* `budscollab-registry-acceptance-request.json`
* `budscollab-registry-publisher-verification.json`
* `budscollab-registry-review-evidence.json`
* `budscollab-registry-signing-request.json`
* `budscollab-registry-install-policy.json`

This lane is the one agents, Eve exports, and external repos should use by
default.

## Hosted publisher lane

`budsui login`, `budsui whoami`, `budsui app preview`, and
`budsui app publish` are hosted BudsCollab service commands. They need public
publisher API docs, publisher token setup, hosted preview availability, and
marketplace review/signing policy before they can be sold as ready.

They are not proof that a local SDK artifact is marketplace-installable.

## Legacy builder lane

`budsui init`, `budsui add`, `budsui dev`, `budsui export`,
`budsui catalog compile`, `budsui catalog import-shadcn`, `budsui card
validate`, and `budsui scene validate` are legacy/internal builder and catalog
utilities for the current monorepo shape.

Before `publicNpmReady` can be true for the full CLI, those commands need to be
removed from the public npm cut, moved to an internal builder CLI package, or
backed by SDK-safe supporting packages.

Current status: `readyArtifactOnlyCut` is true, but `blockedFullCliCut` is also
true. That means the SDK-only artifact entrypoint is selected for the public
`budsui` bin, while hosted publisher and legacy builder commands remain outside
the public artifact-only CLI cut.
The artifact-only CLI cut has not been published to npm.