foldrun 1.2.0 → 2.0.0

package/bin/foldrun.mjs

@@ -185,8 +185,7 @@ const HELP = `foldrun — agents are just folders
   foldrun flags             the feature flags for this account: each on or off, and why — set for this account, for every account, a staged rollout, or the default (--json). Read-only: the platform's super admin changes them
   foldrun history [path]    every change to a deployed workspace, newest first (--id <revision> for its diff, --limit, --to)
   foldrun history restore <path> --id <revision>  put one file back as that revision left it, as a new revision — diff, asks (--yes, --dry-run, --to)
-  foldrun repo ls           a workspace's branches and tags — also diff <branch>, deploy <ref>, merge <branch> (both ask first), rm-branch <branch>, mirror <git-url|off>, mirror-now (--to)
-  foldrun restore <ws> --to <commit|time|age>  put a workspace's source back as it was then — shows the change, asks for the name typed back (--dry-run: the diff only, --yes)
+  foldrun restore <ws> --to <revision|time|age>  put a workspace's source back as it was then — shows the change, asks for the name typed back (--dry-run: the diff only, --yes)
   foldrun backups           how the account is backed up (encrypted?), when it last was, the snapshots it is in — also request --what runs|state|storage|everything --at "<when>" [--to <ws>] [--note]
   foldrun backups requests  every restore asked of the platform team, and where each stands (--json)
   foldrun secrets set NAME  store a secret (prompted, never echoed) — also ls, rm, status; --kind file|ssh|api|service-account|m2m for the other shapes; --site <domain> (repeatable) binds it as it is stored
@@ -294,7 +293,7 @@ Options
   --step <n>                approve, reject: decide only that step; default is every step that is waiting
   --payload <json|text|@f>  approve: release a step waiting on wait: event with this body, recorded as you
   --note "<text>"           approve, reject: guidance the agent reads — or the reason for a refusal; billing credit: the ledger line's note
-  --yes                     approve, stop, rerun (bulk), flow rotate-hook, flow draft, assistant, history restore, restore <ws>, import, billing plan, repo, workspace set name, and every rm/revoke/unshare: skip the confirmation, deliberately (required with no terminal)
+  --yes                     approve, stop, rerun (bulk), flow rotate-hook, flow draft, assistant, history restore, restore <ws>, import, billing plan, workspace set name, and every rm/revoke/unshare: skip the confirmation, deliberately (required with no terminal)
   --json                    report: the raw run record instead of the report; observe, usage, api version, changelog, find, preferences, workspace vocabulary, flags, workspaces, workspaces show, agent ls, flow ls, agent import --list, backups requests, team, hook ls: the raw document; version: {cli, core, platform}
   --events <a,b>            account set notify: failed, awaiting-approval, completed
   --failed                  webhooks deliveries: only the ones that gave up
@@ -324,7 +323,6 @@ Options
   --port <n>                connect: loopback port for the redirect (default 8642 — register http://localhost:8642/callback on the app)
   --authorize-url / --token-url  connect: a provider with no preset
   --role <r>                keys create: viewer, editor (default) or admin
-  --for <workspace>         keys create: a deploy key for one workspace (--access read|write)
   --expires <span>          keys create: when it stops working — 30d, 90d, 365d or never (default never)
   --grace <span>            keys rotate: keep the old key working for 1h or 24h while you swap the new one in (default 0: revoked now)
 

package/docs/api.md

@@ -14,7 +14,7 @@ in common — versions (`Foldrun-Version`), rate limits (`X-RateLimit-*`, `429`)
 One funnel for every caller. A route either takes an authenticated tenant or
 refuses — there is no separate "browser API". The exceptions carry their own
 proof instead of a key: a token or signature (`/s/<token>`, `/api/hooks`,
-`/api/inbox`, `/api/events`, `/api/approve`, `/api/unsubscribe`, `/api/git`, `/api/billing/stripe`,
+`/api/inbox`, `/api/events`, `/api/approve`, `/api/unsubscribe`, `/api/billing/stripe`,
 `/api/billing/confirm`), the sign-in and recovery steps (`/api/auth/signup`,
 `login`, `forgot`, `reset`, `verify`, `mfa/verify`, `session`, `/api/cli/login`,
 `/api/cli/login/<id>`, `/api/cli/authorize` GET, `/api/oauth/callback`), `/api/healthz`, `/api/status`, `/api/status/history`, `/api/version` and `/api/openapi.json`.
@@ -142,9 +142,7 @@ nothing outward, state untouched, receipts on the run). Returns
 `{ ok, runId, steps, test }` (`from` is added when a start step was given); `409 { error, runId }` when the flow has `overlap: skip` and a run is live; with `?wait=true&timeout=<s>` it holds
 on and returns the verdict instead, exactly as `GET .../runs/<id>?wait=true`
 does below, which is where a caller goes on to wait when a piece runs out.
-Left out, `test` is decided by the platform:
-a preview workspace's runs are tests unless the flow says `live: true`;
-everywhere else a run is live.
+Left out, a run is live.
 
 ## Assistant
 
@@ -208,12 +206,9 @@ paying for the steps around it.
 | `/api/workspaces/<ws>/notify/deliveries` | GET | the outbound webhook log: every `notify:` url delivery from this workspace, newest first — `{ deliveries, total, limit, offset, endpoint }`. A delivery is `{ id, event, status, destination, attempts, attemptLog, lastStatusCode, lastError, nextAttemptAt, createdAt, updatedAt, body }`: `id` is the `X-Foldrun-Delivery` header; `status` is `pending` (a retry is due at `nextAttemptAt`), `delivered`, `failed` (gave up after six attempts) or `skipped` (the endpoint was switched off); each attempt is `{ n, at, statusCode, durationMs, response (first 500 characters), error, manual? }`. `body` is what was sent, except that a gate's `approveUrl`/`rejectUrl` (top level and in `links`) read `[redacted]` — they decide without a login, and this log is readable by every role; the receiver still gets them, on a redelivery too. `?status=`, `?event=`, `?limit=` (50, at most 200), `?offset=`. `endpoint` is `{ failingSince, lastSuccessAt, lastFailureAt, disabledAt, disabledReason }` or null. Kept 30 days |
 | `/api/workspaces/<ws>/notify/deliveries/<id>/redeliver` | POST | send one delivery again now — the same id and body, signed afresh, to the URL `notify:` names today. `{ ok, attempt, delivery }`, always `200` when the delivery exists (whether the receiver took it is the answer); `404` when it does not. An accepted redelivery switches a disabled endpoint back on. Needs the permission that runs |
 | `/api/workspaces/<ws>/notify/test` | POST | sends one real notification to whatever this workspace's `notify:` resolves to, and answers `{ ok, destination, detail }` — including the provider's own words when it failed, which are what name the problem. Always `200`: the request was handled, and the result is the answer. Needs the permission that runs, because it sends real mail |
-| `/api/workspaces/<ws>/observe?days=` | GET | the observability report the Observe page renders — per-agent failures and retries, per-tool calls/errors/latency, per-flow duration, day series, recent failures. `days` 1–365, default 30 (`since=`, its older name, still works — deprecated) |
+| `/api/workspaces/<ws>/observe?days=` | GET | the observability report the Observe page renders — per-agent failures and retries, per-tool calls/errors/latency, per-flow duration, day series, recent failures, and `startup` — one row per start-up phase in order, `{ phase, took, at }`, each `{ n, p50, p95, max }` in seconds (`took` is the phase's own share, `at` when it ended counted from the step's start; percentiles need five samples). `days` 1–365, default 30 (`since=`, its older name, still works — deprecated) |
 | `/api/workspaces/<ws>/history?path=&id=&limit=` | GET | every change to the workspace, newest first — `path` narrows to one file, `id` returns one revision with its before/after and a line diff, `limit` 1–500, default 100. A deploy's revision id is its commit |
-| `/git/<tenant>/<ws>.git` | git | the workspace as a git remote — `git clone`, `git push` (a push to main deploys and runs the evals; a push to any other branch deploys a **preview** workspace named `<ws>-preview-<branch>` from that branch's tree and runs its evals there — the scheduler never fires a preview's flows, a preview reads its source's secrets, and deleting the branch deletes the preview). A push while runs are in flight is accepted but **not** applied yet: git warns at push time, and the scheduler applies it when those runs finish. HTTP Basic: any username, an API key as the password |
-| `/git/<tenant>/_library.git` | git | the account library as a git remote — a push replaces the shelf |
-| `/api/workspaces/<ws>/repo?branch=` | GET, POST | GET: branches, tags, mirror settings; `?branch=` a branch's net change against main with diffs. POST `{action}`: `deploy` a `ref` (a rollback is a new commit on main), `merge` a `branch` into main and deploy, `delete-branch`, `mirror` (set `url`, https, credentials via the MIRROR_TOKEN secret), `mirror-now` |
-| `/api/workspaces/<ws>/restore` | POST | put the workspace's source back as it was at a point in its history. `to`: a commit or its prefix, a branch or tag, an ISO date/time (the last commit on main at or before it) or an age (`90m`, `12h`, `3d`, `2w`). `{ to, dryRun: true }` answers `{ to: { sha, at, by, message }, from, added, updated, removed, files: [{ path, change, diff }], blockedBy, noop, issues, warnings }` and writes nothing; `issues` are the deploy checks that would refuse that tree, `warnings` the ones it would deploy with. The restore needs `confirm` set to the workspace's name (400 without) and takes the dry run's `expectRemoved`; it deploys that commit's tree as a new commit on main (undo: restore to `from`), keeps runs, `state/`, storage, secrets and agent-written memory, and is refused 409 while runs are in flight or when it would remove something not in `expectRemoved`. `workspace:write`; audited as `workspace.restored` |
+| `/api/workspaces/<ws>/restore` | POST | put the workspace's source back as it was at a point in its history. `to`: a revision id (`r-…`), the commit a deploy named (or its prefix), an ISO date/time (the last revision at or before it) or an age (`90m`, `12h`, `3d`, `2w`) — every revision since 17 Oct 2026 holds a snapshot of the whole source. `{ to, dryRun: true }` answers `{ to: { id, sha, at, by, message }, from, added, updated, removed, files: [{ path, change, diff }], blockedBy, noop, issues, warnings }` and writes nothing; `issues` are the deploy checks that would refuse that tree, `warnings` the ones it would deploy with. The restore needs `confirm` set to the workspace's name (400 without) and takes the dry run's `expectRemoved`; it deploys that revision's snapshot as a new revision (undo: restore to `from`; `to.sha` is the same id as `to.id`, kept from when revisions were git commits), keeps runs, `state/`, storage, secrets and agent-written memory, and is refused 409 while runs are in flight or when it would remove something not in `expectRemoved`. `workspace:write`; audited as `workspace.restored` |
 
 `status` is one of `queued`, `running`, `awaiting-approval`, `completed`,
 `failed`.
@@ -329,7 +324,7 @@ Reads return which secrets exist, never their values.
 
 | Route | Methods | |
 |---|---|---|
-| `/api/keys` | GET, POST, DELETE | API keys — an admin's (`keys:manage`) to list, mint and revoke. POST `label`, `role` (viewer \| editor \| admin, never above your own, default editor), `workspaces` (names, or `null` for all — never wider than your own scope); `expires` (`30d`, `90d`, `365d`, any number of days up to 3650, or `never` — the default; anything else is a 400, never a key that lives forever); returns `{ ok, key, id, prefix, role, workspaces, expiresAt }`, and the key is shown once. GET lists each key with `createdAt`, `createdBy`, `expiresAt`, `lastUsedAt`, `lastIp` and `replacedBy` (the id of the key a rotation replaced it with; `null` until then) — the last-use pair written at most once a minute per key, the address cut to its /24 (IPv4) or /48 (IPv6). A key past its `expiresAt` is refused with 401 `API key expired on <date>`; the owner is emailed seven days before. Mint, revoke and rotate are written to the audit log. POST with `workspace` and `access: read\|write` mints a deploy key — git clone/push for that workspace only, refused everywhere else. DELETE `id`. `?tenant=` / body `tenant` is read only on an install with no users yet (first-run bootstrap) |
+| `/api/keys` | GET, POST, DELETE | API keys — an admin's (`keys:manage`) to list, mint and revoke. POST `label`, `role` (viewer \| editor \| admin, never above your own, default editor), `workspaces` (names, or `null` for all — never wider than your own scope); `expires` (`30d`, `90d`, `365d`, any number of days up to 3650, or `never` — the default; anything else is a 400, never a key that lives forever); returns `{ ok, key, id, prefix, role, workspaces, expiresAt }`, and the key is shown once. GET lists each key with `createdAt`, `createdBy`, `expiresAt`, `lastUsedAt`, `lastIp` and `replacedBy` (the id of the key a rotation replaced it with; `null` until then) — the last-use pair written at most once a minute per key, the address cut to its /24 (IPv4) or /48 (IPv6). A key past its `expiresAt` is refused with 401 `API key expired on <date>`; the owner is emailed seven days before. Mint, revoke and rotate are written to the audit log. POST with `workspace` or `access` is refused (400): those minted deploy keys for the platform's own git, which went on 17 Oct 2026 — a deploy key minted before is refused everywhere (403). A key for one workspace is `workspaces: ["<ws>"]`. DELETE `id`. `?tenant=` / body `tenant` is read only on an install with no users yet (first-run bootstrap) |
 | `/api/keys/<id>/rotate` | POST | a new key with the old one's label, role, workspaces and deploy scope — and, when it had an end, the same lifetime from today — returned once like a mint (`{ ok, key, id, prefix, role, workspaces, expiresAt, replaced: { id, endsAt } }`). `grace`: `0` (default — the old key is revoked at once), or a duration up to `7d` such as `1h` or `24h`, during which the old key still works and after which it is refused as expired. A key is rotated once: rotating a key already replaced is 409 `this key was already rotated to <prefix>…; rotate that one` — and someone who lost the new key's secret rotates the NEW key, which mints another and ends the lost one (rotating the old one again would leave the lost key working). Two rotations of one key at once mint one key. `keys:manage`; a key outside the caller's scope is 404. Audited as `apikey.rotated` |
 | `/api/team` | GET, POST | members with their roles and workspace scope; mint an invite — `role` (viewer \| editor \| admin, default editor), `workspaces` (names, or omit for all), `email` (bound into the invite: only that address can accept it; sent through the account's `RESEND_API_KEY` unless `send: false`). Returns `path` (the invite's relative URL), `expires`, `sent` and any `sendError` either way; the full link is in the mail |
 | `/api/team/members/<id>` | PATCH, DELETE | change a member's role (`role`) and/or which workspaces they may open (`workspaces`: names, or null for all); remove them |
@@ -473,4 +468,3 @@ signed-in person, never by a key — mints an ordinary API key at their role.
 | `/api/approve/<tenant>/<ws>/<id>?token=` | GET, POST | decide a run parked on a human, from the link in its notification. GET shows what is waiting and two buttons — it never decides, because inbox link-checkers follow GETs. POST `decision` (`approve` or `reject`) and an optional `note`, form-encoded or JSON; answers JSON when `Accept` prefers it. The token is derived from the run id under the install key, not stored, so a key rotation kills every link. Needs `FOLDRUN_PUBLIC_URL` to be minted at all |
 | `/api/workspaces/<ws>/hooks/<flow>` | GET | read the flow's webhook URL without changing it: `{ ok, flow, path, url }` — `path` carries the token, `url` is it made absolute with `FOLDRUN_PUBLIC_URL` (null when that is unset). `workspace:manage`, as rotate and the settings page that shows it, since the URL is a credential. `404` for no such flow, `409` for a flow that is not `trigger: webhook` |
 | `/api/workspaces/<ws>/hooks/<flow>/rotate` | POST | new token, old URLs stop working |
-| `/api/git/<tenant>/<ws>?branch=&dir=` | POST | GitHub push webhook — HMAC-signed, fetches the tarball at that commit and deploys it |

package/docs/backups-and-restore.md

@@ -29,7 +29,7 @@ It holds the database only, not the data volume.
 ### What it does not hold
 
 - Workspace files, run records, `state/`, `memory/`, the vault and each
-  workspace's git history: the data volume is not backed up. A workspace's
+  workspace's history: the data volume is not backed up. A workspace's
   source can still be restored from its own history (below).
 - **Storage file bytes.** These live in object storage (R2), not on the data
   volume. *Unverified:* whether a storage file deleted by mistake can still
@@ -63,18 +63,26 @@ public key).
 
 ## Restoring a workspace yourself
 
-Every change to a workspace — a dashboard save, a deploy, a `git push` — is
-a commit in its own git repository. Restoring puts the workspace's source
-back as it was at one of those commits:
+Every change to a workspace — a dashboard save, a deploy, an import — is a
+revision, and every revision keeps a snapshot of the whole source as it
+stood right after it. Restoring puts the workspace's source back as it was
+at one of them — the platform's own deploy history, so it works the same
+whether or not you keep the source in git:
 
 ```sh
 foldrun restore sales --to 2026-09-28T14:00 --dry-run   # what would change, with the diff
 foldrun restore sales --to 2026-09-28T14:00             # asks you to type the name, then does it
 ```
 
-`--to` takes a commit (or the start of one), a branch or tag, a date or time
-(the last commit at or before it — a time without a zone is read in the
-server's timezone, so add `Z` or an offset to be exact), or an age: `90m`, `12h`, `3d`, `2w`.
+`--to` takes a revision id (`r-…`, from the History page or `foldrun
+history`), the commit a deploy named, a date or time (the last revision at
+or before it — a time without a zone is read in the server's timezone, so
+add `Z` or an offset to be exact), or an age: `90m`, `12h`, `3d`, `2w`.
+A revision's diff is that one change; its snapshot is the whole source as
+it stood on disk just after it, so two people saving at once each see the
+other's change in their snapshot. History holds snapshots from 17 October 2026: each workspace's starts with
+a "history starts here" revision, its source as it stood then, and nothing
+before it can be restored this way.
 
 - **Preview first.** The dry run lists every file that would change, come
   back, or go, with a line diff. Nothing is written.
@@ -82,8 +90,8 @@ server's timezone, so add `Z` or an offset to be exact), or an age: `90m`, `12h`
   back (`confirm` in the API). The CLI sends the removals you were shown, and
   if anything else would now be removed — a file added in between — the
   restore is refused and you are asked to look again.
-- **It is undoable.** A restore is a new commit whose files are the old
-  ones; history says "restored to abc1234". To undo it, restore to the commit
+- **It is undoable.** A restore is a new revision whose files are the old
+  ones; history says "restored to r-…". To undo it, restore to the revision
   it answered as `from`.
 - **It touches only the source.** Runs, `state/`, storage, secrets and the
   memory agents wrote are what a deploy keeps, and a restore is a deploy:
@@ -97,11 +105,12 @@ server's timezone, so add `Z` or an offset to be exact), or an age: `90m`, `12h`
 ```http
 POST /api/workspaces/<ws>/restore
 { "to": "3d", "dryRun": true }
-{ "to": "<sha from the dry run>", "confirm": "<ws>", "expectRemoved": [ … ] }
+{ "to": "<to.id from the dry run>", "confirm": "<ws>", "expectRemoved": [ … ] }
 ```
 
-The workspace's History page lists every commit, and its Repository page can
-deploy any one of them — the same operation, by commit instead of by time.
+The workspace's History page lists every revision; open one and **Roll back
+to this** does the same restore, by revision instead of by time, with its
+preview first.
 
 ## Asking for a restore from a snapshot
 

package/docs/budgets-and-billing.md

@@ -25,8 +25,9 @@ mistake the editor names rather than a cap it quietly keeps.
 When an agent's cap and the flow's both apply to one step, the tighter one
 wins, and the step's error says which line set it: `budget: in the flow
 file` or `budget: on the writer agent`.
-| **runs at once** | `concurrency: 3` in the account's `AGENTS.md`, or Settings → Defaults | the fourth run waits its turn in the queue — never refused, only later. Empty means the install's plan number (`FOLDRUN_PLAN_CONCURRENCY`, which applies only where billing is on), or no cap |
-| **the queue lane** | `priority: high` in the account's `AGENTS.md` (`high` \| `normal` \| `low`) | its runs are claimed before other accounts' normal ones when slots are short; a flow's own `priority:` adds to it. The cap above still holds — a lane jumps the queue, it does not hold the fleet |
+| **runs at once** | `concurrency: 3` in the account's `AGENTS.md`, or Settings → Defaults | the fourth run waits its turn in the queue — never refused, only later. Empty means the install's share (`FOLDRUN_ACCOUNT_CONCURRENCY`) or plan number (`FOLDRUN_PLAN_CONCURRENCY`, which applies only where billing is on), or no cap. Your own number can lower that, never raise it; a higher number comes with a plan |
+| **the queue lane** | the plan's lane (`high` \| `normal` \| `low`); `priority: low` in the account's `AGENTS.md` lowers it, and `high` there counts only with a plan that gives it | when slots are short, accounts take turns, weighted by lane — high 3, normal 2, low 1: every account's first run goes before anyone's second, a fast lane takes three turns to a slow lane's one and never all of them, an account with runs going waits behind one with none, and a run that has waited ten minutes moves up a turn. A flow's own `priority:` orders runs within that. The cap above still holds |
+| **room to start** | the install's `FOLDRUN_RUN_MEMORY_GIB` and `FOLDRUN_ACCOUNT_PODS` | a step whose sandbox would not fit, or whose account already has its most sandboxes running, waits to start — `room: waiting to start — …` on its trail — instead of failing. The wait is not billed; the run page's start-up chip shows it as `room`. A step still waiting after 30 minutes (`FOLDRUN_ROOM_WAIT_SEC`) fails, saying why |
 
 A cap is a literal, never an expression, so it is readable off the file. The
 run cap is hard: a step that reaches its share of the remainder is stopped

package/docs/checks.md

@@ -238,11 +238,48 @@ today.
 
 ### config/unknown-field
 
-*warn.* A frontmatter key in an agent, flow or tool that is one or two
-letters away from a field foldrun reads: `tolls:`, `triger:`,
-`disallowed_tools:`. YAML accepts it, so it is silently ignored, and `tolls:
-[web]` leaves the agent with no tools. A key that looks like no known field
-is left alone, since another tool may own it.
+*warn or info.* A frontmatter key that this kind of file does not read. There
+are three cases, each with its own message:
+- **A near-miss** of a real field (`tolls:`, `triger:`, `disallowed_tools:`) is
+  a warning that names the field it meant. YAML accepts a typo, so it is
+  silently ignored, and `tolls: [web]` leaves the agent with no tools.
+- **A field read somewhere else** is a warning that says where it goes.
+  `timeout: 3600` on an agent is a step option, so it belongs under the step
+  in the flow. `language:` on a flow is read from the agent or `AGENTS.md`.
+- **A field like nothing foldrun reads** (`favourite_colour:`) is a note,
+  since another tool may own it.
+
+### config/wrong-type
+
+*warn.* The right field holding the wrong kind of value: a map where a list
+of names goes (`tools: {web: true}`), a list where one word goes. The runtime
+does not read it. The message says what the field takes.
+
+### config/invalid-value
+
+*warn.* A value that does nothing, or quietly does something else:
+- `effort: extreme` runs at the model's default;
+- `size: giant` becomes `large`;
+- `permissionMode:` other than `plan` is ignored;
+- `trigger: sometimes` never fires;
+- a `schedule:` the scheduler cannot read (`every day`) never fires. This is
+  checked with the scheduler's own cron parser;
+- an unknown HTTP method in `methods:` is dropped;
+- a duration that is not one (`debounce: soon`).
+
+Aliases count as valid: `effort: quick` is `low`. Fields another rule already
+checks in depth (`network:`, `limits:`, `timezone:`, `web:`) are left to it,
+so nothing is reported twice.
+
+### config/missing-field
+
+*warn.* A required field is absent: a skill with no `description:` is never
+loaded, because the model chooses skills by their descriptions.
+
+Every field these four rules know is listed, with its type and values, in one
+place in `@foldrun/core` (`frontmatter-fields.ts`). The editor's completions
+come from the same list, so what the editor suggests and what `check`
+accepts cannot drift apart.
 
 ### check/ignore-needs-reason
 

package/docs/cli.md

@@ -127,7 +127,7 @@ claude.ai or Claude Code there, nor any MCP configuration on disk.
 | `foldrun schedule tick` | Settings' **Run scheduler now**: fire whatever is due this minute and print which flows went (`POST /api/schedule`). They were due anyway; this only makes them go now |
 | `foldrun rerun <run-id>` | the same flow again, from a step: `--from <n>` as the flow file numbers them, or `--agent <name>` for the first step that agent runs. Earlier steps are recorded as skipped. This is the debug loop from the terminal: fix the file, `deploy`, `rerun --from` the step that failed. `--wait` follows the new run like `invoke --wait`; `--to <workspace>` from anywhere. With no run id and a filter (`--status failed`, `--since 24h`, `--until 2h`, `--flow <name>`) it reruns every match from `--from <n>` (default 1), listing and asking first as a bulk `stop` does; `--dry-run` lists only |
 | `foldrun triggers` | why nothing ran. One row per flow that fired in the window: its trigger, how many fires became runs, when it last ran, and every reason for the difference with a count — a duplicate delivery, a throttled or debounced burst, a fire the platform slept through, an `overlap: skip`, a flow switched off by `disable_after:`. A switched-off flow is a non-zero exit; one successful run clears it. `--since <days>` (default 7), `--to <workspace>` |
-| `foldrun observe` | where the account fails, retries and spends: one row per workspace — runs, failed and what share, steps, cost — then the recent failures in their own words. `--to <workspace>` prints that workspace in full, as the Observe page does: per flow (runs, failed, p50/p95 duration, cost), per agent (failed, retried, skipped, p95), per tool (calls, errors, p95 latency, which agents use it). `--since <days>` (default 30), `--json` for the document |
+| `foldrun observe` | where the account fails, retries and spends: one row per workspace — runs, failed and what share, steps, cost — then the recent failures in their own words. `--to <workspace>` prints that workspace in full, as the Observe page does: per flow (runs, failed, p50/p95 duration, cost), per agent (failed, retried, skipped, p95), per tool (calls, errors, p95 latency, which agents use it), and start-up — each phase of a step's first seconds, its own share and when it was done, p50/p95. `--since <days>` (default 30), `--json` for the document |
 | `foldrun usage` | what the account consumed — runs, steps, tokens, compute, storage, per workspace — and what it was charged over `--days <n>` (default 56) from the ledger, per workspace with the change against the period before. `--json` for both documents |
 | `foldrun billing` | the account's balance, whether billing is on at all, what the platform is currently waiving, and the recent ledger entries with what each was for — a run names its workspace, flow and run id; an adjustment carries its own note. `--limit <n>` shows more. `statement [YYYY-MM]` is a month of the ledger (this month by default) — `--csv` for the file an accountant wants, to stdout or `--file <path>`. `wallet` is the burn, the runway and auto top-up; `wallet set auto-top-up --threshold <usd> --amount <usd>` turns it on (a refill of 5–500), `set auto-top-up off` turns it off, `set email <address>` is where receipts go. `details` is who invoices are made out to; `details set --name "…" --abn … --address "line1, city, state, postcode, AU" --email …` changes it, merged with what is there. `portal` prints a link to Stripe's billing portal. Changing the wallet, the details, and the portal are the account owner's; anyone else is told so |
 | `foldrun billing plans` | the Plans page: every plan with its monthly fee, credits, runs at once and workspaces, which one the account is on and this cycle's credits left (`GET /api/billing/plans`). `billing plan <id>` chooses one — a first plan answers with Stripe's checkout page, a change on a live plan is prorated at Stripe at once (asks first; `--yes`); `plan cancel` stops it at the end of the cycle, `plan resume` undoes that until then (`POST`/`DELETE /api/billing/subscribe`) |
@@ -145,9 +145,7 @@ claude.ai or Claude Code there, nor any MCP configuration on disk.
 | `foldrun flags` | the feature flags for this account: each one `on` or `off` and why — `account` (set for this account), `global` (set for every account), `rollout` (a share of accounts, with its percentage) or `default` — and what it does. Read-only: only the platform's super admin changes a flag, in the console. `--json` for the API's answer as it came. See [Feature flags](feature-flags.md) |
 | `foldrun history [path]` | every change to a deployed workspace, newest first: revision id, when, who, the message and the files. A path narrows it to one file; `--id <revision>` prints that revision as diffs; `--limit <n>`; `--to <workspace>` |
 | `foldrun history restore <path> --id <revision>` | the History drawer's **Restore this version**: the file is rewritten with that revision's text as a new revision, `restored <rev> from history`, so the restore is itself undone the same way. Shows the diff against the file now and asks (`--yes`, `--dry-run`); sent with `ifMatch`, so a file that changed since is refused (`--to`) |
-| `foldrun repo ls` | a workspace's repository: main, its branches and tags with their last commit, and the mirror. `repo diff <branch>` is what a branch changes against main; `repo deploy <commit\|branch\|tag>` makes that tree live (a rollback is a new commit on main, itself undoable); `repo merge <branch>` merges into main and deploys. Deploy and merge ask first (`--yes` with no terminal) and print the check issues or the run in flight that refused them |
-| `foldrun repo rm-branch <branch>` | delete a branch (asks; `--yes`). `repo mirror <git-url>` sends every push to main there too, with the workspace's `MIRROR_TOKEN` (`repo mirror off` stops it); `repo mirror-now` pushes main now and prints what the remote said (`--to`) |
-| `foldrun restore <workspace> --to <commit\|time\|age>` | put a workspace's source back as it was then — `--to` is a commit or its prefix, a branch or tag, a date/time (the last commit at or before it) or an age (`90m`, `12h`, `3d`, `2w`). Always shows the change first (`--dry-run`: the full diff and nothing else); the restore asks for the workspace's name typed back (`--yes` with no terminal) and sends the removals it showed, so a file added in between refuses it. A new commit on main, so it prints the `foldrun restore … --to <from>` that undoes it. Runs, `state/`, storage and secrets are not touched. See [Backups and restore](backups-and-restore.md) |
+| `foldrun restore <workspace> --to <revision\|time\|age>` | put a workspace's source back as it was then — `--to` is a revision id (`r-…`, from `foldrun history`), the commit a deploy named, a date/time (the last revision at or before it) or an age (`90m`, `12h`, `3d`, `2w`). Always shows the change first (`--dry-run`: the full diff and nothing else); the restore asks for the workspace's name typed back (`--yes` with no terminal) and sends the removals it showed, so a file added in between refuses it. A new revision, so it prints the `foldrun restore … --to <from>` that undoes it. Runs, `state/`, storage and secrets are not touched. See [Backups and restore](backups-and-restore.md) |
 | `foldrun backups` | how the account is backed up: the schedule, how many are kept, the last snapshot (verified? copied off the server? encrypted?), the snapshots that hold the account, each marked encrypted or not, each workspace's last change, and earlier restore requests (`--limit`, `--json`). `backups request --what runs\|state\|storage\|everything --at "<when>" [--to <workspace>] [--backup <id>] [--note "…"]` asks the platform team for a restore from a snapshot — recorded and emailed; nothing is restored until they do it. `backups requests` lists every request this account has made, and where each stands (`GET /api/account/backups/requests`, `--json`) |
 | `foldrun accounts` | every account signed in on this machine, and which one a bare command acts as. `foldrun profiles` is the same command |
 | `foldrun use <name>` | act as one of them from here on. `foldrun switch <name>` is the same command |
@@ -214,7 +212,6 @@ claude.ai or Claude Code there, nor any MCP configuration on disk.
 | `--client-id` / `--client-secret` | `connect`: the OAuth app; prompted when omitted, the secret never echoed |
 | `--port <n>` | `connect`: the loopback port (default 8642) |
 | `--role <r>` | `keys create`: `viewer`, `editor` (default) or `admin` |
-| `--for <workspace>` | `keys create`: a deploy key for one workspace; `--access read` or `write` |
 | `--expires <span>` | `keys create`: when it stops working — `30d`, `90d`, `365d` or `never` (default) |
 | `--grace <span>` | `keys rotate`: keep the old key working for `1h` or `24h` (default `0`: revoked now) |
 | `--force` | `deploy`: deploy while runs are in flight. `pull`, `storage get`: overwrite local files |
@@ -292,8 +289,7 @@ admin's: a key is never an owner.
 installation; the last one signed in to is the default afterwards, and
 `--url` on any command picks another. `foldrun login --token <key>` stores a
 key made in the dashboard instead of opening a browser — for a machine with
-none, or to hold a deploy key for one workspace — after checking that it
-works.
+none — after checking that it works.
 
 `foldrun whoami` says who the platform thinks you are and where the
 credential came from. `foldrun logout` forgets the key and, when `login`
@@ -301,8 +297,8 @@ made it, revokes it.
 
 **In CI, set `FOLDRUN_TOKEN`** rather than logging in: the environment beats
 the file, so a job with a key in its variables never reads one from disk.
-`foldrun keys create ci --for leads --access write` makes a key that can only
-`git push` that one workspace.
+`foldrun keys create ci --workspaces leads` makes a key that opens that one
+workspace and nothing else on the account.
 
 ## Signing in to a site, for an agent
 
@@ -478,7 +474,6 @@ foldrun logs --to publish-desk     # what ran there lately
 foldrun open runs                  # the same, in the browser
 ```
 
-A push to any branch other than main previews it: the platform deploys the
-branch's tree to `<workspace>-preview-<branch>` and runs its evals there.
-Previews never fire on a schedule, read the source workspace's secrets, and
-disappear when the branch does.
+Previews of a branch come back with the GitHub and GitLab app; until then a
+second workspace (`foldrun deploy --to leads-try`) is the place to try a
+change.

package/docs/deploying.md

@@ -1,9 +1,9 @@
 # Deploying
 
-A workspace deploys by pushing files. Two doors, one mechanism: `foldrun
-deploy` from a folder, or `git push` to the remote every workspace has.
-Both are checked before anything goes live, both refuse to swap files under
-a run in flight, and neither touches what the platform owns.
+A workspace deploys by sending its files: `foldrun deploy` from a folder,
+from your laptop or from CI. Every deploy is checked before anything goes
+live, refuses to swap files under a run in flight, and never touches what
+the platform owns.
 
 ## From a folder
 
@@ -15,67 +15,56 @@ foldrun deploy --to leads --commit $(git rev-parse HEAD)
 ```
 
 In CI there is no browser: set `FOLDRUN_URL` and `FOLDRUN_TOKEN` (a key from
-Settings → API keys, or `foldrun keys create`) and the same commands run.
+Settings → API keys, or `foldrun keys create`) and the same commands run. A
+key for CI should open the one workspace it deploys:
+`foldrun keys create ci --workspaces leads`.
 
-## From git
+`--commit` records which commit of your own repository the files came from;
+the workspace page and its History show it.
 
-Every workspace is a git remote:
+## Your own GitHub or GitLab
 
-```sh
-git clone https://foldrun:<api-key>@app.example.com/git/<account>/<workspace>.git
-# edit, commit
-git push origin main                     # deploys, and runs the evals
-```
-
-Any username, an API key as the password. A **deploy key** — minted for one
-workspace, read or write, with `foldrun keys create ci --for <workspace>
---access write` or on the Settings page — is what a CI job or a contractor
-should hold; it is refused on every other workspace and on every other route.
-
-Push a branch other than `main` and you get a **preview**: a workspace named
-`<workspace>-preview-<branch>` deployed from that branch, with its evals run
-there, its schedules never fired, and its source's secrets. Deleting the
-branch deletes it.
+Keep the folder in your own repository and deploy it from CI with the
+commands above. A connected app — a push to your main branch deploys,
+other branches become previews, a check on every commit — is coming, for
+GitHub first, then GitLab. Until 17 October 2026 every workspace was also a
+git remote on the platform, with deploy keys, branch previews, a mirror and
+a GitHub push webhook; those went, and history moved to the platform's own
+snapshots (below).
 
 ## What a deploy checks
 
 The tree is validated the way `foldrun check` validates it — a step naming an
 agent that does not exist, a tool that resolves to nothing, a knowledge
-concept with no `type:` — and a push with issues is refused with the list.
-Git says so at push time; the workspace on disk is unchanged.
+concept with no `type:` — and a deploy with issues is refused with the list.
+The workspace on disk is unchanged.
 
 ## What a deploy never touches
 
 `runs/`, `state/`, `secrets.json`, and any memory an agent wrote that the
-push does not mention. A deploy that reverted what an agent learned would
+deploy does not mention. A deploy that reverted what an agent learned would
 make every run a little dumber, and a deploy that reset a cursor would make
 the next run redo a fortnight.
 
 ## Runs in flight
 
-A push while a run is in flight — including one parked at an approval gate
-— is **accepted but not applied**. Git warns at push time, and the platform
-applies it the moment those runs finish. Swapping files under a running flow
+A deploy while a run is in flight — including one parked at an approval gate
+— is refused, saying which runs hold it. Swapping files under a running flow
 would mean step 3 reads agents step 1 never saw. `foldrun deploy --force`
 overrides that when you mean it.
 
 ## History and rollback
 
-Every change to a workspace is a revision — a push, a dashboard edit, an
-agent's memory write — with who, when, and a diff, on the workspace's
-History page and at `/api/workspaces/<ws>/history`. A deploy's revision id
-is its commit.
+Every change to a workspace is a revision — a deploy, a dashboard edit, an
+import — with who, when and a diff, on the workspace's History page and at
+`/api/workspaces/<ws>/history`. Every revision also keeps a snapshot of the
+whole source as it stood just after it: the platform's own deploy history,
+so rolling back never needs a repository.
 
-A rollback is a deploy of an earlier ref (`POST …/repo {action: deploy, ref}`
-or the History page), and it lands as a **new commit on `main`** — history
-moves forward, never rewrites. **Preview** beside "Deploy this commit" (and
-"Preview deploy" beside a branch's "Merge & deploy" on the Repository page)
+A rollback is **Roll back to this** on a History row, or
+`foldrun restore <ws> --to <revision|time|age>`, and it lands as a **new
+revision** — history moves forward, never rewrites. **Preview** beside it
 shows first what it would change, add and remove, with diffs, and any run in
 flight that would hold it — the restore dry run
-(`POST …/restore {to, dryRun: true}`), which is the same operation.
-
-## Mirroring
-
-A workspace can mirror to a repository you host — GitHub, GitLab — over
-https with a token held as the `MIRROR_TOKEN` secret. The platform's remote
-stays the mechanism; the mirror is the copy you read elsewhere.
+(`POST …/restore {to, dryRun: true}`), which is the same operation. See
+[Backups and restore](backups-and-restore).

package/docs/flows.md

@@ -338,7 +338,7 @@ normal outcome, recorded as one.
 | `sla` | how long a run is expected to take; past it, one notification |
 | `approvers` | who may decide this flow's gates — addresses, or `admins` |
 | `approve_within` | how long a gate waits before the run is rejected |
-| `live` | `true` to make this flow's runs real where the platform would otherwise make them [test runs](runs#test-runs): in a preview workspace, and as an eval's subject. Only ever an opt-out of the safe default |
+| `live` | `true` to make this flow's runs real where the platform would otherwise make them [test runs](runs#test-runs): as an eval's subject. Only ever an opt-out of the safe default |
 
 Every duration here is written the way `wait:` is — `45s`, `10m`, `2h`, `3d`,
 or bare seconds — and capped at thirty days.
@@ -481,12 +481,11 @@ almost never means "run two". `queue` starts it but holds it until the live one
 finishes. Unset, runs may overlap.
 
 `priority:` decides where the flow's runs stand when the platform has more
-runs than slots. `high` is claimed before the round-robin, `low` after it,
-`normal` (unset) takes its turn. It adds to the account's own `priority:`
-(the plan's lane, set in the account's `AGENTS.md`), so a high flow on a low
-account is normal. The account's `concurrency:` still bounds how many of its
-runs are live at once — a high lane jumps the queue, it does not hold the
-fleet.
+runs than slots. Accounts take turns first, weighted by lane (see [Budgets
+and billing](budgets-and-billing)), and among runs level on that, `high` goes before `normal` (unset) and `normal`
+before `low`. It adds to the account's lane, so a high flow on a low account
+is normal. The account's `concurrency:` still bounds how many of its runs are
+live at once.
 
 ## Model resolution
 

package/docs/glossary.md

@@ -20,8 +20,8 @@ checks and headlines read.
 a blog desk, a Reddit desk — its agents and flows, running on a schedule.
 Nothing in the format is called a desk; it is a workspace.
 
-**deploy** — pushing a workspace's source tree to the platform, by
-`foldrun deploy` or `git push`. Never touches runs, state, secrets or memory.
+**deploy** — sending a workspace's source tree to the platform with
+`foldrun deploy`. Never touches runs, state, secrets or memory.
 
 **eval** — a test for an agent or a flow: a task and what a good answer
 must contain. Runs on every push.

package/docs/introduction.md

@@ -34,7 +34,7 @@ The design bets on three things:
 | **Locally** | `npm install -g foldrun` and a model key | everything on your machine; no account, no server |
 | **Hosted** | an account | ours: schedules, sandboxes, a vault, a team |
 
-The same workspace moves between them with `foldrun deploy` or a `git push`.
+The same workspace moves between them with `foldrun deploy`.
 Start locally; that is where every workspace should be born. The CLI and
 runtime are free from npm; the platform is not distributed — see
 [Running it yourself](self-hosting).

package/docs/runs.md

@@ -17,6 +17,7 @@ Each run holds its steps in group order. A step carries:
 | `data` | the parsed value, for a step with `output: json` |
 | `events` | tool calls, script runs with their timing, verify verdicts, refusals |
 | `costUsd`, `tokens`, `computeSecs`, `startupSecs` | what it cost and how long the sandbox lived — **summed across its attempts** |
+| `startup` | where the step's first seconds went: when each start-up phase ended, in seconds since the step started — `services` (the account's search/browser pods up), `room` (room on the cluster to start — see [Budgets and billing](budgets-and-billing)), `applied` (sandbox created), `ready`, `files` (workspace copied in), `go` (step released), `shim`, `system` (system packages restored), `driver`, `imports`, `tools` (runtime and tools built) and `model` (the model's first text or tool call). Only the phases the step went through; `null` for a step that ran in-process, absent before 17 Oct 2026. The last attempt's |
 | `image` | which runner image the step's sandbox ran (isolated runs on a cluster): `variant` `full` or `slim`, `why`, and `pod: true` when a browsing step ran slim and browsed through the account's browser pod ([slim steps and a lost pod](tools#slim-steps-and-a-lost-pod)) |
 | `browserPod` | on a step that browsed through the pod from slim: `reconnects` (tries), `reconnected` (how many got through: the call went on after it) and `closedAgain` (how many reached the pod only for the call to drop again at once, when any did); when the pod was lost, `lost` (`cause` `lost` or `needs-full`, and `detail`) and `writes` (what the step had written by then, worded); then `fallback: "browser pod lost; re-ran on full"` when it had only read and ran again on the full image, or `failure` — `browser pod died after the step had written <what>` — when it had written and was not re-run |
 | `tries` | one row per attempt, oldest first (and a `status: "lost"` row, `image: "slim"`, before the full re-run when the browser pod was lost under a slim step that had only read — see [tools](tools#slim-steps-and-a-lost-pod)): `n` (the try, numbered in the order they ran), `attempt` (the step's attempt it belongs to, only when that is not `n` — the full re-run after a lost slim try 1 is `n: 2, attempt: 1`), `status`, `costUsd`, `tokens`, `computeSecs`, `startedAt`, `finishedAt`, the attempt's `image` and its `browserPod` line when it had one, and the attempt's last `error` when it failed. A `retry: 2` step that failed twice and then passed has three rows, and its `costUsd` is all three — the run's spend, the flow's `budget:` and the bill read the step's figure, so the figure is the total. A retry is handed what is left of the budget after the failed attempt spent, and nothing left means no retry, said on the record |
@@ -47,6 +48,8 @@ one bar per step with its tool calls marked in milliseconds, so a slow run
 says which step was slow. Every step shows its instruction, what it was
 handed from earlier groups, what it returned, its cost, and how many times it
 reached for a path it was not allowed and was refused (see [Security](security)).
+A **start-up** chip in a step's header says how long it took the step to
+reach the model's first word; hover it for each phase's share.
 
 The page follows the run as it moves, gates included, without a reload: a
 **live** dot beside the status says the stream is connected (amber while it
@@ -124,9 +127,8 @@ cannot reach it.
 Start one with the **Test run** checkbox on the Run button, `foldrun run
 <flow> --test` locally, `foldrun invoke <flow> --test` on a platform, or
 `POST .../flows/<flow>/run` with `{ "test": true }`. An eval's runs are test
-runs, and so is every run in a preview workspace (`<ws>-preview-<branch>`),
-unless the eval or the flow says `live: true` in its frontmatter — the safe
-default is opted out of, never into. A re-run of a test run, or a run started
+runs unless the eval or the flow says `live: true` in its frontmatter — the
+safe default is opted out of, never into. A re-run of a test run, or a run started
 from one of its steps, stays a test.
 
 What the platform does on a test run, in the order a step meets it:

package/docs/self-hosting.md

@@ -51,8 +51,7 @@ foldrun login
 foldrun deploy                           # this folder → a workspace with the same name
 ```
 
-Or push it: every workspace on the platform is a git remote. Nothing about
-the folder changes. What the platform adds is the operating around it —
+Nothing about the folder changes. What the platform adds is the operating around it —
 [Scheduling](scheduling), [Runs](runs) in gVisor sandboxes,
 [Secrets](secrets) in a vault, [Notifications](notifications),
 [Budgets and billing](budgets-and-billing), [Team and access](team-and-access).
@@ -61,6 +60,6 @@ the folder changes. What the platform adds is the operating around it —
 
 On your machine: in the folder. On the platform: your workspace's files and
 every run's record, on our data volume and in the file store, readable
-through the dashboard and the API, exportable as a git clone. A deploy never
+through the dashboard and the API, exportable as a .zip (`foldrun export`). A deploy never
 touches what an agent learned or a run recorded. See [Storage and
 sharing](storage-and-sharing) and [Security](security).

package/docs/team-and-access.md

@@ -44,17 +44,16 @@ connection, or returned as a link to pass on yourself.
 A key is minted with a role (`editor` unless you say otherwise) and acts as
 the account with that role. It can never be wider than the person who made
 it: not a higher role, and not a workspace they cannot open — a key minted
-by someone scoped to two workspaces is scoped to those two. The git remote
-honours the same scope: pushing needs write on that workspace, and pushing
-the library needs admin. Two things a key cannot do: act against a named
+by someone scoped to two workspaces is scoped to those two. Two things a key cannot do: act against a named
 member — inviting, re-roling, removing, transferring need a signed-in person,
 because a key names an account and never a who — and exceed its role.
 A scoped admin sees and revokes only keys inside its own scope; a key wider
 than that, the owner's included, is not in its list.
 
-**Deploy keys** are keys scoped to one workspace's git remote, read or write.
-They clone and push that workspace and are refused everywhere else, which is
-what a CI job or a contractor's checkout should hold.
+A CI job or a contractor should hold a key that opens one workspace —
+`foldrun keys create ci --workspaces leads`, or Settings → API keys. (Deploy
+keys, for the platform's own git, went with it on 17 October 2026; one
+minted before opens nothing.)
 
 A key **is** its account: the platform reads the account off the key, so one
 account's key can never reach another's workspaces. Someone who looks after

package/docs/tools.md

@@ -1787,6 +1787,13 @@ Run `scripts/pace.py --spent <amount> --budget <amount>` from this skill's
 folder, then report the verdict in one sentence.
 ```
 
+| field | |
+|---|---|
+| `name` | defaults to the folder's name |
+| `description` | **required**: what it does and when to use it. A skill without one is never loaded, because the model chooses skills by their descriptions |
+| `when` | run tags: the skill is loaded only on runs carrying one of them |
+| `license`, `compatibility`, `metadata`, `allowed-tools` | the Agent Skills format's optional fields. Accepted and carried, not read by foldrun |
+
 Only names and descriptions sit in context; the agent reads the full file when
 a task matches. So an agent can carry many skills for a few tokens each — which
 is the reason to move a procedure out of `agent.md` in the first place.

package/docs/workspaces.md

@@ -219,11 +219,10 @@ regenerated every run is `storage/`; a value accumulated across runs is
 
 ## What a deploy touches
 
-A deploy — `foldrun deploy`, or a `git push` to the workspace's remote —
-replaces the source tree: agents, flows, tools, skills, evals, knowledge,
+A deploy — `foldrun deploy` — replaces the source tree: agents, flows, tools, skills, evals, knowledge,
 `AGENTS.md`. It **never** touches `runs/`, `state/`, `secrets.json`, or any
-memory an agent wrote that your push does not mention. Those belong to the
-platform, not to git, and a deploy that reverted what an agent learned would
+memory an agent wrote that your deploy does not mention. Those belong to the
+platform, not to your source, and a deploy that reverted what an agent learned would
 make every run a little dumber.
 
 The agent engine's own files are not workspace content either. Each step
@@ -234,14 +233,9 @@ They stay in the sandbox: never copied back, never copied in. (Your own
 `.claude/agents/*.md` at the workspace root is different — a Claude Code
 subagent you wrote, deployed as an agent.)
 
-A push while a run is in flight is accepted and applied when the run
-finishes; git tells you so at push time. A run parked at an approval gate
-counts as in flight. See [Deploying](deploying).
+A deploy while a run is in flight is refused, saying which runs hold it; a
+run parked at an approval gate counts as in flight. See [Deploying](deploying).
 
-## Previews
-
-Push a branch instead of `main` and the platform deploys a copy of the
-workspace named `<workspace>-preview-<branch>` from that branch's tree, runs
-its evals there, and never fires its schedules. It reads the source
-workspace's secrets. Deleting the branch deletes the preview. It is how a
-change to a live desk gets tried without touching the live desk.
+Trying a change to a live desk without touching it is a second workspace —
+`foldrun deploy --to <workspace>-try`. Branch previews come back with the
+GitHub and GitLab app.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "foldrun",
-  "version": "1.2.0",
+  "version": "2.0.0",
   "description": "Agents are just folders. Write them, check them, run them — on your machine.",
   "license": "SEE LICENSE IN LICENSE",
   "type": "module",
@@ -11,7 +11,7 @@
     "node": ">=22"
   },
   "dependencies": {
-    "@foldrun/core": "^1.3.0"
+    "@foldrun/core": "^2.0.0"
   },
   "files": [
     "bin",
@@ -21,7 +21,7 @@
   ],
   "scripts": {
     "e2e": "FOLDRUN_E2E=1 FOLDRUN_DATA=$(mktemp -d /tmp/foldrun-e2e-XXXXXX) node --test --test-timeout=300000 tests/e2e.test.ts",
-    "test": "FOLDRUN_DATA=$(mktemp -d /tmp/foldrun-test-XXXXXX) node --test tests/cli-account.test.ts tests/model-credential.test.ts tests/cli-approvals.test.ts tests/cli-stop.test.ts tests/cli-account-settings.test.ts tests/cli-schedule.test.ts tests/cli-billing.test.ts tests/cli-storage.test.ts tests/cli-scaffold.test.ts tests/cli-secrets.test.ts tests/cli-site-login.test.ts tests/cli-check-library.test.ts tests/cli-check-timezone.test.ts tests/cli-check-frontmatter.test.ts tests/cli-agent-import.test.ts tests/cli-check-subagents.test.ts tests/cli-connect.test.ts tests/cli-accounts.test.ts tests/cli-remote.test.ts tests/cli-stream.test.ts tests/cli-doctor.test.ts tests/cli-tool-test.test.ts tests/cli-agent-run.test.ts tests/cli-check-remote.test.ts tests/cli-shares.test.ts tests/cli-triggers.test.ts tests/cli-providers.test.ts tests/cli-rerun-put.test.ts tests/cli-guide.test.ts tests/cli-runtimes.test.ts tests/cli-deploy-safety.test.ts tests/cli-operator.test.ts tests/cli-flow-patterns.test.ts tests/cli-flow-rm-step.test.ts tests/cli-flow-dup-step.test.ts tests/cli-flow-write-stale.test.ts tests/cli-agent-link-stale.test.ts tests/cli-parity.test.ts tests/cli-invoke-inputs.test.ts tests/cli-audit-keys.test.ts tests/cli-version.test.ts tests/cli-check-web-warnings.test.ts tests/cli-report-image.test.ts tests/cli-check-workspace-paths.test.ts tests/cli-parity-dashboard.test.ts tests/cli-api-standards.test.ts tests/cli-backups-onboarding.test.ts tests/cli-check-limits.test.ts tests/cli-gallery.test.ts tests/cli-status-platform.test.ts tests/cli-webhooks-notifications.test.ts tests/cli-flags.test.ts tests/cli-api-coverage.test.ts tests/cli-hooks.test.ts tests/cli-release.test.ts tests/cli-terminal.test.ts tests/cli-network.test.ts tests/cli-assistant.test.ts tests/cli-check-scan.test.ts",
+    "test": "FOLDRUN_DATA=$(mktemp -d /tmp/foldrun-test-XXXXXX) node --test tests/cli-account.test.ts tests/model-credential.test.ts tests/cli-approvals.test.ts tests/cli-stop.test.ts tests/cli-account-settings.test.ts tests/cli-schedule.test.ts tests/cli-billing.test.ts tests/cli-storage.test.ts tests/cli-scaffold.test.ts tests/cli-secrets.test.ts tests/cli-site-login.test.ts tests/cli-check-library.test.ts tests/cli-check-timezone.test.ts tests/cli-check-frontmatter.test.ts tests/cli-agent-import.test.ts tests/cli-check-subagents.test.ts tests/cli-connect.test.ts tests/cli-accounts.test.ts tests/cli-remote.test.ts tests/cli-stream.test.ts tests/cli-doctor.test.ts tests/cli-tool-test.test.ts tests/cli-agent-run.test.ts tests/cli-check-remote.test.ts tests/cli-shares.test.ts tests/cli-triggers.test.ts tests/cli-providers.test.ts tests/cli-rerun-put.test.ts tests/cli-guide.test.ts tests/cli-runtimes.test.ts tests/cli-deploy-safety.test.ts tests/cli-operator.test.ts tests/cli-flow-patterns.test.ts tests/cli-flow-rm-step.test.ts tests/cli-flow-dup-step.test.ts tests/cli-flow-write-stale.test.ts tests/cli-agent-link-stale.test.ts tests/cli-parity.test.ts tests/cli-invoke-inputs.test.ts tests/cli-audit-keys.test.ts tests/cli-version.test.ts tests/cli-check-web-warnings.test.ts tests/cli-report-image.test.ts tests/cli-check-workspace-paths.test.ts tests/cli-parity-dashboard.test.ts tests/cli-api-standards.test.ts tests/cli-backups-onboarding.test.ts tests/cli-check-limits.test.ts tests/cli-gallery.test.ts tests/cli-status-platform.test.ts tests/cli-webhooks-notifications.test.ts tests/cli-flags.test.ts tests/cli-api-coverage.test.ts tests/cli-hooks.test.ts tests/cli-release.test.ts tests/cli-terminal.test.ts tests/cli-network.test.ts tests/cli-assistant.test.ts tests/cli-check-scan.test.ts tests/cli-published.test.ts",
     "release": "node scripts/release.mjs",
     "typecheck": "tsc -p tsconfig.json",
     "docs:sync": "node scripts/sync-docs.mjs",

package/src/commands.mjs

@@ -999,6 +999,10 @@ function narrowCheck(findings, root, opts, label, accountRoot = root) {
     out = out.filter((f) => want.has(f.rule) || want.has(f.rule.split("/")[0]) || want.has(categoryOf(f.rule)));
   }
   if (opts.security) out = out.filter((f) => SECURITY_CATEGORIES.has(categoryOf(f.rule)));
+  // check's own skill rule already says a skill has no description, as an
+  // error; the schema's note would say it twice. Only when that error is
+  // still in the report — `--rule config/missing-field` keeps the note.
+  out = out.filter((f) => !(f.rule === "config/missing-field" && out.some((g) => g.file === f.file && g.rule === "skill/config" && /no description|needs name and description/.test(g.message))));
   const file = path.join(root, ".foldrun", "check-baseline.json");
   if (opts.writeBaseline) {
     const created = new Date().toISOString();
@@ -3732,8 +3736,7 @@ const sleep = (ms) => new Promise((r) => setTimeout(r, ms));
  * asks "is this your terminal?"; the person says yes; the key that makes
  * lands here and is kept in ~/.foldrun/credentials.json. No key to copy,
  * nothing pasted into a shell history. `--token` skips the browser and
- * stores a key made in the dashboard — for a machine with no browser, or a
- * deploy key for one workspace.
+ * stores a key made in the dashboard — for a machine with no browser.
  */
 async function login(flags) {
   const url = normaliseUrl(flags.url ?? env("FOLDRUN_URL") ?? defaultPlatform() ?? DEFAULT_PLATFORM);
@@ -3968,8 +3971,7 @@ async function doctor(flags) {
  *
  *   keys ls                          every key, live and revoked
  *   keys create <label> [--role r]   an account key (editor unless said)
- *   keys create <label> --for <ws> [--access read|write]
- *                                    a deploy key: git clone/push for one workspace
+ *   keys create <label> --workspaces <ws>  one that opens that workspace alone
  *   keys revoke <id>
  *   keys create <label> --expires 90d  it stops working in 90 days (30d, 365d, never)
  *   keys rotate <id> [--grace 1h]      a new key, same label/role/scope; the old
@@ -3993,7 +3995,8 @@ async function keysCmd(positional, flags) {
     console.log("");
     const day = (iso) => (iso ? iso.slice(0, 10) : "");
     for (const k of keys) {
-      const what = k.scope ? `deploy · ${k.scope.workspace} (${k.scope.access})` : `${k.role ?? "admin"} · ${k.workspaces ? k.workspaces.join(",") || "no workspaces" : "all workspaces"}`;
+      // A deploy key opened the platform's own git, gone since 17 Oct 2026.
+      const what = k.scope ? "deploy key · opens nothing since the platform's git went — revoke it" : `${k.role ?? "admin"} · ${k.workspaces ? k.workspaces.join(",") || "no workspaces" : "all workspaces"}`;
       const expired = !k.revokedAt && k.expiresAt && Date.parse(k.expiresAt) <= Date.now();
       const state = k.revokedAt ? c.red("revoked") : expired ? c.red("expired") : c.green("live");
       console.log(`  ${state.padEnd(20)} ${k.id}  ${k.prefix}…  ${c.bold(k.label)}  ${c.dim(what)}${k.createdBy ? c.dim(`  by ${k.createdBy}`) : ""}`);
@@ -4008,8 +4011,6 @@ async function keysCmd(positional, flags) {
   if (verb === "create" || verb === "new") {
     if (!arg) throw new Error("what is the key for? foldrun keys create <label>");
     const body = { label: arg };
-    if (typeof flags.for === "string") body.workspace = flags.for;
-    if (typeof flags.access === "string") body.access = flags.access;
     if (typeof flags.role === "string") body.role = flags.role;
     // --expires 30d|90d|365d|never; unsaid, the key never expires.
     if (typeof flags.expires === "string") body.expires = flags.expires;
@@ -6207,10 +6208,34 @@ function filesWritten(run) {
   return [...out].filter(Boolean);
 }
 
+/** Trim what prose puts around a URL: trailing markdown/punctuation and a
+ *  trailing `)` that nothing in the URL opened — so `(url)` comes back bare,
+ *  but a wikipedia `..._(bar)` keeps its balanced `)`. `[` and `]` are not
+ *  URL chars, so a markdown `](url)` never carries a bracket in. */
+function trimUrl(u) {
+  let prev;
+  do {
+    prev = u;
+    u = u.replace(/[.,;:!?*_~`]+$/, "");
+    if (u.at(-1) === ")" && u.split(")").length > u.split("(").length) u = u.slice(0, -1);
+  } while (u !== prev);
+  return u;
+}
+
 /** Every address a run said it published to, from its summary and conclusions. */
-function published(run) {
+export function published(run) {
   const text = [run.summary ?? "", ...(run.steps ?? []).map((s) => s.conclusion ?? s.result ?? "")].join("\n");
-  return [...new Set((text.match(/https?:\/\/[^\s)"'<>\]]+/g) ?? []).map((u) => u.replace(/[.,;]+$/, "")))];
+  return [...new Set((text.match(/https?:\/\/[^\s"'<>`\[\]]+/g) ?? []).map(trimUrl).filter(Boolean))];
+}
+
+/** How long the step took to reach the model's first word — the record's
+ *  `startup` phases (seconds since the step started); null before 17 Oct
+ *  2026 and for in-process steps. */
+export function startupLabel(step) {
+  const ph = step.startup;
+  if (!ph || typeof ph !== "object") return null;
+  const end = typeof ph.model === "number" ? ph.model : Math.max(...Object.values(ph).filter((v) => typeof v === "number"));
+  return Number.isFinite(end) ? `start-up ${end.toFixed(1)}s` : null;
 }
 
 /** Which runner image a step ran on, as the run page's chip says it:
@@ -6303,6 +6328,7 @@ async function reportCmd(runId, flags, layout) {
       step.status,
       step.attempts > 1 ? `${step.attempts} attempts` : null,
       imageLabel(step),
+      startupLabel(step),
       step.costUsd ? `$${step.costUsd.toFixed(4)}` : null,
       step.startedAt && step.finishedAt
         ? humanDuration(Date.parse(step.finishedAt) - Date.parse(step.startedAt))
@@ -8166,6 +8192,8 @@ function sinceDays(flags, fallback) {
 }
 
 const secs = (n) => (n == null ? "—" : humanDuration(n * 1000));
+/** Seconds that are often under one — start-up phases. */
+const fine = (n) => (n == null ? "—" : n < 1 ? `${Math.round(n * 1000)}ms` : `${n.toFixed(2)}s`);
 const pct = (a, b) => (b ? `${Math.round((a / b) * 100)}%` : "—");
 
 /** One workspace's observability report, as the Observe page reads it. */
@@ -8182,6 +8210,9 @@ function printObservation(o) {
   table("flows", ["flow", "runs", "failed", "p50", "p95", "cost"], (o.flows ?? []).map((f) => [f.flow, f.runs, f.failed, secs(f.seconds?.p50), secs(f.seconds?.p95), `$${f.costUsd.toFixed(2)}`]));
   table("agents", ["agent", "steps", "failed", "retried", "skipped", "p95", "cost"], (o.agents ?? []).map((a) => [a.agent, a.steps, a.failed, a.retried, a.skipped, secs(a.seconds?.p95), `$${a.costUsd.toFixed(2)}`]));
   table("tools", ["tool", "calls", "errors", "p95", "used by"], (o.tools ?? []).map((t) => [t.name, t.calls, t.errors, t.ms?.p95 == null ? "—" : `${Math.round(t.ms.p95)}ms`, (t.agents ?? []).join(", ")]));
+  // Where a step's first seconds go, phase by phase (FOL-29): each phase's
+  // own share, and when it was done counted from the step's start.
+  table("start-up", ["start-up", "n", "took p50", "p95", "done by p50", "p95"], (o.startup ?? []).map((p) => [p.phase, p.took?.n ?? 0, fine(p.took?.p50), fine(p.took?.p95), fine(p.at?.p50), fine(p.at?.p95)]));
   const fails = (o.failures ?? []).slice(0, 8);
   if (fails.length) {
     console.log(`\n  ${c.dim("recent failures")}`);
@@ -8704,85 +8735,6 @@ async function historyCmd(positional, flags, layout) {
   return 0;
 }
 
-/**
- * `foldrun repo ls | diff <branch> | deploy <ref> | merge <branch>` — the
- * Repository page: branches, what one changes, deploy any commit (a rollback
- * is a new commit on main), merge a branch into main and deploy it.
- */
-async function repoCmd(positional, flags, layout) {
-  const url = platformFor(flags, "repo");
-  const ws = platformWorkspace(flags, layout, "repo");
-  const [verb = "ls", arg] = positional;
-  const base = `/api/workspaces/${enc(ws)}/repo`;
-  if (verb === "ls" || verb === "list") {
-    const r = await remoteCall(url, flags, base);
-    console.log(`\n  ${c.bold(ws)}  ${c.dim(`main ${r.main ? String(r.main).slice(0, 7) : "— nothing committed yet"}`)}`);
-    const refs = (title, list) => {
-      if (!list?.length) return;
-      console.log(`\n  ${c.dim(title)}`);
-      const w = Math.max(...list.map((b) => b.name.length));
-      for (const b of list) console.log(`  ${b.name === "main" ? c.green("●") : c.dim("○")} ${c.bold(pad(b.name, w))}  ${c.dim(String(b.sha).slice(0, 7))}  ${firstLine(b.subject, 60)}  ${c.dim(b.at ? `${ago(b.at)} ago` : "")}`);
-    };
-    refs("branches", r.branches);
-    refs("tags", r.tags);
-    if (r.settings?.mirror) console.log(`\n  ${c.dim(`mirror ${r.settings.mirror}${r.mirror?.at ? ` · last push ${ago(r.mirror.at)} ago${r.mirror.ok === false ? " (failed)" : ""}` : ""}`)}`);
-    console.log(`\n  ${c.dim(`foldrun repo diff <branch> · repo merge <branch> · repo deploy <ref> --to ${ws}`)}\n`);
-    return 0;
-  }
-  if (verb === "diff") {
-    if (!arg) throw new Error("`foldrun repo diff <branch> --to <workspace>` — what it changes against main");
-    const r = await remoteCall(url, flags, `${base}?branch=${enc(arg)}`);
-    if (!r.files?.length) console.log(`\n  ${c.dim(`${arg} changes nothing against main`)}\n`);
-    console.log();
-    for (const f of r.files ?? []) {
-      printOps(f.path, f.diff ?? []);
-      console.log();
-    }
-    return 0;
-  }
-  if (verb === "rm-branch") {
-    if (!arg || arg === "main") throw new Error("`foldrun repo rm-branch <branch> --to <workspace>` — any branch but main");
-    if (!(await sureToDelete(flags, "repo rm-branch", `branch ${arg} in ${ws}`))) return 1;
-    await remoteCall(url, flags, base, { method: "POST", body: JSON.stringify({ action: "delete-branch", branch: arg }) });
-    console.log(`\n  ${c.green("✓")} branch ${arg} deleted ${c.dim(`in ${ws}`)}\n`);
-    return 0;
-  }
-  if (verb === "mirror") {
-    if (!arg) throw new Error("`foldrun repo mirror <git-url> --to <workspace>` (every push to main goes there too, with the workspace's MIRROR_TOKEN) or `repo mirror off`");
-    const r = await remoteCall(url, flags, base, { method: "POST", body: JSON.stringify({ action: "mirror", url: arg === "off" ? null : arg }) });
-    console.log(`\n  ${c.green("✓")} ${r.settings?.mirror ? `main is mirrored to ${r.settings.mirror}` : "no mirror"} ${c.dim(`· ${ws}${r.settings?.mirror ? " · `foldrun repo mirror-now` pushes it now" : ""}`)}\n`);
-    return 0;
-  }
-  if (verb === "mirror-now") {
-    const r = await remoteCall(url, flags, base, { method: "POST", body: JSON.stringify({ action: "mirror-now" }) });
-    const st = r.status;
-    if (!st) {
-      console.log(`\n  ${c.dim(`${ws} has no mirror — \`foldrun repo mirror <git-url> --to ${ws}\` sets one`)}\n`);
-      return 1;
-    }
-    console.log(`\n  ${st.ok ? c.green("✓") : c.red("✗")} mirror ${st.ok ? `has ${String(st.sha ?? "").slice(0, 7)}` : "push failed"}${st.detail ? ` — ${st.detail}` : ""} ${c.dim(ws)}\n`);
-    return st.ok ? 0 : 1;
-  }
-  if (verb !== "deploy" && verb !== "merge") throw new Error(`unknown repo verb "${verb}" — ls, diff <branch>, deploy <ref>, merge <branch>, rm-branch <branch>, mirror <url|off>, mirror-now`);
-  if (!arg) throw new Error(verb === "deploy" ? "`foldrun repo deploy <commit|branch|tag> --to <workspace>`" : "`foldrun repo merge <branch> --to <workspace>`");
-  if (verb === "merge" && arg === "main") throw new Error("main is what a branch merges into — name the branch");
-  console.log(
-    `\n  ${c.yellow("!")} ${verb === "deploy" ? `deploying ${c.bold(arg)} makes it what is live in ${ws} — a new commit on main, which can itself be undone` : `merging ${c.bold(arg)} into main deploys the result to ${ws}`}`,
-  );
-  if (!(await confirmed(flags, `repo ${verb}`, `${verb === "deploy" ? "Deploy" : "Merge"} it? [y/N] `))) {
-    console.log(`\n  ${c.dim(`nothing ${verb === "deploy" ? "deployed" : "merged"}`)}\n`);
-    return 1;
-  }
-  const r = await remoteCall(url, flags, base, { method: "POST", body: JSON.stringify(verb === "deploy" ? { action: "deploy", ref: arg } : { action: "merge", branch: arg }) });
-  if (r.applied) {
-    console.log(`\n  ${c.green("✓")} ${verb === "deploy" ? `${arg} is live` : `${arg} merged and live`} ${c.dim(`in ${ws} · main ${String(r.main ?? r.sha ?? "").slice(0, 7)}`)}\n`);
-    return 0;
-  }
-  console.log(`\n  ${c.red("✗")} not deployed${r.blockedBy ? ` — a run is in flight (${Array.isArray(r.blockedBy) ? r.blockedBy.join(", ") : r.blockedBy})` : ""}`);
-  for (const i of r.issues ?? []) console.log(`  ${c.red("error")}  ${c.bold(i.where)}  ${i.message}`);
-  console.log();
-  return 1;
-}
 
 /**
  * `foldrun onboarding` — the account's getting-started steps, each worked
@@ -8877,7 +8829,7 @@ async function backupsCmd(positional, flags) {
     }
   }
   if (b.workspaces?.length) {
-    console.log(`\n  ${c.dim("restore a workspace's source yourself — foldrun restore <workspace> --to <commit|time|3d> --dry-run")}`);
+    console.log(`\n  ${c.dim("restore a workspace's source yourself — foldrun restore <workspace> --to <revision|time|3d> --dry-run")}`);
     const w = Math.max(...b.workspaces.map((x) => x.name.length));
     for (const x of b.workspaces) {
       console.log(`  ${pad(x.name, w)}  ${x.lastChange ? c.dim(`last change ${when(x.lastChange.at)} — ${firstLine(x.lastChange.message, 50)}`) : c.dim("no history yet")}`);
@@ -8891,8 +8843,12 @@ async function backupsCmd(positional, flags) {
   return 0;
 }
 
+/** A revision as the CLI prints it: a git sha shortened as git does, a
+ *  platform revision id (r-…) whole — it is what --to takes back. */
+const revShort = (id) => (/^[0-9a-f]{40}$/.test(String(id)) ? String(id).slice(0, 7) : String(id));
+
 /**
- * `foldrun restore <workspace> --to <commit|branch|tag|time|age> [--dry-run]`
+ * `foldrun restore <workspace> --to <revision|time|age> [--dry-run]`
  * — the workspace's source as it was then. Always shows the change first;
  * the restore asks for the workspace's name typed back (or --yes), and
  * sends the removals it showed, so a file added in between refuses it.
@@ -8900,11 +8856,11 @@ async function backupsCmd(positional, flags) {
 async function restoreCmd(positional, flags) {
   const url = platformFor(flags, "restore");
   const ws = positional[0];
-  if (!ws) throw new Error("`foldrun restore <workspace> --to <commit|time|3d> [--dry-run]`");
-  if (typeof flags.to !== "string" || !flags.to.trim()) throw new Error("--to <commit, date or age> — the point to restore to, e.g. --to 2026-09-28T14:00 or --to 3d");
+  if (!ws) throw new Error("`foldrun restore <workspace> --to <revision|time|3d> [--dry-run]`");
+  if (typeof flags.to !== "string" || !flags.to.trim()) throw new Error("--to <revision, date or age> — the point to restore to, e.g. --to 2026-09-28T14:00 or --to 3d");
   const base = `/api/workspaces/${enc(ws)}/restore`;
   const plan = await remoteCall(url, flags, base, { method: "POST", body: JSON.stringify({ to: flags.to, dryRun: true }) });
-  console.log(`\n  ${c.bold(ws)} → ${c.bold(String(plan.to.sha).slice(0, 7))}  ${c.dim(`${when(plan.to.at)} · ${plan.to.by} · ${firstLine(plan.to.message, 60)}`)}`);
+  console.log(`\n  ${c.bold(ws)} → ${c.bold(revShort(plan.to.id ?? plan.to.sha))}  ${c.dim(`${when(plan.to.at)} · ${plan.to.by} · ${firstLine(plan.to.message, 60)}`)}`);
   if (plan.noop) {
     console.log(`  ${c.dim(`${ws} already matches that point — nothing to restore`)}\n`);
     return 0;
@@ -8930,13 +8886,13 @@ async function restoreCmd(positional, flags) {
   }
   const r = await remoteCall(url, flags, base, {
     method: "POST",
-    body: JSON.stringify({ to: plan.to.sha, confirm: ws, expectRemoved: plan.removed }),
+    body: JSON.stringify({ to: plan.to.id ?? plan.to.sha, confirm: ws, expectRemoved: plan.removed }),
   });
   if (r.noop) {
-    console.log(`\n  ${c.dim(`${ws} already matches ${String(plan.to.sha).slice(0, 7)}`)}\n`);
+    console.log(`\n  ${c.dim(`${ws} already matches ${revShort(plan.to.id ?? plan.to.sha)}`)}\n`);
     return 0;
   }
-  console.log(`\n  ${c.green("✓")} ${ws} restored to ${String(r.to.sha).slice(0, 7)} ${c.dim(`· main ${String(r.main ?? "").slice(0, 7)} · undo: foldrun restore ${ws} --to ${String(r.from ?? "").slice(0, 7)}`)}\n`);
+  console.log(`\n  ${c.green("✓")} ${ws} restored to ${revShort(r.to.id ?? r.to.sha)} ${c.dim(`· main ${revShort(r.main ?? "")} · undo: foldrun restore ${ws} --to ${String(r.from ?? "")}`)}\n`);
   return 0;
 }
 
@@ -10413,7 +10369,8 @@ export async function run(command, positional, flags, workspace, layout) {
       if (positional[0] === "restore") return historyRestoreCmd(positional, flags, layout);
       return historyCmd(positional, flags, layout);
     case "repo":
-      return repoCmd(positional, flags, layout);
+      // The platform's own git went on 17 Oct 2026.
+      throw new Error("`foldrun repo` is gone with the platform's own git — `foldrun history` lists a workspace's revisions and `foldrun restore <ws> --to <revision|time|age>` rolls back");
     case "restore":
       return restoreCmd(positional, flags);
     case "backups":