ur-agent 1.34.0 → 1.35.1

package/docs/AGENT_UPGRADE_1.20.0.md

@@ -1,42 +0,0 @@
-# UR-AGENT 1.20.0 Upgrade Notes
-
-UR 1.20.0 adds IDE integration and a richer tool surface for agent workflows.
-
-## What Changed
-
-- **ACP server** — `ur acp serve|stop|status` exposes an HTTP+JSON-RPC Agent
-  Communication Protocol server for VS Code/Cursor/Zed-like editors. It lists
-  tools, calls tools, sends tasks, and reports status. Existing A2A and MCP
-  support remains unchanged.
-- **`ur exec`** — run one or more prompts in non-interactive mode with optional
-  concurrency, worktrees, and output capture.
-- **New built-in tools** exposed through the agent loop, MCP server, and ACP
-  server:
-  - `GitHub` — PR/issue/repo operations via the `gh` CLI.
-  - `Api` — REST HTTP calls with JSON/text output and path extraction.
-  - `Browser` — headless browser automation (fetch/goto/click/type/evaluate/
-    screenshot); interactive actions require `UR_BROWSER_TOOL=1`.
-  - `Docker` — container and compose operations via the `docker` CLI.
-  - `TestRunner` — auto-detect and run project tests.
-  - `Database` — SQL queries against SQLite, Postgres, MySQL, and DuckDB.
-- File-system and terminal tools (`FileRead`, `FileEdit`, `FileWrite`, `Glob`,
-  `Grep`, `Bash`, `PowerShell`) remain built in and are now also reachable via
-  ACP/MCP.
-
-## New Commands
-
-```sh
-ur acp serve --host 127.0.0.1 --port 8123
-ur acp status --json
-ur exec "refactor the parser" --concurrency 2 --json
-ur exec --file prompts.jsonl --output-dir ./outputs
-```
-
-## Validate
-
-```sh
-ur acp status
-ur exec --dry-run "add tests"
-bun run typecheck
-bun test
-```

package/docs/AGENT_UPGRADE_1.21.0.md

@@ -1,58 +0,0 @@
-# Upgrading to UR-AGENT v1.21.0
-
-## What's new
-
-v1.21.0 adds a set of worktree-first agent skills and a command to manage the worktrees they create.
-
-- **Agent skill runner** — `src/services/agents/agentSkillRunner.ts` wraps
-  `startBackgroundTask({ worktree: true, pr: true })`, polls the background run to
-  completion, and returns a PR-style summary with branch, commits, PR URL, and
-  diff summary.
-- **New bundled slash skills** — each skill expands into a prompt that instructs
-  the model to work in an isolated git worktree and produce a clean branch,
-  commits, and PR:
-  - `/debug-v2` — reproduce, root-cause, and fix a bug with a regression test
-  - `/refactor` — safe, test-backed refactoring
-  - `/paper-implementation` — implement an algorithm or system from a paper/URL
-  - `/benchmark` — add or run benchmarks and commit results
-  - `/security-review` — audit code for security issues, fix low-risk items
-  - `/dockerize` — add Dockerfile, compose file, health checks, `.dockerignore`
-  - `/latex-paper` — generate or compile a LaTeX paper/report
-- **Matching agent templates** — `debug-v2`, `refactor`, `paper-implementation`,
-  `benchmark`, `security-review`, `dockerize`, and `latex-paper` are now part of
-  `AGENT_TEMPLATES`. Install them with `ur agent-templates install`.
-- **`ur worktree`** — `ur worktree list|status|clean` inspects and cleans up UR
-  agent worktrees.
-
-## Quick examples
-
-```sh
-# Run a bug-fix agent in an isolated worktree
-ur -p /debug-v2 "parser crashes on empty input"
-
-# Same through the CLI
-ur bg run "reproduce and fix parser crash on empty input" --worktree --pr
-
-# List active worktrees and clean up finished ones
-ur worktree list
-ur worktree clean --dry-run
-ur worktree clean
-
-# Install the new agent templates
-ur agent-templates install debug-v2 refactor benchmark security-review dockerize latex-paper paper-implementation
-```
-
-## For users of `/debug`
-
-The existing `/debug` skill still reads the session debug log. `/debug-v2` is a
-separate skill for bug-fix work in a worktree. You can keep using `/debug` for
-diagnosing the current session and use `/debug-v2` (or `ur bg run ... --worktree
---pr`) when you want a branch + PR.
-
-## Upgrade steps
-
-1. Pull the release and run `bun install`.
-2. Run `bun run typecheck` and `bun test` to confirm the local state.
-3. Install agent templates if you want the new `.ur/agents/*.md` files:
-   `ur agent-templates install`.
-4. No settings or project file migration is required.

package/docs/AGENT_UPGRADE_1.22.0.md

@@ -1,48 +0,0 @@
-# Upgrading to UR-AGENT v1.22.0
-
-## What's new
-
-v1.22.0 turns `ur eval` into a real agent benchmark tool.
-
-- **Execution metrics** — headless `ur -p` child runs now write a metrics JSON file
-  via `UR_EVAL_METRICS_FILE`. The eval runner reads it and also runs
-  `git diff --stat` and an optional per-case `expect.testCommand`. Captured
-  metrics: cost USD, input/output tokens, model, API duration, files changed,
-  insertions/deletions, command failures, human-edit heuristics, and test
-  pass/fail.
-- **Parallel-safe by design** — each child writes its own metrics file, so
-  future parallel eval runs will not corrupt shared cost state.
-- **Richer dashboard** — `ur eval dashboard` and
-  `ur eval report <suite> --dashboard` generate local HTML dashboards with
-  summary cards (pass rate, test pass rate, cost, tokens, files changed, command
-  failures, human edits, duration) and a per-case timeline showing model, time,
-  cost, tokens, diffs, test result, and output preview.
-- **Per-case metrics persistence** — `ur eval run <suite> --metrics` writes
-  each case's metrics to `.ur/evals/.runs/<suite>/<case>.json`.
-- **Aggregate reporting** — `ur eval report <suite>` now prints totals for cost,
-  tokens, files changed, command failures, human edits, duration, and test pass
-  rate.
-
-## Quick examples
-
-```sh
-# Run the starter suite and print JSON with metrics
-ur eval run starter --metrics --json
-
-# Write a single-suite HTML timeline dashboard
-ur eval report starter --dashboard
-
-# Generate the combined dashboard across all saved reports
-ur eval dashboard
-
-# Import a SWE-bench-style export and run it
-ur eval bench swe-bench --file issues.jsonl --name my-bench
-ur eval run my-bench --metrics
-```
-
-## Upgrade steps
-
-1. Pull the release and run `bun install`.
-2. Run `bun run typecheck` and `bun test` to confirm the local state.
-3. Rebuild the bundled CLI: `bun run bundle`.
-4. No settings or project file migration is required.