jonah-fleet 1.16.0 → 1.17.0

package/CHANGELOG.md

@@ -5,23 +5,31 @@ 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.16.0](https://github.com/juliendurandeu/jonah-fleet/compare/v1.15.1...v1.16.0) (2026-09-19)
+## [1.17.0](https://github.com/juliendurandeu/jonah-fleet/compare/v1.16.0...v1.17.0) (2026-09-19)
 
 
 ### Features
 
-* **orchestration:** routine run failure ingestion, dynamic target binding, and auto-closure ([#232](https://github.com/juliendurandeu/jonah-fleet/issues/232)) ([b76b3fc](https://github.com/juliendurandeu/jonah-fleet/commit/b76b3fccd767e5cc9517d977fd08c8979baf64b6))
+* **orchestration:** adopt 4-part human escalation card in peer-review routine ([#235](https://github.com/juliendurandeu/jonah-fleet/issues/235)) ([#256](https://github.com/juliendurandeu/jonah-fleet/issues/256)) ([053ef9b](https://github.com/juliendurandeu/jonah-fleet/commit/053ef9b48b7d19b1a503f59c9755b74b99624cc8))
 
-## [Unreleased] - 2026-09-19
+## [Unreleased]
 
 ### Features
 
+* **orchestration:** adopt 4-part human escalation card in peer-review routine on round-5 escalation ([#235](https://github.com/juliendurandeu/jonah-fleet/issues/235))
 * **orchestration:** add Routine Run Failure Ingestion & Auto-Closure Protocol to `ORCHESTRATION.md`, unifying prior failure memory and resolution lifecycle across `autowork` and `peer-review`.
 * **prompts:** add Dynamic Target Binding in Scan mode to `autowork.md` and `peer-review.md`, dynamically updating `$ROUTINE_ISSUE_NUMBER` titles with `(Issue #N)` or `(PR #M)` upon claiming so crashed runs are never anonymous.
 * **prompts:** add Prior Failure Ingestion Protocol to `autowork.md` and `peer-review.md`, inspecting past open failed routine issues to extract error logs and crash milestones before implementation or review.
 * **prompts:** add resolution-triggered auto-closure to `autowork.md` and `peer-review.md`, automatically commenting on and closing past failed routine issues for a target once work is marked ready or merged.
 * **housekeeping:** expand `issues-housekeeping.md` to sweep and close stale untargeted `status:failure` routine issues older than 48 hours or whose targets are resolved, eliminating backlog clutter.
 
+## [1.16.0](https://github.com/juliendurandeu/jonah-fleet/compare/v1.15.1...v1.16.0) (2026-09-19)
+
+
+### Features
+
+* **orchestration:** routine run failure ingestion, dynamic target binding, and auto-closure ([#232](https://github.com/juliendurandeu/jonah-fleet/issues/232)) ([b76b3fc](https://github.com/juliendurandeu/jonah-fleet/commit/b76b3fccd767e5cc9517d977fd08c8979baf64b6))
+
 ## [1.15.1](https://github.com/juliendurandeu/jonah-fleet/compare/v1.15.0...v1.15.1) (2026-09-19)
 
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "jonah-fleet",
-  "version": "1.16.0",
+  "version": "1.17.0",
   "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

@@ -313,6 +313,7 @@ How autonomous routines escalate decisions, ambiguities, and blockers to human m
    - **Recommended Path**: The agent's recommended decision and reasoning, allowing maintainers to unblock execution with a simple confirmation.
 3. **Cross-Routine Enforcement**:
    - `autowork.md`: Required when tripping the Ambiguity Gate (Step 12), encountering a 2nd-strike permanent blocker (`needs-human`), or hitting the review Ping-Pong Cap (Step 3b).
+   - `peer-review.md`: Required when round cap `N >= 5` is reached with unresolved blocking findings, applying `needs-human` and escalating to repo maintainer.
    - `triage/SKILL.md`: Required when transitioning issues or PRs to `needs-info` or `ready-for-human`.
    - `issues-housekeeping.md`: Required when auditing and escalating ambiguous, stale, or infeasible issues with `needs-human` or `needs-info`.
 

package/templates/prompts/peer-review.md

@@ -27,7 +27,7 @@ The run is SUCCESS only if ALL of these are true:
 
 - [ ] Identified the target PR: if one was named in the invocation, reviewed exactly that PR; otherwise listed open PRs and selected one by priority
 - [ ] Ran the code-review pass (`/code-review` and security pass), and posted findings as inline review comments
-- [ ] Took exactly one final action: squash-merged (if PR is good, CI green and present; executed Autonomous Issue Synthesis if unlinked; closed tracking issue explicitly if referenced) OR posted findings and **converted the PR back to draft** (`gh pr ready <N> --undo`) for author/autowork in-session fixes OR, if round cap reached at round 5 with blocking findings, converted to draft and escalated to human
+- [ ] Took exactly one final action: squash-merged (if PR is good, CI green and present; executed Autonomous Issue Synthesis if unlinked; closed tracking issue explicitly if referenced) OR posted findings and **converted the PR back to draft** (`gh pr ready <N> --undo`) for author/autowork in-session fixes OR, if round cap reached at round 5 with blocking findings, converted to draft and escalated to human via the 4-part escalation card with `needs-human`
 - [ ] If merging: captured deferred non-blocking findings per materiality bar (filed follow-up issues for material ones, batched or dropped immaterial ones)
 - [ ] If in Scan mode and no eligible PRs exist, logged SUCCESS with "No PRs to review"
 
@@ -35,7 +35,7 @@ If any criterion cannot be met, stop immediately and log FAILURE with the reason
 
 ## Constraints
 
-- **Max rounds per PR**: 5 — at round 5 the run must terminate in a merge (if no blocking findings remain) or human escalation, never another ordinary bounce.
+- **Max rounds per PR**: 5 — at round 5 the run must terminate in a merge (if no blocking findings remain) or human escalation (via the mandatory 4-part escalation card with `needs-human`), never another ordinary bounce.
 - **Max iterations**: 65 — after 65 tool call rounds without completing Definition of Done, STOP. Log FAILURE with category `token_limit`.
 - **Max scope**: one PR per run. Do not review a second PR after finishing the first.
 - **No speculative work**: review only the diff in the PR.
@@ -159,7 +159,16 @@ If the PR is clean and approved for merge, but lacks a `Closes #N` tracking link
 
 - **If Blocking findings exist**:
   - If `N < 5`: Post inline comments, submit review as `COMMENT`, and convert PR to draft (`gh pr ready <N> --undo`).
-  - If `N >= 5`: Convert PR to draft, post summary comment escalating to repo maintainer, and apply `needs-human` label.
+  - If `N >= 5`: Convert PR to draft, apply `needs-human` label, and post summary escalation comment to the PR formatted with the mandatory 4-part escalation card:
+    ```markdown
+    ## 🛑 Escalation: Human Decision Required
+    - **Decision Needed**: [1 focused question or choice]
+    - **Evidence ("Why I believe this")**: [Specific files, lines, test outputs, or conflicting docs]
+    - **Evaluated Options & Trade-offs**:
+      - *Option A*: [Pros / Cons]
+      - *Option B*: [Pros / Cons]
+    - **Recommended Path**: [Agent recommendation]
+    ```
 - **If Clean (or only Non-blocking findings)**:
   - If the PR branch has minor mechanical merge conflicts against `origin/main` (e.g. adjacent `CHANGELOG.md` entries from concurrent merges) while code and tests are sound, resolve the conflict mechanically via `/resolving-merge-conflicts` before squash-merging rather than bouncing the PR back to draft.
   - If PR lacks `Closes #N`, execute Autonomous Issue Synthesis (Step 5.5).