@meistrari/remy-cli 1.20.0-rc.2 → 1.20.0-rc.4

package/README.md

@@ -66,7 +66,7 @@ Published files and Tela Pages appear in the timeline. File artifacts include th
 
 **Download files:** `/files` or `Ctrl+F` opens a session file picker, newest first, containing Remy’s published artifacts and attachments sent by everyone in that session, with author/source labels. Repeated updates to an artifact appear once, using its newest title and URL. Select with arrows or `j`/`k`; `Enter` (or `d`) downloads to `~/Downloads`, creating that directory if needed. Remy shows progress and the full saved path. Existing files are preserved: another `report.txt` becomes `report (1).txt`. Press `o` for the Web preview or `c` to copy its URL; previews use your browser sign-in. Tela Pages open their canonical URL instead of downloading. The picker also works in closed sessions. `Esc` cancels an unfinished download and returns to the conversation with your draft intact, without stopping Remy. Errors stay visible for an explicit retry, which requests fresh download authorization. Files are saved without executing or extracting them. This picker covers published files and message attachments; embedded tool-output media remains available through **View event in Web**.
 
-System observations appear as **system notifications** with the system actor, source, and a generic JSON data view. Remy preserves unknown actor IDs and notification formats rather than treating them as user messages or commands. When a notification starts agent work, retained history can associate it with a known accepted Remy turn without adding a synthetic prompt. Delivery is at-least-once, so an uncertain retry can produce additional distinct turns and repeat model or tool effects; Remy preserves those turns rather than presenting the association as proof of exactly-once execution. The CLI has no control for creating notifications.
+System observations appear as **system notifications** with the system actor, source, and a generic JSON data view. Remy preserves unknown actor IDs and notification formats rather than treating them as user messages or commands. Once the runtime accepts a notification, retained history can associate it with the known Remy turn that it started or joined without adding a synthetic prompt. The retained timeline keeps a turn-starting observation before that turn's start and a joined observation after the active turn's start, at the observation's original event position. Delivery is at-least-once, so an uncertain retry can produce additional distinct turns or repeat effects in an active turn; Remy preserves every observed turn rather than presenting the association as proof of exactly-once execution. The CLI has no control for creating notifications.
 
 When Remy creates a plan, the session shows its checklist in the timeline and keeps `Plan <done>/<total>` with the current item pinned above the composer. Updates change the same checklist instead of producing repeated rows, and an unfinished plan remains visible after reconnecting or between turns. The collapsed timeline shows up to five plan items; press `Ctrl+O` for the complete checklist and activity detail.
 

package/dist/remy.js

@@ -40740,7 +40740,7 @@ var compactMarkRows = 9;
 var compactMinWidth = 48;
 var compactMinHeight = 20;
 var markBrightnessGain = 4.2;
-var remyCliVersion = "1.20.0-rc.2";
+var remyCliVersion = "1.20.0-rc.4";
 async function showRemySplash({
   createRenderer = createRemyRenderer,
   durationMs = splashDurationMs,

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@meistrari/remy-cli",
-    "version": "1.20.0-rc.2",
+    "version": "1.20.0-rc.4",
     "description": "Remy, the Coding Agent terminal client.",
     "type": "module",
     "bin": {