@hecer/yoke 1.6.0 → 1.6.2

package/canon/skills/yoke-retrofit/SKILL.md

@@ -1,26 +1,26 @@
----
-name: yoke-retrofit
-description: Use when asked to "retrofit", "yoke this project", or set up the Yoke harness in a project — runs the shared setup wizard and configures the same behavior for Claude, Codex, and Gemini.
----
-
-# Yoke Retrofit
-
-Set up or update Yoke through the shared `yoke setup` contract.
-
-1. Inspect the project and identify the current host (`claude`, `codex`, or `gemini`).
-2. Ask these setup questions one at a time and give a direct recommendation:
-   - target agents (recommend the current host; use `all` for deliberately cross-agent projects),
-   - code-graph tool,
-   - autonomous loop on/off,
-   - default runner (recommend the current host),
-   - decision mode: `auto` or `critical`.
-3. Recommend the code graph based on this project:
-   - **Serena** is LSP-accurate and best for large typed codebases or systematic symbol refactors where a missed reference is costly. It needs a language server per language.
-   - **graphify** is fast and multimodal, and is best for exploration, migration, onboarding, or mixed code and document repositories. Its graph is an index and can become stale.
-4. Apply the answers without a second round of prompts:
-   `yoke setup . --yes --host=<host> --agent=<agents> --code-graph=<choice> --runner=<runner> --decision-policy=<auto|critical> --loop|--no-loop`.
-   A human who runs `yoke setup .` directly receives the same five terminal questions.
-5. Show the generated report and backup paths. Existing files are backed up under `.yoke/backup/`; settings are merged where supported.
-6. If an old generated `CLAUDE.md` or `GEMINI.md` contained project-specific instructions, restore them inside its `<!-- yoke:preserve:start -->` / `<!-- yoke:preserve:end -->` block. Preserve blocks survive every later retrofit.
-
-The generated harness includes the provider-neutral `yoke-workflow` skill. It owns the planning questions, approved-plan handoff, autonomous stories, and critical-decision resume flow.
+---
+name: yoke-retrofit
+description: Use when asked to "retrofit", "yoke this project", or set up the Yoke harness in a project — runs the shared setup wizard and configures the same behavior for Claude, Codex, and Gemini.
+---
+
+# Yoke Retrofit
+
+Set up or update Yoke through the shared `yoke setup` contract.
+
+1. Inspect the project and identify the current host (`claude`, `codex`, or `gemini`).
+2. Ask these setup questions one at a time and give a direct recommendation:
+   - target agents (recommend the current host; use `all` for deliberately cross-agent projects),
+   - code-graph tool,
+   - autonomous loop on/off,
+   - default runner (recommend the current host),
+   - decision mode: `auto` or `critical`.
+3. Recommend the code graph based on this project:
+   - **Serena** is LSP-accurate and best for large typed codebases or systematic symbol refactors where a missed reference is costly. It needs a language server per language.
+   - **graphify** is fast and multimodal, and is best for exploration, migration, onboarding, or mixed code and document repositories. Its graph is an index and can become stale.
+4. Apply the answers without a second round of prompts:
+   `yoke setup . --yes --host=<host> --agent=<agents> --code-graph=<choice> --runner=<runner> --decision-policy=<auto|critical> --loop|--no-loop`.
+   A human who runs `yoke setup .` directly receives the same five terminal questions.
+5. Show the generated report and backup paths. Existing files are backed up under `.yoke/backup/`; settings are merged where supported.
+6. If an old generated `CLAUDE.md` or `GEMINI.md` contained project-specific instructions, restore them inside its `<!-- yoke:preserve:start -->` / `<!-- yoke:preserve:end -->` block. Preserve blocks survive every later retrofit.
+
+The generated harness includes the provider-neutral `yoke-workflow` skill. It owns the planning questions, approved-plan handoff, autonomous stories, and critical-decision resume flow.

package/canon/skills/yoke-workflow/SKILL.md

@@ -1,20 +1,20 @@
----
-name: yoke-workflow
-description: Use when the user asks Yoke to plan and build a feature, run stories autonomously, continue a Yoke loop, or only interrupt for major decisions.
----
-
-# Yoke Workflow
-
-Provide the same interaction contract in Claude, Codex, and Gemini.
-
-1. Read `.yoke/config.yaml`. If it is missing, offer `yoke setup . --host=<current-agent>` and run the setup flow before planning.
-2. Plan before starting the loop. Inspect the project, then ask one focused question at a time only where the answer changes product behavior, scope, architecture, security, data ownership, external cost, or an irreversible choice. Include a recommended answer. Resolve routine implementation details yourself.
-3. Summarize the agreed design in `.yoke/plan.md`, including goals, non-goals, constraints, and decisions. Use the `authoring-prd` skill to turn it into small stories with testable acceptance criteria. Run `yoke prd check .`.
-4. Ask once for approval of the complete plan and story set. Do not begin implementation before that approval.
-5. If `loop.enabled` is true, run the stories without routine follow-up questions using the configured runner. Prefer `yoke loop run . --max=5 --isolate`, report status after each batch, and continue until complete or genuinely blocked.
-6. Respect `loop.decisionPolicy`:
-   - `auto`: choose the most suitable option from the plan, current code, and established conventions. Record the interpretation and continue.
-   - `critical`: routine ambiguity is still resolved automatically. If the loop reports a pending critical decision, run `yoke loop decision .`, present its options and recommendation to the user, ask exactly that question, then run `yoke loop answer . --choice=<id> --rationale="<answer>"`. The answer command records the decision and resumes the same story.
-7. Never ask whether to run tests, review, commit, or continue to the next approved story. Those are part of the approved workflow.
-
-The user's configured commit identity is authoritative. Do not add an AI co-author unless `commit.allowCoAuthors` explicitly permits it.
+---
+name: yoke-workflow
+description: Use when the user asks Yoke to plan and build a feature, run stories autonomously, continue a Yoke loop, or only interrupt for major decisions.
+---
+
+# Yoke Workflow
+
+Provide the same interaction contract in Claude, Codex, and Gemini.
+
+1. Read `.yoke/config.yaml`. If it is missing, offer `yoke setup . --host=<current-agent>` and run the setup flow before planning.
+2. Plan before starting the loop. Inspect the project, then ask one focused question at a time only where the answer changes product behavior, scope, architecture, security, data ownership, external cost, or an irreversible choice. Include a recommended answer. Resolve routine implementation details yourself.
+3. Summarize the agreed design in `.yoke/plan.md`, including goals, non-goals, constraints, and decisions. Use the `authoring-prd` skill to turn it into small stories with testable acceptance criteria. Run `yoke prd check .`.
+4. Ask once for approval of the complete plan and story set. Do not begin implementation before that approval.
+5. If `loop.enabled` is true, run the stories without routine follow-up questions using the configured runner. Prefer `yoke loop run . --max=5 --isolate`, report status after each batch, and continue until complete or genuinely blocked.
+6. Respect `loop.decisionPolicy`:
+   - `auto`: choose the most suitable option from the plan, current code, and established conventions. Record the interpretation and continue.
+   - `critical`: routine ambiguity is still resolved automatically. If the loop reports a pending critical decision, run `yoke loop decision .`, present its options and recommendation to the user, ask exactly that question, then run `yoke loop answer . --choice=<id> --rationale="<answer>"`. The answer command records the decision and resumes the same story.
+7. Never ask whether to run tests, review, commit, or continue to the next approved story. Those are part of the approved workflow.
+
+The user's configured commit identity is authoritative. Do not add an AI co-author unless `commit.allowCoAuthors` explicitly permits it.

package/canon/tools/codex-rtk-hook.mjs

@@ -1,36 +1,36 @@
 import { spawnSync } from 'node:child_process'
-import { resolve } from 'node:path'
-import { pathToFileURL } from 'node:url'
-
-function rtkCheck(command) {
-  const result = spawnSync('rtk', ['hook', 'check', command], { encoding: 'utf8', timeout: 3000 })
-  return result.status === 0 ? result.stdout.trim() : ''
-}
-
-export function rewriteHookInput(input, check = rtkCheck) {
-  if (input?.tool_name !== 'Bash' && input?.toolName !== 'Bash') return null
-  const toolInput = input.tool_input ?? input.toolInput
-  const command = toolInput?.command
-  if (typeof command !== 'string' || command.trim() === '') return null
-  const rewritten = check(command)
-  if (!rewritten || rewritten === command) return null
-  return {
-    hookSpecificOutput: {
-      hookEventName: 'PreToolUse',
-      updatedInput: { ...toolInput, command: rewritten },
-    },
-  }
-}
-
-async function main() {
-  let raw = ''
-  for await (const chunk of process.stdin) raw += chunk
-  try {
-    const output = rewriteHookInput(JSON.parse(raw))
-    if (output) process.stdout.write(JSON.stringify(output))
-  } catch {
-    // Compression is an optimization. Malformed input must never block Codex.
-  }
-}
-
-if (process.argv[1] && pathToFileURL(resolve(process.argv[1])).href === import.meta.url) await main()
+import { resolve } from 'node:path'
+import { pathToFileURL } from 'node:url'
+
+function rtkCheck(command) {
+  const result = spawnSync('rtk', ['hook', 'check', command], { encoding: 'utf8', timeout: 3000 })
+  return result.status === 0 ? result.stdout.trim() : ''
+}
+
+export function rewriteHookInput(input, check = rtkCheck) {
+  if (input?.tool_name !== 'Bash' && input?.toolName !== 'Bash') return null
+  const toolInput = input.tool_input ?? input.toolInput
+  const command = toolInput?.command
+  if (typeof command !== 'string' || command.trim() === '') return null
+  const rewritten = check(command)
+  if (!rewritten || rewritten === command) return null
+  return {
+    hookSpecificOutput: {
+      hookEventName: 'PreToolUse',
+      updatedInput: { ...toolInput, command: rewritten },
+    },
+  }
+}
+
+async function main() {
+  let raw = ''
+  for await (const chunk of process.stdin) raw += chunk
+  try {
+    const output = rewriteHookInput(JSON.parse(raw))
+    if (output) process.stdout.write(JSON.stringify(output))
+  } catch {
+    // Compression is an optimization. Malformed input must never block Codex.
+  }
+}
+
+if (process.argv[1] && pathToFileURL(resolve(process.argv[1])).href === import.meta.url) await main()

package/canon/tools/graphify.md

@@ -1,3 +1,3 @@
-# Tool: graphify (code-graph)
-
-MIT, multimodal code/doc graph. Wired as an MCP server for all three agents (stdio). Prefer symbol/graph lookups over reading whole files. Caveat: heuristic edges (INFERRED/AMBIGUOUS) and a static index that can go stale — rebuild on significant changes.
+# Tool: graphify (code-graph)
+
+MIT, multimodal code/doc graph. Wired as an MCP server for all three agents (stdio). Prefer symbol/graph lookups over reading whole files. Caveat: heuristic edges (INFERRED/AMBIGUOUS) and a static index that can go stale — rebuild on significant changes.

package/canon/tools/playwright-mcp.md

@@ -1,3 +1,3 @@
-# Tool: Playwright MCP (browser / dogfooding)
-
-Microsoft Playwright MCP, Apache-2.0. Wired as an MCP server for all three agents — the only browser tool with native MCP parity across Claude/Codex/Gemini. Used for QA, dogfooding user flows, screenshots, and deploy verification.
+# Tool: Playwright MCP (browser / dogfooding)
+
+Microsoft Playwright MCP, Apache-2.0. Wired as an MCP server for all three agents — the only browser tool with native MCP parity across Claude/Codex/Gemini. Used for QA, dogfooding user flows, screenshots, and deploy verification.

package/canon/tools/rtk.md

@@ -1,7 +1,7 @@
-# Tool: rtk (token compression)
-
-Per-agent wiring (generated by Baustein B):
-
-- **Claude Code:** PreToolUse hook auto-rewrites commands (`git status` → `rtk git status`). On Windows this needs WSL; otherwise fall back to instruction mode (this file injected into CLAUDE.md telling the agent to prefix commands with `rtk`).
-- **Codex CLI:** inject `RTK.md` / AGENTS.md instruction.
-- **Gemini CLI:** no hook system — register rtk as an MCP tool or inject the GEMINI.md instruction.
+# Tool: rtk (token compression)
+
+Per-agent wiring (generated by Baustein B):
+
+- **Claude Code:** PreToolUse hook auto-rewrites commands (`git status` → `rtk git status`). On Windows this needs WSL; otherwise fall back to instruction mode (this file injected into CLAUDE.md telling the agent to prefix commands with `rtk`).
+- **Codex CLI:** inject `RTK.md` / AGENTS.md instruction.
+- **Gemini CLI:** no hook system — register rtk as an MCP tool or inject the GEMINI.md instruction.

package/canon/tools/serena.md

@@ -1,9 +1,9 @@
-# Tool: Serena (code-graph, LSP-accurate)
-
-MIT, MCP-first. The alternative to graphify, selected via `yoke retrofit --code-graph=serena`. Serena uses real language servers (LSP) for symbol-accurate, cross-file retrieval and refactoring (`find_symbol`, `find_referencing_symbols`, rename/move) — no static index that goes stale, so it will not miss a reference.
-
-Wired as an MCP server for all three agents. Best for large, strongly-typed codebases (TypeScript, Python, Go) doing systematic refactoring, where missing a caller is costly.
-
+# Tool: Serena (code-graph, LSP-accurate)
+
+MIT, MCP-first. The alternative to graphify, selected via `yoke retrofit --code-graph=serena`. Serena uses real language servers (LSP) for symbol-accurate, cross-file retrieval and refactoring (`find_symbol`, `find_referencing_symbols`, rename/move) — no static index that goes stale, so it will not miss a reference.
+
+Wired as an MCP server for all three agents. Best for large, strongly-typed codebases (TypeScript, Python, Go) doing systematic refactoring, where missing a caller is costly.
+
 Caveat: needs one language server per language (can be fiddly on Windows for exotic languages) and requires `uv`. The launch command is a best-effort template — adjust to your install, e.g. `uvx --from git+https://github.com/oraios/serena serena-mcp-server`.
 
 Yoke disables Serena's automatic web-dashboard launch in generated MCP configurations. The

package/dist/agents/process.js

@@ -81,6 +81,11 @@ export function startProviderProcess(agent, invocation, options = {}) {
         telemetry: telemetry.finish(),
     });
     const finalize = (exitCode) => {
+        // Windows can emit close before taskkill's process-tree state is observable.
+        // Reconfirm here so successful termination does not leave a stale ownership record.
+        if (termination && pid !== undefined && !terminationConfirmed) {
+            terminationConfirmed = terminateProcessTree(pid, true);
+        }
         const details = evidence();
         if (recordFailure) {
             finish({ ...details, kind: 'spawn-failed', error: recordFailure });

package/dist/agents/providers.js

@@ -13,7 +13,7 @@ const argsFor = (agent, permissions) => {
             return ['exec', '--dangerously-bypass-approvals-and-sandbox', '--json'];
         if (permissions === 'read-only')
             return ['exec', '--sandbox', 'read-only', '--json'];
-        return ['exec', '--full-auto', '--json'];
+        return ['exec', '--sandbox', 'workspace-write', '--approve-for-me', '--json'];
     }
     if (permissions === 'unsafe')
         return ['--yolo'];

package/dist/loop/cleanup.js

@@ -6,6 +6,7 @@ import { processIncarnation } from '../agents/process-incarnation.js';
 import { acquireTakeoverLease, acquireTakeoverRecoveryLease, lockPath, takeoverLockPath, readLock, isPidAlive, releaseTakeoverLease, releaseTakeoverRecoveryLease, takeoverRecoveryPath, } from './lock.js';
 import { killProcessForCleanup, killProcessTreeForCleanup } from './watchdog.js';
 import { cleanupClaims } from './claims.js';
+import { clearStatus } from './reporter.js';
 // Reap orphaned runners PROJECT-SCOPED: kill only pids recorded in this project's
 // .yoke/runner.pid files (main dir + each worktree). Never by process-name or
 // command-line pattern — that takes down runners belonging to OTHER projects,
@@ -223,6 +224,8 @@ export function runLoopCleanup(targetDir, opts = {}) {
             rmSync(lockFile, { force: true });
             console.log('Removed stale loop lock.');
         }
+        if (failed === 0)
+            clearStatus(targetDir);
         console.log(removed === 0 && failed === 0 ? 'No destructive cleanup performed.' : `Removed ${removed} worktree(s)${failed > 0 ? `, ${failed} failed` : ''}.`);
         return failed === 0 ? 0 : 1;
     }

package/dist/loop/reporter.js

@@ -1,4 +1,4 @@
-import { existsSync, readFileSync, writeFileSync, mkdirSync, renameSync, appendFileSync, statSync } from 'node:fs';
+import { existsSync, readFileSync, writeFileSync, mkdirSync, renameSync, appendFileSync, statSync, rmSync } from 'node:fs';
 import { join } from 'node:path';
 export const LOG_CAP_BYTES = 256 * 1024;
 // Append a line to .yoke/loop.log, keeping the file bounded: once it exceeds
@@ -77,6 +77,9 @@ export function readStatus(dir) {
         return null;
     }
 }
+export function clearStatus(dir) {
+    rmSync(statusPath(dir), { force: true });
+}
 export function makeReporter(dir, opts = {}, now = () => new Date()) {
     const sink = opts.log ?? ((line) => process.stdout.write(line + '\n'));
     const emitConsole = (line) => { if (!opts.quiet)

package/dist/loop/watchdog.js

@@ -62,8 +62,10 @@ export function killProcessTreeForCleanup(pid, platform = process.platform, runT
     }
 }) {
     if (platform === 'win32') {
+        // taskkill reports a non-zero status when the process disappeared between
+        // observation and cleanup; that is already the desired terminal state.
         if (runTaskkill('taskkill', ['/PID', String(pid), '/T', '/F']) !== 0)
-            return false;
+            return !isProcessAlive(pid);
         return confirmProcessStopped(pid, isProcessAlive);
     }
     try {

package/dist/prd/command.js

@@ -5,23 +5,23 @@ import { acceptanceText, criterionCommandProblem, isAcceptanceCriterion, loadPrd
 import { agentInvocation, buildWatchdogInvocation, runAgent, isAgentAvailable, } from '../loop/runner.js';
 import { resolveIdleMs } from '../loop/run-command.js';
 import { detectHostAgent, resolveRunnerAgent } from '../agents/host.js';
-export const PRD_TEMPLATE = `# Yoke PRD — the loop picks the lowest-priority open story each iteration.
-# Story format (see canon/loop/prd.schema.md):
-# - id: STORY-1
-#   title: scaffold the project with a runnable test suite
-#   priority: 1
-#   needs: []             # optional story IDs that must pass first
-#   area: foundation      # optional collision domain for parallel runs
-#   agent: codex          # optional claude|codex|gemini affinity
-#   acceptance:
-#     - id: suite-runs
-#       text: "the project test suite can run"
-#       verify: ["npm run test:suite-runs"]
-#     - id: scaffold-starts
-#       text: "the scaffolded application starts"
-#       verify: ["npm run test:scaffold-starts"]
-#   passes: false
-[]
+export const PRD_TEMPLATE = `# Yoke PRD — the loop picks the lowest-priority open story each iteration.
+# Story format (see canon/loop/prd.schema.md):
+# - id: STORY-1
+#   title: scaffold the project with a runnable test suite
+#   priority: 1
+#   needs: []             # optional story IDs that must pass first
+#   area: foundation      # optional collision domain for parallel runs
+#   agent: codex          # optional claude|codex|gemini affinity
+#   acceptance:
+#     - id: suite-runs
+#       text: "the project test suite can run"
+#       verify: ["npm run test:suite-runs"]
+#     - id: scaffold-starts
+#       text: "the scaffolded application starts"
+#       verify: ["npm run test:scaffold-starts"]
+#   passes: false
+[]
 `;
 export const MAX_PLANNING_BRIEF_CHARS = 20_000;
 export const MAX_PLANNING_BRIEF_BYTES = MAX_PLANNING_BRIEF_CHARS * 4;

package/dist/retrofit/planners/claude.js

@@ -6,21 +6,21 @@ import { hasWsl } from '../wsl.js';
 import { detectGstack } from '../gstack.js';
 import { PRESERVE_SCAFFOLD } from '../preserve.js';
 import { skillPackageActions } from '../skill-actions.js';
-const GSTACK_COMPOSE = `## Composed tools (gstack detected)
-
-This project also has [gstack](https://github.com/garrytan/gstack) installed. For capabilities Yoke does not ship, prefer gstack's skills:
-
-- Live-browser QA → \`/qa\`
-- Security audit → \`/cso\`
-- Ship / deploy → \`/ship\`, \`/land-and-deploy\`
+const GSTACK_COMPOSE = `## Composed tools (gstack detected)
+
+This project also has [gstack](https://github.com/garrytan/gstack) installed. For capabilities Yoke does not ship, prefer gstack's skills:
+
+- Live-browser QA → \`/qa\`
+- Security audit → \`/cso\`
+- Ship / deploy → \`/ship\`, \`/land-and-deploy\`
 `;
-const claudeMd = (rtkNote, composeNote) => `# Project Instructions
-
-This project uses the Yoke harness. Baseline instructions:
-
-@AGENTS.md
-${rtkNote ? `\n${rtkNote}\n` : ''}${composeNote ? `\n${composeNote}\n` : ''}
-${PRESERVE_SCAFFOLD}
+const claudeMd = (rtkNote, composeNote) => `# Project Instructions
+
+This project uses the Yoke harness. Baseline instructions:
+
+@AGENTS.md
+${rtkNote ? `\n${rtkNote}\n` : ''}${composeNote ? `\n${composeNote}\n` : ''}
+${PRESERVE_SCAFFOLD}
 `;
 export function planClaude(canonDir, targetDir, wslAvailable = hasWsl(), codeGraph = 'graphify', gstackDetected = detectGstack(targetDir)) {
     const manifest = loadManifest(join(canonDir, 'manifest.yaml'));

package/dist/retrofit/preserve.js

@@ -1,7 +1,7 @@
 export const PRESERVE_START = '<!-- yoke:preserve:start -->';
 export const PRESERVE_END = '<!-- yoke:preserve:end -->';
-export const PRESERVE_SCAFFOLD = `${PRESERVE_START}
-<!-- Project-specific instructions go here. Yoke keeps this block across retrofits. -->
+export const PRESERVE_SCAFFOLD = `${PRESERVE_START}
+<!-- Project-specific instructions go here. Yoke keeps this block across retrofits. -->
 ${PRESERVE_END}`;
 /**
  * Extract the inner content of every balanced preserve-marker pair, in order.

package/docs/MIGRATING-TO-1.0.md

@@ -1,33 +1,33 @@
-# Migrating to Yoke 1.0
-
-Yoke 1.0 changes unsafe implicit behavior into explicit policy.
-
-## Runner permissions
-
-The default is `runner.permissions: safe`. Automation that intentionally requires a full
-sandbox bypass must pass `--unsafe` or configure `runner.permissions: unsafe`. Use
-`read-only` for planning and probing.
-
-## Reviews
-
-Reviewers write `.yoke/review-verdict.json`; Yoke validates and consumes it. The reviewer must
-differ from the implementer unless `--allow-self-review` is explicit. CI can add `--json`.
-
-## Commit ownership
-
-Yoke resolves identity before implementation. Configure it when Git has no identity:
-
-```yaml
-commit:
-  authorName: HECer
-  authorEmail: hec_er@web.de
-  allowCoAuthors: false
-```
-
-## PRDs, audit, and cleanup
-
-Existing PRDs remain valid. Optional `needs`, `area`, and `agent` fields add dependencies,
-collision domains, and affinity. Enable the story audit gate with `audit.enabled: true` and
-version suppressions with `suppressionsVersion: 1`.
-
-`yoke loop cleanup` now reports retained worktrees. Add `--remove-worktrees` for deletion.
+# Migrating to Yoke 1.0
+
+Yoke 1.0 changes unsafe implicit behavior into explicit policy.
+
+## Runner permissions
+
+The default is `runner.permissions: safe`. Automation that intentionally requires a full
+sandbox bypass must pass `--unsafe` or configure `runner.permissions: unsafe`. Use
+`read-only` for planning and probing.
+
+## Reviews
+
+Reviewers write `.yoke/review-verdict.json`; Yoke validates and consumes it. The reviewer must
+differ from the implementer unless `--allow-self-review` is explicit. CI can add `--json`.
+
+## Commit ownership
+
+Yoke resolves identity before implementation. Configure it when Git has no identity:
+
+```yaml
+commit:
+  authorName: HECer
+  authorEmail: hec_er@web.de
+  allowCoAuthors: false
+```
+
+## PRDs, audit, and cleanup
+
+Existing PRDs remain valid. Optional `needs`, `area`, and `agent` fields add dependencies,
+collision domains, and affinity. Enable the story audit gate with `audit.enabled: true` and
+version suppressions with `suppressionsVersion: 1`.
+
+`yoke loop cleanup` now reports retained worktrees. Add `--remove-worktrees` for deletion.

package/docs/MIGRATING-TO-1.1.md

@@ -1,27 +1,27 @@
-# Migrating to Yoke 1.1
-
-Yoke 1.1 makes Claude, Codex, and Gemini share the same setup, planning, runner-selection, and decision behavior.
-
-Run the setup wizard once in an existing project:
-
-```bash
-npx @hecer/yoke@1.1.0 setup .
-```
-
-It preserves existing Yoke configuration and asks for target agents, code graph, loop state, default runner, and decision mode. A non-interactive agent can apply explicit choices with `--yes`.
-
-The new config fields are optional and backward-compatible:
-
-```yaml
-runner:
-  agent: codex
-  permissions: safe
-loop:
-  enabled: true
-  timeoutMinutes: 30
-  decisionPolicy: critical  # auto | critical
-```
-
-`loop.onAmbiguity: resolve|abort` and `--on-ambiguity=` still work. Prefer `decisionPolicy` for new projects: `auto` resolves routine choices without asking; `critical` pauses only for high-impact decisions and continues after `yoke loop answer`. Resume restores the original isolation, review, runner, permissions, timeout, and policy flags instead of silently weakening the run. If the restart cannot begin, `yoke loop resume` retries from the request-bound state stored under Git's private state directory.
-
-Restart an already-open Codex task after retrofit if it does not discover the newly generated `.agents/skills/yoke-workflow/SKILL.md`.
+# Migrating to Yoke 1.1
+
+Yoke 1.1 makes Claude, Codex, and Gemini share the same setup, planning, runner-selection, and decision behavior.
+
+Run the setup wizard once in an existing project:
+
+```bash
+npx @hecer/yoke@1.1.0 setup .
+```
+
+It preserves existing Yoke configuration and asks for target agents, code graph, loop state, default runner, and decision mode. A non-interactive agent can apply explicit choices with `--yes`.
+
+The new config fields are optional and backward-compatible:
+
+```yaml
+runner:
+  agent: codex
+  permissions: safe
+loop:
+  enabled: true
+  timeoutMinutes: 30
+  decisionPolicy: critical  # auto | critical
+```
+
+`loop.onAmbiguity: resolve|abort` and `--on-ambiguity=` still work. Prefer `decisionPolicy` for new projects: `auto` resolves routine choices without asking; `critical` pauses only for high-impact decisions and continues after `yoke loop answer`. Resume restores the original isolation, review, runner, permissions, timeout, and policy flags instead of silently weakening the run. If the restart cannot begin, `yoke loop resume` retries from the request-bound state stored under Git's private state directory.
+
+Restart an already-open Codex task after retrofit if it does not discover the newly generated `.agents/skills/yoke-workflow/SKILL.md`.