chore: version packages

2026-10-07 16:09:43 +02:00 · 2026-09-15 00:07:19 +02:00
parent 70fc6b32d5
commit 88e3faa456
10 changed files with 81 additions and 68 deletions
@@ -1,18 +0,0 @@
---
-"aicodeman": patch
---
-
-fix(webview): let a proxied single-page app route on its own path, and recover a frame that reloads
-
-A dashboard served through a web tab saw `/webview/<cap>/` as its `location.pathname`, and
-no app has a route for that: a React Router, Vue Router or Vite dev-server page painted its
-HTML and CSS and then replaced them with its own "page not found" the moment its script ran.
-The proxy's runtime shim now rewrites the history entry to the path the page would see on its
-own origin before any page script runs, while every URL the page emits still goes through
-the existing rewrite layers (plus `Worker`, `sendBeacon` and `window.open`, which the masked
-Referer can no longer rescue). A navigation the page starts itself afterwards — a dev
-server's full-reload HMR, a root-absolute `location.href` — lands on Codeman's root with no
-capability; it is recognised by shape (an iframe navigation asking for HTML for a path Codeman
-does not serve), answered with a static page that tells the owning tab which path was lost,
-and the tab remounts the frame inside the prefix at that path. That answer is served before
-the credential checks, so it never counts as a failed login.
@@ -1,34 +0,0 @@
---
-"aicodeman": patch
---
-
-File previews, downloads and text reads now work in a **remote (SSH) case**.
-
-A remote case's working directory is an absolute path on the *remote* host, but the
-file routes resolved it with local `fs` — so a clicked path (or the File Viewer) always
-failed as "File not found" even though the file existed and the session was clearly
-working in that directory. `GET /api/sessions/:id/file-raw`, `file-content`,
-`file-preview` and `file-thumbnail` now resolve and read through the same
-`buildSshConnectionArgs()` connection the launch uses (`src/remote-files.ts`, one
-`realpath`+`stat` probe per request returning both the file and the workspace root).
-
-Clicked paths that point OUTSIDE the case directory (a remote `/tmp` scratchpad capture,
-a screenshot elsewhere in the remote home) go through the attachment routes, which had
-the same local-`fs` assumption: registration, the by-id `raw` stream, the metadata poll
-and the attachment history list now resolve over ssh as well, so the click-path works
-whether the file sits inside or outside the case. Which host a record is read from
-follows the SESSION, never the path string — the same absolute path means a different
-file on each host, and a remote session never falls back to a local file.
-
-The guards are unchanged in strength: the workspace boundary is still enforced (now
-resolved on the host that can actually resolve it), the sensitive-path blocklist and
-the size cap (`CODEMAN_MAX_DOWNLOAD_BYTES`) still apply before any bytes are read, and
-`Range` requests keep working, so remote `<video>`/`<audio>` seeking behaves like a
-local file. An unreachable host is reported as `502` with the remote reason instead of
-a misleading 404. Nothing is ever copied to the Codeman host.
-
-Still not available for remote cases, and now said explicitly instead of 404-ing:
-editing a file (`edit=1` / `PUT` answer 400, the viewer hides its Edit affordance),
-office-document previews and generated thumbnails (both need the bytes on the server's
-disk), the file tree / path picker, and `tail-file`. Docker cases are unaffected (their
-workspace is bind-mounted at the same absolute path).
@@ -1,5 +0,0 @@
---
-"aicodeman": patch
---
-
-Add Shift+Left and Shift+Right buttons to the default and extended mobile agent keyboard bars, shown only on Codex sessions, enabling Codex queued-message editing and prompt-stack navigation. Flush locally buffered drafts before navigation and keep terminal focus after taps.
@@ -1,5 +0,0 @@
---
-"aicodeman": patch
---
-
-Fix an invisible terminal text selection on the light skins (#360). Every xterm palette declared its selection colour under the key `selection`, which xterm.js renamed to `selectionBackground` in v5. An `ITheme` is a plain object, so the unknown key was dropped without an error and every skin fell back to xterm's own default of `rgba(255,255,255,0.3)`: unnoticeable on the dark skins, which wanted roughly that anyway, and effectively invisible on Paper Gray, Solarized Light, Catppuccin Latte and Rosé Pine Dawn, where white at 30% over a near-white background moves a channel by about 3/255. Selecting text on those skins now highlights it, with desktop drag-select and the mobile long-press both fixed by the same rename.