orizu 0.4.0 → 0.5.0

package/vendor/skills/orizu-cli/SKILL.md

@@ -22,8 +22,10 @@ Skip this skill when:
 
 - Node.js 20+ installed.
 - Install the CLI: `npm i -g orizu`.
-- Install this skill from the CLI package: `orizu install-skill --agent codex --yes` (or `--agent claude`; advanced target IDs remain available via `--target`).
+- Run `orizu setup` to sign in, initialize the workbench, and install the global Codex/Claude Code skill symlinks.
+- Or install this skill directly from the CLI package with `orizu install-skill --agent codex --yes` (or `--agent claude`; advanced target IDs remain available via `--target`).
 - Or read the bundled skill in place without installing: `orizu skills path --json` returns `root`, `skillMd`, `source`, `cliVersion`, and `skillHash`.
+- Before doing Orizu work, verify the runtime with `orizu --version` and `orizu capabilities --json`. If the CLI is missing or stale, pause and ask the user to update it.
 - After CLI upgrades, check installed copies with `orizu skills status` and refresh them with `orizu skills update`.
 - Rediscover the command surface any time with `orizu --help`, `orizu <group> --help`, or `orizu capabilities --json`.
 - Every command supports `--json` (prefix `orizu --json <cmd>` or trailing flag) and emits a single JSON document; prefer it over parsing human-formatted text. Long-running commands emit the JSON summary as the final stdout line.
@@ -89,6 +91,8 @@ orizu tasks create --project <teamSlug>/<projectSlug> --dataset <datasetId> --ap
 
 # Open the returned task URL and test the draft manually before assigning.
 orizu tasks publish --task <taskId> --assignees <userId1,userId2>
+# Or publish exact row assignments:
+orizu tasks publish --task <taskId> --assignment-file ./assignments.jsonl
 
 orizu tasks status --task <taskId>
 orizu tasks report set --task <taskId> --report-file ./task-report.md
@@ -175,9 +179,9 @@ Detailed walkthrough — GEPA mechanics, Orizu-tracked optimization, optional DS
 # Execution rules
 
 - Prefer explicit flags in non-TTY contexts; reserve interactive fallback for TTY.
-- Canonical selectors: `--team`, `--project`, `--app`, `--task`, `--dataset`, `--assignees`.
-- `tasks create` creates drafts by default. Test the returned task URL manually, then use `tasks publish --task <taskId> --assignees <userId1,userId2>` after approval.
-- `tasks assign` and `tasks publish` take user IDs, not emails.
+- Canonical selectors: `--team`, `--project`, `--app`, `--task`, `--dataset`, `--assignees`, `--assignment-file`.
+- `tasks create` creates drafts by default. Test the returned task URL manually, then use `tasks publish --task <taskId> --assignees <userId1,userId2>` or `tasks publish --task <taskId> --assignment-file <path>` after approval.
+- `tasks assign --assignees` and `tasks publish --assignees` take user IDs, not emails. `--assignment-file` accepts emails or user IDs in JSONL rows shaped as `{ "rowId": "...", "assignee": "..." }` or `{ "rowId": "...", "assignees": ["..."] }`.
 - `datasets edit-rows` requires a non-empty string `id` on each row in `--file`.
 - `datasets delete-rows` uses `--row-ids` as the canonical selector.
 - `datasets delete` requires interactive terminal confirmation; there is no non-interactive confirmation option.

package/vendor/skills/orizu-cli/references/cli-reference.md

@@ -42,7 +42,7 @@ orizu skills path [--skill-md] [--json]
 orizu skills status [--json]
 orizu skills update [--dry-run] [--json]
 orizu install-skill [--agent <claude|codex>]... [--scope global|project] [--mode auto|link|copy] [--yes] [--dry-run] [--json]
-orizu setup [--agent <claude|codex>]... [--skip-login] [--no-install] [--workspace|--no-workspace] [--no-handoff] [--yes] [--dry-run] [--no-input] [--json]
+orizu setup [--team <slug>] [--agent <claude|codex>]... [--workspace [path]|--no-workspace] [--validate] [--fix] [--no-symlinks] [--verbose] [--no-install] [--handoff] [--yes] [--dry-run] [--no-input|--non-interactive] [--json]
 orizu setup prompt [--json]
 ```
 
@@ -50,8 +50,8 @@ Behavior:
 - `capabilities --json` returns the full machine-readable command manifest, including `globalOptions`.
 - `skills path --json` returns where this skill's source lives (`root`, `skillMd`, `source`, `cliVersion`, `skillHash`) so you can read it without installing, and verify an installed copy matches the CLI.
 - `skills status` reports each install target as missing/current/stale/broken-link; `skills update` refreshes stale copies and repairs broken symlinks.
-- `install-skill` selects targets by agent name; `--scope global` (default) installs user-level, `--scope project` into the repo. Project-scope installs always copy; global installs symlink when the CLI path is stable. Advanced target IDs remain available via `--target`.
-- `orizu setup` is the guided onboarding flow (login → agent integration → `.orizu/` workspace → handoff prompt). `orizu setup prompt` prints the repo-adoption prompt for handing to a coding agent.
+- `install-skill` selects targets by agent name; `--scope global` (default) installs user-level (`~/.codex/skills`, `~/.claude/skills`), `--scope project` installs into the repo. Project-scope installs always copy; global installs symlink when the CLI path is stable. Advanced target IDs remain available via `--target`.
+- `orizu setup` is the guided onboarding flow (login → team workspace contract → global coding-agent skill install). Use `orizu setup --team <slug>` for agent-friendly setup of the current directory; after authentication it materializes every project in that team. Use `--workspace <path>` only when setting up or validating another directory. Interactive setup offers Codex when `~/.codex` exists and Claude Code when `~/.claude` exists; pass `--agent codex --agent claude` for non-interactive installs. The contract uses root `AGENTS.md`, `CLAUDE.md`, `Memory.md`, `orizu.team.json`, project manifests, primitive directories, and gitignore policy. `.orizu/` and `.logs/` are ignored cache/generated state, not the durable contract. `orizu setup prompt` prints the repo-adoption prompt for handing to a coding agent; pass `orizu setup --handoff` only when you want that prompt printed inline after setup.
 
 ### Teams
 
@@ -186,23 +186,28 @@ orizu tasks create \
 Behavior:
 - task creation creates a draft by default and returns a task URL to test manually before assigning
 - use `--publish --assignees <userIdOrEmail1,userIdOrEmail2>` only when you intentionally want to create and ship immediately
+- use `--assignment-file <path>` instead of `--assignees` when specific rows should go to specific labellers
 - after manually approving a draft, run `orizu tasks publish --task <taskId> --assignees <userId1,userId2>`
+- or run `orizu tasks publish --task <taskId> --assignment-file <path>` to publish the exact row map
 - task creation resolves and stores the app's pinned current `version_id` at create time
 - downstream consumers (exports, judges, optimization) should trust the task's pinned `version_id`, not the app's current pointer
 - dataset compatibility is validated against that pinned app version before the task is inserted
 - malformed JSON and mixed-type assignee arrays fail with deterministic `400` responses
 - assignment fanout enforces unique `(assignee, row)` pairs; `--labels-per-item` cannot exceed the number of unique assignees, and the backend shortfalls instead of duplicating
+- explicit assignment manifests are JSONL with `rowId` plus `assignee` or `assignees`; row IDs are canonical dataset row `id` values, assignees may be emails or user IDs, and V1 publish requires whole-dataset uniform coverage
 
 Publish:
 
 ```bash
 orizu tasks publish --task <taskId> --assignees <userId1,userId2>
+orizu tasks publish --task <taskId> --assignment-file ./assignments.jsonl
 ```
 
 Assign:
 
 ```bash
 orizu tasks assign --task <taskId> --assignees <userId1,userId2>
+orizu tasks assign --task <taskId> --assignment-file ./assignments.jsonl --replace-existing
 ```
 
 Status:
@@ -301,6 +306,8 @@ orizu tasks create \
 
 # Open the returned task URL and test the draft manually before assigning.
 orizu tasks publish --task <taskId> --assignees <userId1,userId2>
+# Or publish a deterministic row map:
+orizu tasks publish --task <taskId> --assignment-file ./assignments.jsonl
 
 orizu tasks status --task <taskId>
 orizu tasks export --task <taskId> --format csv --out ./support-round1.csv
@@ -321,7 +328,8 @@ Use these shortcuts only in TTY environments where prompts can run.
 
 - `tasks create` creates a draft by default, does not require `--assignees`, and pins the app's current version when the task is created.
 - `tasks create --publish --assignees <...>` intentionally creates and ships immediately.
-- `tasks assign` and `tasks publish` expect user IDs, not emails.
+- `tasks create|publish|assign --assignment-file <path>` is mutually exclusive with `--assignees` and accepts emails or user IDs in the JSONL manifest.
+- `tasks assign --assignees` and `tasks publish --assignees` expect user IDs, not emails.
 - Assignment queue reads are assignee-self-only; use task status/export as the operator summary path.
 - Assignment completion payloads are validated against the pinned app-version `output_json_schema`.
 - `datasets delete-rows` requires `--row-ids`.