* `plan_reject_hole_max`: A composed plan was rejected because its hole-punch operation count exceeded `hole-max`.
* `plan_reject_total_max`: A composed plan was rejected because its total operation count exceeded `total-max`.
* `plan_snap_extra`: A dst plan's space debt included extra reference cost for unsharing snapshot metadata, because the dst has references in a multi-member snapshot family (`rewrite.snapshot-sharing`).
+ * `plan_src_edge_blocked`: The coverage search skipped a candidate match because its src range is already used by an earlier dedupe in the same plan (each src range may be used once per plan).
* `plan_src_gap`: A dst plan was abandoned before executing because the src extent's references leave a gap in the matched range, so part of the pair has no src file offset. Handled like a vanished src ref.
* `plan_src_gone`: A dst plan was abandoned before executing because a planned source window had no covering ref at all — the ref vanished from the refetched refs list (file range overwritten, file or snapshot deleted) between planning and execution. Expected filesystem churn; the extent is rescanned in a later cycle.
* `plan_src_open_fail`: A dst plan was abandoned before executing because every ref covering a planned source window failed to open (deleted files or snapshots lingering in the refs list). Expected filesystem churn; the extent is rescanned in a later cycle.
+ * `plan_src_overlap`: Plan composition found two selected matches using the same src range. The coverage search prevents this, so it indicates a bug; the plan is abandoned with an error.
* `plan_start`: A planner pass over one start extent began.
* `plan_worse_than_null`: The winning plan had a space debt above the do-nothing floor — an invariant violation guard; for a non-forced start the null floor should always win in that case.