@open-tomato/rafa 0.35.0 → 0.37.0

package/README.md

@@ -829,10 +829,11 @@ creates the `.rafa/` folders and the board labels newer versions expect,
 and records the version in `rafa.lock` at the repository root, a small
 JSON file meant to be committed. It works within a patch range: the
 installed version must share the major and minor of the one the lock
-records, and a project with no lock is adopted. It prints every change
-first, and `--dry-run` stops there; otherwise it asks once, or takes
-`--yes`. The rest of `rafa update` (`self`, `project`, `board`, `next`,
-`latest`) is in development and says so (#713).
+records. Below 1.0.0 it also crosses newer minors, so a lock at 0.34.1
+moves to 0.36.0, and a project with no lock is adopted. It prints every
+change first, and `--dry-run` stops there; otherwise it asks once, or
+takes `--yes`. The rest of `rafa update` (`self`, `project`, `board`,
+`next`, `latest`) is in development and says so (#713).
 
 ## Runtime
 

package/dist/bundled/operators/agents/rafa-stretch-engineer.md

@@ -130,10 +130,10 @@ One loop at a time; never two at once inside a stretch.
 
    `setsid` is Linux's; on macOS start it with `nohup` alone and log the
    difference as a gap. Detached loops are a gap of their own.
-3. Watch it: read the log's `rafa·` lines and `rafa loop status`. Wait
-   with a background check on the log, never a tight loop of reads. No
-   foreground command waits longer than 60 seconds; longer waits run in
-   the background.
+3. Watch it: `rafa loop wait --until=pr,no-pr,halt,error,exit` reads the
+   `.rafa/runs/<session-id>.events.ndjson` file your loop wrote, not the
+   log. No foreground command waits longer than 60 seconds; longer waits
+   run in the background.
 4. Merge its pull request:
    - Into `stretch/<n>`: `rafa pr merge <pr> --skip-checks`. The merge push
      runs `verify` asynchronously; read the result at the pit stop.

package/dist/bundled/operators/agents/rafa-stretch-watchtower.md

@@ -55,17 +55,17 @@ Four sources, all on this machine:
 
 ## How you wait
 
-- **A Monitor on the loop log**, so each `rafa·` line, a `blocked` line, an
-  `error` line or a `halt` line reaches you as it is written. Match every
-  ending, not only the good ones:
+Watch the running loop's events from `.rafa/runs/<session-id>.events.ndjson`:
 
-  ```bash
-  tail -F .rafa/stretch/<n>/loop-<issue>.log | grep --line-buffered -E 'rafa· (task|wrap-up|pr|no pr|halt|error)'
-  ```
+```bash
+rafa loop wait --until=blocked,quiet:<minutes>,exit
+```
 
-  A Monitor stops after 30 minutes at most; restart it at every wake.
-- **`/loop`**, self-paced, every 10 to 30 minutes, for the slower checks:
-  the agent's status and the quiet-loop timing.
+The `<minutes>` is 2× the p90 task time from `rafa effort dashboard`. With
+no baseline yet, use 30 minutes and say so in the alert. The wait exits
+when a task blocks, when the loop is quiet for that long, or when the loop
+ends. Between waits, read the agent's session status and check the hook
+rule at every wake: `/loop`, self-paced, every 10 to 30 minutes.
 
 ## How you alert