@series-a/cli 0.23.1 → 1.0.0

package/package.json

@@ -1,61 +1,26 @@
 {
   "name": "@series-a/cli",
-  "version": "0.23.1",
-  "description": "AdvisorPro command-line interface — drive leads, campaigns, sequences and agents from your terminal.",
+  "version": "1.0.0",
+  "private": false,
+  "description": "Setu CLI — build, review and publish claimable practice and dentist profiles.",
   "type": "module",
+  "license": "UNLICENSED",
+  "publishConfig": {
+    "access": "public"
+  },
   "bin": {
-    "advisoros": "bin/advisoros.mjs"
+    "setu": "./bin/setu.mjs"
   },
-  "files": [
-    "bin/",
-    "src/",
-    "README.md",
-    "SKILLS.md",
-    "CHANGELOG.md",
-    "LICENSE"
-  ],
   "engines": {
     "node": ">=20"
   },
   "scripts": {
-    "start": "node bin/advisoros.mjs",
-    "smoke": "node bin/advisoros.mjs --help >/dev/null && node bin/advisoros.mjs --version >/dev/null && node -e \"import('node:fs').then(({readFileSync})=>{const s=readFileSync('bin/advisoros.mjs','utf8');if(!s.startsWith('#!/usr/bin/env node')){console.error('Missing shebang in bin/advisoros.mjs');process.exit(1)}})\"",
-    "prepublishOnly": "npm run smoke",
-    "changeset": "changeset",
-    "version-packages": "changeset version",
-    "release": "npm run smoke && changeset publish --access public"
-  },
-  "dependencies": {
-    "commander": "^12.1.0",
-    "chalk": "^5.3.0",
-    "cli-table3": "^0.6.5",
-    "ora": "^8.1.1",
-    "prompts": "^2.4.2"
-  },
-  "devDependencies": {
-    "@changesets/cli": "^2.27.9"
+    "smoke": "node ./bin/setu.mjs --version && node ./bin/setu.mjs --help > /dev/null"
   },
-  "publishConfig": {
-    "access": "public"
-  },
-  "repository": {
-    "type": "git",
-    "url": "git+https://github.com/series-a/advisoros.git",
-    "directory": "tools/cli"
-  },
-  "homepage": "https://advisoros.series-a.co",
-  "bugs": {
-    "url": "https://github.com/series-a/advisoros/issues"
-  },
-  "keywords": [
-    "advisoros",
-    "cli",
-    "linkedin",
-    "campaigns",
-    "leads",
-    "sequences",
-    "agent-api"
-  ],
-  "author": "AdvisorPro",
-  "license": "UNLICENSED"
+  "files": [
+    "bin",
+    "lib",
+    "README.md",
+    "CHANGELOG.md"
+  ]
 }

package/LICENSE

@@ -1,7 +0,0 @@
-Copyright (c) AdvisorPro / Series A. All rights reserved.
-
-This package is distributed under a proprietary license. Use is permitted only
-by AdvisorPro customers and partners against their own workspace API keys. Do not
-redistribute, sublicense, or use against workspaces you do not own without
-written permission.
-

package/SKILLS.md

@@ -1,319 +0,0 @@
-# AdvisorPro Skills Guide for AI Agents
-
-This file teaches any AI agent — CLI user or MCP client — how to operate
-AdvisorPro safely and effectively. It covers the mental model, the core
-workflows (campaigns, content, brand), the safety rails you must respect,
-and the tricks that separate a smooth run from a failed one.
-
-Two surfaces, one backend:
-
-- **CLI** — `advisoros` binary (`npm i -g @series-a/cli`), authenticates with
-  an API key saved per profile in `~/.advisoros/config.json`.
-- **MCP server** — `advisoros-mcp`, 44 tools, OAuth for the signed-in user.
-
-Both talk to the same `/agent-api` gateway. Everything is **scoped to one
-workspace**. Every mutation is **audited** (who, when, what, outcome).
-
----
-
-## 1. The non-negotiable first steps
-
-### MCP
-1. **Always call `list_workspaces` first.** Every other tool requires a
-   `workspace_id`. You can only see workspaces you belong to — never guess an
-   ID from another session.
-2. Read the tool description before calling: destructive tools document their
-   own confirmation protocol.
-
-### CLI
-```bash
-advisoros login --profile main          # saves API key + workspace
-advisoros whoami                        # confirm the active profile/workspace
-```
-Global flags on every command: `--json` (machine output — **always use this
-when an AI is parsing the result**), `-w/--workspace`, `-p/--profile`,
-`--api-key`, `--as-agent <name>` (labels your audit rows — set it to your
-agent's name).
-
----
-
-## 2. Mental model
-
-- **Leads** are people. They enter via import and are enriched from LinkedIn
-  afterwards. Dedupe key is `(workspace_id, linkedin_url)` — re-importing the
-  same URL upserts, never duplicates.
-- **Sequences** are message trees (steps with actions, delays, branches).
-  They are **not append-only** — steps can be edited, deleted, re-parented,
-  or wholesale replaced.
-- **Campaigns** bind leads + a sequence + sender LinkedIn accounts + a daily
-  limit. Lifecycle: draft → launch → pause/resume → archive/delete.
-- **Content** items are drafts until scheduled/published. Nothing is ever
-  auto-published from a draft.
-- **Knowledge base** grounds all AI generation. Only **confirmed
-  human-authored** items train the voice and count as citable evidence.
-- **Agents** run asynchronously: you get a `job_id` back, then poll.
-
----
-
-## 3. LinkedIn safety — read this before any outreach
-
-LinkedIn account safety overrides everything else. The server (not the CLI or
-MCP) is the enforcing authority; you are expected to check before acting.
-
-Hard limits (server-enforced):
-- Invite note: **200 characters**
-- Direct message: **8,000 characters** (CLI caps client-side at 7,900)
-- Comment: **1,250 characters**
-- Per sender: **~25 invites/day, ~80 messages/day**
-
-Rules for agents:
-- **Before planning outreach or a bulk import, check capacity.**
-  CLI: `advisoros safety check` / `safety limits` / `safety reads`.
-  MCP: `linkedin_safety` (returns remaining capacity, cooldowns, and
-  `safe_bulk_import_size`).
-- **A cooldown or a 429 is not a failure.** Back off using `Retry-After` /
-  `retry_after_seconds` and retry. Never hammer.
-- `campaigns launch` and `sequences validate` run the same char-limit checks
-  the server enforces — **validate before launch**, not after.
-
----
-
-## 4. How to create a campaign (end to end)
-
-### The fast path: `campaign-flow`
-One command does import → sequence → launch → status:
-
-```bash
-advisoros campaign-flow \
-  --name "Q3 CFO outreach" \
-  --file leads.csv \
-  --goal "Book discovery calls with CFOs" \
-  --senders <senderId1>,<senderId2> \
-  --daily-limit 25 \
-  --launch
-```
-Add `--dry-run` first to print the plan without touching the API.
-
-### The step-by-step path
-```bash
-# 1. Check capacity
-advisoros safety check
-
-# 2. Import leads (auto-chunks at 200/call, upserts on linkedin_url)
-advisoros leads import --file leads.csv
-# or from a source:
-advisoros leads import-from linkedin_search --query "CFO fintech London"
-# Sales Navigator (queued in the background, cap-aware):
-advisoros leads import-from sales_nav_url --url "<sales-nav-search-url>" --limit 500
-advisoros leads import-schedules            # progress, ETA, why it is waiting
-advisoros leads import-schedule pause|resume|cancel <scheduleId>
-
-# 3. Build or pick a sequence
-advisoros sequences create --name "CFO 3-touch"
-advisoros sequences add-step <seqId> --action sendInvitation --message "..."
-advisoros sequences add-step <seqId> --action wait --days 3
-advisoros sequences add-step <seqId> --action sendMessage --message "..."
-advisoros sequences validate <seqId>      # same checks as launch — do this
-
-# 4. Create the campaign and attach everything
-advisoros campaigns create --name "Q3 CFO outreach" \
-  --sequence <seqId> --senders <id1,id2> --daily-limit 25
-advisoros campaigns add-leads <campaignId> --file leads.csv
-
-# 5. Preflight, then launch (launch runs preflight itself and asks --confirm)
-advisoros campaigns preflight <campaignId>
-advisoros campaigns launch <campaignId> --confirm
-```
-
-MCP equivalent: `import_leads` → `manage_sequence` → `update_campaign` →
-`manage_campaign` (`preflight`, then `launch`).
-
-### After launch
-```bash
-advisoros campaigns stats <id>     # funnel: invites → accepts → replies → meetings
-advisoros campaigns health <id>    # run state, stalls, retries, watchdog
-advisoros campaigns events <id>    # full event log
-```
-
----
-
-## 5. Sequences: the tricks
-
-- Allowed step actions: `viewProfile`, `addReaction`, `sendInvitation`,
-  `sendMessage`, `wait`. Nothing else — the server rejects unknown actions.
-- `sequences show <id>` accepts a **unique ID prefix**, not just full UUIDs.
-- `replace-steps` is **atomic**: it swaps the whole tree from a JSON file,
-  validated server-side. Prefer it over many `add-step` calls when an AI is
-  generating a full sequence.
-- `update-step` patches one step in place; `delete-step` re-parents its
-  children automatically.
-- Message templates support `{first_name}`-style tokens; the server guards
-  against unfilled tokens (~20-char guard). Keep variables real.
-- Waits can be expressed in days/hours/minutes. A lead who **replies is
-  removed from all further automation automatically** — never re-add them.
-
----
-
-## 6. Keeping a consistent brand
-
-Brand consistency lives in three places; keep all three in sync.
-
-### a) The brand record (visual identity)
-```bash
-advisoros brand show                 # colours, fonts, logos, tagline, imagery
-advisoros brand set --primary-color "#1B4B8F" --font-heading "Inter"
-advisoros brand fields               # every editable field
-advisoros brand imagery set --style "minimal editorial" --mood "calm, expert"
-advisoros brand logos set --variant primary --url https://...
-advisoros brand social set --linkedin https://linkedin.com/company/...
-```
-MCP: `manage_brand` (same fields; supports partial updates, add/remove of
-motifs and reference URLs, logo upload, and the imagery direction that steers
-**every generated image**).
-
-### b) Tone of voice (written identity)
-```bash
-advisoros voice show                 # directive + apply-by-default flag
-advisoros voice set --directive "..." --apply-default
-advisoros voice sync                 # re-pull from Business Build
-advisoros voice references           # KB items used as writing samples
-advisoros voice add-reference <knowledgeItemId>
-advisoros voice set-primary <knowledgeItemId>   # pin the benchmark sample
-advisoros voice card                 # measured voice card (stylometric targets)
-advisoros voice score --file draft.md    # score text against the voice
-advisoros voice redraft --file draft.md  # rewrite in the author's voice
-```
-MCP: `tone_of_voice`.
-
-**The rule that matters:** only knowledge items confirmed as human-authored
-count as voice-training material. Confirm them first (`voice add-reference`,
-or MCP `curate_knowledge` with `approve`). AI-authored items are down-weighted
-and labelled in every retrieval — don't try to train the voice on them.
-
-### c) Knowledge base (factual identity)
-```bash
-advisoros knowledge add --url https://...     # auto-scraped + AI-classified
-advisoros knowledge add --title "..." --text "..." --category positioning
-advisoros knowledge list
-advisoros knowledge reclassify <id>
-```
-Categories: positioning, proof-points, frameworks, personas, case-studies,
-transcripts, market-intel, general. Generation is grounded in the KB — a thin
-KB means generic output. Feed it real positioning and real proof points.
-
-### Generating on-brand output
-```bash
-advisoros content generate --topic "..." --type linkedin_post   # KB + reference
-                                                                # grounded, URL-sanitised
-advisoros content citations <id>    # every source recorded for a draft
-```
-MCP: `generate_graphic` / `refine_graphic` for images (returns public URLs,
-uses the brand imagery direction automatically), `create_content_draft` for
-text (drafts only — nothing auto-publishes).
-
----
-
-## 7. Content strategy & calendar
-
-```bash
-advisoros strategies ideate --weeks 4          # multi-week arc from KB + signals
-advisoros strategies create ...
-advisoros strategies resume <id>               # continue an interrupted build
-advisoros content list / show / approve / schedule / publish
-advisoros content bulk-approve                 # approve everything pending
-advisoros calendar list / create
-```
-Scheduling routes through Taplio when connected, otherwise the built-in cron
-scheduler. MCP: `content_strategy`, `content_strategy_posts`,
-`schedule_content`, `manage_content`.
-
----
-
-## 8. Running agents (async jobs)
-
-```bash
-advisoros agents list
-advisoros agents run <name>              # returns a job_id immediately
-advisoros agents job <jobId>             # poll until terminal
-```
-MCP: `trigger_agent` (or `history: true` for recent runs).
-
-Watch recipe:
-```bash
-JOB=$(advisoros agents run news-monitor --json | jq -r .job_id)
-until advisoros agents job "$JOB" --json | jq -e '.status=="completed"'; do
-  sleep 15
-done
-```
-A job ends in a **terminal state** (`completed` or `failed`). Content jobs
-also carry `content_ids` and trace steps — if a job stays `running`, poll
-longer (large articles take minutes); don't resubmit, dispatch is
-exactly-once.
-
----
-
-## 9. Destructive actions — the confirm protocol
-
-Deletion is allowed but always two-step:
-
-- CLI: `campaigns delete <id>` is dry-run by default; re-run with `--force`.
-- MCP: `manage_campaign` / `manage_sequence` with `operation: "delete"`:
-  first `dry_run: true` to see the impact, then `confirm: true` to execute.
-  Campaigns that already dispatched activity also require `force: true`.
-
-`archive` is the reversible alternative — prefer it when unsure.
-
----
-
-## 10. Tricks & gotchas
-
-1. **`--json` everywhere.** Human tables are for humans; parse JSON.
-2. **`--as-agent <name>` on every call.** Your actions appear in
-   `advisoros audit list` — make them attributable.
-3. **Mutation responses are live.** Every campaign/sequence mutation returns
-   the freshly re-read record with live counts. List `stats` snapshots can
-   lag — trust the `live` block after a mutation.
-4. **Imports are idempotent.** Re-importing the same leads upserts on
-   `(workspace_id, linkedin_url)`. Safe to retry after a crash.
-5. **Inbox sends are dry-run by default.** `inbox send`/`reply` exit code `2`
-   without `--confirm` — nothing hits LinkedIn until you confirm.
-6. **Intelligence before content.** `signals list` and the watchlist (P0–P3
-   priorities) drive what the content agents write about. A tuned watchlist +
-   rich KB + confirmed voice references = on-topic, on-voice output.
-7. **`export <resource> <action>`** turns any list into CSV for offline work.
-8. **`kb sync`** mirrors the knowledge base into an Obsidian vault — one-way
-   push only, never a source of truth in the other direction.
-9. **`integrations status`** is read-only health. It will never return
-   credentials — don't ask it to.
-10. **Transcripts are anonymised** before storage. You will never see raw PII
-    from `meetings`/`list_transcripts`; that's by design.
-11. **Rate limits:** per-key sliding window. On HTTP 429, respect
-    `Retry-After`. Empty results are never used as a throttle signal — if you
-    get an empty list, the data is genuinely empty.
-12. **MCP writes are limited** to leads, knowledge items, drafts, and the
-    management tools above. Nothing auto-publishes; publishing is a deliberate
-    `manage_content publish_now` / `content publish` call.
-
----
-
-## 11. Cheatsheet
-
-| Task | CLI | MCP tool |
-|---|---|---|
-| Discover workspaces | `workspaces list` (admin) | `list_workspaces` (first!) |
-| Check LinkedIn capacity | `safety check` | `linkedin_safety` |
-| Import leads | `leads import` / `import-from` | `import_leads` |
-| Track Sales Nav imports | `leads import-schedules` / `import-schedule` | `lead_import_schedules` |
-| Build a sequence | `sequences create/add-step/replace-steps/validate` | `manage_sequence` |
-| Launch a campaign | `campaign-flow` or `campaigns create/add-leads/launch` | `manage_campaign` |
-| Campaign funnel | `campaigns stats` | `campaign_analytics` |
-| Brand identity | `brand show/set/imagery/logos/social` | `manage_brand` |
-| Voice | `voice show/set/references/score` | `tone_of_voice` |
-| Knowledge | `knowledge add/list/reclassify` | `add_knowledge_item`, `curate_knowledge` |
-| Generate content | `content generate` | `create_content_draft`, `generate_graphic` |
-| Schedule | `content schedule` / `calendar create` | `schedule_content` |
-| Run an agent | `agents run` + `agents job` | `trigger_agent` |
-| Who did what | `audit list` | `list_audit` |
-
-When in doubt: `advisoros <command> --help`, `docs/cli.md`, and
-`docs/agent-api.md` are the canonical references.

package/bin/advisoros.mjs

@@ -1,2 +0,0 @@
-#!/usr/bin/env node
-import "../src/index.mjs";

package/src/api.mjs

@@ -1,102 +0,0 @@
-import { randomUUID } from "node:crypto";
-import { createRequire } from "node:module";
-import { getProfile, DEFAULTS } from "./config.mjs";
-
-const CLI_VERSION = (() => {
-  try {
-    return createRequire(import.meta.url)("../package.json").version;
-  } catch {
-    return "unknown";
-  }
-})();
-
-export class AdvisorOSApiError extends Error {
-  constructor(message, { status, body } = {}) {
-    super(message);
-    this.name = "AdvisorOSApiError";
-    this.status = status;
-    this.body = body;
-  }
-}
-
-/**
- * Invoke the AdvisorPro /agent-api router.
- * Resolves credentials from --profile / env / saved config in that order.
- */
-export async function call(resource, action, params = {}, opts = {}) {
-  const profileName = opts.profile || process.env.ADVISOROS_PROFILE || "default";
-  const stored = await getProfile(profileName);
-  const apiKey = opts.apiKey || process.env.ADVISOROS_API_KEY || stored?.apiKey;
-  const workspaceId =
-    opts.workspaceId ||
-    process.env.ADVISOROS_WORKSPACE_ID ||
-    stored?.workspaceId;
-  const baseUrl =
-    opts.baseUrl ||
-    process.env.ADVISOROS_BASE_URL ||
-    stored?.baseUrl ||
-    DEFAULTS.baseUrl;
-  const agentName =
-    opts.agentName ||
-    process.env.ADVISOROS_AGENT_NAME ||
-    stored?.agentName ||
-    "advisoros-cli";
-
-  const actorEmail =
-    opts.actorEmail || process.env.ADVISOROS_ACTOR_EMAIL || stored?.email || null;
-  const actorUserId =
-    opts.actorUserId || process.env.ADVISOROS_ACTOR_USER_ID || stored?.userId || null;
-
-  if (!apiKey) {
-    throw new AdvisorOSApiError(
-      "No API key configured. Run `advisoros login` or set ADVISOROS_API_KEY.",
-    );
-  }
-  // workspaces resource doesn't require a workspace_id in the envelope.
-  if (!workspaceId && resource !== "workspaces") {
-    throw new AdvisorOSApiError(
-      "No workspace configured. Run `advisoros login` again or pass --workspace.",
-    );
-  }
-
-  const body = {
-    agent_name: agentName,
-    workspace_id: workspaceId ?? "",
-    resource,
-    action,
-    params,
-  };
-
-  let res;
-  try {
-    res = await fetch(baseUrl, {
-      method: "POST",
-      headers: {
-        "Content-Type": "application/json",
-        "x-service-account-key": apiKey,
-        "x-surface": "cli",
-        "x-client-name": "advisoros-cli",
-        "x-client-version": CLI_VERSION,
-        "x-correlation-id": opts.correlationId || randomUUID(),
-        ...(actorUserId ? { "x-actor-user-id": actorUserId } : {}),
-        ...(actorEmail ? { "x-actor-email": actorEmail } : {}),
-      },
-      body: JSON.stringify(body),
-    });
-  } catch (e) {
-    throw new AdvisorOSApiError(`Network error: ${e.message}`);
-  }
-
-  const text = await res.text();
-  let json;
-  try { json = JSON.parse(text); } catch { json = { raw: text }; }
-
-  if (!res.ok || json?.success === false) {
-    throw new AdvisorOSApiError(
-      json?.error || `HTTP ${res.status}`,
-      { status: res.status, body: json },
-    );
-  }
-  return json;
-}
-