wealthbox-cli 1.1.6__tar.gz → 1.2.0__tar.gz

wealthbox_cli-1.2.0/.claude-plugin/marketplace.json

@@ -0,0 +1,25 @@
+{
+  "$schema": "https://code.claude.com/schemas/marketplace.json",
+  "name": "massive-value",
+  "description": "Marketplace for the Wealthbox CRM agent skill (and future Wealthbox-related plugins).",
+  "owner": {
+    "name": "Kadin Bullock"
+  },
+  "plugins": [
+    {
+      "name": "wealthbox-crm",
+      "source": "./plugins/wealthbox-crm",
+      "description": "Wealthbox CRM agent skill — natural-language CRM automation backed by the `wbox` CLI.",
+      "version": "1.2.0",
+      "category": "productivity",
+      "tags": [
+        "wealthbox",
+        "crm",
+        "financial-advisor"
+      ],
+      "homepage": "https://github.com/massive-value/wealthbox-cli",
+      "repository": "https://github.com/massive-value/wealthbox-cli",
+      "license": "Apache-2.0"
+    }
+  ]
+}

wealthbox_cli-1.2.0/.codex-plugin/plugin.json

@@ -0,0 +1,16 @@
+{
+  "name": "wealthbox-crm",
+  "description": "Wealthbox CRM agent skill — drive contacts, tasks, notes, events, and households via natural language. Bundles SKILL.md, references, and firm-bootstrap workflow. Requires the `wbox` CLI (auto-install instructions in SKILL.md).",
+  "version": "1.2.0",
+  "author": "Kadin Bullock",
+  "homepage": "https://github.com/massive-value/wealthbox-cli",
+  "repository": "https://github.com/massive-value/wealthbox-cli",
+  "license": "Apache-2.0",
+  "skills": "./codex-skill",
+  "keywords": [
+    "wealthbox",
+    "crm",
+    "financial-advisor",
+    "wealth-management"
+  ]
+}

{wealthbox_cli-1.1.6 → wealthbox_cli-1.2.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: wealthbox-cli
-Version: 1.1.6
+Version: 1.2.0
 Summary: CLI and client library for the Wealthbox CRM API
 Project-URL: Homepage, https://github.com/massive-value/wealthbox-cli
 Project-URL: Documentation, https://massive-value.github.io/wealthbox-cli/
@@ -70,6 +70,17 @@ Description-Content-Type: text/markdown
 
 ## Quick Start
 
+**No Python? No problem.** One-line installer (works on a fresh machine):
+
+| Platform | Command |
+|----------|---------|
+| macOS / Linux | `curl -LsSf https://raw.githubusercontent.com/massive-value/wealthbox-cli/main/scripts/install.sh \| bash` |
+| Windows (PowerShell) | `irm https://raw.githubusercontent.com/massive-value/wealthbox-cli/main/scripts/install.ps1 \| iex` |
+
+The installer pulls in [uv](https://github.com/astral-sh/uv) (which provisions Python automatically), installs `wbox`, prompts for your Wealthbox API token, and offers to install the AI agent skill.
+
+Already have Python? You can install directly:
+
 ```bash
 pip install wealthbox-cli
 wbox config set-token        # paste your Wealthbox API token (masked)
@@ -136,21 +147,51 @@ The skill translates your intent into the correct `wbox` commands, handles flag
 
 ### Install
 
-One command, same on every OS:
+Two ways depending on which agent you use:
+
+#### Option A — Claude Code plugin marketplace (recommended for Claude Code users)
+
+Inside Claude Code:
+
+```
+/plugin marketplace add massive-value/wealthbox-cli
+/plugin install wealthbox-crm@massive-value
+```
+
+The plugin auto-updates daily. The skill is installed under `~/.claude/plugins/cache/`. Firm data is stored at the canonical machine-level path (`~/.config/wbox/firm/` or `%APPDATA%\wbox\firm\`) — see [Where firm data lives](#where-firm-data-lives) below — and survives plugin auto-updates.
+
+The `wbox` CLI is still required as the execution engine. The bundled SKILL.md tells the agent to install it via the Phase 1 bootstrap if missing.
+
+#### Option B — `wbox skills install` (Claude Code, Codex, or local project scope)
 
 ```bash
 pip install wealthbox-cli
 wbox config set-token        # paste your Wealthbox API token
-wbox skills install          # interactive: pick Claude Code, Codex, or both
+wbox skills install          # interactive: pick Claude Code (user/project), Codex, or all
 ```
 
 The installer asks which platforms to target, copies the skill into the right directory (`~/.claude/skills/` for Claude Code, `~/.codex/skills/` for Codex — both use `SKILL.md`), and offers to bootstrap your firm's customizations from the Wealthbox API.
 
+#### Option C — Codex marketplace (when the openai/skills PR lands)
+
+Pending submission to [openai/skills](https://github.com/openai/skills) (status tracked in CHANGELOG). Until then, use Option B for Codex.
+
 > **Upgrading from < 1.1.6?** Earlier versions installed the codex skill as `AGENTS.md`. That was wrong — codex uses `SKILL.md` for skills (and `AGENTS.md` only as the project-level instructions file, in place of `CLAUDE.md`). If your codex install still has `AGENTS.md`, reinstall with `wbox skills install --platform codex --force`.
 
 ### First agent run captures firm conventions
 
-`wbox skills bootstrap` populates the API-derived files (categories, custom fields, users) — that's the *quantitative* half. The *qualitative* half (firm defaults, naming conventions, named workflows, required fields) happens the first time an agent invokes the skill: it walks you through the questions in `bootstrap.md` and stamps `firm.onboarded_at` in `_meta.json` when done. On subsequent runs the bootstrap path is skipped automatically.
+`wbox skills bootstrap` populates the API-derived files (categories, custom fields, users) — that's the *quantitative* half. The *qualitative* half (firm defaults, naming conventions, named workflows, required fields) happens the first time an agent invokes the skill: it walks you through the questions in `bootstrap.md` and stamps `onboarded_at` in the canonical firm `_meta.json` when done. On subsequent runs the bootstrap path is skipped automatically.
+
+### Where firm data lives
+
+Firm data is stored at one canonical machine-level path — **not** inside each skill install. This way it survives plugin auto-updates, skill template upgrades, and works the same across Claude Code, Codex, or any other host:
+
+| Platform | Firm data path |
+|----------|----------------|
+| macOS / Linux | `~/.config/wbox/firm/` |
+| Windows | `%APPDATA%\wbox\firm\` |
+
+Run `wbox skills firm-path` to print the resolved path. The bundled SKILL.md tells the agent to call this command and read firm files from that directory.
 
 ### Refresh after firm changes
 
@@ -160,22 +201,20 @@ If your firm adds or renames category values, custom fields, or users:
 wbox skills refresh
 ```
 
-This updates the generated half of the skill's firm files; hand-edited policy is preserved.
+This updates the generated half (categories, custom-fields, users); hand-edited policy is preserved.
 
 ### Other commands
 
 ```bash
-wbox skills list             # show where the skill is installed + last bootstrap time
-wbox skills doctor           # diagnose install state + token
-wbox skills sync             # copy firm/ from one install to others (Claude Code <-> Codex)
-wbox skills upgrade          # refresh template files (SKILL.md, references/, ...) preserving firm/
-wbox skills mark-onboarded   # stamp firm.onboarded_at after qualitative Q&A (the agent calls this for you)
-wbox skills uninstall        # remove the skill
+wbox skills list             # show install state per platform + canonical firm path
+wbox skills doctor           # diagnose install state + token + firm state
+wbox skills firm-path        # print canonical firm directory (for the agent)
+wbox skills upgrade          # refresh template files in every install; firm data is unaffected
+wbox skills mark-onboarded   # stamp onboarded_at in firm meta (the agent calls this for you)
+wbox skills uninstall        # remove the skill template; firm data is preserved
 ```
 
-When the CLI ships a newer template (improved SKILL.md, new reference docs, etc.), `wbox skills upgrade` re-copies the bundled template into every installed platform without touching your firm-specific data in `firm/`. Each install records the template's CLI version in `_meta.json`, so the agent can detect drift and prompt you to upgrade when needed.
-
-`wbox skills sync` is useful if you maintain firm conventions in one platform's install (e.g., your Claude Code user scope) and want the same `firm/` files mirrored to Codex or to a project-scoped `.claude/skills/` folder. The command runs as a wizard by default; pass `--source`, `--target`, and `--yes` for non-interactive use.
+When the CLI ships a newer template (improved SKILL.md, new reference docs, etc.), `wbox skills upgrade` re-copies the bundled template into every installed platform. Firm data lives outside the skill dir, so it's untouched. Each install records the template's CLI version in its own `_meta.json`, so the agent can detect drift and prompt you to upgrade when needed.
 
 ### Works with other agents too
 

{wealthbox_cli-1.1.6 → wealthbox_cli-1.2.0}/README.md

@@ -29,6 +29,17 @@
 
 ## Quick Start
 
+**No Python? No problem.** One-line installer (works on a fresh machine):
+
+| Platform | Command |
+|----------|---------|
+| macOS / Linux | `curl -LsSf https://raw.githubusercontent.com/massive-value/wealthbox-cli/main/scripts/install.sh \| bash` |
+| Windows (PowerShell) | `irm https://raw.githubusercontent.com/massive-value/wealthbox-cli/main/scripts/install.ps1 \| iex` |
+
+The installer pulls in [uv](https://github.com/astral-sh/uv) (which provisions Python automatically), installs `wbox`, prompts for your Wealthbox API token, and offers to install the AI agent skill.
+
+Already have Python? You can install directly:
+
 ```bash
 pip install wealthbox-cli
 wbox config set-token        # paste your Wealthbox API token (masked)
@@ -95,21 +106,51 @@ The skill translates your intent into the correct `wbox` commands, handles flag
 
 ### Install
 
-One command, same on every OS:
+Two ways depending on which agent you use:
+
+#### Option A — Claude Code plugin marketplace (recommended for Claude Code users)
+
+Inside Claude Code:
+
+```
+/plugin marketplace add massive-value/wealthbox-cli
+/plugin install wealthbox-crm@massive-value
+```
+
+The plugin auto-updates daily. The skill is installed under `~/.claude/plugins/cache/`. Firm data is stored at the canonical machine-level path (`~/.config/wbox/firm/` or `%APPDATA%\wbox\firm\`) — see [Where firm data lives](#where-firm-data-lives) below — and survives plugin auto-updates.
+
+The `wbox` CLI is still required as the execution engine. The bundled SKILL.md tells the agent to install it via the Phase 1 bootstrap if missing.
+
+#### Option B — `wbox skills install` (Claude Code, Codex, or local project scope)
 
 ```bash
 pip install wealthbox-cli
 wbox config set-token        # paste your Wealthbox API token
-wbox skills install          # interactive: pick Claude Code, Codex, or both
+wbox skills install          # interactive: pick Claude Code (user/project), Codex, or all
 ```
 
 The installer asks which platforms to target, copies the skill into the right directory (`~/.claude/skills/` for Claude Code, `~/.codex/skills/` for Codex — both use `SKILL.md`), and offers to bootstrap your firm's customizations from the Wealthbox API.
 
+#### Option C — Codex marketplace (when the openai/skills PR lands)
+
+Pending submission to [openai/skills](https://github.com/openai/skills) (status tracked in CHANGELOG). Until then, use Option B for Codex.
+
 > **Upgrading from < 1.1.6?** Earlier versions installed the codex skill as `AGENTS.md`. That was wrong — codex uses `SKILL.md` for skills (and `AGENTS.md` only as the project-level instructions file, in place of `CLAUDE.md`). If your codex install still has `AGENTS.md`, reinstall with `wbox skills install --platform codex --force`.
 
 ### First agent run captures firm conventions
 
-`wbox skills bootstrap` populates the API-derived files (categories, custom fields, users) — that's the *quantitative* half. The *qualitative* half (firm defaults, naming conventions, named workflows, required fields) happens the first time an agent invokes the skill: it walks you through the questions in `bootstrap.md` and stamps `firm.onboarded_at` in `_meta.json` when done. On subsequent runs the bootstrap path is skipped automatically.
+`wbox skills bootstrap` populates the API-derived files (categories, custom fields, users) — that's the *quantitative* half. The *qualitative* half (firm defaults, naming conventions, named workflows, required fields) happens the first time an agent invokes the skill: it walks you through the questions in `bootstrap.md` and stamps `onboarded_at` in the canonical firm `_meta.json` when done. On subsequent runs the bootstrap path is skipped automatically.
+
+### Where firm data lives
+
+Firm data is stored at one canonical machine-level path — **not** inside each skill install. This way it survives plugin auto-updates, skill template upgrades, and works the same across Claude Code, Codex, or any other host:
+
+| Platform | Firm data path |
+|----------|----------------|
+| macOS / Linux | `~/.config/wbox/firm/` |
+| Windows | `%APPDATA%\wbox\firm\` |
+
+Run `wbox skills firm-path` to print the resolved path. The bundled SKILL.md tells the agent to call this command and read firm files from that directory.
 
 ### Refresh after firm changes
 
@@ -119,22 +160,20 @@ If your firm adds or renames category values, custom fields, or users:
 wbox skills refresh
 ```
 
-This updates the generated half of the skill's firm files; hand-edited policy is preserved.
+This updates the generated half (categories, custom-fields, users); hand-edited policy is preserved.
 
 ### Other commands
 
 ```bash
-wbox skills list             # show where the skill is installed + last bootstrap time
-wbox skills doctor           # diagnose install state + token
-wbox skills sync             # copy firm/ from one install to others (Claude Code <-> Codex)
-wbox skills upgrade          # refresh template files (SKILL.md, references/, ...) preserving firm/
-wbox skills mark-onboarded   # stamp firm.onboarded_at after qualitative Q&A (the agent calls this for you)
-wbox skills uninstall        # remove the skill
+wbox skills list             # show install state per platform + canonical firm path
+wbox skills doctor           # diagnose install state + token + firm state
+wbox skills firm-path        # print canonical firm directory (for the agent)
+wbox skills upgrade          # refresh template files in every install; firm data is unaffected
+wbox skills mark-onboarded   # stamp onboarded_at in firm meta (the agent calls this for you)
+wbox skills uninstall        # remove the skill template; firm data is preserved
 ```
 
-When the CLI ships a newer template (improved SKILL.md, new reference docs, etc.), `wbox skills upgrade` re-copies the bundled template into every installed platform without touching your firm-specific data in `firm/`. Each install records the template's CLI version in `_meta.json`, so the agent can detect drift and prompt you to upgrade when needed.
-
-`wbox skills sync` is useful if you maintain firm conventions in one platform's install (e.g., your Claude Code user scope) and want the same `firm/` files mirrored to Codex or to a project-scoped `.claude/skills/` folder. The command runs as a wizard by default; pass `--source`, `--target`, and `--yes` for non-interactive use.
+When the CLI ships a newer template (improved SKILL.md, new reference docs, etc.), `wbox skills upgrade` re-copies the bundled template into every installed platform. Firm data lives outside the skill dir, so it's untouched. Each install records the template's CLI version in its own `_meta.json`, so the agent can detect drift and prompt you to upgrade when needed.
 
 ### Works with other agents too
 

{wealthbox_cli-1.1.6/src/wealthbox_tools/skills → wealthbox_cli-1.2.0/codex-skill}/wealthbox-crm/SKILL.md

@@ -8,22 +8,34 @@ description: Use when the user wants to interact with Wealthbox CRM — creating
 Execute Wealthbox CRM operations via the `wbox` CLI. Supports contacts, tasks, notes, events,
 opportunities, projects, workflows, households, and read-only lookups (categories, users, activity, me).
 
+## Firm Configuration Path
+
+Firm-specific data (categories, custom-fields, users, hand-edited
+policy, identity, onboarded marker) lives at one canonical path per
+machine — **not** inside this skill's directory. Run:
+
+```bash
+wbox skills firm-path
+```
+
+to print the directory. Cache the result for the rest of the session.
+All references to `<firm>/<file>` below mean files inside that directory.
+
 ## First Run
 
-If `_meta.json.firm.onboarded_at` is missing in this skill's directory,
-the firm has not been onboarded yet on this machine. Before handling the
-user's request:
+If `<firm>/_meta.json` is missing, or it exists but has no
+`onboarded_at` key, the firm has not been onboarded yet on this machine.
+Before handling the user's request:
 
 1. Read `bootstrap.md` in this skill's directory.
 2. Follow it end-to-end.
-3. The final step writes `_meta.json.firm.onboarded_at`, which makes
+3. The final step writes `<firm>/_meta.json.onboarded_at`, which makes
    this check pass on subsequent runs.
 
-`firm.onboarded_at` is the qualitative-onboarding marker. The CLI
-bootstrap (`wbox skills bootstrap`) only populates the API-derived
-parts of `firm` (identity, generated files); it intentionally does
-*not* set `onboarded_at`, because that requires the per-firm Q&A in
-`bootstrap.md`.
+`onboarded_at` is the qualitative-onboarding marker. The CLI bootstrap
+(`wbox skills bootstrap`) only populates the API-derived parts of firm
+data (identity, generated files); it intentionally does *not* set
+`onboarded_at`, because that requires the per-firm Q&A in `bootstrap.md`.
 
 ## Staleness Check
 
@@ -45,7 +57,13 @@ across every installed platform while preserving `firm/`.
 
 ## Prerequisites
 
-- `wbox` CLI installed (`pip install wealthbox-cli`)
+- `wbox` CLI installed. If `wbox --version` fails, run the bootstrap installer:
+  ```bash
+  # macOS / Linux
+  curl -LsSf https://raw.githubusercontent.com/massive-value/wealthbox-cli/main/scripts/install.sh | bash
+  # Windows (PowerShell)
+  irm https://raw.githubusercontent.com/massive-value/wealthbox-cli/main/scripts/install.ps1 | iex
+  ```
 - Token configured via one of: `wbox config set-token`, `WEALTHBOX_TOKEN` env var, or `.env` file
 
 Verify with: `wbox me`
@@ -75,15 +93,15 @@ Verify with: `wbox me`
 
 1. **Parse intent** — identify which resource(s) and action(s) the user needs
 2. **Load reference** — read ONLY the relevant `references/<resource>.md` file(s) from this skill's directory
-3. **Check firm config** — read `firm/<resource>.md` for the resource(s) you're touching. Also read `firm/categories.md` and `firm/custom-fields.md` when you need valid values for category-constrained flags (avoid repeat API probes).
+3. **Check firm config** — read `<firm>/<resource>.md` for the resource(s) you're touching (where `<firm>` is the path returned by `wbox skills firm-path`). Also read `<firm>/categories.md` and `<firm>/custom-fields.md` when you need valid values for category-constrained flags (avoid repeat API probes).
 4. **Fill gaps** — if required information is missing, ask the user. Prefer multiple-choice when options are known (e.g., contact type, priority level). If the user is unfamiliar with Wealthbox, explain what the field means.
 5. **Execute** — run the `wbox` command(s) via Bash
 6. **Report** — show the result. For create/update, confirm what was created with the record ID.
 
 ## Multi-Step Workflows
 
-When `firm/workflows.md` defines named workflows (e.g., "onboarding", "meeting followup"):
-1. Read the workflow definition from `firm/workflows.md`
+When `<firm>/workflows.md` defines named workflows (e.g., "onboarding", "meeting followup"):
+1. Read the workflow definition from `<firm>/workflows.md`
 2. Load all referenced resource reference files
 3. Walk through each step, gathering input as needed
 4. Execute commands in sequence, passing IDs forward (e.g., new contact ID → linked note/task)

wealthbox_cli-1.2.0/codex-skill/wealthbox-crm/bootstrap.md

@@ -0,0 +1,127 @@
+# First-Run Bootstrap
+
+You were told to read this because `<firm>/_meta.json.onboarded_at` is missing
+on this machine — where `<firm>` is the canonical firm directory printed by
+`wbox skills firm-path`. Follow every step below, then run the marker command
+in Step 4 so this bootstrap path is skipped on future invocations.
+
+## Step 1 — Fetch API-derived firm data
+
+First, find the firm directory:
+
+```bash
+wbox skills firm-path
+```
+
+Cache that path. If `<firm>/_meta.json` already exists with an `identity` and
+`files` map, the CLI bootstrap has already run on this machine and you can
+skip to Step 2. Otherwise, run:
+
+```bash
+wbox skills bootstrap
+```
+
+It populates these files at the canonical firm path (machine-level — survives
+plugin auto-updates and skill template upgrades):
+
+- `<firm>/categories.md` — every category type + valid values (paginated; complete)
+- `<firm>/custom-fields.md` — custom fields per document type + valid values (paginated; complete)
+- `<firm>/users.md` — user id -> name -> email (paginated; complete)
+- `<firm>/_meta.json` — firm identity, refresh timestamps, and the CLI version
+  that ran the bootstrap. Does **not** set `onboarded_at` — that's Step 4.
+- Stub files: `<firm>/contacts.md`, `<firm>/tasks.md`, `<firm>/notes.md`,
+  `<firm>/events.md`, `<firm>/opportunities.md`, `<firm>/projects.md`,
+  `<firm>/workflows.md` — one-line TODOs you will fill in next.
+
+Verify `<firm>/_meta.json` now exists with an `identity` key before continuing.
+
+## Step 2 — Gather firm policy (per-resource)
+
+For each hand-edited stub below, open `firm-examples/<resource>.md` (alongside
+this `bootstrap.md` in the skill directory) to see a filled-in example, then
+ask the advisor the listed questions. Record answers in
+`<firm>/<resource>.md`, replacing the stub TODO.
+
+Read `<firm>/categories.md` and `<firm>/custom-fields.md` first so every
+multiple-choice prompt offers **real** values from the firm's workspace.
+If the advisor mentions a tag, custom-field option, or user that you can't
+find in those files, flag it — they're generated from a paginated fetch and
+*should* be complete. A missing entry usually means the value doesn't exist
+in the workspace yet (rather than a pagination gap).
+
+### `<firm>/contacts.md`
+
+- Default contact type for new people? (pick from `<firm>/categories.md` ->
+  contact_types)
+- Default contact source? (contact_sources)
+- Default assigned-to user? (pick from `<firm>/users.md`)
+- Preferred email type? (email_types)
+- Preferred phone type? (phone_types)
+- Household naming convention? (e.g. `"The {LastName} Family"`)
+- When should a household be created automatically? (e.g. married couple)
+- Required fields for person / household / org / trust?
+
+### `<firm>/tasks.md`
+
+- Default priority when unspecified?
+- Default assigned-to rule? (e.g. same as linked contact)
+- Default due-date frame? (today / this-week / next-week / this-month)
+- Named task templates the firm reuses? (e.g. "Welcome call", "Collect
+  documents") — include name, priority, frame, description for each.
+
+### `<firm>/notes.md`
+
+- Prefix or format convention for meeting notes?
+- Are notes always linked to a contact (never orphan)?
+
+### `<firm>/events.md`
+
+- Default state? (confirmed, tentative)
+- Default meeting duration?
+- Event naming convention?
+
+### `<firm>/opportunities.md`
+
+- Default pipeline? (from opportunity_pipelines)
+- Default stage for new prospects? (from opportunity_stages)
+- Default probability?
+- Required fields on create?
+
+### `<firm>/projects.md`
+
+- Any standard project templates?
+- Conventions for linking projects to contacts?
+
+### `<firm>/workflows.md`
+
+- Workflow templates the firm uses, with template IDs.
+- Named multi-step workflows. Common ones:
+  - **Onboarding**: contact -> household -> intake note -> tasks -> opportunity -> workflow
+  - **Meeting followup**: note -> action-item tasks -> (optional) opportunity update
+  - **Annual review**: event -> workflow -> note
+
+## Step 3 — Catch-all
+
+Ask the advisor: "Is there any firm convention, custom process, or preference
+I haven't asked about that I should follow?" Append freeform answers to
+`<firm>/workflows.md` under a `## Other Conventions` heading.
+
+## Step 4 — Mark the firm onboarded
+
+Run:
+
+```bash
+wbox skills mark-onboarded
+```
+
+This stamps `onboarded_at` in `<firm>/_meta.json`. The First Run check in
+`SKILL.md` keys off this field, so future invocations will skip the
+bootstrap path automatically.
+
+## Step 5 — Confirm and continue
+
+Tell the advisor: "First-run setup complete — firm data populated for <firm
+name>." Then return to the user's original request.
+
+You don't need to delete this file or trim `SKILL.md`. The first-run check
+keys on `<firm>/_meta.json.onboarded_at`, which now exists.

{wealthbox_cli-1.1.6 → wealthbox_cli-1.2.0}/docs/changelog.md

@@ -6,6 +6,31 @@ This project uses [Semantic Versioning](https://semver.org/).
 
 ---
 
+## [1.2.0](https://github.com/massive-value/wealthbox-cli/releases/tag/v1.2.0) — 2026-05-02
+
+### Changed
+
+- **Firm data hoisted to a canonical machine-level path.** `firm/` and the firm metadata (`identity`, `files` timestamps, `onboarded_at`) now live at `~/.config/wbox/firm/` (macOS/Linux) or `%APPDATA%\wbox\firm\` (Windows) — one source of truth per machine. Previously each skill install had its own `firm/` and embedded the firm section in `<skill_dir>/_meta.json`. The new layout survives plugin auto-updates, skill template upgrades, and reinstalls without risking the firm bootstrap state being wiped, and removes the duplication problem when the same skill is installed via multiple paths (Claude Code marketplace + manual install + Codex). Per-install `_meta.json` is retained for the per-install `template.cli_version` field.
+- `SKILL.md` now instructs the agent to run `wbox skills firm-path` to find the firm directory, then read `<firm>/<resource>.md` files from there. `bootstrap.md` updated to match.
+
+### Added
+
+- `wbox skills firm-path` — prints the canonical firm directory. Used by the agent to locate firm data, and useful for ad-hoc inspection.
+- Automatic migration: any command that reads firm state (`bootstrap`, `refresh`, `doctor`, `list`, `mark-onboarded`, `firm-path`) detects legacy `<skill_dir>/firm/` and `<skill_dir>/_meta.json.firm` data on first run and moves it to the canonical path. If multiple installs have legacy data, the one with the most recent `onboarded_at` (or generated-files timestamp) wins.
+- **Claude Code plugin marketplace.** `.claude-plugin/marketplace.json` at the repo root, plus a self-contained plugin at `plugins/wealthbox-crm/` with `.claude-plugin/plugin.json`. Users can now install with `/plugin marketplace add massive-value/wealthbox-cli` then `/plugin install wealthbox-crm@massive-value` directly inside Claude Code. The custom marketplace works immediately; an Anthropic official-marketplace submission is in flight.
+- **Codex plugin manifest** at `.codex-plugin/plugin.json` plus a `codex-skill/` mirror of the skill template, ready for the openai/skills PR and a future Codex marketplace listing once self-serve publishing opens.
+- `scripts/sync-plugin.py` — keeps the plugin and codex copies in sync with the canonical skill template at `src/wealthbox_tools/skills/wealthbox-crm/`. Run before committing skill template changes.
+
+### Removed
+
+- `wbox skills sync` is gone. Firm data is now machine-level, so there's nothing to sync between platform installs.
+
+### Deprecated
+
+- `--platform` flag on `bootstrap`, `refresh`, and `mark-onboarded` is accepted but ignored, with a warning. Firm operations are no longer scoped per platform.
+
+---
+
 ## [1.1.6](https://github.com/massive-value/wealthbox-cli/releases/tag/v1.1.6) — 2026-05-01
 
 ### Fixed

{wealthbox_cli-1.1.6 → wealthbox_cli-1.2.0}/docs/getting-started.md

@@ -6,7 +6,23 @@ This guide walks you through installing **wealthbox-cli** and configuring it to
 
 ## Installation
 
-### From PyPI (recommended)
+### One-line installer (no Python required)
+
+If you don't have Python installed, the bootstrap script handles everything: it installs [uv](https://github.com/astral-sh/uv) (which provisions Python automatically), installs `wbox`, prompts for your API token, and offers to install the AI agent skill.
+
+=== "macOS / Linux"
+
+    ```bash
+    curl -LsSf https://raw.githubusercontent.com/massive-value/wealthbox-cli/main/scripts/install.sh | bash
+    ```
+
+=== "Windows (PowerShell)"
+
+    ```powershell
+    irm https://raw.githubusercontent.com/massive-value/wealthbox-cli/main/scripts/install.ps1 | iex
+    ```
+
+### From PyPI (recommended for Python users)
 
 ```bash
 pip install wealthbox-cli

wealthbox_cli-1.2.0/plugins/wealthbox-crm/.claude-plugin/plugin.json

@@ -0,0 +1,17 @@
+{
+  "name": "wealthbox-crm",
+  "description": "Wealthbox CRM agent skill — drive contacts, tasks, notes, events, and households via natural language. Bundles SKILL.md, references, and firm-bootstrap workflow. Requires the `wbox` CLI (auto-install instructions in SKILL.md).",
+  "version": "1.2.0",
+  "author": {
+    "name": "Kadin Bullock"
+  },
+  "homepage": "https://github.com/massive-value/wealthbox-cli",
+  "repository": "https://github.com/massive-value/wealthbox-cli",
+  "license": "Apache-2.0",
+  "keywords": [
+    "wealthbox",
+    "crm",
+    "financial-advisor",
+    "wealth-management"
+  ]
+}