@notis_ai/cli 0.2.0-beta.178.1 → 0.2.0-beta.1792022492092.1

package/skills/notis-apps/cli.md

@@ -1,34 +1,26 @@
-# Notis CLI — App Development Workflow
+# Notis CLI: Space Development Workflow
 
-When running outside the Notis container, use the `notis` CLI to work with Notis Apps locally.
+When running outside the Notis container, use the `notis` CLI to build Notis Spaces locally. Space views are
+Vite + React source using `@notis/sdk`. The product `notis-apps` skill and its release guide own the workflow;
+this file lists the commands generated from the CLI's own help.
 
-Notis apps are Vite + React projects using `@notis/sdk`. Workspace runs released versions only.
-Local and cloud create/edit requests authorize Workspace delivery after checks; explicit read-only,
-preview-only or no-deploy requests stop at local artifacts without remote mutation. Store publication
-requires separate approval.
+Create and edit requests authorize delivery to the installed Space after checks; explicit read-only, preview-only
+or no-deploy requests stop at local artifacts without remote mutation. Store publication requires separate approval.
 
 ## Core workflow
 
-1. Preserve local edits; pull the exact existing released app and current deployment base. For an
-   unreleased container, recover original source (or scaffold locally if unrecoverable), reconcile
-   its exact ID/current version/edit permission/scope and run apps link <app-id> <source-directory>
-   --expected-version 0. If a release has appeared, preserve local source separately and pull/reapply
-   on that current release. Never pull missing source or create another remote recovery app.
-2. Build and automatically verify before new remote creation. Browser tooling is required.
-3. Reconcile exact profile/app identity and personal/team scope. Create only if absent; never duplicate
-   a failed first-release container. Prepare only necessary backward-compatible resource changes.
-4. Deploy the same linked app. Deploy builds, verifies a frozen snapshot, then uploads those bytes.
-   `--skip-build` still verifies and rejects stale output. No Store media requirement applies.
-5. Read back the exact installed ID/version/Portal URL, run live verification, and open the installed
-   app in Portal. Report unknown or deployed-but-unverified outcomes; never blindly redeploy.
+1. `spaces pull` the exact existing Space (source, resource list, Skill folders and lock file), or `spaces init`
+   a new collection view.
+2. `spaces build` and `spaces verify` the selected source with fictional fixtures.
+3. `spaces deploy`, or `spaces preview` then `spaces promote`, within the user's authorization. Changed Skill
+   folders and resource links commit with the source release.
+4. Read back the published revision, then `views find` and `views render` its live view link.
 
-For source restoration, pull the current release into a fresh checkout and historical source into
-another folder. Replace source while retaining the current profile/app link and deployment base,
-change the package release label, check resource compatibility and deploy as a new release.
+`notis apps` is the legacy App group for accounts not yet moved to Spaces; a legacy App cannot declare Skills.
 
-## Reports
+## Reports and HTML
 
-For a standalone live report, use `reports init → build → verify/preview → save` instead of the app deployment workflow above. Author exactly one route with kind: report, declare its tools, and supply a readable context file. No installed app or database is required. Revisions preserve the record ID and require its freshly read revision. See the product `notis-reports` skill for source recovery, ownership and readback. These commands do not deploy an app or publish a Store listing.
+Interactive reports are independent Space views. Save self-contained HTML pages and reports in Notis Notes with its Save HTML Skill; pages and reports saved before Spaces open there too. See the canonical product guidance for build, revision, native file and view-link rules.
 
 ## Commands
 
@@ -42,258 +34,426 @@ Examples:
 - `npx --package @notis_ai/cli@latest -- notis doctor`
 - `npx --package @notis_ai/cli@latest -- notis doctor --json`
 
-### `npx --package @notis_ai/cli@latest -- notis apps list`
+### `npx --package @notis_ai/cli@latest -- notis spaces screenshot <url>`
 
-List apps the current profile can access.
+Capture a full-height PNG of a live view with your current access.
 
-When to use: Discover existing apps before linking or deploying.
+When to use: Check the actual deployed view; writes are blocked and current access is checked again before any output is saved.
+
+Options:
+- `--width <pixels>` — 1440 (default) or 390.
+- `--output-dir <path>` — New output directory; defaults to a unique .notis/renders directory. Existing files are never overwritten.
+
+Examples:
+- `npx --package @notis_ai/cli@latest -- notis spaces screenshot <view-link> --width 390`
+
+### `npx --package @notis_ai/cli@latest -- notis spaces init <name> [dir]`
+
+Scaffold an editable collection view with first-party record components.
+
+When to use: Start a local Space collection source for an existing linked database. Does not create or deploy remote resources.
+
+Options:
+- `--database-key <key>` — Portable key of the database this Space links.
+- `--path <path>` — Descriptive view path; defaults to records.
+- `--title-property <id>` — Canonical title/number property ID, or the title column (default).
+
+Examples:
+- `npx --package @notis_ai/cli@latest -- notis spaces init Notes ./notes --database-key notes --path notes`
+
+### `npx --package @notis_ai/cli@latest -- notis spaces navigation bind <space-id>`
+
+Bind a named destination for the next source publication without granting target access.
+
+When to use: Connect a portable navigation alias to an existing Space or exact record before building and publishing.
+
+Options:
+- `--alias <name>` — Declared portable navigation alias.
+- `--target <json>` — Exact {space_id,document_id?}, or null to remove the draft binding.
+- `--revision <number>` — Current source Space metadata revision.
+- `--dry-run` — Check current source/target access and revision without changing anything.
+
+Examples:
+- `npx --package @notis_ai/cli@latest -- notis spaces navigation bind <space-id> --alias history --target '{"space_id":"<history-id>"}' --revision 2 --dry-run`
+
+### `npx --package @notis_ai/cli@latest -- notis spaces resources name <space-id> <binding-id>`
+
+Give an included resource a portable alias before the first source revision.
+
+When to use: Prepare staged resources for source authoring without replacing their IDs, scope or owners.
+
+Options:
+- `--alias <name>` — Stable lowercase alias to use in source.
+- `--revision <number>` — Current Space metadata revision.
+- `--dry-run` — Check naming, current access and revision without changing metadata.
+
+Examples:
+- `npx --package @notis_ai/cli@latest -- notis spaces resources name <space-id> <binding-id> --alias weekly-report --revision 0 --dry-run`
+
+### `npx --package @notis_ai/cli@latest -- notis spaces links list <space-id>`
+
+List the databases, Skills, automations and records linked into one Space.
+
+When to use: Find a link binding and its revision before removing it, including a link left behind by a deleted Skill.
+
+Examples:
+- `npx --package @notis_ai/cli@latest -- notis spaces links list <space-id>`
+
+### `npx --package @notis_ai/cli@latest -- notis spaces links remove <space-id> <binding-id>`
+
+Remove one database, Skill or automation link from a Space by its binding.
+
+When to use: Unlist a resource from a Space you edit, including a link whose Skill was deleted. The resource keeps its ID; removing the last available link of a live resource keeps it as its owner's standalone resource.
+
+Options:
+- `--revision <number>` — Current binding revision from spaces links list.
+- `--request-id <key>` — Stable intent key; reuse it unchanged when retrying this removal.
+
+Examples:
+- `npx --package @notis_ai/cli@latest -- notis spaces links remove <space-id> <binding-id> --revision 1 --request-id remove-link-1`
+
+### `npx --package @notis_ai/cli@latest -- notis spaces aliases list`
+
+List the old App page links you manage and the Space each one opens.
+
+When to use: Find an old App page link that opens a binned Space (trashed: true) before repointing it.
+
+Options:
+- `--legacy-id <id>` — Old App ID the links belong to.
+- `--kind <kind>` — app (default), report or html.
+
+Examples:
+- `npx --package @notis_ai/cli@latest -- notis spaces aliases list --legacy-id <app-id>`
+
+### `npx --package @notis_ai/cli@latest -- notis spaces aliases repoint`
+
+Point one old App page link at a live Space you edit.
+
+When to use: Repair an old App page link whose Space was binned. You must own the old App or edit the Space the link opens now, and edit the new Space; everyone who opens the link still needs their own access to it.
+
+Options:
+- `--legacy-id <id>` — Old App ID the link belongs to.
+- `--route <slug>` — Old App page route from spaces aliases list.
+- `--space <space-id>` — Live Space the old link should open.
+- `--expected-space <space-id>` — Space the link opens now; the change is refused if it moved since you listed it.
+- `--selection-param <name>` — Declared view parameter that receives the old page selection, if any.
+- `--request-id <key>` — Stable intent key; reuse it unchanged when retrying this change.
+- `--dry-run` — Check authority and the new Space without changing the link.
+
+Examples:
+- `npx --package @notis_ai/cli@latest -- notis spaces aliases repoint --legacy-id <app-id> --route pages --space <space-id> --expected-space <binned-space-id> --request-id repoint-pages --dry-run`
+
+### `npx --package @notis_ai/cli@latest -- notis spaces pull <space-id> [dir]`
+
+Pull one editable Space source snapshot, its resource list and its Skill folders into an empty directory.
+
+When to use: Edit a Space you can administer: the source, its links (resources.json) and every editable linked Skill (skills/<alias>/) arrive together, with a local lock file so a later deploy sends only what you changed.
+
+Options:
+- `--revision <number>` — Exact published source revision; defaults to the current one.
 
 Examples:
-- `npx --package @notis_ai/cli@latest -- notis apps list`
-- `npx --package @notis_ai/cli@latest -- notis apps list --json`
+- `npx --package @notis_ai/cli@latest -- notis spaces pull <space-id> ./space-source`
 
-### `npx --package @notis_ai/cli@latest -- notis apps init <name> [dir]`
+### `npx --package @notis_ai/cli@latest -- notis spaces verify [dir]`
 
-Scaffold a new Notis app project.
+Render one frozen Space with offline fixtures and validate its current action authorizations.
 
-When to use: Start a new Notis app. Use --from with a published Store app when one is close to the desired app; otherwise creates the bare Vite + React project.
+When to use: Check immutable build bytes and authoring compatibility without executing actions or publishing.
 
 Options:
-- `--from <slug>` — Start from a published Store app listed by `notis apps scaffolds list`. Downloads its source from the public app registry.
+- `--space <key>` — Exact source key from the workspace index.
+- `--space-id <id>` — Exact existing destination Space.
+- `--reuse-grants <json>` — Explicit action-key to saved-grant-ID map. Otherwise your own connections are used.
+- `--reuse-grants-only` — Never authorize new actions. Reuse only the supplied saved grants; other declarations remain unavailable. Requires existing bound databases.
 
 Examples:
-- `npx --package @notis_ai/cli@latest -- notis apps scaffolds list`
-- `npx --package @notis_ai/cli@latest -- notis apps init "Mind the Flo"`
-- `npx --package @notis_ai/cli@latest -- notis apps init "My CRM" --from databases`
-- `npx --package @notis_ai/cli@latest -- notis apps init "My App" ~/code/my-app`
+- `npx --package @notis_ai/cli@latest -- notis spaces verify . --space overview --space-id <space-id>`
 
-### `npx --package @notis_ai/cli@latest -- notis apps scaffolds list`
+### `npx --package @notis_ai/cli@latest -- notis spaces preview [dir]`
 
-List published Store apps available as scaffolds.
+Seal a checked unpublished revision of the same Space and return its authenticated preview link.
 
-When to use: Discover published Store apps to start from before creating a new app. Every app published to the public Store is automatically a scaffold; use --search to narrow the catalog.
+When to use: Review a checked candidate using current Editor access without changing live source or cloning the Space.
 
 Options:
-- `--search <term>` — Filter scaffolds by name, tagline, description, or category.
+- `--space <key>` — Exact source key from the workspace index.
+- `--space-id <id>` — Exact existing destination Space.
+- `--reuse-grants <json>` — Explicit action-key to saved-grant-ID map. Otherwise your own connections are used.
+- `--reuse-grants-only` — Never authorize new actions. Reuse only the supplied saved grants; other declarations remain unavailable. Requires existing bound databases.
+- `--request-id <key>` — Stable intent key. Reuse after timeouts or lost replies.
+- `--dry-run` — Validate without uploading or publishing.
 
 Examples:
-- `npx --package @notis_ai/cli@latest -- notis apps scaffolds list`
-- `npx --package @notis_ai/cli@latest -- notis apps scaffolds list --search journal`
-- `npx --package @notis_ai/cli@latest -- notis apps init "My App" --from databases`
+- `npx --package @notis_ai/cli@latest -- notis spaces preview . --space overview --space-id <space-id> --request-id release-1`
 
-### `npx --package @notis_ai/cli@latest -- notis apps create <name> [dir]`
+### `npx --package @notis_ai/cli@latest -- notis spaces deploy [dir]`
 
-Create a new remote Notis app and optionally link a local project to it.
+Publish one built Space with a retry-safe, independent source revision.
 
-When to use: Provision a fresh remote app before the first deploy. Pass a project directory to link it immediately.
+When to use: Update only the selected existing Space; this does not publish to the Store or change siblings.
 
 Options:
-- `--team-id <id>` — Create or reuse the exact team-scoped app (default: personal).
+- `--space <key>` — Exact source key from the workspace index.
+- `--space-id <id>` — Exact existing destination Space.
+- `--reuse-grants <json>` — Explicit action-key to saved-grant-ID map. Otherwise your own connections are used.
+- `--reuse-grants-only` — Never authorize new actions. Reuse only the supplied saved grants; other declarations remain unavailable. Requires existing bound databases.
+- `--request-id <key>` — Stable intent key. Reuse after timeouts or lost replies.
+- `--dry-run` — Validate without uploading or publishing.
+
+Examples:
+- `npx --package @notis_ai/cli@latest -- notis spaces deploy . --space overview --space-id <space-id> --request-id release-1`
+
+### `npx --package @notis_ai/cli@latest -- notis spaces promote <release-id> [dir]`
+
+Publish the exact sealed Space revision, with its pending Skill and link changes, after current permission and concurrency checks.
+
+When to use: Finish a reviewed preview without rebuilding or substituting a different candidate. The Skill edits, new Skills and list changes the preview carried go live in the same transaction.
+
+Examples:
+- `npx --package @notis_ai/cli@latest -- notis spaces promote <release-id>`
+
+### `npx --package @notis_ai/cli@latest -- notis spaces abandon <release-id>`
+
+Close an unpublished Space preview without changing its live source, Skills or links, or deleting action history.
+
+When to use: Stop using a candidate while preserving live source and completed effects.
 
 Examples:
-- `npx --package @notis_ai/cli@latest -- notis apps create "My App"`
-- `npx --package @notis_ai/cli@latest -- notis apps create "My App" .`
+- `npx --package @notis_ai/cli@latest -- notis spaces abandon <release-id>`
 
-### `npx --package @notis_ai/cli@latest -- notis apps build [dir]`
+### `npx --package @notis_ai/cli@latest -- notis spaces list`
 
-Build and package the app into .notis/output/.
+List Spaces currently available to your account.
 
-When to use: Prepare the app for verification or deployment.
+When to use: Discover accessible Spaces without exposing an issuer-wide resource catalogue.
 
 Examples:
-- `npx --package @notis_ai/cli@latest -- notis apps build`
-- `npx --package @notis_ai/cli@latest -- notis apps build ./my-app`
+- `npx --package @notis_ai/cli@latest -- notis spaces list`
 
-### `npx --package @notis_ai/cli@latest -- notis apps verify [dir]`
+### `npx --package @notis_ai/cli@latest -- notis spaces get <space-id>`
 
-Validate that every route renders and reports Store listing readiness.
+Read one accessible Space and its scoped resources.
 
-When to use: Any time after notis apps build, and before deploy. Catches render-time crashes and missing runtime calls. Incomplete listing media is reported as a warning; pass --listing to fail on it instead.
+When to use: Inspect the current published revision and named capabilities before executing.
 
 Options:
-- `--routes <slugs>` — Comma-separated route slugs. Default: every route in manifest.
-- `--port <n>` — Loopback port. Default: auto-pick.
-- `--skip-build` — Skip notis apps build; reuse existing .notis/output/.
-- `--mode <mode>` — stub | live. Default stub. Live posts to /portal_views/runtime_query with the CLI JWT and fails routes whose runtime calls all errored.
-- `--listing` — Fail instead of warn when the Store listing (tagline, categories, screenshots, changelog) is incomplete.
-- `--no-browser` — Start the harness server and print URLs; do not drive agent-browser.
-- `--keep-open` — Leave server + browser session running after report (for manual triage).
+- `--record <record-key>` — Fixed record context, when this is a record-scoped Space.
 
 Examples:
-- `npx --package @notis_ai/cli@latest -- notis apps verify`
-- `npx --package @notis_ai/cli@latest -- notis apps verify --routes notes`
-- `npx --package @notis_ai/cli@latest -- notis apps verify --mode live`
-- `npx --package @notis_ai/cli@latest -- notis apps verify --listing  # gate on Store listing readiness before publish`
-- `npx --package @notis_ai/cli@latest -- notis apps verify --no-browser  # start the harness, drive agent-browser yourself`
+- `npx --package @notis_ai/cli@latest -- notis spaces get <space-id>`
 
-### `npx --package @notis_ai/cli@latest -- notis apps screenshot [dir]`
+### `npx --package @notis_ai/cli@latest -- notis spaces action <space-id> <action-id>`
 
-Capture configured listing route/scenario states via the headless harness.
+Execute a declared action using its saved authorization.
 
-When to use: Generate the 3–6 declared metadata/screenshot-N.png files for the App Store listing. Apps are icon-led (like Raycast) — there is no cover image, only these screenshots. Each screenshot may set a focus selector to remove empty canvas and a light or dark theme that also controls its Store frame. Run before notis apps verify / deploy / publish.
+When to use: Use Space capabilities as the actual actor, with the saved issuer connection and payer.
 
 Options:
-- `--routes <slugs>` — Comma-separated route slugs. Default: every configured screenshot state.
-- `--port <n>` — Loopback port. Default: auto-pick.
-- `--width <px>` — Viewport width. Default: 2000.
-- `--height <px>` — Viewport height. Default: 1250 (16:10).
-- `--output-dir <dir>` — Where to write screenshot-N.png. Default: metadata/.
-- `--mode <mode>` — stub | live. Default stub. Live renders against real data via the CLI JWT (requires a linked app), so screenshots show actual content instead of empty states.
-- `--raw` — Write the unframed harness capture instead of the default Store presentation.
-- `--skip-build` — Skip notis apps build; reuse existing .notis/output/.
+- `--revision <number>` — Exact published source revision.
+- `--preview-release <id>` — Exact sealed candidate ID; requires current Editor access.
+- `--schema-revision <number>` — Native schema revision; required for native row writes.
+- `--inputs <json>` — Declared action input values; defaults to {}.
+- `--record <record-key>` — Fixed record context, when this is a record-scoped Space.
+- `--request-id <key>` — Stable intent key. Reuse after timeouts or lost replies.
+- `--dry-run` — Validate current access and action inputs without executing or billing.
 
 Examples:
-- `npx --package @notis_ai/cli@latest -- notis apps screenshot  # honors notis.config.ts screenshot scenarios`
-- `npx --package @notis_ai/cli@latest -- notis apps screenshot --routes home,history`
-- `npx --package @notis_ai/cli@latest -- notis apps screenshot --mode live  # populated screenshots from real data`
-- `npx --package @notis_ai/cli@latest -- notis apps screenshot --raw  # diagnostic capture without Store framing`
+- `npx --package @notis_ai/cli@latest -- notis spaces action <space-id> refresh --revision 1 --inputs '{}' --request-id refresh-1 --dry-run`
 
-### `npx --package @notis_ai/cli@latest -- notis apps link <app-id> [dir]`
+### `npx --package @notis_ai/cli@latest -- notis spaces viewer-read <space-id> <operation>`
 
-Link a local project to a remote Notis app.
+Run one declared viewer read as yourself.
 
-When to use: Connect a local project to an existing app for deployment.
+When to use: Check what an explorer Space shows you: the databases or Skills you can open, with your own access and never an issuer grant.
 
 Options:
-- `--expected-version <version>` — Link only if the remote deployment version still matches this non-negative integer.
+- `--revision <number>` — Exact published source revision.
+- `--preview-release <id>` — Exact sealed candidate ID; requires current Editor access.
+- `--input <json>` — Read input, e.g. {"database_id":"<id>"}; defaults to {}.
+- `--record <record-key>` — Fixed record context, when this is a record-scoped Space.
 
 Examples:
-- `npx --package @notis_ai/cli@latest -- notis apps link abc123`
-- `npx --package @notis_ai/cli@latest -- notis apps link abc123 ./my-app`
-- `npx --package @notis_ai/cli@latest -- notis apps link abc123 ./recovered-app --expected-version 0`
+- `npx --package @notis_ai/cli@latest -- notis spaces viewer-read <space-id> list_databases --revision 3`
+- `npx --package @notis_ai/cli@latest -- notis spaces viewer-read <space-id> query_database --revision 3 --input '{"database_id":"<id>","request":{"page_size":20}}'`
 
-### `npx --package @notis_ai/cli@latest -- notis apps pull <app-id> [dir]`
+### `npx --package @notis_ai/cli@latest -- notis spaces grants list <space-id>`
 
-Download a Notis app source snapshot into a local project folder.
+Inspect authorization records for a Space you can edit.
 
-When to use: Edit an installed app. Preserve local edits, pull and link its persisted source, then build, verify and deploy.
+When to use: Inspect issuers and exact constraints without exposing connection secrets.
 
 Options:
-- `--force` — Overwrite a non-empty target directory.
-- `--source-version <n>` — Pull a specific app source version (default: latest).
+- `--record <record-key>` — Fixed record context, when this is a record-scoped Space.
 
 Examples:
-- `npx --package @notis_ai/cli@latest -- notis apps pull abc123`
-- `npx --package @notis_ai/cli@latest -- notis apps pull abc123 ./my-app --force --source-version 3`
+- `npx --package @notis_ai/cli@latest -- notis spaces grants list <space-id>`
 
-### `npx --package @notis_ai/cli@latest -- notis apps deploy [dir]`
+### `npx --package @notis_ai/cli@latest -- notis spaces grants create <space-id>`
 
-Build, verify and release the linked Workspace app.
+Authorize an exact template using your current connection.
 
-When to use: Build, verify and release the linked personal or team Workspace app. This command does not publish to the Store.
+When to use: Create a Space-bound authorization; the server resolves the signed-in issuer connection.
 
 Options:
-- `--app-id <id>` — Override linked app ID.
-- `--skip-build` — Reuse unchanged build output; automated verification still runs.
+- `--template <file>` — Canonical action template JSON file.
+- `--record <record-key>` — Fixed record context, when this is a record-scoped Space.
+- `--request-id <key>` — Stable intent key. Reuse after timeouts or lost replies.
+- `--dry-run` — Validate the template and Editor access without creating a grant.
+
+Examples:
+- `npx --package @notis_ai/cli@latest -- notis spaces grants create <space-id> --template action.json --request-id grant-1 --dry-run`
+
+### `npx --package @notis_ai/cli@latest -- notis spaces grants revoke <grant-id>`
+
+Revoke one saved Space authorization.
+
+When to use: Stop future dispatches for an authorization you issued or can administer.
 
 Examples:
+- `npx --package @notis_ai/cli@latest -- notis spaces grants revoke <grant-id>`
 
-### `npx --package @notis_ai/cli@latest -- notis apps publish [dir]`
+### `npx --package @notis_ai/cli@latest -- notis spaces store list`
 
-Submit the deployed app for Store review.
+List Space Store listings you can see.
 
-When to use: After the user explicitly confirms the App Details page and Store listing are ready. Requires the current local project to match the latest deployed version.
+When to use: Find Space templates published to your team or approved for everyone, and your own listings.
 
 Options:
-- `--app-id <id>` — Override linked app ID.
-- `--confirm-ready` — Confirm the user approved the current App Details page for Store submission.
+- `--channel <team|public>` — Only one channel.
 
 Examples:
-- `npx --package @notis_ai/cli@latest -- notis apps publish --confirm-ready`
-- `npx --package @notis_ai/cli@latest -- notis apps publish ./my-app --confirm-ready`
+- `npx --package @notis_ai/cli@latest -- notis spaces store list --channel team`
 
-### `npx --package @notis_ai/cli@latest -- notis apps duplicate [dir]`
+### `npx --package @notis_ai/cli@latest -- notis spaces store get <listing-id>`
 
-Duplicate an app into an independent copy with its own databases.
+Read one Store listing with its versions and your installs.
 
-When to use: When the same app should run for a second purpose - a notes app for blog drafts alongside one for bookmarks. The copy shares no data with the source.
+When to use: Check what a listing contains, its review state and whether your copies have an update.
+
+Examples:
+- `npx --package @notis_ai/cli@latest -- notis spaces store get <listing-id>`
+
+### `npx --package @notis_ai/cli@latest -- notis spaces store installs`
+
+List the Spaces you installed from the Store.
+
+When to use: See which installed copies have an update or conflicts to resolve.
+
+Examples:
+- `npx --package @notis_ai/cli@latest -- notis spaces store installs`
+
+### `npx --package @notis_ai/cli@latest -- notis spaces store publish <space-id>`
+
+Publish a Space and its sub-Spaces as the next Store version.
+
+When to use: Share a Space as an installable template: team listings publish at once, public ones wait for review.
 
 Options:
-- `--app-id <id>` — App to duplicate. Defaults to the app this project is linked to.
-- `--name <name>` — Name for the duplicate (default: the source name followed by "copy").
-- `--copy-documents <mode>` — Which rows to copy: 'declared' (default, the starter content a fresh install would have), 'all', or 'none'.
+- `--channel <team|public>` — Where to publish.
+- `--metadata <json>` — Listing name, tagline, description, category, icon, accent.
+- `--starter <json>` — Starter row IDs per database ({"<database-id>":["<record-key>"]}).
+- `--notes <text>` — Release notes for this version.
+- `--request-id <key>` — Stable intent key. Reuse after timeouts or lost replies.
+- `--dry-run` — Show the package counts and review diff without publishing.
 
 Examples:
-- `npx --package @notis_ai/cli@latest -- notis apps duplicate --name "Blog"`
-- `npx --package @notis_ai/cli@latest -- notis apps duplicate --app-id abc123 --name "Bookmarks" --copy-documents none`
+- `npx --package @notis_ai/cli@latest -- notis spaces store publish <space-id> --channel team --request-id publish-1 --dry-run`
+
+### `npx --package @notis_ai/cli@latest -- notis spaces store install <listing-id>`
 
-### `npx --package @notis_ai/cli@latest -- notis apps doctor [dir]`
+Install a Store listing as your own independent copy.
 
-Check project health and readiness.
+When to use: Add a published Space template to your account; your copy keeps your changes on later updates.
 
-When to use: Diagnose issues with a Notis app project.
+Options:
+- `--name <name>` — Name of the installed top Space.
+- `--parent <space-id>` — Install under one of your Spaces.
+- `--request-id <key>` — Stable intent key. Reuse after timeouts or lost replies.
+- `--dry-run` — Show what the copy contains without installing.
 
 Examples:
-- `npx --package @notis_ai/cli@latest -- notis apps doctor`
-- `npx --package @notis_ai/cli@latest -- notis apps doctor ./my-app`
+- `npx --package @notis_ai/cli@latest -- notis spaces store install <listing-id> --request-id install-1`
 
-### `npx --package @notis_ai/cli@latest -- notis reports init <name> [dir]`
+### `npx --package @notis_ai/cli@latest -- notis spaces store update <install-id>`
 
-Init a standalone live SDK report.
+Update an installed copy, keeping your changes, or resolve its conflicts.
 
-When to use: Author a private standalone document using the shared view runtime; no app or database is required.
+When to use: Take a newer Store version: unchanged parts update, your edits stay, and parts both sides changed become conflicts you resolve.
+
+Options:
+- `--resolve <json>` — Per conflict key: "keep_mine" or "take_theirs".
+- `--request-id <key>` — Stable intent key. Reuse after timeouts or lost replies.
+- `--dry-run` — Show the three-way plan without changing anything.
 
 Examples:
-- `npx --package @notis_ai/cli@latest -- notis reports init "Weekly report" ./weekly-report`
+- `npx --package @notis_ai/cli@latest -- notis spaces store update <install-id> --request-id update-1 --dry-run`
+- `npx --package @notis_ai/cli@latest -- notis spaces store update <install-id> --resolve '{"skill:<key>":"keep_mine"}' --request-id resolve-1`
+
+### `npx --package @notis_ai/cli@latest -- notis spaces store unpublish <listing-id>`
 
-### `npx --package @notis_ai/cli@latest -- notis reports build [dir]`
+Stop new installs of a Store listing.
 
-Build a standalone live SDK report.
+When to use: Withdraw a listing: existing copies keep working and a version waiting for review is withdrawn.
 
-When to use: Author a private standalone document using the shared view runtime; no app or database is required.
+Options:
+- `--request-id <key>` — Stable intent key. Reuse after timeouts or lost replies.
+
+Examples:
+- `npx --package @notis_ai/cli@latest -- notis spaces store unpublish <listing-id> --request-id unpublish-1`
+
+### `npx --package @notis_ai/cli@latest -- notis spaces build [dir]`
+
+Build one independent Space and save its frozen source/artifact snapshot.
+
+When to use: Prepare a selected Space for verification without publishing it or changing siblings.
+
+Options:
+- `--space <key>` — Exact source key from the workspace Space index.
 
 Examples:
-- `npx --package @notis_ai/cli@latest -- notis reports build ./weekly-report`
+- `npx --package @notis_ai/cli@latest -- notis spaces build . --space overview`
 
-### `npx --package @notis_ai/cli@latest -- notis reports verify [dir]`
+### `npx --package @notis_ai/cli@latest -- notis spaces inspect [dir]`
 
-Verify a standalone live SDK report.
+Inspect one local Space definition and its declared capabilities.
 
-When to use: Author a private standalone document using the shared view runtime; no app or database is required.
+When to use: Read the selected source definition without loading sibling definitions or account resources.
 
 Options:
-- `--routes <slugs>` — Comma-separated route slugs. Default: every route in manifest.
-- `--port <n>` — Loopback port. Default: auto-pick.
-- `--skip-build` — Skip notis apps build; reuse existing .notis/output/.
-- `--mode <mode>` — stub | live. Default stub. Live posts to /portal_views/runtime_query with the CLI JWT and fails routes whose runtime calls all errored.
-- `--no-browser` — Start the harness server and print URLs; do not drive agent-browser.
-- `--keep-open` — Leave server + browser session running after report (for manual triage).
-- `--document-id <id>` — Saved report for live verification.
-- `--expected-revision <revision>` — Saved report revision for live verification.
+- `--space <key>` — Exact source key from the workspace Space index.
 
 Examples:
-- `npx --package @notis_ai/cli@latest -- notis reports verify ./weekly-report`
+- `npx --package @notis_ai/cli@latest -- notis spaces inspect . --space overview`
 
-### `npx --package @notis_ai/cli@latest -- notis reports preview [dir]`
+### `npx --package @notis_ai/cli@latest -- notis views find`
 
-Preview a standalone live SDK report.
+Find the views you can open for a record, database, view link, Space or search.
 
-When to use: Author a private standalone document using the shared view runtime; no app or database is required.
+When to use: Get fresh view-qualified links and declared URL parameters before citing or opening a view.
 
 Options:
-- `--routes <slugs>` — Comma-separated route slugs. Default: every route in manifest.
-- `--port <n>` — Loopback port. Default: auto-pick.
-- `--skip-build` — Skip notis apps build; reuse existing .notis/output/.
-- `--mode <mode>` — stub | live. Default stub. Live posts to /portal_views/runtime_query with the CLI JWT and fails routes whose runtime calls all errored.
-- `--no-browser` — Start the harness server and print URLs; do not drive agent-browser.
-- `--keep-open` — Leave server + browser session running after report (for manual triage).
-- `--document-id <id>` — Saved report for live verification.
-- `--expected-revision <revision>` — Saved report revision for live verification.
+- `--record-key <id>` — Find views that show this exact native record.
+- `--database-id <id>` — Find views over this database.
+- `--url <url>` — Resolve this view link and its current parameters.
+- `--space-id <id>` — Describe this Space view.
+- `--query <text>` — Search accessible view names, descriptions and readable context.
 
 Examples:
-- `npx --package @notis_ai/cli@latest -- notis reports preview ./weekly-report`
+- `npx --package @notis_ai/cli@latest -- notis views find --record-key <record-key>`
+- `npx --package @notis_ai/cli@latest -- notis views find --url <view-link>`
+- `npx --package @notis_ai/cli@latest -- notis views find --query inbox`
 
-### `npx --package @notis_ai/cli@latest -- notis reports save [dir]`
+### `npx --package @notis_ai/cli@latest -- notis views render <url>`
 
-Build, verify and save a standalone live report document.
+Render a live view as Markdown and a full-height PNG with your current access.
 
-When to use: Persist an independently owned report, not an app release.
+When to use: Check the actual deployed view; writes are blocked and current access is checked again before any output is saved.
 
 Options:
-- `--document-id <id>` — Existing report document to update.
-- `--expected-revision <revision>` — Current saved report revision; required for updates.
-- `--title <title>` — Required, including updates. Document title.
-- `--context-file <file>` — Required. UTF-8 readable report content and structure.
+- `--outputs <kinds>` — Comma-separated markdown,screenshot (default both).
+- `--width <pixels>` — 1440 (default) or 390.
+- `--output-dir <path>` — New output directory; defaults to a unique .notis/renders directory. Existing files are never overwritten.
 
 Examples:
-- `npx --package @notis_ai/cli@latest -- notis reports save ./weekly-report --title "Weekly review" --context-file ./context.md`
+- `npx --package @notis_ai/cli@latest -- notis views render <view-link> --outputs markdown,screenshot`