@notis_ai/cli 0.2.0-beta.113.1 → 0.2.0-beta.116.1

package/skills/notis-apps/cli.md

@@ -232,6 +232,21 @@ 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 apps duplicate [dir]`
+
+Duplicate an app into an independent copy with its own databases.
+
+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.
+
+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'.
+
+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 apps doctor [dir]`
 
 Check project health and readiness.

package/skills/notis-cli/SKILL.md

@@ -49,9 +49,9 @@ Treat the Notis CLI the same way you would treat a Composio-style tool router fl
 
 Use this section when the goal is to create or update a Notis app from a local workspace.
 
-Notis apps are Vite + React projects using `@notis/sdk`. The workflow is init or pull, dev, build, verify, create/link, deploy.
+Notis apps are Vite + React projects using `@notis/sdk`. The workflow is init or pull, dev, build, verify, create/link, deploy, then an explicitly confirmed Store submission when requested.
 
-Important: `deploy` means updating the installed app artifact for the current user or team. To list an app in the public Notis App Store, the owner opens the app details page in the Notis Portal, sets visibility to Team or Public, then uses Publish/Update. The CLI does not publish to the store; the backend opens the registry PR using a service token.
+Important: `deploy` only updates the installed app artifact for the current user or team. Store submission is a separate, user-gated step. After the user explicitly confirms that the current App Details page and Store listing are ready, `apps publish --confirm-ready` submits the matching deployed version through the backend review flow.
 
 ### App development workflow
 
@@ -74,6 +74,8 @@ Important: `deploy` means updating the installed app artifact for the current us
    - `npx --package @notis_ai/cli@latest -- notis apps deploy`
 9. Check project health:
    - `npx --package @notis_ai/cli@latest -- notis apps doctor`
+10. Only after the user explicitly approves the current Store preview, submit the deployed version:
+   - `npx --package @notis_ai/cli@latest -- notis apps publish --confirm-ready`
 
 ### App development rules
 
@@ -82,7 +84,8 @@ Important: `deploy` means updating the installed app artifact for the current us
 - Link before `deploy`, or pass `--app-id <id>` when intentionally deploying without writing local link state.
 - Use `npx --package @notis_ai/cli@latest -- notis apps doctor` to diagnose configuration or dependency issues.
 - Use `npx --package @notis_ai/cli@latest -- notis apps list` to discover existing app IDs before linking.
-- For App Store publishing, do not use the CLI. The user opens the app details page in the Notis Portal, sets visibility to Team or Public, then uses Publish/Update. The backend opens the registry PR on their behalf using a service token. Do not invent any CLI store-publish command.
+- Never treat deploy approval as Store approval. Set visibility to Team or Public first, then run `apps publish --confirm-ready` only after the user explicitly confirms the current App Details page and Store listing.
+- `apps publish --confirm-ready` submits the deployed snapshot through the same backend review flow as App Details. It must reject missing confirmation, incomplete listing media, a local/deployed version mismatch, private visibility, or an existing pending review.
 
 ### App development command reference
 
@@ -96,9 +99,10 @@ Important: `deploy` means updating the installed app artifact for the current us
 - `npx --package @notis_ai/cli@latest -- notis apps link` -- associate the project with a remote app
 - `npx --package @notis_ai/cli@latest -- notis apps deploy` -- upload the artifact and editable source snapshot to the linked installed app in Notis
 - `npx --package @notis_ai/cli@latest -- notis apps deploy --direct` -- deploy directly to Supabase storage, bypassing the backend server (auto-fallback when server is down)
+- `npx --package @notis_ai/cli@latest -- notis apps publish --confirm-ready` -- submit the matching deployed version for Team or Public Store review after explicit user confirmation
 - `npx --package @notis_ai/cli@latest -- notis apps doctor` -- run project diagnostics
 
-App Store publishing is portal-only — there is no CLI publish command.
+App Details remains the visual review surface and offers the same Publish/Update action. The CLI command is for agents completing an already approved submission; it does not weaken the separate confirmation gate.
 
 If the task is specifically about app structure, runtime behavior, or database/view packaging, pair this skill with the `notis-apps` skill. Use `notis-cli` for the command workflow and `notis-apps` for the product/runtime contract.
 

package/skills/notis-onboarding/BRIEF.md

@@ -0,0 +1,93 @@
+You are onboarding someone to Notis from inside their coding agent. You already
+have a shell and an authenticated Notis CLI, so you do the setup for them and
+report what you did.
+
+Run every Notis operation as:
+
+```bash
+npx --package @notis_ai/cli@latest -- notis tools exec <TOOL> --arguments '<json>'
+```
+
+Never invent tool names. `notis tools search "<what you need>"` finds them.
+
+## 1. Collect the basics
+
+The fields onboarding collects, wherever it runs. Both the conversational
+onboarding assistant and the CLI brief reference this partial so the two paths
+can never quietly collect different things.
+
+All of these land through `LOCAL_NOTIS_SAVE_USER_SETTINGS`: `full_name` on the
+user row, the rest merged into the `settings` blob.
+
+| Field | Setting key | What it is for |
+|---|---|---|
+| First name | `full_name` | How Notis addresses the user. Deduce from the email before asking. |
+| Occupation / role | `position` | Tailors examples and suggestions. |
+| Language | `language` | The language Notis replies in. |
+| Time zone | `timezone` | Anchors every scheduled and time-relative request. Ask; never guess silently. |
+| Attribution | `attribution` | Where they heard about Notis. Asked once, never again. |
+
+Rules that hold on every surface:
+
+* Ask one question at a time. A wall of questions reads as a form, and people
+  abandon forms.
+* Skip anything already known or confidently deducible, and say what you deduced
+  rather than asking the user to confirm a blank.
+* Save as soon as you have the basics rather than batching to the end — a user who
+  drops out halfway should not lose what they already told you.
+
+
+You are in a terminal, so there is no phone number to infer a country from. Take
+the language and time zone from the shell environment if you can read them, state
+what you inferred, and let the user correct you. Then save:
+
+```bash
+npx --package @notis_ai/cli@latest -- notis tools exec LOCAL_NOTIS_SAVE_USER_SETTINGS \
+  --arguments '{"full_name":"...","position":"...","language":"...","timezone":"..."}'
+```
+
+## 2. Connect one app, then immediately read from it
+
+Ask what they use day to day. Gmail, Google Calendar, Notion, Slack, Linear, and
+their CRM are the common answers. For each:
+
+```bash
+npx --package @notis_ai/cli@latest -- notis tools link <toolkit>
+```
+
+Give the user the returned URL and wait. Confirm with `notis tools toolkits`.
+
+Then — and this is the step that makes onboarding land — run one read-only action
+through the connection and show them the actual result: today's calendar events,
+their most recent email threads, the databases in their Notion. A connected
+integration is a claim; their own data on screen is proof.
+
+If they connect nothing, fall back to installing a public app:
+`LOCAL_NOTIS_LIST_PUBLIC_APP_STORE`, then `LOCAL_NOTIS_INSTALL_APP` with
+`destination_type="personal"`.
+
+## 3. Finish onboarding
+
+**Do this. It is not optional.**
+
+```bash
+npx --package @notis_ai/cli@latest -- notis tools exec LOCAL_NOTIS_COMPLETE_TUTORIAL --arguments '{}'
+```
+
+Until this runs, every message the user sends on every channel is routed to the
+onboarding assistant — so an agent that collects everything and skips this leaves
+them permanently stuck talking to an onboarding bot.
+
+Verify with `LOCAL_NOTIS_GET_INTEGRATIONS_STATUS` and tell them what is connected.
+
+## What this plan does not include
+
+Do **not** call `LOCAL_NOTIS_INSERT_REMINDER` or any automation tool during
+onboarding. Reminders, automations, voice, and the messaging channels are paid
+features; calling them here fails at the worst possible moment. If the user asks
+for a reminder or a recurring task, say plainly that it needs an upgrade and offer
+`LOCAL_NOTIS_GET_SUBSCRIPTION_STATUS` so they can see their plan.
+
+What they *do* have: 1,000+ integrations through this CLI, skills that sync to
+their coding agents, long-term memory, notes and databases, and the ability to
+build Notis apps from this machine.

package/src/cli.js

@@ -5,6 +5,7 @@ import { Command } from 'commander';
 import { COMMAND_SPECS, GROUP_SUMMARIES } from './command-specs/index.js';
 import { OutputManager } from './runtime/output.js';
 import { asCliError } from './runtime/errors.js';
+import { reportCliCommand } from './runtime/telemetry.js';
 import {
   DEFAULT_PROFILE,
   resolveOutputMode,
@@ -130,6 +131,7 @@ function attachSpec(program, parentMap, spec, specs) {
   }
 
   command.action(async (...raw) => {
+    const startedAt = Date.now();
     const commanderCommand = raw[raw.length - 1];
     const argumentValues = raw.slice(0, -1);
     const globalOptions = commanderCommand.optsWithGlobals();
@@ -152,10 +154,24 @@ function attachSpec(program, parentMap, spec, specs) {
         output,
       });
       process.exitCode = typeof exitCode === 'number' ? exitCode : 0;
+      await reportCliCommand({
+        spec,
+        runtime,
+        result: process.exitCode === 0 ? 'success' : 'failed',
+        durationMs: Date.now() - startedAt,
+        error: process.exitCode === 0 ? null : { exitCode: process.exitCode },
+      });
     } catch (error) {
       const runtime = buildErrorRuntime(globalOptions);
       const output = new OutputManager(runtime);
       const cliError = asCliError(error);
+      await reportCliCommand({
+        spec,
+        runtime,
+        result: 'failed',
+        durationMs: Date.now() - startedAt,
+        error: cliError,
+      });
       process.exitCode = output.emitError({
         command: spec.command_path.join(' '),
         error: cliError,