@notis_ai/cli 0.2.0 → 0.2.1

package/README.md

@@ -84,7 +84,7 @@ Examples:
 
 Scaffold a new Notis app project.
 
-When to use: Start a new Notis app. Creates a Next.js project with @notis/sdk pre-configured.
+When to use: Start a new Notis app. Creates a Vite + React project with @notis/sdk pre-configured.
 
 Examples:
 - `notis apps init "Mind the Flo"`
@@ -106,36 +106,48 @@ Examples:
 
 ### `notis apps dev [dir]`
 
-Run the Next.js 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 Development tab.
+
+Options:
+- `--port <number>` — Local bundle server port (default: 5173).
+- `--no-open` — Do not auto-open the desktop Portal Development tab.
 
 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 artifact locally for testing.
+Headless render smoke each route in a stub-runtime harness.
 
-When to use: Smoke-test the exact artifact 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 +159,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 and links the directory to the app.
+
+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.
@@ -156,11 +182,13 @@ When to use: Ship the installed app to production for the linked user/team app.
 Options:
 - `--app-id <id>` — Override linked app ID.
 - `--skip-build` — Skip the build step (use existing .notis/output/).
+- `--direct` — Upload directly to Supabase storage, bypassing the backend server. Auto-fallback on network errors.
 
 Examples:
 - `notis apps deploy`
 - `notis apps deploy --skip-build`
 - `notis apps deploy --app-id abc123`
+- `notis apps deploy --direct`
 
 ### `notis apps doctor [dir]`
 
@@ -270,6 +298,7 @@ Options:
 - `--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":{}}'`

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@notis_ai/cli",
-  "version": "0.2.0",
+  "version": "0.2.1",
   "description": "Agent-first Notis CLI for apps, databases, and generic tool execution",
   "type": "module",
   "bin": {
@@ -9,11 +9,14 @@
   "files": [
     "bin/",
     "src/",
+    "template/",
     "README.md"
   ],
   "scripts": {
     "docs:generate": "node ./scripts/generate-docs.js",
     "docs:check": "node ./scripts/generate-docs.js --check",
+    "release:prepare": "node ./scripts/prepare-publish.js --apply",
+    "cli:set-mode": "node ./scripts/set-cli-mode.js",
     "test": "node --test"
   },
   "engines": {
@@ -29,5 +32,8 @@
     "ai",
     "agent-skills"
   ],
+  "publishConfig": {
+    "access": "public"
+  },
   "license": "MIT"
 }