@opvs-ai/cli 0.14.0 → 0.15.1

package/README.md

@@ -118,6 +118,57 @@ Override workspace selection and settings without modifying config:
 opvs boards list                           # List all boards
 opvs boards get <id>                       # Board details + columns
 opvs boards create -n "Sprint 1"           # Create a board
+opvs boards templates --board-type factory # Presets + each column's claim wiring
+opvs boards create -n "Build" --board-type factory --column-preset factory-full
+opvs projects add-board <project-uuid> <new-board-uuid>  # REQUIRED for a factory board — see below
+opvs boards set-routing ASP --harness codex          # Board routing defaults ('none' clears)
+opvs boards projects ASP                             # Projects claiming the board (none|resolved|ambiguous)
+opvs boards add-to-project ASP <project-uuid>        # Additive
+opvs boards move-to-project ASP <project-uuid> --yes # REMOVES it from every other project — previews first
+opvs boards health ASP --profile factory             # Unsupplied thresholds print NOT CHECKED
+opvs boards apply-preset ASP factory-full            # DRY RUN by default; --yes applies
+opvs boards apply-preset ASP factory-full --yes --json | jq .applied  # ONE JSON document: the applied plan
+opvs boards update ASP --archived true               # Hidden from `boards list`; cards stay CLAIMABLE
+```
+
+> ⚠️ **A factory board claims NOTHING until it is in exactly ONE active project.** Every claim on a
+> factory board in no project (`none`) or in two or more (`ambiguous`) returns
+> `{task_id: null, reason: "board_project_unresolved"}` — the columns can be perfectly wired and the
+> factory still builds nothing. `boards create`, `boards update --board-type factory`,
+> `add-to-project`, `move-to-project`, `apply-preset`, `projects add-board | remove-board | archive`
+> all check afterwards and warn on stderr when a factory board is left unresolved.
+
+### Members
+
+```bash
+opvs members list <boardId>
+opvs members add <boardId> --user <uuid>                 # or --agent <uuid>; a member of YOUR brand
+opvs members invite <boardId> --email x@y.com --role commenter  # outside your brand → a guest of this board
+opvs members remove <boardId> <uuid> --type agent        # --type defaults to user
+```
+
+> `--role` (viewer | commenter | editor) caps an **external guest** only; a member of your own brand
+> keeps full access whatever you pass.
+
+### Columns
+
+```bash
+opvs columns list <boardId>
+opvs columns update <columnId> --claimable-by-roles builder   # REPLACES the role set
+opvs columns update <columnId> --on-claim-move-to executing --sla-minutes 120 --sla-action comment
+opvs columns update <columnId> --managed-by user:<uuid>        # owner inbox + SLA @mention; grants nothing
+opvs columns update <columnId> --wip-limit none                # 'none' clears; 'ten' is refused, not a clear
+```
+
+> ⚠️ A role on ANY column changes the whole board: role-less workers are then held to
+> declared columns only. `--on-done-move-to` is advisory — nothing moves a card by it today.
+
+### Projects
+
+```bash
+opvs projects set-routing <project-uuid> --model claude-opus-5
+opvs projects health <project-uuid> --profile planner-orchestration
+opvs projects bundle set <project-uuid> --command ship --command-body ship=./ship.md  # a body map REPLACES
 ```
 
 ### Tasks
@@ -129,6 +180,12 @@ opvs tasks get <id>                        # Task details
 opvs tasks create --board <id> -t "Title"  # Create task
 opvs tasks update <id> --status review     # Update status
 opvs tasks update <id> --result-file out.md  # Attach result from file
+opvs tasks update <id> --pr 1201 --branch fix/x --worktree llm16:/root/OPVS-x --deploy-needs agentboard
+opvs tasks update <id> --blocked-reason "CI red" --status blocked   # the reason alone changes no status
+opvs tasks create --board <id> -t "Title" --workflow-doc ship --workflow-rule "Never force-push" --estimate 45
+opvs tasks claim <boardId> --role builder  # Take ONE runnable card; there is no lease
+opvs tasks search -q OSB-78                # By ref, PR number (#1256), title, description
+opvs tasks search -q deploy --board OSB,ASP --status pending --column Review --offset 20
 ```
 
 ### Comments
@@ -137,6 +194,9 @@ opvs tasks update <id> --result-file out.md  # Attach result from file
 opvs comments list <task-id>               # List task comments
 opvs comments add <task-id> "message"      # Add inline comment
 opvs comments add <task-id> -f output.md   # Comment from file
+opvs comments add <task-id> "x" --internal # A LABEL — every reader still sees it
+opvs comments edit <comment-id> "new text" # Any board writer can edit any comment; old text is not kept
+opvs files fetch-url <task-id> <url>       # Store the file's BYTES on the card (attach-url keeps a link)
 ```
 
 ### Docs

package/dist/.build-stamp.json

@@ -1,9 +1,9 @@
 {
   "stamp_version": 1,
   "package": "@opvs-ai/cli",
-  "version": "0.14.0",
-  "source_digest": "1aaeceffd9ec2bce9fa7b87a30607a8847e306696b95429bdf230adae7c11d76",
-  "source_files": 38,
-  "built_at": "2026-09-11T12:20:56.934Z",
+  "version": "0.15.1",
+  "source_digest": "89167e4c4459cfe842c705996bfa50b6d8abf2e910c65af7d61a6a9ca985d8bf",
+  "source_files": 41,
+  "built_at": "2026-09-15T21:57:07.190Z",
   "node": "v22.22.0"
 }

package/dist/commands/boards.d.ts

@@ -2,4 +2,61 @@
  * opvs boards — board CRUD
  */
 import { Command } from "commander";
+interface ColumnChange {
+    slug: string;
+    name: string;
+    action: string;
+    changes?: Record<string, unknown[]>;
+    cards_affected?: number;
+    notes?: string[];
+}
+interface PresetConflict {
+    slug: string;
+    code: string;
+    detail: string;
+    blocking?: boolean;
+}
+interface ApplyPresetPlan {
+    preset?: string;
+    board_type?: string;
+    mode?: string;
+    applied?: boolean;
+    columns?: ColumnChange[];
+    conflicts?: PresetConflict[];
+    summary?: Record<string, number>;
+    extra_columns?: string[];
+}
+/**
+ * Print an apply-preset plan: one line per column with the card count it puts
+ * in scope, then conflicts and the columns the preset leaves alone. The card
+ * count is the number an operator reads to decide whether to apply, so it is
+ * on every row rather than only in the summary.
+ */
+export declare function renderPresetPlan(plan: ApplyPresetPlan): string;
+/**
+ * The columns whose planned change differs between the dry run the operator saw
+ * and the plan the server actually applied (ASP-118 F14).
+ *
+ * The apply is a SECOND request with no plan token or version check
+ * (`board_preset_service.py`), so another session can change the columns in
+ * between — and then a different set of rebinds and card counts is written
+ * than the one on screen. Same shape as `move-to-project`'s `removed_from`
+ * comparison: the server's answer is the truth, and a difference is reported.
+ *
+ * @returns one line per differing column slug; empty when they match.
+ */
+export declare function presetPlanDrift(preview: ApplyPresetPlan, applied: ApplyPresetPlan): string[];
 export declare function registerBoardCommands(program: Command): void;
+/**
+ * Parse repeatable `--manager slug=type:id` into the `managers` map
+ * `ApplyPresetRequest` takes. The shape is checked here because the server's
+ * coherence rule (a `user` needs `managed_by_user_id`, an `agent` needs
+ * `managed_by_agent_id`) is exactly what a hand-typed flag gets wrong, and a
+ * whole-request 422 names the field path rather than the flag.
+ */
+export declare function parseManagers(raw: string[]): Record<string, {
+    managed_by_type: "user" | "agent";
+    managed_by_user_id?: string;
+    managed_by_agent_id?: string;
+}>;
+export {};