@notis_ai/cli 0.2.0-beta.191.1 → 0.2.0-beta.197.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.
+New reports are independent Space views. Existing database report payloads render inside their database's main view. Use the installed HTML Space's saving Skill for self-contained HTML. See the canonical product guidance for build, revision, native file and view-link rules.
 
 ## Commands
 
@@ -42,258 +34,373 @@ 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 apps list`
-- `npx --package @notis_ai/cli@latest -- notis apps list --json`
+- `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 apps init <name> [dir]`
+### `npx --package @notis_ai/cli@latest -- notis spaces pull <space-id> [dir]`
 
-Scaffold a new Notis app project.
+Pull one editable Space source snapshot, its resource list and its Skill folders into an empty directory.
 
-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: 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:
-- `--from <slug>` — Start from a published Store app listed by `notis apps scaffolds list`. Downloads its source from the public app registry.
+- `--revision <number>` — Exact published source revision; defaults to the current one.
 
 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 pull <space-id> ./space-source`
 
-### `npx --package @notis_ai/cli@latest -- notis apps scaffolds list`
+### `npx --package @notis_ai/cli@latest -- notis spaces verify [dir]`
 
-List published Store apps available as scaffolds.
+Render one frozen Space with offline fixtures and validate its current action authorizations.
 
-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: Check immutable build bytes and authoring compatibility without executing actions or publishing.
 
 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.
 
 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 verify . --space overview --space-id <space-id>`
 
-### `npx --package @notis_ai/cli@latest -- notis apps create <name> [dir]`
+### `npx --package @notis_ai/cli@latest -- notis spaces preview [dir]`
 
-Create a new remote Notis app and optionally link a local project to it.
+Seal a checked unpublished revision of the same Space and return its authenticated preview link.
 
-When to use: Provision a fresh remote app before the first deploy. Pass a project directory to link it immediately.
+When to use: Review a checked candidate using current Editor access without changing live source or cloning the Space.
 
 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 preview . --space overview --space-id <space-id> --request-id release-1`
+
+### `npx --package @notis_ai/cli@latest -- notis spaces deploy [dir]`
+
+Publish one built Space with a retry-safe, independent source revision.
+
+When to use: Update only the selected existing Space; this does not publish to the Store or change siblings.
+
+Options:
+- `--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 apps create "My App"`
-- `npx --package @notis_ai/cli@latest -- notis apps create "My App" .`
+- `npx --package @notis_ai/cli@latest -- notis spaces promote <release-id>`
 
-### `npx --package @notis_ai/cli@latest -- notis apps build [dir]`
+### `npx --package @notis_ai/cli@latest -- notis spaces abandon <release-id>`
 
-Build and package the app into .notis/output/.
+Close an unpublished Space preview without changing its live source, Skills or links, or deleting action history.
 
-When to use: Prepare the app for verification or deployment.
+When to use: Stop using a candidate while preserving live source and completed effects.
 
 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 abandon <release-id>`
+
+### `npx --package @notis_ai/cli@latest -- notis spaces list`
+
+List Spaces currently available to your account.
 
-### `npx --package @notis_ai/cli@latest -- notis apps verify [dir]`
+When to use: Discover accessible Spaces without exposing an issuer-wide resource catalogue.
+
+Examples:
+- `npx --package @notis_ai/cli@latest -- notis spaces list`
 
-Validate that every route renders and reports Store listing readiness.
+### `npx --package @notis_ai/cli@latest -- notis spaces get <space-id>`
 
-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.
+Read one accessible Space and its scoped resources.
+
+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 spaces grants list <space-id>`
+
+### `npx --package @notis_ai/cli@latest -- notis spaces grants create <space-id>`
+
+Authorize an exact template using your current connection.
+
+When to use: Create a Space-bound authorization; the server resolves the signed-in issuer connection.
+
+Options:
+- `--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 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 revoke <grant-id>`
 
-### `npx --package @notis_ai/cli@latest -- notis apps deploy [dir]`
+### `npx --package @notis_ai/cli@latest -- notis spaces store list`
 
-Build, verify and release the linked Workspace app.
+List Space Store listings you can see.
 
-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: Find Space templates published to your team or approved for everyone, and your own listings.
 
 Options:
-- `--app-id <id>` — Override linked app ID.
-- `--skip-build` — Reuse unchanged build output; automated verification still runs.
+- `--channel <team|public>` — Only one channel.
 
 Examples:
+- `npx --package @notis_ai/cli@latest -- notis spaces store list --channel team`
+
+### `npx --package @notis_ai/cli@latest -- notis spaces store get <listing-id>`
+
+Read one Store listing with its versions and your installs.
 
-### `npx --package @notis_ai/cli@latest -- notis apps publish [dir]`
+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>`
 
-Submit the deployed app for Store review.
+### `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`
 
-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.
+### `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>` — Override linked app ID.
-- `--confirm-ready` — Confirm the user approved the current App Details page for Store submission.
+- `--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 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 publish <space-id> --channel team --request-id publish-1 --dry-run`
 
-### `npx --package @notis_ai/cli@latest -- notis apps duplicate [dir]`
+### `npx --package @notis_ai/cli@latest -- notis spaces store install <listing-id>`
 
-Duplicate an app into an independent copy with its own databases.
+Install a Store listing as your own independent copy.
 
-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: Add a published Space template to your account; your copy keeps your changes on later updates.
 
 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'.
+- `--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 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 install <listing-id> --request-id install-1`
 
-### `npx --package @notis_ai/cli@latest -- notis apps doctor [dir]`
+### `npx --package @notis_ai/cli@latest -- notis spaces store update <install-id>`
 
-Check project health and readiness.
+Update an installed copy, keeping your changes, or resolve its conflicts.
 
-When to use: Diagnose issues with a Notis app project.
+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 apps doctor`
-- `npx --package @notis_ai/cli@latest -- notis apps doctor ./my-app`
+- `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 reports init <name> [dir]`
+### `npx --package @notis_ai/cli@latest -- notis spaces store unpublish <listing-id>`
 
-Init a standalone live SDK report.
+Stop new installs of a Store listing.
 
-When to use: Author a private standalone document using the shared view runtime; no app or database is required.
+When to use: Withdraw a listing: existing copies keep working and a version waiting for review is withdrawn.
+
+Options:
+- `--request-id <key>` — Stable intent key. Reuse after timeouts or lost replies.
 
 Examples:
-- `npx --package @notis_ai/cli@latest -- notis reports init "Weekly report" ./weekly-report`
+- `npx --package @notis_ai/cli@latest -- notis spaces store unpublish <listing-id> --request-id unpublish-1`
 
-### `npx --package @notis_ai/cli@latest -- notis reports build [dir]`
+### `npx --package @notis_ai/cli@latest -- notis spaces build [dir]`
 
-Build a standalone live SDK report.
+Build one independent Space and save its frozen source/artifact snapshot.
 
-When to use: Author a private standalone document using the shared view runtime; no app or database is required.
+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`

package/skills/notis-cli/AGENT_INSTRUCTIONS.md

@@ -1,7 +1,7 @@
 <!-- notis-cli:instructions:start -->
 ## Notis CLI
 
-Use the Notis CLI (`npx --package @notis_ai/cli@latest -- notis ...`) whenever the task involves the user's personal data or connected services: integrations (Gmail, Google Calendar, Notion, Slack, GitHub, ...), long-term memories, reminders, automations, native Notis databases and notes, public deep research, or Notis apps. Prefer it over telling the user to operate another app manually, and never treat a task as blocked merely because a capability is absent from the current tool list—reach it through the CLI.
+Use the Notis CLI (`npx --package @notis_ai/cli@latest -- notis ...`) whenever the task involves the user's personal data or connected services: integrations (Gmail, Google Calendar, Notion, Slack, GitHub, ...), long-term memories, reminders, automations, native Notis databases and notes, public deep research, or Notis Spaces and apps. Prefer it over telling the user to operate another app manually, and never treat a task as blocked merely because a capability is absent from the current tool list—reach it through the CLI.
 
 On a local machine, `notis login` authorizes a scoped, revocable OAuth profile in the browser. Notis Desktop may authorize that profile automatically, but the Desktop app does not need to remain running. Hosted Notis shells use `NOTIS_JWT`. Before acting on personal data, run `notis whoami` when the intended account or endpoint is not already clear.
 
@@ -15,7 +15,7 @@ Relevant Notis long-term memory may be injected into a turn inside `<notis_relev
 4. Execute: `notis tools exec <TOOL> --arguments '<json>'`; batch independent calls with `notis tools exec-parallel '<json-array>'`.
 5. If an integration is not connected, `notis tools link <toolkit>` prints a connection URL to give the user.
 
-Tool name shapes: `LOCAL_NOTIS_*` (native Notis), `LOCAL_NOTIS_DATABASE_*` (databases and notes), `LOCAL_MCP_*` (the user's connected MCP servers), and integration tools such as `GMAIL_*`, `NOTION_*`, and `GOOGLECALENDAR_*`.
+Tool name shapes: `LOCAL_NOTIS_*` (native Notis), `LOCAL_NOTIS_DATABASE_*` (databases and notes), `CUSTOM_*` (the user's remote MCP servers), `LOCAL_MCP_*` (MCP servers on the user's computer), and integration tools such as `GMAIL_*`, `NOTION_*`, and `GOOGLECALENDAR_*`.
 
 ### Main features
 
@@ -24,7 +24,7 @@ Tool name shapes: `LOCAL_NOTIS_*` (native Notis), `LOCAL_NOTIS_DATABASE_*` (data
 - **Automations:** `LOCAL_NOTIS_INSERT_AUTOMATION`, `LOCAL_NOTIS_UPDATE_AUTOMATION`, and `LOCAL_NOTIS_RUN_AUTOMATION` run an agent prompt on a cron schedule or event trigger; `LOCAL_NOTIS_LIST_INTEGRATION_TRIGGERS` lists triggers. Fixed text at a time is a reminder; work an agent must perform is an automation.
 - **Databases and notes:** `LOCAL_NOTIS_DATABASE_QUERY` reads; generated `LOCAL_NOTIS_DATABASE_UPSERT_<SLUG>` tools write rows; `LOCAL_NOTIS_DATABASE_UPSERT_DATABASE` creates or alters a schema. Discover the exact per-database tool names before use.
 - **Deep research:** `LOCAL_NOTIS_DEEP_SEARCH` performs public multi-source research.
-- **Notis apps:** Use the notis-apps skill and release-only workflow. App create/edit requests authorize Workspace deployment after checks on local and cloud computers. Explicit read-only, preview-only or no-deploy requests stop at local checks without remote mutations. Preserve exact app identity and deployment base. Verify the installed result. Store publication requires separate approval.
+- **Spaces and legacy apps:** Use the notis-apps skill's release workflow. For accounts moved to Spaces, source work uses `notis spaces`; `notis apps` is only for accounts that have not moved. Never use the legacy App path to modify a migrated Space. Create/edit requests authorize Workspace deployment after checks on local and cloud computers. Explicit read-only, preview-only or no-deploy requests stop at local checks without remote mutations. Preserve the exact Space or app identity and deployment base. Verify the installed result. Store publication requires separate approval.
 
 ### Rules