shuttle-ctl resume: file review-comment so dispatcher takes resume path

check_resume_intent/3 reads the latest --kind review-comment event for
payload.resume_mode == "previous" to decide whether to invoke
`claude --resume <uuid>`. Without this event, CLI-resumed fibers always
got a fresh worker even when shuttle.session.id was set — the resume
path was unreachable from CLI. Kanban worked because it writes the
review-comment correctly; CLI didn't.

Fix: after writing the block in the non-standing resume path, if
shuttle.session.id is set, file a review-comment with
resume_mode=previous. Mirrors exactly what the kanban's "Resume
previous" button does.

New helper: appendFeltHistoryReviewComment(host, fiberID, summary,
resumeMode) in history.go — same best-effort pattern as
appendFeltHistory but adds --kind review-comment + --field resume_mode.
Relies on the felt fix (commit 4166815) that allows --summary "".

Integration test coverage: dispatch_integration_test.exs
"CLI resume after fix: review-comment filed → --resume in run-script"

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: cailmdaley

cmd/shuttle/history.go

@@ -13,3 +13,19 @@ func appendFeltHistory(host, fiberID, summary string) error {
 	_ = cmd.Run()
 	return nil
 }
+
+// appendFeltHistoryReviewComment files a `--kind review-comment` event so the
+// dispatcher's check_resume_intent/3 can read resume_mode from the latest event.
+// Summary may be empty (felt ≥ commit 4166815 accepts --summary "").
+func appendFeltHistoryReviewComment(host, fiberID, summary, resumeMode string) error {
+	if host == "" {
+		return nil
+	}
+	cmd := exec.Command("felt", "-C", host, "history", "append", fiberID,
+		"--kind", "review-comment",
+		"--summary", summary,
+		"--field", "resume_mode="+resumeMode,
+	)
+	_ = cmd.Run()
+	return nil
+}

cmd/shuttle/lifecycle.go

@@ -106,6 +106,18 @@ closed fiber back into active work.`,
 					fmt.Printf("  status: %s → active\n", statusBefore)
 				}
 			}
+
+			// File a review-comment so the dispatcher's check_resume_intent/3
+			// can detect resume intent. Without this event the dispatcher always
+			// takes the fresh path — shuttle.session.id alone is insufficient
+			// because check_resume_intent reads only the latest review-comment.
+			// Mirror what the kanban's "Resume previous" button does.
+			if f.Block.Session != nil && f.Block.Session.ID != "" {
+				sessionID := f.Block.Session.ID
+				summary := "resumed via shuttle-ctl; session " + sessionID + " available for reattach"
+				_ = appendFeltHistoryReviewComment(host, fiberID, summary, "previous")
+				fmt.Printf("  resume_mode: previous (session %s)\n", sessionID)
+			}
 			return nil
 		},
 	}