cobro-mcp 0.9.4 → 0.10.0

package/CHANGELOG.md

@@ -4,6 +4,22 @@ All notable changes to this project are documented here. The format follows [Kee
 
 ## [Unreleased]
 
+## [0.10.0] — 2026-09-24
+### Added
+- Batches carry the page they were picked on (batches[].page), and status/done accept an optional batchId so an agent can work through several batches in order.
+- Queue: the panel has two tabs — This page and Queue (N). Drafts from several pages appear as cards (one draft per page); Send delivers them in order, the toolbar shows progress like "Working 1/3", and finished pages collapse into a done row that clears when you pick again.
+- The browser moves to a batch's page when the agent starts working on it (status with batchId) or finishes it (done with batchId); if it cannot, the toolbar shows a "view /path" link that replays the highlight on arrival.
+- If you leave the page the agent is editing, the browser stops following it for that round and the toolbar shows a "view /path" link when it finishes.
+
+### Changed
+- Sending a new batch no longer marks an earlier unanswered batch as abandoned; sent batches stay until done.
+- While the agent works, Select only opens the queue (picking resumes after done, or on the agent's next wait); the Send button appears only when there is something to send.
+- The refresh-strategy chip moved from the toolbar into the settings popover (gear); the toolbar now shows only Select, the agent status and the hint.
+
+### Fixed
+- Under the reload strategy the done highlight now appears after the page reloads.
+- Drafts made in one tab are no longer wiped when you edit a draft in another tab of the same session (draft updates are now per page).
+
 ## [0.9.4] — 2026-09-22
 ### Fixed
 - Source locations are no longer dropped when the project directory itself sits under a node_modules path (library detection is now relative to the project root).
@@ -24,8 +40,8 @@ All notable changes to this project are documented here. The format follows [Kee
 - React: `react.source` now points at the picked element's own JSX line when that line is in your code. Previously it was the nearest component's call site — for elements written directly inside a page component (e.g. Next.js app router pages) that was the mount point or nothing. The component call site is still available as `react.callers[0]`.
 
 ### Fixed
-- React: elements rendered by a component library (MUI, Radix, …) now resolve react.source to the JSX call site in your code instead of losing the location (React 19) or pointing into node_modules (React ≤18).
-- React: when the element sits under a one-line pass-through wrapper you wrote around a library component, the payload now carries the call sites above it (`react.callers`, up to 2), so the agent isn't stranded on a file with nothing to change. Reported by u/QuanTradin on r/mcp, along with the component-library case above.
+- React: elements rendered by a component library (MUI, Radix, …) now resolve react.source to the JSX call site in your code instead of losing the location (React 19) or pointing into node_modules (React ≤18). Reported by u/QuanTradin (r/mcp).
+- React: when the element sits under a one-line pass-through wrapper you wrote around a library component, the payload now carries the call sites above it (`react.callers`, up to 2), so the agent isn't stranded on a file with nothing to change. Reported by u/QuanTradin (r/mcp).
 - React on Next.js (Turbopack): sectioned source maps are now resolved and `file://` sources are reported relative to the project root, so elements on app-router pages get a `react.source` (previously nothing).
 - Next.js (Turbopack) dev servers are now detected as hot-reloading, so `done` no longer reloads the page.