{"version":"2.1.260","anchor":"job-delete-telemetry-now-records-whether-worktree-discard-wa","canonical_anchor":"job-delete-telemetry-now-records-whether-worktree-discard-wa","heading":"job_delete telemetry now records whether worktree discard was confirmed","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/job-delete-telemetry-now-records-whether-worktree-discard-wa","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### job_delete telemetry now records whether worktree discard was confirmed\n\nJob deletion telemetry now records whether worktree discard was actually confirmed.\n\n`job_delete` telemetry events, for both the worktree-left-in-place path and the default path, now include a `discard_confirmed` field (`discardConfirmed` on the delete-session return value) reflecting whether the user confirmed discarding a worktree.\n\n- Area: Sessions\n- Names: `discard_confirmed`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}