@notis_ai/cli 0.2.0-beta.21.1 → 0.2.0-beta.35.1

package/README.md

@@ -1,21 +1,23 @@
 # @notis_ai/cli
 
-Agent-first Notis CLI for apps, databases, and generic tool execution.
+Agent-first Notis CLI for apps and generic tool execution.
 
 ## Install
 
-The Notis CLI is bundled automatically with the Notis desktop app.
+The Notis CLI is bundled automatically with the Notis desktop app. Install and sign into Notis Desktop to install the `notis` command, write the local CLI config, and keep the bundled CLI, `notis-cli`, and `notis-apps` skills updated.
+
+For CI, hosted agents, or internal scripts, pass a non-persisted token with `NOTIS_JWT=<token>`.
 
 ## Quick Start
 
 ```bash
 notis --help
-notis auth status
+notis doctor
 notis apps list
-notis db list
+notis tools search "list Notis databases"
 ```
 
-If you're using the desktop app, login and logout keep the CLI profile in sync automatically.
+The desktop app owns sign-in and keeps the CLI profile in sync automatically.
 
 The CLI defaults to `json` output in agent or non-TTY contexts and `table` output in interactive terminals.
 
@@ -29,45 +31,6 @@ The CLI defaults to `json` output in agent or non-TTY contexts and `table` outpu
 - `--timeout-ms <n>` — HTTP timeout in milliseconds
 - `--idempotency-key <key>` — Override the generated idempotency key for mutating commands
 
-## Auth
-
-### `notis auth login`
-
-Store credentials for a named CLI profile.
-
-When to use: Use this before authenticated commands, especially in fresh environments or CI profiles.
-
-Options:
-- `--jwt <token>` — JWT token to store for the profile.
-
-Examples:
-- `notis auth login --jwt <token>`
-- `notis auth login --profile staging --api-base http://localhost:3001`
-
-### `notis auth logout`
-
-Remove the stored JWT for the active profile.
-
-When to use: Use this to clear local credentials without touching other profiles.
-
-Examples:
-- `notis auth logout`
-- `notis auth logout --profile staging`
-
-### `notis auth status`
-
-Inspect local auth configuration and optionally verify it against the API.
-
-When to use: Use this before automating commands to confirm the active profile and token health.
-
-Options:
-- `--verify` — Perform a live authenticated roundtrip to the API.
-
-Examples:
-- `notis auth status`
-- `notis auth status --verify --json`
-
-
 ## Apps
 
 ### `notis apps list`
@@ -84,58 +47,81 @@ Examples:
 
 Scaffold a new Notis app project.
 
-When to use: Start a new Notis app. Creates a Vite + React project with @notis/sdk pre-configured.
+When to use: Start a new Notis app. Use --from with a bundled scaffold when one is close to the desired app; otherwise creates the bare Vite + React project.
+
+Options:
+- `--from <slug>` — Start from a bundled scaffold listed by `notis apps scaffolds list`.
 
 Examples:
+- `notis apps scaffolds list`
 - `notis apps init "Mind the Flo"`
+- `notis apps init "My CRM" --from notis-database`
 - `notis apps init "My App" ./my-app`
 
+### `notis apps scaffolds list`
+
+List bundled Notis app scaffolds.
+
+When to use: Discover the fixed scaffold catalog shipped with the CLI before starting a new app.
+
+Examples:
+- `notis apps scaffolds list`
+- `notis apps init "My App" --from notis-database`
+
 ### `notis apps create <name> [dir]`
 
 Create a new remote Notis app and optionally link a local project to it.
 
 When to use: Provision a fresh remote app before the first deploy. Pass a project directory to link it immediately.
 
-Options:
-- `--description <text>` — Optional app description.
-- `--icon <lucide:icon>` — Optional Lucide icon, for example lucide:dices.
-
 Examples:
 - `notis apps create "My App"`
-- `notis apps create "My App" . --description "Internal tool" --icon lucide:layout-dashboard`
+- `notis apps create "My App" .`
 
 ### `notis apps dev [dir]`
 
-Run the Vite dev server for local development.
+Develop Notis apps inside the Electron desktop Portal with automatic local bundle reloads.
 
-When to use: Iterate on app UI with hot reload. SDK hooks return mock data.
+When to use: Run this inside a single app or a monorepo root with apps/<name>/notis.config.ts. It discovers every app, starts the local bundle server, registers desktop-local dev sessions, and opens the Electron Portal to the local development app.
+
+Options:
+- `--port <number>` — Local bundle server port (default: 5173).
+- `--no-open` — Do not auto-open the desktop Portal local development app.
 
 Examples:
 - `notis apps dev`
 - `notis apps dev ./my-app`
+- `notis apps dev ./workspace --port 5200`
 
 ### `notis apps build [dir]`
 
 Build and package the app into .notis/output/.
 
-When to use: Prepare the app for preview or deployment.
+When to use: Prepare the app for verification or deployment.
 
 Examples:
 - `notis apps build`
 - `notis apps build ./my-app`
 
-### `notis apps preview [dir]`
+### `notis apps verify [dir]`
 
-Serve the built bundle locally for testing.
+Headless render smoke each route in a stub-runtime harness.
 
-When to use: Smoke-test the exact bundle that will be deployed. Databases use seed data.
+When to use: After notis apps build, before deploy. Catches render-time crashes and missing runtime calls that the build step cannot detect.
 
 Options:
-- `--port <number>` — Server port (default: 8787).
+- `--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.
+- `--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).
 
 Examples:
-- `notis apps preview`
-- `notis apps preview --port 3000`
+- `notis apps verify`
+- `notis apps verify --routes notes`
+- `notis apps verify --mode live`
+- `notis apps verify --no-browser  # start the harness, drive agent-browser yourself`
 
 ### `notis apps link <app-id> [dir]`
 
@@ -147,6 +133,20 @@ Examples:
 - `notis apps link abc123`
 - `notis apps link abc123 ./my-app`
 
+### `notis apps pull <app-id> [dir]`
+
+Download a Notis app source snapshot into a local project folder.
+
+When to use: Edit an installed app locally. Pulls the persisted source, links the directory to the app/version, then continue with npm install, notis apps dev, notis apps build, and notis apps deploy.
+
+Options:
+- `--force` — Overwrite a non-empty target directory.
+- `--version <n>` — Pull a specific app source version (default: latest).
+
+Examples:
+- `notis apps pull abc123`
+- `notis apps pull abc123 ./my-app --force`
+
 ### `notis apps deploy [dir]`
 
 Build and upload the app to the linked Notis app.
@@ -175,54 +175,6 @@ Examples:
 - `notis apps doctor ./my-app`
 
 
-## Databases
-
-### `notis db list`
-
-List native Notis databases.
-
-When to use: Use this to find database ids and slugs before querying or updating schemas.
-
-Examples:
-- `notis db list`
-- `notis db list --json`
-
-### `notis db upsert`
-
-Create or update a native database schema.
-
-When to use: Use this when you need to provision a new database or adjust an existing schema.
-
-Options:
-- `--operation <create|update>` — Create a new database or update an existing one.
-- `--database-id <id>` — Database id for update operations.
-- `--title <text>` — Database title.
-- `--description <text>` — Database description.
-- `--icon <lucide-icon-name>` — Database icon (Lucide icon name, e.g. database).
-- `--properties <json>` — JSON array of property definitions.
-
-Examples:
-- `notis db upsert --operation create --title "Tasks"`
-- `notis db upsert --operation update --database-id db_123 --title "Tasks V2"`
-
-### `notis db query <database-slug>`
-
-Run a structured query against a native Notis database.
-
-When to use: Use this when the database slug is known and you need direct filters, sorts, or pagination.
-
-Options:
-- `--filter <json>` — Structured query filter JSON.
-- `--sort <json>` — Sort JSON object or array.
-- `--page-size <n>` — Page size between 1 and 100.
-- `--offset <n>` — Zero-based offset.
-- `--cursor <value>` — Pagination cursor alias for next_offset.
-
-Examples:
-- `notis db query tasks --page-size 50`
-- `notis db query tasks --filter '{"property":"Status"}'`
-
-
 ## Generic Tools
 
 ### `notis tools toolkits`
@@ -271,15 +223,15 @@ Options:
 - `--arguments <json>` — JSON object, @file path, or - for stdin.
 - `--get-schema` — Display the tool parameter schema without executing.
 - `--dry-run` — Validate arguments against the tool schema without executing.
-- `--watch <seconds>` — Re-execute on an interval and stream results.
+- `--toolkits <csv-or-json>` — Optional toolkit namespace(s) to use when resolving the tool.
 
 Examples:
 - `notis tools exec notis-default-query --arguments '{"database_slug":"tasks","query":{}}'`
+- `notis tools exec notis-default-get_database --arguments '{"database_slug":"tasks"}'`
 - `notis tools exec notis-default-query --get-schema`
 - `notis tools exec notis-default-query --dry-run --arguments '{"database_slug":"tasks","query":{}}'`
 - `notis tools exec notis-default-query --arguments @query.json`
 - `notis tools exec notis-default-query --arguments - < query.json`
-- `notis tools exec notis-default-query --watch 10 --arguments '{"database_slug":"tasks","query":{}}'`
 
 ### `notis tools exec-parallel <calls>`
 
@@ -313,6 +265,16 @@ Examples:
 - `notis doctor`
 - `notis doctor --json`
 
+### `notis whoami`
+
+Display the active profile, user, and available toolkits.
+
+When to use: Use this to quickly confirm which account and environment a command will target.
+
+Examples:
+- `notis whoami`
+- `notis whoami --json`
+
 ### `notis describe <command...>`
 
 Describe a first-class CLI command in detail.
@@ -320,14 +282,14 @@ Describe a first-class CLI command in detail.
 When to use: Use this when an agent or human needs the exact shape, examples, and semantics of a command.
 
 Examples:
-- `notis describe apps push`
-- `notis describe db query`
+- `notis describe apps deploy`
+- `notis describe tools exec`
 
 
 ## Local Development
 
 ```bash
-cd cli/npm
+cd packages/cli
 npm install
 node ./bin/notis.js --help
 npm run docs:generate

package/dist/scaffolds/notes/app/globals.css

@@ -0,0 +1,3 @@
+@tailwind base;
+@tailwind components;
+@tailwind utilities;

package/dist/scaffolds/notes/app/layout.tsx

@@ -0,0 +1,6 @@
+import '@notis/sdk/styles.css';
+import './globals.css';
+
+export default function AppShell({ children }: { children: React.ReactNode }) {
+  return children;
+}