jonah-fleet 1.37.0 → 1.37.1

package/CHANGELOG.md

@@ -5,6 +5,19 @@ All notable changes to `jonah-fleet` will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [1.37.1](https://github.com/Jonah-Projects/jonah-fleet/compare/v1.37.0...v1.37.1) (2026-10-12)
+
+
+### Bug Fixes
+
+* **prompts:** prevent autowork repetition polling loops on in-flight peer-review PRs ([#713](https://github.com/Jonah-Projects/jonah-fleet/issues/713)) ([ceb76f8](https://github.com/Jonah-Projects/jonah-fleet/commit/ceb76f84c78b16d9075b1b4e453c6ae8696c1d88))
+
+## [Unreleased]
+
+### Fixed
+
+- **prompts:** prevent autowork repetition polling loops on in-flight peer-review PRs, define the Active Peer Review & Non-Draft Awaiting Review Invariant in `autowork.md`, and protect `Starting review (round N)` claim windows in `ORCHESTRATION.md`
+
 ## [1.37.0](https://github.com/Jonah-Projects/jonah-fleet/compare/v1.36.0...v1.37.0) (2026-10-11)
 
 
@@ -26,18 +39,6 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 * **terminal-card:** refine backlog triage hints for radar digests and needs-attention issues ([#692](https://github.com/Jonah-Projects/jonah-fleet/issues/692)) ([935ef75](https://github.com/Jonah-Projects/jonah-fleet/commit/935ef75a5e4cbd607bc75f0767901f6f6d7927a8))
 
-## [Unreleased] - 2026-10-11
-
-### Added
-
-- **memory:** partition `LESSONS.md` operational memory ingestion by routine role (`[autowork]`, `[peer-review]`, `[general]`) to prevent unbounded prompt token bloat while maintaining high-signal operational memory
-- **runner:** add head-tail streaming truncation circuit breaker (`DEFAULT_MAX_LINES = 500`, `DEFAULT_MAX_BYTES = 64KB`) for command execution and large tool outputs to prevent context overflow and worker stalls
-
-
-### Fixed
-
-- **terminal-card:** refine backlog triage hints to provide targeted unblock advice for radar digests and `needs-attention` issues instead of generic `needs-human` prompts
-
 ## [1.35.1](https://github.com/Jonah-Projects/jonah-fleet/compare/v1.35.0...v1.35.1) (2026-10-10)
 
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "jonah-fleet",
-  "version": "1.37.0",
+  "version": "1.37.1",
   "description": "Standalone autonomous agent fleet with Symphony orchestration, claim protocols, and continuous improvement loops",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",

package/templates/prompts/ORCHESTRATION.md

@@ -28,7 +28,7 @@ Autowork triggers pass the target issue via environment variables (`TARGET_ISSUE
 
 Invariants deliberately upheld from this spec:
 
-- **Single-flight per issue and PR convergence** — at most one run works an issue or pull request at a time, enforced by the autowork claim protocol (assign → read-back → earliest-timestamp tiebreak). For **umbrella** issues, single-flight is maintained at the _child-issue_ level so slices progress cleanly.
+- **Single-flight per issue and PR convergence** — at most one run works an issue or pull request at a time, enforced by the autowork claim protocol (assign → read-back → earliest-timestamp tiebreak). For **umbrella** issues, single-flight is maintained at the _child-issue_ level so slices progress cleanly. Pull requests actively claimed by peer review (`Starting review (round N)` within 2 hours) or awaiting review are strictly protected from concurrent autowork convergence and repetitive polling loops.
 - **Recover dead-run claims** — a crashed run's orphaned claim is released back to the pool rather than starving the issue or PR, both opportunistically during candidate selection and periodically via issues housekeeping.
 - **Reader/writer separation** — the routine that authors a PR never merges it; the Peer Review routine is the sole merge authority for pull requests.
 - **Warm-Context Review Synchronization** — Autowork maintains an active warm session during implementation, polling for Peer Review's verdict. When Peer Review bounces a PR to draft with findings, Autowork immediately detects the draft state in-session, applies fixes directly to its warm working tree, and re-marks the PR ready—re-firing Peer Review for Round N+1 without cold-start overhead.
@@ -54,7 +54,7 @@ Single source of truth for both autowork candidate reclamation and housekeeping
 
 Single source of truth for Autowork Phase 1 pull request convergence. An assigned pull request or draft PR with unaddressed review comments is a _stale claim_ (safe to reclaim and reassign by another runner) only when **all** of these hold:
 
-1. **It carries an autowork claim comment**: The PR thread contains `🔒 Addressing review findings by autowork run …` or `🔒 Addressing review findings by local autowork session …`.
+1. **It carries an autowork claim comment or peer-review marker**: The PR thread contains `🔒 Addressing review findings by autowork run …`, `🔒 Addressing review findings by local autowork session …`, or `Starting review (round N) …`.
 2. **The claim is old**: The most recent claim comment's `created_at` is **more than 2 hours** ago. (2 hours instead of 6 hours because PR review convergence is a rapid turnaround loop).
 3. **No active commits or review activity**: No new commit has been pushed to the PR branch within the last 2 hours.
 

package/templates/prompts/autowork.md

@@ -61,6 +61,7 @@ If any criterion cannot be met, stop immediately and log FAILURE with the reason
 - Do not fall into the **Telemetry Rabbit Hole**: do not spend cycles instrumenting elaborate fallback telemetry or defensive error handling for features that suffer from lack of user intent rather than software bugs.
 - Do not guess or invent arbitrary specifications for ambiguous issues — post the 4-part escalation card ('Why I believe this'), label `needs-info`, and release the claim instead of blindly writing code.
 - Do not call `schedule` or yield the turn with plain text while waiting for background verification tasks — stay in the tool loop until the Definition of Done is met.
+- Do not busy-poll external routine issues, PRs under review, or background tasks in a repetitive tool loop; never poll in a loop with identical commands (e.g. repeated `gh issue view <peer_review_run>` or `gh run view`) without making progress.
 - Do not write implementation code before proving that the reproduction test or verifier fails (the Red Gate).
 - Do not pause or prompt rhetorical questions ("Shall I continue?", "Should I start implementing?")—proceed autonomously.
 - Do not use bare `git commit` or blind `git add .` without scoping specific paths (`git commit -m "..." -- <paths>`).
@@ -92,9 +93,10 @@ b. **Eligible → claim, then implement.** Call `get_me` once to learn your own
 ### Phase 1: Converge on open work (Scan mode; skipped in Targeted mode)
 
 1. List all open PRs needing attention (specifically draft PRs bounced back by peer review or open PRs with review comments: `gh pr list --state open --json number,title,isDraft,headRefName,assignees,labels,author`, excluding automated release PRs `release-please--*` / `chore(main): release*`).
+   - **Active Peer Review & Non-Draft Awaiting Review Invariant**: In Phase 1, only PRs that have been **bounced to draft** with actionable review findings, or PRs with **unaddressed review comments** (threads from peer review requiring code changes), require convergence. If a PR is ready for review (`isDraft: false`), or carries an active peer-review claim comment (`Starting review (round N)` posted within the last 2 hours), or has no unaddressed review comments / changes requested, you DO NOT OWN THIS PR. You MUST NOT attempt to address it, MUST NOT block, and MUST NEVER poll its review run issue (e.g. `gh issue view <peer_review_run>`). Skip this PR immediately and evaluate the next PR or proceed directly to Phase 2.
    1a. **PR Claim Protocol (Single-Flight PR Convergence)**:
    - For each open PR needing attention (bounced to draft with actionable findings, or open with unaddressed review comments):
-   - **Check eligibility**: re-read candidate PR (`gh pr view <PR> --json assignees,comments`). Skip PRs currently assigned to another live runner or carrying an active claim comment posted within the last 2 hours (unless stale claim per `ORCHESTRATION.md`).
+   - **Check eligibility**: re-read candidate PR (`gh pr view <PR> --json assignees,comments`). Skip PRs currently assigned to another live runner or carrying an active claim comment posted within the last 2 hours per the invariant above (unless stale claim per `ORCHESTRATION.md`).
    - Call `get_me` once to learn your own login if not already known.
    - **Claim atomically**: assign yourself to the PR (`gh pr edit <PR> --add-assignee <login>`) AND post a claim comment on the PR:
      - In **Cloud Actions**: `🔒 Addressing review findings by autowork run {run_url} {timestamp}`