agentty 0.8.11 → 0.9.1

package/CHANGELOG.md

@@ -7,6 +7,91 @@ this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.htm
 
 ## [Unreleased]
 
+## [v0.9.1] - 2026-05-02
+
+### Changed
+
+- agentty: enable the `arboard` `wayland-data-control` backend so clipboard image
+  capture works on Wayland compositors such as Hyprland, and update runtime-flow,
+  keybinding, and workflow docs to describe X11 and Wayland clipboard sources.
+- Clarify workspace crate names, validation guidance, UI helper guidance, and
+  constructor guidance in agent instructions while removing obsolete nested instruction
+  files from stale example/proof directories.
+- Bump workspace crate metadata and lockfile package versions to `0.9.1`.
+
+### Contributors
+
+- @minev-dev
+
+## [v0.9.0] - 2026-05-02
+
+### Added
+
+- agentty: accept image paste payloads from `Ctrl+Shift+V` and copied PNG files in the
+  prompt input flow.
+- agentty: add branch and path columns to the `Projects` table so repository identity is
+  visible without opening a project.
+- testty: add the named `StartupWait` preset enum (`Default`, `FastNative`, `SlowNode`,
+  `Custom { stable_ms, timeout_ms }`) plus the `Journey::wait_for_startup_preset` and
+  `Journey::wait_for_startup_default` constructors so test authors can pick a documented
+  startup-wait profile instead of hand-tuning raw `(stable_ms, timeout_ms)` numbers per
+  project. `StartupWait` is re-exported from `testty::prelude`. The historical
+  `Journey::wait_for_startup(stable_ms, timeout_ms)` entry point keeps working and now
+  routes through `StartupWait::Custom`.
+- testty: add `match_*` recipe siblings for composing reusable frame assertions.
+
+### Changed
+
+- agentty: move the activity heatmap into the `Projects` tab, add aggregate work stats
+  to the `Projects` table, keep the `Stats` tab focused on global aggregates, and hide
+  non-repository workspaces from the project list.
+- agentty: tighten shared tab-page spacing and split project activity from project info
+  so the `Projects` tab has denser, clearer panels.
+- testty: HTML proof report now renders structured `match_*` failures (those carried on
+  `AssertionResult::failure`) with a side-by-side context-and-frame block. The context
+  column surfaces the `Expected` variant, the optional `Region` coordinates, and the
+  matched-span list; the frame column shows `AssertionFailure::frame_excerpt` inside a
+  `<pre>` with a column ruler and per-row gutters whose labels are anchored to the
+  region's `(col, row)` so reported coordinates match the live frame. The ruler defaults
+  to the compact two-row tens-and-ones layout and adds a hundreds row above the tens row
+  whenever the excerpt extends past column 99, so absolute coordinates beyond column 99
+  can be recovered by stacking the digits at any tens-marked column instead of being
+  truncated by `(col / 10) % 10`. The column ruler is sized by terminal cell width (via
+  `unicode-width`) so wide glyphs in the excerpt do not desync the labels from real
+  terminal positions. Needle highlighting in the excerpt is scoped to what the
+  underlying matcher actually validated: every-match matchers (`TextInRegion`,
+  `NotVisible`, `MatchCount`) wrap every occurrence of the needle in a `needle-hit` span
+  using the same one-character advance as `TerminalFrame::find_text`, so overlapping
+  matches like `ana` in `banana` are no longer silently dropped, while first-match-only
+  matchers (`ForegroundColor`, `BackgroundColor`, `Highlighted`, `NotHighlighted`) only
+  highlight the first occurrence so the report does not imply that secondary occurrences
+  were checked. For every-match matchers, strictly overlapping byte ranges are merged
+  into a single span so the emitted HTML stays well-formed, while adjacent matches like
+  `ab` in `abab` keep their distinct spans so the report shows both hits. The
+  `needle-hit` style uses background color only with no horizontal padding so
+  highlighted cells stay aligned with the column ruler. The matched-span list now also
+  surfaces the actual `foreground`, `background`, and style flags (`bold`, `italic`,
+  `underline`, `inverse`, `dim`) carried on each `MatchedSpan`, so color- and
+  highlight-style failures expose the actual cell state next to the structured
+  `Expected` description instead of forcing readers back to the assertion-line summary.
+  The `Expected` description for color and highlight expectations is also reworded to
+  read as "first match of '<needle>' with foreground color ..." (and the equivalent for
+  background, highlight, and not-highlight) so the report makes it explicit that the
+  underlying matchers only validate the first matched span. Legacy entries pushed
+  through `ProofReport::add_assertion` keep the historical one-line `pass`/`fail` shape
+  unchanged.
+- Bump workspace crate metadata and lockfile package versions to `0.9.0`.
+
+### Fixed
+
+- agentty: isolate E2E project discovery from the host home directory so tests only see
+  repositories created for the current scenario.
+
+### Contributors
+
+- @andagaev
+- @minev-dev
+
 ## [v0.8.11] - 2026-05-02
 
 ### Added

package/npm-shrinkwrap.json

@@ -23,7 +23,7 @@
       "hasInstallScript": true,
       "license": "Apache-2.0",
       "name": "agentty",
-      "version": "0.8.11"
+      "version": "0.9.1"
     },
     "node_modules/@isaacs/cliui": {
       "engines": {
@@ -542,5 +542,5 @@
     }
   },
   "requires": true,
-  "version": "0.8.11"
+  "version": "0.9.1"
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "artifactDownloadUrls": [
-    "https://github.com/agentty-xyz/agentty/releases/download/v0.8.11"
+    "https://github.com/agentty-xyz/agentty/releases/download/v0.9.1"
   ],
   "bin": {
     "agentty": "run-agentty.js"
@@ -68,7 +68,7 @@
       "zipExt": ".tar.xz"
     }
   },
-  "version": "0.8.11",
+  "version": "0.9.1",
   "volta": {
     "node": "18.14.1",
     "npm": "9.5.0"