{"version":"2.1.222","anchor":"resuming-into-a-missing-or-unverifiable-worktree-is-now-expl","canonical_anchor":"resuming-into-a-missing-or-unverifiable-worktree-is-now-expl","heading":"Resuming into a missing or unverifiable worktree is now explained","tier":"notice","area":"Worktrees","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222\/e\/resuming-into-a-missing-or-unverifiable-worktree-is-now-expl","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222","markdown":"### Resuming into a missing or unverifiable worktree is now explained\n\nResuming into a missing worktree now warns you, and headless runs exit with an error instead of continuing.\n\n**What**\n\nWorktree re-entry on resume returns a structured outcome that the session reports, instead of quietly continuing without isolation.\n\n**Details**\n\n- a vanished worktree clears the binding and continues without isolation\n- an unverifiable or rejected pin keeps the binding\n- interactive sessions show a warning message; headless and print paths write an error to stderr and exit non-zero rather than continuing unisolated\n- telemetry `tengu_worktree_resume_root_rejected` carries the reason and a poisoned flag\n\n**Evidence**\n\n`The worktree binding has been cleared.`\n\n- Area: Worktrees\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 0\/5"}