diff --git a/.claude/commands/pr-loop.md b/.claude/commands/pr-loop.md
new file mode 100644
index 0000000..e82e945
--- /dev/null
+++ b/.claude/commands/pr-loop.md
@@ -0,0 +1,29 @@
+---
+description: Arm (or re-arm) the autonomous PR-loop cron and run one tick now
+---
+
+You are (re)arming this project's autonomous PR loop. The loop is session-scoped (cron jobs die when Claude Code exits and may not persist across restarts even when durable), so it is lost at the start of each new session. This command restores the whole loop in one step. Do BOTH parts.
+
+The repo is derived from the git remote (`gh repo view --json nameWithOwner -q .nameWithOwner`); the bot login defaults to `$BOT_LOGIN`. Nothing here is project-specific — it reads `.claude/gates.json`, `.claude/scripts/*`, and `docs/USAGE.md`.
+
+## 1. (Re)arm the cron — idempotent
+- Call `CronList`. If a job already exists whose prompt mentions "autonomous PR loop", leave it (do not duplicate) and report its id + schedule.
+- Otherwise `CronCreate` with `durable: true`, schedule `6,21,36,51 * * * *`, and the EXACT prompt below (STEP 0 will self-adjust the cadence on the first tick).
+
+Prompt to use (the tick logic, with adaptive STEP 0):
+
+> Run one tick of the autonomous PR loop. Resolve the repo with `gh repo view --json nameWithOwner -q .nameWithOwner`. Follow docs/USAGE.md and .claude/agents/*; reviewer lenses + consensus per .claude/gates.json; PRs are created/updated via .claude/scripts/bot-gh.sh (bot author), commits stay as the owner.
+>
+> STEP 0 — adaptive cadence: count open PRs (base = gates.json merge.baseBranch, default main) and open issues labelled module:*. Desired cadence = FAST "* * * * *" if there is ≥1 open PR OR ≥1 open module:* issue; else IDLE "17 * * * *". If this job's current schedule != desired, CronDelete this job and CronCreate a durable replacement with this SAME prompt at the desired schedule.
+>
+> Then, in order:
+> 1. POLL: run `bash .claude/scripts/notify-poll.sh`; summarize new issues / PR comments / reviews and the open-PR status section.
+> 2. MERGE: run `bash .claude/scripts/merge-ready.sh`; report each PR merged or why skipped. (It only merges PRs the owner APPROVED that are CI-green & mergeable; never approves.)
+> 3. ADDRESS FEEDBACK: run `bash .claude/scripts/pr-feedback.sh`; for each PR it lists (bot-authored, with unaddressed CHANGES_REQUESTED), run orchestrator→worktree implementer→reviewer-lenses on the SAME branch, push to update the PR in place, and post the `<!-- claude-addressed -->` marker comment. Do NOT merge here.
+> 4. ADVANCE: ONLY when there are ZERO open PRs — pick the lowest-numbered open module:* issue with no feat/issue-<n>-* branch; drive it through the orchestrator (scope → worktree implementer → gate.sh gates → reviewer lenses → bot PR). One issue in flight at a time.
+> 5. If nothing actionable, reply exactly one line: "No actionable activity."
+
+## 2. Run one tick now
+Execute steps 1–5 above immediately so the loop doesn't wait for the next cron fire. Report what happened (polled items, merges, feedback addressed, issue advanced — or "no actionable activity").
+
+Notes: requires the bot machine account set up per docs/USAGE.md (`GH_BOT_TOKEN` in `.env`, bot is a write collaborator) so PRs are bot-authored and the owner can formally Approve them. For a tighter in-session cadence you can also run `/loop 5m /pr-loop`.
diff --git a/.claude/scripts/merge-ready.sh b/.claude/scripts/merge-ready.sh
index 191bc85..0d74b2e 100644
--- a/.claude/scripts/merge-ready.sh
+++ b/.claude/scripts/merge-ready.sh
@@ -20,6 +20,7 @@
 # (bot-gh.sh). Repo is derived from the git remote; override with $1 (owner/repo).
 # The approver defaults to the repo owner; override with $MERGE_APPROVER.
 # Pre-approve `bash .claude/scripts/merge-ready.sh` in .claude/settings.json.
+
 set -euo pipefail
 export PATH="$HOME/.local/bin:$PATH"