From ddbce306be5ddd35b4aa94bd3a5ce8d5f5b1aa20 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marc-Andr=C3=A9=20Bombeck?= Date: Tue, 28 Jul 2026 00:09:10 +0200 Subject: [PATCH] fix(backup): drop the manifest key the records spread already carries The assembly picked `manifest` out of the records section by hand, one line under the comment explaining that both sections are spread precisely so nobody has to pick their keys. It resolved to the same value the spread had already placed, at the same position, so the emitted file is byte-identical either way. Left in, it is the pattern that lost the custom cycle symptoms sitting next to the note about how that happened. --- src/lib/export/full-backup-payload.ts | 1 - 1 file changed, 1 deletion(-) diff --git a/src/lib/export/full-backup-payload.ts b/src/lib/export/full-backup-payload.ts index fe7b4707e..f8bbe25a9 100644 --- a/src/lib/export/full-backup-payload.ts +++ b/src/lib/export/full-backup-payload.ts @@ -369,7 +369,6 @@ export async function buildFullBackupPayload( unit: n.unit, source: n.source, })), - manifest: records.manifest, }; return {