toolroll 0.9.84 → 0.9.86

package/CHANGELOG.md

@@ -1,5 +1,71 @@
 # Changelog
 
+## 0.9.86 — 2026-11-02
+
+- **Old tasks tidy themselves.** A routine's newer run puts away its older
+  ones, a release task goes once its version ships or a newer attempt
+  replaces it, and a "Checks failed on main" notice goes once main passes
+  again. Running work, tasks you filed, and tasks handed to a person are
+  never touched. Each one says why it was put away.
+- **Put away old tasks, in one step.** Needs you → **Put away old tasks**
+  shows exactly what would go and why, grouped, with a box to untick each
+  one; your password puts away exactly that list. **Put away** works on a
+  single task too. Nothing is deleted: the **Archived** view keeps every
+  task's history and has **Restore**. The same from the terminal:
+  `toolroll task tidy --preview`, then the `--apply --digest` command it
+  prints; `task archive`, `task restore`, `task list --view archived`.
+- **Flows can drive a browser, once you allow it.** A flow step that starts a
+  browser (like the nightly journeys) now runs in its sandbox when a person
+  has allowed it: **Allow browser** on the flow page shows the exact script
+  and asks for your password, or `toolroll flows browser <flow> on`. Changing
+  the script ends the approval. Without it, the step waits with one line
+  saying what to allow, instead of crashing.
+- **Deploys no longer stop halfway.** A deploy now proves the release
+  read-only and writes its "deploying" marker separately, so it finishes
+  instead of stopping with "attempt to write a readonly database".
+
+## 0.9.85 — 2026-11-01
+
+- **Point at the exact screenshot.** Choose **Comment** beside a result's
+  screenshot and your note, the chat confirmation and the revision all carry
+  that exact image. In chat, reply to a screenshot and the note keeps it. A
+  screenshot that later stops verifying never blocks you: keep the note
+  without it, and the original stays in history.
+- **Projects → Activity.** See the project's Ready backlog and the last 60
+  days of finished work: revisions, recorded spend and how much of it is
+  known, who completed what, and check outcomes. The lead can read the same
+  report (`get_project_activity`), and so can `toolroll project activity
+  --json`. Unknown costs stay unknown.
+- **youiyoux change requests become tasks by themselves.** In a project that
+  uses youiyoux, each open change request in `.youi/requests` is filed once as
+  a task with its goal, exclusions, files and requirements, and waits for your
+  approval: no mode, grant or schedule approves it. Toolroll writes the task's
+  status beside the request for youiyoux to show, with links to the task and
+  to what needs you (your console address, or this computer's own console).
+  Settings → Integrations has a youiyoux row per project, with **Turn off**.
+- **Approve youiyoux requests from chat, all at once.** Each pass sends one
+  card to your paired chat listing every new task with every word of its
+  terms, with **Approve all** and each task's own **Approve**, two taps each.
+  Only the exact words shown are approved; a task whose terms changed, or that
+  doesn't fit one message, is named and left for Toolroll. Needs approving
+  from chat turned on.
+- **A task shows the youiyoux request it came from**: the request, page,
+  component and file:line, on its page and its approval.
+- **youiyoux options requests: options back on the Screens canvas.** An
+  options request becomes a task that may write one file, its options. Once
+  the result is ready for review, Toolroll copies that file from the result
+  into the project for youiyoux's hub, only when it is safe and never over a
+  file already there. Picking an option or dismissing them in the hub marks
+  the task complete without merging its branch, with who decided what in its
+  history; a task that needs more stays ready for review and says why.
+- **A youiyoux request's status reads done once its task is complete.**
+- **Security updates.** The mail, Slack and Discord libraries and their
+  dependencies are updated, closing five of seven known vulnerabilities. The
+  remaining one sits inside the sandbox library, has no fix yet, and is in a
+  part Toolroll never runs.
+- **A short README**, with guides for the rest and a page written for
+  agents (`docs/agents.md`, `llms.txt`).
+
 ## 0.9.84 — 2026-11-01
 
 - **An honest Spend page, in Settings.** See API dollars, plan usage and