makea-cli 0.1.24__tar.gz → 0.2.1__tar.gz

{makea_cli-0.1.24 → makea_cli-0.2.1}/.claude/skills/create-supplier-profile/SKILL.md

@@ -3,8 +3,8 @@ name: create-supplier-profile
 description: >-
   Create a new Makea supplier profile from scratch (admin), the schema-driven way:
   first fetch the live supplier profile schema (the field taxonomy) with
-  `makea-cli get-supplier-profile-schema`, then build a valid v2 payload against
-  it, then upload with `makea-cli add-supplier`. Use this whenever you need to
+  `makea-cli admin get supplier-profile-schema`, then build a valid v2 payload against
+  it, then upload with `makea-cli admin create supplier`. Use this whenever you need to
   onboard / register / create a supplier, turn raw supplier info (a website, a
   brochure, an email, a few notes) into a structured profile, or are asked to
   "add a supplier", "create a supplier profile", "onboard [company]". The AI does
@@ -27,7 +27,7 @@ Flow: **fetch schema → build payload → upload.**
 
 ## Step 0 — Auth & CLI setup
 
-You need a working, authenticated `makea-cli`. If `makea-cli list-suppliers`
+You need a working, authenticated `makea-cli`. If `makea-cli admin list supplier`
 returns JSON, you're good. If it prints `尚未登录` / "not logged in" or
 `command not found`, run the **`makea-cli-setup`** skill first (install + token
 refresh + login).
@@ -35,7 +35,7 @@ refresh + login).
 Quick smoke-test:
 
 ```bash
-makea-cli list-suppliers 2>&1 | head -3
+makea-cli admin list supplier 2>&1 | head -3
 ```
 
 ---
@@ -43,7 +43,7 @@ makea-cli list-suppliers 2>&1 | head -3
 ## Step 1 — Fetch the schema (taxonomy)
 
 ```bash
-makea-cli get-supplier-profile-schema
+makea-cli admin get supplier-profile-schema
 ```
 
 Returns `{success, schema}`. The `schema` object you care about:
@@ -122,7 +122,7 @@ is for. Confirm anything ambiguous with the user before uploading.
 ## Step 3 — Upload
 
 ```bash
-makea-cli add-supplier --file supplier.json
+makea-cli admin create supplier --file supplier.json
 ```
 
 The file root may be the flat supplier object (recommended) or the full envelope
@@ -140,7 +140,7 @@ schema (Step 2), and re-run. Common codes: `required_missing`,
 ## Step 4 — Verify
 
 ```bash
-makea-cli list-suppliers | python3 -c "
+makea-cli admin list supplier | python3 -c "
 import json, sys
 data = json.load(sys.stdin)
 search = 'acme'  # lowercase fragment of the company name
@@ -164,4 +164,4 @@ user.
 - **`supplier_id` is auto-generated** when omitted. Provide one only if you need
   it to equal a Cognito sub up front (usually you don't — link later).
 - **Documents** (catalogue, images, business_license, …) are uploaded separately
-  with `makea-cli upload-supplier-document` after the profile exists.
+  with `makea-cli admin upload supplier-document` after the profile exists.

{makea_cli-0.1.24 → makea_cli-0.2.1}/.claude/skills/link-supplier-user/SKILL.md

@@ -70,7 +70,7 @@ export PATH="$PATH:/sessions/modest-brave-newton/.local/bin"
 Quick smoke-test:
 
 ```bash
-makea-cli list-suppliers 2>&1 | head -3
+makea-cli admin list supplier 2>&1 | head -3
 ```
 
 If you see JSON, you're authenticated. If you see "尚未登录", the token is still broken.
@@ -110,7 +110,7 @@ Confirm with the user if there are multiple matches. The right one is typically
 
 ```bash
 export PATH="$PATH:/sessions/modest-brave-newton/.local/bin"
-makea-cli list-suppliers | python3 -c "
+makea-cli admin list supplier | python3 -c "
 import json, sys
 data = json.load(sys.stdin)
 suppliers = data.get('result', [])
@@ -133,7 +133,7 @@ equal to the newly registered user, and one with `null` — the one with `null`
 Always preview before writing anything:
 
 ```bash
-makea-cli backfill-supplier-id \
+makea-cli admin backfill supplier-id \
   --user-id "<cognito_sub / new user_id>" \
   --old-supplier-id "<old profile UUID>" \
   --dry-run
@@ -155,7 +155,7 @@ with the user before proceeding.
 ## Step 5 — Apply
 
 ```bash
-makea-cli backfill-supplier-id \
+makea-cli admin backfill supplier-id \
   --user-id "<cognito_sub>" \
   --old-supplier-id "<old_supplier_id>" \
   --apply
@@ -176,7 +176,7 @@ Only do this if the user explicitly asks. The old `SUPPLIER#{old_id}` partition
 marked `is_migrated` but still present. To remove it permanently:
 
 ```bash
-makea-cli backfill-supplier-id \
+makea-cli admin backfill supplier-id \
   --user-id "<cognito_sub>" \
   --old-supplier-id "<old_supplier_id>" \
   --apply \
@@ -194,8 +194,8 @@ After linking, verify by pulling all quote requests and supplier links for the n
 
 ```bash
 export PATH="$PATH:/sessions/modest-brave-newton/.local/bin"
-makea-cli get-quote-requests-by-supplier-id "<cognito_sub>"
-makea-cli get-supplier-links-by-supplier-id "<cognito_sub>"
+makea-cli admin list quote-request --supplier "<cognito_sub>"
+makea-cli admin list supplier-link "<cognito_sub>"
 ```
 
 Present the results as a clean table per product: link name, sampling price, production
@@ -213,7 +213,7 @@ price tiers (with currency), lead times.
 | Thing                            | Where to find it                                                                    |
 | -------------------------------- | ----------------------------------------------------------------------------------- |
 | Supplier `user_id` (Cognito sub) | `/admin/users` search by name/email                                                 |
-| Old `supplier_id`                | `makea-cli list-suppliers` — look for `supplier_user_id: null`                      |
+| Old `supplier_id`                | `makea-cli admin list supplier` — look for `supplier_user_id: null`                      |
 | Credentials path                 | `/sessions/modest-brave-newton/mnt/Application Support--makea-cli/credentials.json` |
 
 

{makea_cli-0.1.24 → makea_cli-0.2.1}/.claude/skills/makea-cli-setup/SKILL.md

@@ -35,7 +35,7 @@ makea-cli version 2>&1 | head -1 || echo "NOT_INSTALLED"
 If that prints a version, test auth with a low-cost call:
 
 ```bash
-makea-cli list-suppliers 2>&1 | head -c 200
+makea-cli admin list supplier 2>&1 | head -c 200
 ```
 
 - JSON output → **already set up, you're done.** Skip to "Confirm & report".
@@ -110,7 +110,7 @@ Connecting to a **non-production** environment? Set these before `makea-cli auth
 Re-run the smoke-test from Step 0:
 
 ```bash
-makea-cli list-suppliers 2>&1 | head -c 200
+makea-cli admin list supplier 2>&1 | head -c 200
 ```
 
 JSON back → tell the user **"✓ makea-cli is installed and logged in."** and
@@ -132,6 +132,6 @@ Step 2 and confirm the browser flow completed.
 | Logout | `makea-cli auth --logout` |
 
 The credentials JSON holds `id_token`, `refresh_token`, `expires_in`,
-`saved_at`. Run `makea-cli --help` for the full command list (list-users,
-list-suppliers, list-product-orders, create-quote-request, download-document,
-upload-*-document, backfill-supplier-id, …).
+`saved_at`. Run `makea-cli --help` for the full command list (admin list user,
+admin list supplier, admin list product-order, admin create quote-request, admin download document,
+upload-*-document, admin backfill supplier-id, …).

{makea_cli-0.1.24 → makea_cli-0.2.1}/.claude/skills/payment-revenue-report/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: payment-revenue-report
-description: Report payment received and platform revenue (service fee + transaction fee) across a date range. Use when the user asks about platform totals, or wants a drill-down by user / product / product category. Backed by the makea-cli `get-cumulative-payment-and-platform-revenue` command and existing order-listing commands.
+description: Report payment received and platform revenue (service fee + transaction fee) across a date range. Use when the user asks about platform totals, or wants a drill-down by user / product / product category. Backed by the makea-cli `admin get revenue-metrics` command and existing order-listing commands.
 ---
 
 # Payment & platform revenue report
@@ -18,7 +18,7 @@ the question the user is asking:
 
 | Mode | When | How |
 | --- | --- | --- |
-| **A. Platform totals** | User wants the whole-platform aggregate over a time range. | One direct admin API call: `makea-cli get-cumulative-payment-and-platform-revenue`. |
+| **A. Platform totals** | User wants the whole-platform aggregate over a time range. | One direct admin API call: `makea-cli admin get revenue-metrics`. |
 | **B. Per-user / per-product / per-category drill-down** | User wants revenue attributed to a specific designer, product, or category. | The admin cumulative endpoint does **not** support these filters. Fetch the relevant orders with the existing list commands and aggregate the fees client-side. |
 
 Always confirm which mode is needed before running anything. If the user is
@@ -72,7 +72,7 @@ boundary mistakes.
 ### 2. Run the command
 
 ```bash
-makea-cli get-cumulative-payment-and-platform-revenue \
+makea-cli admin get revenue-metrics \
   --start-date 2026-01-01 \
   --end-date   2026-03-31 \
   --granularity month \
@@ -146,15 +146,15 @@ Choose the entry point based on what you are drilling into:
 1. List the designer's product orders:
 
    ```bash
-   makea-cli list-product-orders --user-id <user_id>
+   makea-cli admin list product-order --user-id <user_id>
    ```
 
 2. For each product order's `product_reference_id`, pull the sampling and
    production orders:
 
    ```bash
-   makea-cli list-sampling-orders-by-product   <product_reference_id>
-   makea-cli list-production-orders-by-product <product_reference_id>
+   makea-cli admin list sampling-order --product   <product_reference_id>
+   makea-cli admin list production-order --product <product_reference_id>
    ```
 
 3. Filter the returned orders to those whose **payment timestamp** falls in
@@ -172,8 +172,8 @@ Choose the entry point based on what you are drilling into:
 
 ### By product
 
-Skip step 1 and go straight to `list-sampling-orders-by-product` /
-`list-production-orders-by-product` with the known `product_reference_id`.
+Skip step 1 and go straight to `admin list sampling-order --product` /
+`admin list production-order --product` with the known `product_reference_id`.
 
 ### By product category
 
@@ -194,8 +194,8 @@ There is no admin list-products-by-category CLI command today. Do this:
 - **Transaction fee is hard-coded at 2.8%.** If that constant changes in
   `FeeCalculationHelper.py` it will silently diverge from this skill. Keep
   the magic number centralized in one place in any scratch script you write.
-- **Pagination.** `list-product-orders`, `list-all-sampling-orders`, and
-  `list-all-production-orders` page with `--limit` / `--offset`. For a time
+- **Pagination.** `admin list product-order`, `admin list sampling-order`, and
+  `admin list production-order` page with `--limit` / `--offset`. For a time
   window that could contain many orders, loop until `has_more` / the returned
   page is empty before aggregating — do not silently truncate.
 - **Timezones.** Date ranges are interpreted by the server as calendar dates.
@@ -214,12 +214,12 @@ There is no admin list-products-by-category CLI command today. Do this:
 
 ## Related commands already in the CLI
 
-- `list-users` — find a user id to drill down on.
-- `list-product-orders --user-id <id>` — product (SKU) rows for one designer.
-- `list-all-sampling-orders` — global sampling order list.
-- `list-all-production-orders [--type PRODUCTION|RESTOCK]` — global 大货 list.
-- `list-sampling-orders-by-product <id>` — sampling orders for one product.
-- `list-production-orders-by-product <id>` — production orders for one product.
+- `admin list user` — find a user id to drill down on.
+- `admin list product-order --user-id <id>` — product (SKU) rows for one designer.
+- `admin list sampling-order` — global sampling order list.
+- `admin list production-order [--type PRODUCTION|RESTOCK]` — global 大货 list.
+- `admin list sampling-order --product <id>` — sampling orders for one product.
+- `admin list production-order --product <id>` — production orders for one product.
 
 ## Upstream reference
 

{makea_cli-0.1.24 → makea_cli-0.2.1}/.claude/skills/supplier-user-id-migration/SKILL.md

@@ -2,7 +2,7 @@
 name: supplier-user-id-migration
 description: >-
   Migrates supplier data when DynamoDB supplier_id does not match Cognito user sub.
-  Admins use makea-cli backfill-supplier-id (calls garmentby-service admin API).
+  Admins use makea-cli admin backfill supplier-id (calls garmentby-service admin API).
   Server-only modes (S3-only, delete-old-partition-only) and reconcile_quote_request_stage_status
   still run from garmentby-service with manage.py. Use when the user mentions supplier migration,
   wrong supplier_id, supplierReferenceId, backfill_supplier_id, quote request stage/status,
@@ -19,7 +19,7 @@ Production expects **`supplier_id` == Cognito `sub` (user_id)**. If a profile wa
 
 Requires an admin Makea account and existing `makea-cli` browser login (same as other admin commands).
 
-**CLI command:** `makea-cli backfill-supplier-id`
+**CLI command:** `makea-cli admin backfill supplier-id`
 
 It calls **`POST /admin/supplier/backfill_supplier_id_with_quote_requests`**, which wraps the same logic as `manage.py backfill_supplier_id` on the server (profile, Cognito, optional S3/DOCUMENT#, product links, link→quote-request backfill, orders, optional delete old partition at end).
 
@@ -27,25 +27,25 @@ It calls **`POST /admin/supplier/backfill_supplier_id_with_quote_requests`**, wh
 
 ```bash
 # Always dry-run first (default)
-makea-cli backfill-supplier-id \
+makea-cli admin backfill supplier-id \
   --user-id "<cognito_sub>" \
   --old-supplier-id "<wrong_supplier_uuid>"
 
 # Apply writes
-makea-cli backfill-supplier-id \
+makea-cli admin backfill supplier-id \
   --user-id "<cognito_sub>" \
   --old-supplier-id "<wrong_supplier_uuid>" \
   --apply
 
 # Full run but defer S3/documents (server will skip step 2b)
-makea-cli backfill-supplier-id \
+makea-cli admin backfill supplier-id \
   --user-id "<cognito_sub>" \
   --old-supplier-id "<wrong_supplier_uuid>" \
   --apply \
   --skip-s3-documents
 
 # Only link→quote-request backfill (profile/Cognito/links already fixed)
-makea-cli backfill-supplier-id \
+makea-cli admin backfill supplier-id \
   --user-id "<cognito_sub>" \
   --old-supplier-id "<wrong_supplier_uuid>" \
   --apply \

makea_cli-0.2.1/CHANGELOG.md

@@ -0,0 +1,144 @@
+# Changelog
+
+## 0.2.1
+
+Each persona can now clear its own queue. `list task` and `list action` could show
+you the work; nothing could close it.
+
+- **designer**: `list action`, `update task --complete|--dismiss`,
+  `update action --acknowledge|--snooze DAYS|--dismiss`,
+  `update note --accept|--reject` (a task the assistant proposed),
+  `update proposal --note N` (apply one proposed spec change),
+  `update suggested-action -a note:action` (accept several at once, one write).
+- **supplier**: `list task`, `list quote-edit-request`, `update task`, `update action`,
+  `update quote <rfq> <link> --file` (revise a quote already sent), and
+  `update rfq --status|--archive|--accept-terms` — a factory could submit a quote
+  but had no way to correct it or answer the invitation.
+
+Acknowledging an action does not close it: an action is closed by the fact it asks
+for. The help text says so, because the opposite assumption is easy to make and
+produces a dashboard that lies.
+
+## 0.2.0
+
+**The command names changed.** Every command is now `makea-cli <persona> <verb> <noun>`:
+the persona says who is acting (`admin` / `designer` / `supplier`), and the verb says whether
+the command reads or writes. The old flat names still work as hidden aliases that forward to
+the new command and print a deprecation line on stderr — **they are removed in the next minor
+release**, so move scripts and skills over now.
+
+Why: the CLI is becoming the action surface for Beeboo. An agent harness has to decide, from
+the command text alone and before running it, who is acting and whether this is a read or a
+write. A flat list of 58 names could not answer either question; `submit-supplier-quote` is an
+*admin* command acting *on behalf of* a supplier, and nothing in the name said so.
+
+### New in 0.2.0
+
+- **`--describe`** on any command prints its machine-readable definition (flags, backend path,
+  declared side effects, approval grade). `makea-cli --describe --json` prints the whole manifest.
+- **JSON by default when piped.** A terminal still gets pretty-printed output; a pipe gets one
+  plain JSON document. `--json` forces the plain form anywhere.
+- **`--fields a,b,c`** on reads keeps only those keys, on the payload or on each of its rows.
+- **`--limit N`** on every `list`. Where the backend pages, it is passed through; where it does
+  not, the rows are capped locally and the payload says how many were dropped (`truncated`,
+  `returned`, `omitted`). There is no default cap: several skills depend on reading a whole
+  table, and a silent default would make them quietly wrong. A response with no single list of
+  rows (several lists, no obvious one) is left alone and says so in `limit_note` rather than
+  pretending the flag applied.
+- **`--dry-run`** on every write prints the exact request (method, URL, body) and sends nothing.
+- **`--idempotency-key K`** on every write, sent as the `Idempotency-Key` header.
+- **Exit codes**: `0` ok, `2` usage, `3` not logged in or the login cannot act as this persona,
+  `4` the backend refused (4xx), `5` the call did not complete (5xx / network / timeout). A read
+  that exits 5 is simply retryable; a **write** that exits 5 may or may not have been applied, so
+  re-read state before retrying it. Writes are never retried automatically.
+- **Errors are JSON on stderr**, with the exit code inside.
+- **Secrets are redacted** from all output (JWTs, `Bearer …`, impersonation/delegation tokens).
+- **A persona pre-check**: a command whose persona your token cannot act as fails with exit 3
+  before any request. The backend remains the real boundary; this only saves a round trip.
+
+### New commands
+
+The `designer` and `supplier` personas are new. They mirror what the in-product assistant can
+already do, so the same operation is available from a terminal, a script and an agent:
+
+- **designer** (21 new): `create note`, `create rfq`, `create sampling-order`, `get collection`, `get lifecycle`, `get product`, `get quote-advice`, `get tech-pack`, `get tech-pack-history`, `list channel`, `list collection`, `list library-element`, `list payment`, `list product`, `list production-order`, `list sampling-order`, `list shipping-order`, `list supplier-link`, `list task`, `search note`, `update product`
+- **supplier** (12 new): `create note`, `download document`, `get pack`, `get pack-changes`, `get profile`, `get rfq`, `list action`, `list channel`, `list note`, `list production-order`, `list rfq`, `submit quote`
+- **admin** (2 new): `get quote-request`, `list quote-request`
+
+### Renamed
+
+| 0.1 | 0.2 |
+|---|---|
+| `add-supplier` | `admin create supplier` |
+| `analytics-active-users` | `admin get active-users` |
+| `analytics-feature-usage` | `admin get feature-usage` |
+| `analytics-query` | `admin get analytics-query` |
+| `analytics-top-clicks` | `admin get top-clicks` |
+| `analytics-top-features` | `admin get top-features` |
+| `backfill-supplier-id` | `admin backfill supplier-id` |
+| `convert-currency` | `admin get currency-conversion` |
+| `create-quote-request` | `admin create quote-request` |
+| `create-user` | `admin create user` |
+| `designer-create-collection` | `designer create collection` |
+| `designer-download-document` | `designer download document` |
+| `designer-link-product-to-collection` | `designer set product-collection` |
+| `designer-upload-document` | `designer upload document` |
+| `designer-upsert-product` | `designer create product` |
+| `download-document` | `admin download document` |
+| `download-product-document` | `admin download product-document` |
+| `extract-ai-tech-spec` | `admin get tech-spec-extraction` |
+| `get-cumulative-payment-and-platform-revenue` | `admin get revenue-metrics` |
+| `get-supplier-links-by-supplier-id` | `admin list supplier-link` |
+| `get-supplier-profile-schema` | `admin get supplier-profile-schema` |
+| `library-create` | `admin create library-element` |
+| `library-delete` | `admin delete library-element` |
+| `library-list` | `admin list library-element` |
+| `library-schema` | `admin get library-schema` |
+| `library-update` | `admin update library-element` |
+| `list-all-production-orders` | `admin list production-order` |
+| `list-all-restock-orders` | `admin list restock-order` |
+| `list-all-sampling-orders` | `admin list sampling-order` |
+| `list-all-shipping-orders` | `admin list shipping-order` |
+| `list-misc-payments-by-product` | `admin list misc-payment` |
+| `list-product-orders` | `admin list product-order` |
+| `list-suppliers` | `admin list supplier` |
+| `list-users` | `admin list user` |
+| `production-groups-generate` | `admin generate pricing-groups` |
+| `production-groups-set` | `admin set pricing-groups` |
+| `production-pricing-show` | `admin get production-pricing` |
+| `production-tiers-set` | `admin set production-tiers` |
+| `production-variants-set` | `admin set production-variants` |
+| `save-product-tech-spec` | `admin update tech-spec` |
+| `send-email` | `admin send email` |
+| `submit-supplier-quote` | `admin submit quote` |
+| `update-quote-request` | `admin update quote-request` |
+| `update-supplier` | `admin update supplier` |
+| `update-supplier-quote` | `admin update quote` |
+| `update-user-profile` | `admin update user` |
+| `upload-financial-documents` | `admin upload financial-document` |
+| `upload-link-document` | `admin upload link-document` |
+| `upload-product-document` | `admin upload product-document` |
+| `upload-production-order-document` | `admin upload production-order-document` |
+| `upload-production-progress-document` | `admin upload production-progress-document` |
+| `upload-sampling-order-document` | `admin upload sampling-order-document` |
+| `upload-supplier-document` | `admin upload supplier-document` |
+
+### Merged
+
+These four became flags on a single command, because they were the same read with a different filter:
+
+| 0.1 | 0.2 |
+|---|---|
+| `list-sampling-orders-by-product <id>` | `admin list sampling-order --product <id>` |
+| `list-production-orders-by-product <id>` | `admin list production-order --product <id>` |
+| `get-quote-requests <id>` | `admin list quote-request  (and admin get quote-request <id> for one)` |
+| `get-quote-requests-by-supplier-id <id>` | `admin list quote-request --supplier <id>` |
+
+### Compatibility notes
+
+- `typer` is pinned to `<0.25`. From 0.25 typer vendors its own copy of click, so a `TyperGroup`
+  is no longer a `click.Group` and the shared switches above cannot be attached to it. Lifting the
+  ceiling means reworking `makea_cli/main.py` at the same time.
+- The npm wrapper is unchanged: it still forwards to `python3 -m makea_cli` and now propagates the
+  new exit codes.
+