@tryarcanist/cli 0.1.255 → 0.1.257

package/README.md

@@ -15,7 +15,6 @@ Requires Node.js 22 or newer.
 ```bash
 arcanist auth login                 # paste a token from Settings > CLI
 arcanist sessions create https://github.com/your-org/your-repo "fix the login bug"
-arcanist sessions create https://github.com/your-org/your-repo "fix ARC-1635" --linear-issue https://linear.app/team/issue/ARC-1635/fix-login
 ```
 
 ```bash
@@ -201,7 +200,7 @@ arcanist sessions create your-org/your-repo "retry-safe create" --idempotency-ke
 
 `--wait` blocks until the created prompt finishes, prints the resulting PR/branch line in human-readable mode when it is already available, and exits non-zero if the prompt finishes with `status: failed`, making it suitable for cron or other schedulers that alert on command failure. JSON mode waits quietly and prints the create payload after the prompt completes successfully. `--poll-interval <ms>` tunes the completion check frequency.
 
-`--auto-verify` is a deprecated no-op. The verifier child is no longer spawned at publish — QA runs only on an explicit request (GitHub `/qa`, Slack `/qa`, API, or the UI "Verify"/"QA Test PR" button). The flag is accepted for backward compatibility and no longer starts a verifier.
+`--auto-verify` is a deprecated no-op. The verifier child is no longer spawned at publish. The flag is accepted for backward compatibility and no longer starts a verifier.
 
 Use `--browser-identity <id|none>` to attach a business browser identity to the session, or pass `none` to explicitly start without one. Access is authorized by the control plane when the session is created.
 
@@ -211,11 +210,6 @@ Use `--start-branch <branch>` to resume an existing branch with its history inst
 
 Use `--continue-pr <url>` to continue an open same-repo pull request. The control plane checks out the PR head branch before the prompt runs. `--continue-mode update-pr` updates the referenced PR; `--continue-mode new-pr` starts from that PR head but leaves publish free to open a fresh PR. `auto` is the default and currently resolves to same-PR update for supported open same-repo PRs.
 
-Use `--linear-issue <id|url>` to attach a Linear issue reference to the created session.
-The CLI echoes the request value as `linearIssue` in JSON output; pickup writeback occurs after the first prompt is durably enqueued.
-Use `--jira-issue <key|url>` to attach a Jira issue reference to the created session.
-The CLI echoes the request value as `jiraIssue` in JSON output; pickup writeback occurs after the first prompt is durably enqueued.
-
 Repeatable `--uploaded-file <path>` flags attach local UTF-8 text files to the prompt. Uploaded file names come from the local basename; directory components are not sent.
 
 Sessions always start from a fresh sandbox (the warm sandbox pool was removed).
@@ -227,36 +221,6 @@ The CLI derives separate session and prompt idempotency keys from the provided v
 
 JSON mode returns `{sessionId, sessionUrl?, repoUrl, model?, reasoningEffort?, autoVerify?, baseBranch?, startBranch?, continuePrUrl?, continueMode?, onboarding?, promptId?}`. With `--wait`, JSON mode also includes best-effort result fields when available: `prUrl?`, `publishedBranch?`, and `lastBranch?`.
 
-### `arcanist sessions qa <pr-url>`
-
-Starts a QA verification session for an existing GitHub pull request.
-
-```bash
-arcanist sessions qa https://github.com/your-org/your-repo/pull/123
-arcanist sessions qa https://github.com/your-org/your-repo/pull/123 --model gpt-5.4
-arcanist sessions qa https://github.com/your-org/your-repo/pull/123 --reasoning-effort xhigh
-arcanist sessions qa https://github.com/your-org/your-repo/pull/123 --wait
-arcanist sessions qa https://github.com/your-org/your-repo/pull/123 --idempotency-key 1f0e6f1a-...
-```
-
-The PR URL must be `https://github.com/<owner>/<repo>/pull/<number>`.
-The CLI derives the repo from that URL, creates a QA session with `qa: true` and `targetPrUrl`, then enqueues the verifier prompt (skipped when the server signals `promptAlreadyEnqueued`).
-Inspect progress with the session URL or the session events stream.
-
-`--model` pins the model for the QA session, and the CLI rejects an unknown model before any network call.
-When `--model` is omitted, the default is used.
-
-`--wait` blocks until the enqueued QA prompt finishes and exits non-zero if the prompt fails.
-JSON mode waits quietly and prints the create payload after the prompt completes successfully.
-`--poll-interval <ms>` tunes completion polling.
-
-`--idempotency-key <uuid>` is for manually retrying a QA request that may have reached the server.
-The CLI derives separate session and prompt idempotency keys from the provided value.
-If session creation succeeds but prompt enqueue fails, retry the same command with the same `--idempotency-key`.
-
-JSON mode returns `{sessionId, sessionUrl?, repoUrl, targetPrUrl, model?, reasoningEffort?, promptId?}`.
-`promptId` is absent when the coordinator already enqueued the verifier prompt (no duplicate send). Active-verifier and per-PR run-limit conflicts both use exit code `4`; active-verifier errors include the existing session handle when the server returns it.
-
 ### `arcanist sessions send <session-id> [prompt]`
 
 Sends a follow-up message to an existing session.
@@ -423,44 +387,6 @@ arcanist models list --json
 
 JSON mode returns `{models}`.
 
-### `arcanist automations create <repo-url> [prompt]`
-
-Creates a scheduled automation for a GitHub repo. Create/delete require a write-scoped CLI token; read-scoped tokens can list automations. The server validates repo access, normalizes cron expressions, dedupes retries by repo+cron+prompt, and caps each business at 20 enabled rules.
-
-```bash
-arcanist automations create your-org/your-repo "summarize new regressions" --cron "*/15 * * * *"
-arcanist automations create your-org/your-repo "audit N+1s" --cron "0 13 * * 5" --model gpt-5.5
-arcanist automations create your-org/your-repo "/audit-prod-docs https://docs.tryarcanist.com/" --cron "0 8 * * *" --slack-team-id T0123ABC --slack-channel-id C0456DEF
-printf "summarize new regressions" | arcanist automations create your-org/your-repo --prompt-stdin --cron "*/15 * * * *" --json
-arcanist automations create https://github.com/your-org/your-repo - --cron "0 14 * * 1-5" --name "Weekday summary"
-```
-
-Use `--model <model>` to pin the model for sessions started by the automation. When `--model` is omitted the Codex default is used.
-
-Use `--slack-team-id <team-id>` together with `--slack-channel-id <channel-id>` to deliver each completed automation digest into a Slack channel. Both flags are required together; the target workspace must already be connected to Arcanist and the bot must already be in the channel.
-
-JSON mode prints the created rule. Human-readable mode prints the rule ID, repo, normalized cron, and next fire time.
-
-### `arcanist automations list`
-
-```bash
-arcanist automations list
-arcanist automations list --limit 20 --json
-arcanist automations list --cursor <cursor>
-arcanist automations list --all --json
-```
-
-Default output reads one page. `--all` follows pagination until completion. JSON mode returns `{items, nextCursor}`.
-
-### `arcanist automations delete <id>`
-
-Deletes a scheduled automation. Interactive mode prompts for confirmation; pass `--yes` for non-interactive use. `--json` requires `--yes`.
-
-```bash
-arcanist automations delete rule_123
-arcanist automations delete rule_123 --yes --json
-```
-
 ### `arcanist tokens list`
 
 ```bash