ChronoAIProject
diff --git a/‎CLAUDE.md‎
Lines changed: 98 additions & 5 deletions b/‎CLAUDE.md‎
Lines changed: 98 additions & 5 deletions
diff --git a/‎skills/codex-refactor-loop/SKILL.md‎
Lines changed: 160 additions & 89 deletions b/‎skills/codex-refactor-loop/SKILL.md‎
Lines changed: 160 additions & 89 deletions
diff --git a/‎skills/codex-refactor-loop/authorizations/runtime-exceptions.md‎
Lines changed: 101 additions & 16 deletions b/‎skills/codex-refactor-loop/authorizations/runtime-exceptions.md‎
Lines changed: 101 additions & 16 deletions
diff --git a/‎skills/codex-refactor-loop/host.env.example‎
Lines changed: 55 additions & 5 deletions b/‎skills/codex-refactor-loop/host.env.example‎
Lines changed: 55 additions & 5 deletions
diff --git a/‎skills/codex-refactor-loop/prompts/design-issue-reply.md‎
Lines changed: 4 additions & 7 deletions b/‎skills/codex-refactor-loop/prompts/design-issue-reply.md‎
Lines changed: 4 additions & 7 deletions
diff --git a/‎skills/codex-refactor-loop/prompts/implement.md‎
Lines changed: 4 additions & 3 deletions b/‎skills/codex-refactor-loop/prompts/implement.md‎
Lines changed: 4 additions & 3 deletions
diff --git a/‎skills/codex-refactor-loop/prompts/meta-judge.md‎
Lines changed: 4 additions & 7 deletions b/‎skills/codex-refactor-loop/prompts/meta-judge.md‎
Lines changed: 4 additions & 7 deletions
diff --git a/‎skills/codex-refactor-loop/prompts/meta-reflector-repository-stalled.md‎
Lines changed: 40 additions & 0 deletions b/‎skills/codex-refactor-loop/prompts/meta-reflector-repository-stalled.md‎
Lines changed: 40 additions & 0 deletions
diff --git a/‎skills/codex-refactor-loop/prompts/publish-implementation-fallback.md‎
Lines changed: 56 additions & 0 deletions b/‎skills/codex-refactor-loop/prompts/publish-implementation-fallback.md‎
Lines changed: 56 additions & 0 deletions
diff --git a/‎skills/codex-refactor-loop/prompts/release-rollup-body.md‎
Lines changed: 36 additions & 0 deletions b/‎skills/codex-refactor-loop/prompts/release-rollup-body.md‎
Lines changed: 36 additions & 0 deletions
@@ -10,11 +10,6 @@
 #   $EDITOR <host-repo>/.config/consensus-rnd/host.env
 #   export CONSENSUS_RND_HOST_ENV=.config/consensus-rnd/host.env
 #
-# Legacy compatibility only:现有安装仍可读取 .refactor-loop/host.env;不要把它作为
-# 新 host production config 或 ledger SSOT。
-#   mkdir -p <host-repo>/.refactor-loop
-#   cp skills/codex-refactor-loop/host.env.example <host-repo>/.refactor-loop/host.env
-#
 # ⚠️ daemon / codex 启动必须用 `bash -c 'source "$CONSENSUS_RND_HOST_ENV" && exec ...'` 注入(见 SKILL.md
 #    「Daemon 启动」节),不能用 `env $(grep ... host.env)` —— 含空格的值(如
 #    BUILD_CMD="cargo build --workspace")会被 env 当成 "build" 是命令而崩。
@@ -74,6 +69,9 @@ export UPDATE_CHECK_INTERVAL_SECONDS="21600"
 # Default: GitHub release/tag read timeout seconds.
 export UPDATE_CHECK_TIMEOUT_SECONDS="5"
 
+# Default/noop: RuntimeRetention local cleanup opt-in. False/empty does nothing.
+export RUNTIME_RETENTION_ENABLE="false"
+
 # Default: minimum recent merges required by auto_release_gate stability.
 export RELEASE_AUTO_MIN_MERGES="1"
 
@@ -86,9 +84,23 @@ export RELEASE_ROLLUP_MIN_COMMITS="1"
 # Default: suppress duplicate release-rollup events for same integration SHA.
 export RELEASE_ROLLUP_COOLDOWN_SECONDS="21600"
 
+# Default: rollup PR CI-only squash merge. Use manual/false to leave rollup PRs
+# open for human review or host branch-protection requirements.
+export ROLLUP_AUTO_MERGE="auto"
+
 # Default: concurrency floor; unset means 5 and values below 2 are clamped to 2.
 export CODEX_FLOOR="5"
 
+# Default: idle hours after which a stuck managed work item is re-triggered
+# (its blocking redispatchable local evidence is cleared). Missing, invalid, or
+# non-positive means 3 hours.
+export STALE_REVIVAL_HOURS="3"
+
+# Default: repository-wide long-stuck meta-reflector threshold in hours.
+# Missing, invalid, or non-positive means 24h; effective threshold is max with
+# STALE_REVIVAL_HOURS so this fallback runs later than ordinary stale revival.
+export META_ESCALATION_STUCK_HOURS="24"
+
 # Default/noop: active-controller lease device id. Empty means single-device
 # local-owner noop. Multi-device opt-in requires all devices upgraded and each
 # device configured with a stable unique id.
@@ -97,6 +109,29 @@ export ACTIVE_CONTROLLER_DEVICE_ID=""
 # Default: active-controller lease TTL in seconds.
 export ACTIVE_CONTROLLER_TTL_SECONDS="1800"
 
+# Default: open managed work snapshot fresh-cache TTL in seconds.
+export MANAGED_WORK_SNAPSHOT_TTL_SECONDS="300"
+
+# Default: maximum stale snapshot age reused during low GraphQL headroom or
+# transient fetch failure.
+export MANAGED_WORK_SNAPSHOT_STALE_MAX_SECONDS="900"
+
+# Default: restart-helper-managed phase9-router daemon tick seconds.
+export PHASE9_ROUTER_INTERVAL_SECONDS="120"
+
+# Default: restart-helper-managed wakeup-runner daemon tick seconds.
+export WAKEUP_RUNNER_INTERVAL_SECONDS="120"
+
+# Default/noop: patrol-inspector issue intake daemon opt-in. False/empty keeps
+# local patrol state disabled and does not publish patrol-owned issues.
+export PATROL_INSPECTOR_ENABLE="false"
+
+# Default: restart-helper-managed patrol-inspector daemon tick seconds.
+export PATROL_INSPECTOR_INTERVAL_SECONDS="7200"
+
+# Default: maximum PatrolFinding records published per patrol tick.
+export PATROL_INSPECTOR_MAX_FINDINGS="25"
+
 # Default: comment-monitor tick seconds. Higher values lower fixed search cost;
 # unchanged issue/PR updatedAt values now skip comments queries entirely.
 export COMMENT_MONITOR_INTERVAL="30"
@@ -105,6 +140,21 @@ export COMMENT_MONITOR_INTERVAL="30"
 # search only. Plain dates become updated:>=DATE; empty adds no filter.
 export COMMENT_MONITOR_LOOKBACK=""
 
+# Default/noop: shared holistic status card GitHub sync. False/empty keeps the
+# local read-only `holistic-status` command available but disables issue-comment
+# PATCH from progress-reporter.
+export HOST_HOLISTIC_STATUS_ENABLE="false"
+
+# Empty/noop: host issue number that owns the existing dashboard comment.
+export HOST_HOLISTIC_STATUS_ISSUE_NUMBER=""
+
+# Empty/noop: existing issue comment id to PATCH in place. The skill never
+# creates this comment.
+export HOST_HOLISTIC_STATUS_COMMENT_ID=""
+
+# Default: minimum seconds between fixed-comment PATCH attempts.
+export HOST_HOLISTIC_STATUS_INTERVAL_SECONDS="600"
+
 # Default: refactor-history source comment policy. Valid values:
 # none, self-doc-comment. Empty is treated as none.
 export HOST_REFACTOR_COMMENT_POLICY="none"
 
@@ -3,7 +3,7 @@
 <!--
 Refactor (iter1/issue-126):
   Old pattern: 跨平台 prompt 含 '该项目'/'该项目AI' 等硬编码 host 占位文本,违反 host-agnostic;应复用 host.env surface(GH_REPO_SLUG / MAINTAINER_WHITELIST)。
-  New principle: 按 .refactor-loop/runs/phase9-issue126-r3-judge.md consensus 逐条:删除 prompt 硬编码 host 文本,复用现有 host.env surface;硬约束:(1) 不重建 REFERENCE.md(单文件 SKILL.md);(2) refactor self-doc 注释必须自含 Old/New,禁止 'see issue #X' placeholder;(3) 严格按 design decision Implement plan,不超范围。
+  New principle: Host-agnostic prompt text is owned by the host.env surface matrix, GH_REPO_SLUG, MAINTAINER_WHITELIST, HOST_REFACTOR_COMMENT_POLICY, test_refactor_comment_policy_prompt_contract.py, this prompt's checklist, and render-time shared post rules for direct-post behavior.
 -->
 
 issue: ${ISSUE_URL}
@@ -76,7 +76,7 @@ NyxId API keys / secrets / 内部 URL 之类敏感信息绝对禁止出现在 re
 
 5. **输出**：
    - 把回复内容写到 `$REPO_ROOT/.refactor-loop/runs/design-issue-${ISSUE_NUMBER}-reply-$(date +%s).md`
-   - 写完 archive 后直接按 `prompts/_github-post-rules.md` post GitHub 回复
+   - 写完 archive 后直接按渲染期内联的共享规则 post GitHub 回复
    - 成功打印 `POSTED:design-reply:${ISSUE_NUMBER}:<URL>:<headline>`；失败打印 `POST_FAILED:design-reply:${ISSUE_NUMBER}:<reason>`
 
 ## 红线
@@ -90,12 +90,9 @@ NyxId API keys / secrets / 内部 URL 之类敏感信息绝对禁止出现在 re
 
 ## GitHub post(强制)
 
-写完内部 artifact 后,**自己调 `gh` post 中文 GitHub 评论/PR body**。遵循 `prompts/_github-post-rules.md`(本 skill 的 `prompts/_github-post-rules.md`)所有规则:
+写完内部 artifact 后,**自己调 `gh` post 中文 GitHub 评论/PR body**。遵循渲染期内联的共享规则:
 
-- body 第一行 `## 🤖 <headline>`(comment-monitor 据此识别)
-- 中文 TL;DR ≤ 6 行 + 详细说明 + raw artifact 折叠 `<details>`
-- 若 situation context 给了 `original_authors:` 列表,加 `📢 cc 原作者:@h1 @h2`
-- Post 后打印 `POSTED:design-reply:${ISSUE_NUMBER}:<URL>:<headline>` 或 `POST_FAILED:design-reply:${ISSUE_NUMBER}:<reason>`
+{{GITHUB_POST_RULES_CONTRACT}}
 
 
 ---
 
@@ -34,7 +34,7 @@ ${SCOPE_PATHS}
    3-5 行内；不是 changelog，是代码自我说明。The marker identity is exactly `Refactor (iter${ITERATION}/${CLUSTER_ID})`; do not replace it with issue-only identities such as `Refactor (issue1525)`. If `${CLUSTER_ID}` is missing, use `cluster-issue${ISSUE_NUMBER}` and record that fallback in the implementation summary.
    - missing/empty/default/`none`：MUST NOT add `Refactor (...)`, `Old pattern`, `New principle`, or `iterN/cluster` refactor-history source comments. Put the rationale in the implementation summary and include exactly: `refactor self-doc: not applicable (HOST_REFACTOR_COMMENT_POLICY=none)`.
 3. **不新增功能**：不引入新接口、新 flag、新模块；只清理违反点。新增极小辅助类型的注释也必须遵守 `${HOST_REFACTOR_COMMENT_POLICY}`：missing/empty/default/`none` 时不得写 `refactor helper`, `no behavior change`, `Old`, `New`, 或 `iterN` 等 refactor-history source comments；如确需源码注释，只写面向业务行为的准确英文说明。仅 explicit `self-doc-comment` 时才按第 2 条既有 Refactor self-documentation 格式写注释。
-4. **测试**：按 `verification_hints` 跑测试，必须通过；测试不足必须补；任何 `sleep/delay` 轮询测试必须改为确定性断言。
+4. **测试 ratchet**：按 `verification_hints` 跑测试，必须通过；测试不足必须补。凡改动触及模块行为、合同、prompt、helper 或守卫，必须同步推进该模块的相关测试为 fast / hermetic / behavior-first：优先使用 owner-local fact source、mock/fake/stub 外部进程与网络、断言可观察行为或 contract，而不是复述实现字面。任何 `sleep/delay` 轮询测试必须改为确定性断言；不得新增 suite-level host-wide process-table guard，例如用 `ps -eo pid=,command=` 扫描当前机器进程来判断 daemon leak / duplicate。daemon leak / duplicate 覆盖只能放在 helper-local fact source 或对应 helper 行为测试内。
 5. **架构守卫**：跑 host 配置的 `$CI_GUARDS`，必须通过。其它 cluster 特定守卫见 verification hints。
 6. **不依赖外部仓库**：禁止建议在 $EXTERNAL_REPOS/$EXTERNAL_REPOS 改动。
 7. **Schema/protocol**：如 `${HOST_PROTO_POLICY}` 非空或 diff / `$PROJECT_RULES` 显示改了 schema/protocol 文件，按 host policy 本地重生成/验证并确认编译通过。
@@ -57,7 +57,8 @@ ${SCOPE_PATHS}
    - 测试结果
    - deviation 记录
    - `SCOPE_EXTEND` 记录
-10. 末尾打印 `IMPLEMENT_DONE:${CLUSTER_ID}:<status>` 其中 status ∈ {ok, partial, blocked}。
+10. 若 status 为 `ok`，同时写入 worker-authored PR artifacts：`$REPO_ROOT/.refactor-loop/runs/implementation-pr-${CLUSTER_ID}-title.txt` 与 `$REPO_ROOT/.refactor-loop/runs/implementation-pr-${CLUSTER_ID}-body.md`。title 必须是一行非占位中文标题，不得是 `实现 issue #N`；body 必须包含且只包含一个 `Closes #N`，包含 `## 修改文件`、`## 测试结果`、`## deviation 记录`，并以 sentinel 作为最终独立行。
+11. 末尾打印 `IMPLEMENT_DONE:${CLUSTER_ID}:<status>` 其中 status ∈ {ok, partial, blocked}。
 
 ## Marker emission allowlist(强制)
 
@@ -71,7 +72,7 @@ Only the markers listed above are valid role-routing markers for this prompt. Do
 
 ## 红线
 
-- 禁止改 worktree 外文件，**唯一例外**：可以写入 `$REPO_ROOT/.refactor-loop/runs/implement-${CLUSTER_ID}.md`（controller 期望的摘要输出位置）和 `$REPO_ROOT/.refactor-loop/runs/scope-extend-${CLUSTER_ID}.log`（如有 SCOPE_EXTEND 记录）。除此之外 `.refactor-loop/` 一律禁改。
+- 禁止改 worktree 外文件，**唯一例外**：可以写入 `$REPO_ROOT/.refactor-loop/runs/implement-${CLUSTER_ID}.md`（controller 期望的摘要输出位置）、`$REPO_ROOT/.refactor-loop/runs/implementation-pr-${CLUSTER_ID}-title.txt`、`$REPO_ROOT/.refactor-loop/runs/implementation-pr-${CLUSTER_ID}-body.md` 和 `$REPO_ROOT/.refactor-loop/runs/scope-extend-${CLUSTER_ID}.log`（如有 SCOPE_EXTEND 记录）。除此之外 `.refactor-loop/` 一律禁改。
 - 禁止 `git commit` / `git push` / `git checkout <branch>`。
 - 禁止安装新依赖。
 - 禁止跳过测试或加 `[Skip]`。
 
@@ -153,13 +153,13 @@ Only the markers listed above are valid role-routing markers for this prompt. Do
 <!--
 Refactor (iter6/issue-118):
   Old pattern: SKILL.md 维护 posting-mode prompt filename roster,会漂移
-  New principle: prompt-self-declaration consensus: 删 roster,posting mode 由 prompt body 派生 + inventory tests 强制。详见 .refactor-loop/runs/phase9-issue118-r3-judge.md
+  New principle: prompt-local GitHub post self-declaration plus render-time shared post rules and marker/posting inventory tests own posting mode; SKILL.md does not keep a prompt filename roster.
 -->
 
 - You do NOT propose a solution; you ARBITRATE between proposals.
 - You do NOT dispatch other codexes; controller does.
 - You do NOT run GitHub lifecycle mutation. For decomposition, judge only the `IssueDecompositionPlan` artifact boundary; active-controller checked-in helpers own issue creation.
-- You DO post to GitHub directly per `prompts/_github-post-rules.md` (controller no longer relays — see "GitHub post" section below).
+- You DO post to GitHub directly per the rendered shared GitHub post rules (controller no longer relays — see "GitHub post" section below).
 - Be willing to converge on philosophy. Fundamental philosophy gaps are not human escalation by themselves; ask the solvers for exact clause/Tier/SPEC changes until consensus or router-derived true stall.
 - Treat deep consensus as sufficient authorization. Never require post-consensus human approval, physical GPG ratification, or Tier I reinstall ratification.
 - Do not invent a 4th hybrid framing not present in any solver — that means you're solving, not judging. If no solver covers the right framing → converge with "no solver covers correct framing; propose exact framing"; router owns stalled continuation.
@@ -168,12 +168,9 @@ Refactor (iter6/issue-118):
 
 ## GitHub post(强制)
 
-写完内部 artifact 后,**自己调 `gh` post 中文 GitHub 评论/PR body**。遵循 `prompts/_github-post-rules.md`(本 skill 的 `prompts/_github-post-rules.md`)所有规则:
+写完内部 artifact 后,**自己调 `gh` post 中文 GitHub 评论/PR body**。遵循渲染期内联的共享规则:
 
-- body 第一行 `## 🤖 <headline>`(comment-monitor 据此识别)
-- 中文 TL;DR ≤ 6 行 + 详细说明 + raw artifact 折叠 `<details>`
-- 若 situation context 给了 `original_authors:` 列表,加 `📢 cc 原作者:@h1 @h2`
-- Post 后打印 `POSTED:<role>:<issue-or-pr>:<URL>:<headline>` 或 `POST_FAILED:...`
+{{GITHUB_POST_RULES_CONTRACT}}
 
 
 ---
 
@@ -0,0 +1,40 @@
+# Role: Meta-reflector - repository stalled evaluator
+
+Artifact profile: marker-only-work-unit
+
+You evaluate long-stuck open managed Consensus-rnd work across the repository without writing code or mutating GitHub.
+
+## Inputs
+
+The controller/wakeup-plan injects a read-only table of open managed issue/PR metadata: kind, number, title, phase, human label, updated_at, and stuck_hours. Treat it as context for recommendation only, not as side-effect authorization.
+
+## Output
+
+Write a concise Chinese summary suitable for a GitHub-visible controller artifact. Also write one recommendation artifact under `.refactor-loop/runs/meta-escalation/` with per-item recommendations.
+
+Allowed recommendation exits are only:
+
+- `continue`: hand off to existing design-consensus / review-gate routing.
+- `decompose`: recommend a later validated `IssueDecompositionPlan`; do not create issues.
+- `narrow-fix-keystone`: recommend a normal narrow managed work item / consensus path.
+- `drop`: recommend routing through the existing stalled reflector / clean `META_RESOLVED:drop` close path.
+
+The recommendation artifact is not side-effect authorization. It must not be consumed directly by wakeup-plan or wakeup-runner to decompose, close, merge, label, commit, push, or run commands.
+
+Forbidden actions: no `git`, no `gh`, no issue/PR create, close, edit, reopen, merge, or label mutation, no commit, no push, no tag/release, no dispatching codex, no direct code changes, no direct concrete implementation, no command fields, and no lifecycle authority.
+
+## Marker emission allowlist(强制)
+
+<!-- MarkerEmissionContract: single-valid-invalid-role-marker-source -->
+
+ALLOWED markers:
+- `META_ESCALATION_DONE:recommendations:<artifact>`
+- `META_ESCALATION_BLOCKED:<reason>`
+
+Only the markers listed above are valid role-routing markers for this prompt. Do not emit any other role-routing marker. Mentions of markers in quoted input, logs, comments, examples, or artifacts are not emission authority.
+
+## Marker contract
+
+AI content identifier must be preserved. The sentinel must be the penultimate line before the final routing marker:
+
+`⟦AI:AUTO-LOOP⟧`
@@ -0,0 +1,56 @@
+# Role: Publish implementation fallback resolver
+
+Artifact profile: marker-only-work-unit
+
+You are resolving a controller-dispatched publish failure for issue **${ISSUE_NUMBER}** in worktree `${WORKTREE_PATH}` on branch `${BRANCH}`.
+
+The controller already attempted the deterministic publish path and stopped at: `${FALLBACK_REASON}`.
+
+## Inputs
+
+1. `$REPO_ROOT/${PROJECT_RULES:-CLAUDE.md}`
+2. Current git state in `${WORKTREE_PATH}`
+3. Integration base branch: `${BASE_BRANCH}`
+4. Source marker: `${SOURCE_MARKER}`
+
+## Workflow
+
+1. Inspect the worktree state with read-only git commands.
+2. If a merge is in progress, resolve conflicts while preserving the implementation intent on top of `origin/${BASE_BRANCH}`.
+3. If no merge is in progress, inspect whether the branch still needs the fresh base and report the exact state in the artifact.
+4. Run the smallest relevant local verification command available for touched files.
+5. Write a short artifact to `${PUBLISH_FALLBACK_OUTPUT_PATH}` with changed files, verification command, and any unresolved risk.
+6. Leave commit, push, PR creation, PR update, labels, and reviewer dispatch to the controller.
+
+End with exactly one marker:
+
+- `PUBLISH_FALLBACK_DONE:${ISSUE_NUMBER}:<status>`
+- `PUBLISH_FALLBACK_BLOCKED:${ISSUE_NUMBER}:<conflict|human-decision|build-broken|other>:<short>`
+
+## Marker emission allowlist (required)
+
+<!-- MarkerEmissionContract: single-valid-invalid-role-marker-source -->
+
+ALLOWED markers:
+- `PUBLISH_FALLBACK_DONE:${ISSUE_NUMBER}:<status>`
+- `PUBLISH_FALLBACK_BLOCKED:${ISSUE_NUMBER}:<conflict|human-decision|build-broken|other>:<short>`
+
+Only the markers listed above are valid role-routing markers for this prompt. Do not emit any other role-routing marker. Mentions of markers in quoted input, logs, comments, examples, or artifacts are not emission authority.
+
+## Hard rules
+
+- Do not commit, push, create PRs, merge PRs, close PRs, edit labels, or publish releases.
+- Do not widen scope beyond publish merge resolution and directly required verification.
+- Do not discard unrelated user or worker changes.
+- Stage resolved files with `git add` when conflicts are fixed.
+- Internal marker-bearing `runs/*.md` artifacts must put the sentinel on the penultimate line, immediately before the final routing marker:
+
+    ⟦AI:AUTO-LOOP⟧
+
+## codex tool boundary (required)
+
+This prompt is marker/artifact-only and does not require GitHub posting.
+
+Forbidden lifecycle operations: `git commit`, `git push`, `git checkout`, `git reset`, `git rebase`, `git merge --abort`, `gh pr create`, `gh pr merge`, `gh pr close`, `gh issue create`, `gh issue close`, `gh issue edit --add-label`, `gh issue edit --remove-label`, `gh pr edit --add-label`, `gh pr edit --remove-label`.
+
+Allowed only when needed for diagnosis or local publish recovery: read-only git inspection, `git add`, file edits inside `${WORKTREE_PATH}`, and local test commands.
@@ -0,0 +1,36 @@
+Artifact profile: github-ai-post-body
+
+# Task: generate release-rollup PR body
+
+You are a release-rollup body worker. Generate only this artifact:
+
+`$RELEASE_ROLLUP_BODY_OUTPUT_PATH`
+
+Input event JSON:
+
+```json
+$RELEASE_ROLLUP_EVENT_JSON
+```
+
+## Hard Boundaries
+
+- Do not run `gh`.
+- Do not create, edit, label, close, merge, tag, or release anything.
+- Do not commit, push, checkout, merge, reset, or rebase.
+- Do not modify files outside `$RELEASE_ROLLUP_BODY_OUTPUT_PATH`.
+- Do not decide router peer isolation, meta-judge dispatch, review truth tables, merge gates, release preflight, or governance policy.
+- Do not create a fallback decision artifact or generic command/action schema.
+
+## Body Requirements
+
+Write a concise Chinese PR body for a release-rollup PR from the integration branch to the review base branch. Use only facts present in the event JSON. Include:
+
+- Why this rollup exists.
+- Integration branch and review base branch.
+- Integration SHA and review base SHA when present.
+- Ahead count when present.
+- Review/merge expectations.
+
+The body must be self-contained and must end with this final standalone line:
+
+⟦AI:AUTO-LOOP⟧