diff --git a/_docs/_process_leftovers/2026-05-14_az_403_cancellation_pending_tracker.md b/_docs/_process_leftovers/2026-05-14_az_403_cancellation_pending_tracker.md
deleted file mode 100644
index 7bc6061..0000000
--- a/_docs/_process_leftovers/2026-05-14_az_403_cancellation_pending_tracker.md
+++ /dev/null
@@ -1,49 +0,0 @@
-# Leftover — AZ-403 Jira transition to Cancelled (pending tracker write)
-
-**Timestamp**: 2026-05-14T08:35:00+03:00
-**Author**: agent (autodev cycle 1, Step 7 batch loop, replay-redesign docs phase)
-
-## What was blocked
-
-A Jira `transitionJiraIssue` call to move `AZ-403` (gps-denied-replay-cli Dockerfile + SBOM diff CI step) from its current status to **Cancelled**, plus a comment explaining the cancellation reason.
-
-The transition was NOT performed during this docs phase because the docs phase did not touch the tracker (the replay-redesign was a docs-only change; the tracker write properly belongs to the next time autodev's tracker-write path runs, which is the standard implement / batch-loop step where Jira transitions happen).
-
-## Full payload (replay this on next tracker-write opportunity)
-
-```yaml
-tracker: jira
-cloudId: denyspopov.atlassian.net
-projectKey: AZ
-issueIdOrKey: AZ-403
-
-action: transitionJiraIssue
-target_status: Cancelled
-comment: |
-  Cancelled per ADR-011 (replay-as-configuration; see `_docs/02_document/architecture.md`
-  § ADR-011). The replay binary no longer exists as a separate Docker image — the airborne
-  image serves both live and replay modes from a single source tree with `config.mode = "replay"`
-  chosen at startup. No SBOM-diff CI step is needed because there are no per-replay
-  exclusions to enforce (C10/C11/C12 are already excluded from the airborne image by
-  ADR-002 + ADR-004; C6 is REQUIRED in replay per epic AZ-265 AC-3).
-
-  Original task file moved to `_docs/02_tasks/done/AZ-403_replay_dockerfile_ci.md` with a
-  cancellation banner; AZ-404's dependency on this ticket removed from
-  `_docs/02_tasks/_dependencies_table.md`. No replacement ticket — the replay-mode
-  console-script entry point ships from the airborne image via AZ-402.
-```
-
-## Reason for deferral
-
-The current turn is a docs-only redesign; the tracker write properly belongs to the next tracker-touching step (autodev's standard implement / batch-loop tracker-transition step) so a single batched tracker pass picks up the AZ-403 cancellation alongside any other tracker transitions for AZ-401/402/404/405 if they accompany the implementation step.
-
-This is a NON-user-input blocker (`.cursor/rules/tracker.mdc` Leftovers Mechanism qualifying case) — no user decision is pending; replaying the call is straightforward when the tracker is next touched.
-
-## Replay obligation
-
-At the next autodev start, OR at the next batch implementation step that performs Jira transitions, the agent MUST:
-
-1. Read this file.
-2. Issue the `transitionJiraIssue` call with the payload above.
-3. On success → delete this file.
-4. On failure → update the file timestamp + reason, surface to the user only if the failure shape requires user input (auth, missing transition target, missing permission).