next.js

8a473f45 - turbo-tasks-backend: add persistence delete/tombstone plumbing for GC (#95975)

turbo-tasks-backend: add persistence delete/tombstone plumbing for GC (#95975) ## What The persistence-layer mechanism to tombstone (delete) tasks from the on-disk cache. A GC-collected task is represented as a `SnapshotItem::Delete` that rides the same streaming iterator `save_snapshot` already consumes for puts, so tombstones are applied in the same commit/batch as the snapshot with no side-channel. - `SnapshotItem` becomes an enum: `Put { … }` (the existing path) and `Delete(TaskDeletion)`. - `TurboWriteBatch::delete/value_delete` passthrough to `turbo_persistence`. - `save_snapshot` applies deletes inline in the parallel put phase ## Note `SnapshotItem::Delete` is `#[allow(dead_code)]` here: this PR lands the persistence-side *handling* and its tests, but nothing *emits* a `Delete` yet. The GC pass that soft-deletes tasks and serializes them to `Delete` lands in the next PR in the stack. So this PR is a no-op at runtime. --------- Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>