fix: send full asset manifest during preflight deploys

When preflight was used, the API merged the entire previous deployment's
asset manifest to fill in skipped assets. This caused stale entries from
old builds (renamed/deleted hashed files) to accumulate in the serving
manifest and DB, growing forever across deploys.

Now the CLI sends the full asset manifest as a FormData field alongside
the changed files. The API uses this as the authoritative path list
instead of blindly merging from the previous deployment. Falls back to
old behavior for older CLIs.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: yyx990803

packages/void/src/cli/deploy.ts

@@ -291,6 +291,7 @@ async function runStaticDeploy(
     headerRules,
     redirectRules,
   );
+  if (neededSet) formData.append("assetManifest", JSON.stringify(assetManifest));
   formData.append("source", getTokenSource());
   if (commit) formData.append("commit", commit);
 
@@ -551,6 +552,7 @@ async function runFrameworkDeploy(
     redirectRules,
     dialect,
   });
+  if (neededSet) formData.append("assetManifest", JSON.stringify(assetManifest));
   formData.append("source", getTokenSource());
   if (commit) formData.append("commit", commit);
 
@@ -877,6 +879,7 @@ async function runFullDeploy(
     redirectRules,
     dialect,
   );
+  if (neededSet) formData.append("assetManifest", JSON.stringify(assetManifest));
   formData.append("source", getTokenSource());
   if (commit) formData.append("commit", commit);