[SaladDay]

File-heavy idle sandboxes can exceed microsandbox's 4 MiB filesystem checkpoint budget, fail suspension and resume repeatedly. Set a bounded 64 MiB budget in the isolated SDK configuration while retaining ownership and native integrity checks.

When a Web follow-up request loses its response during environment restoration, Parsar now confirms receipt using the original idempotency key, then follows the existing durable Turn ledger instead of reporting a failed submission. Explicit 4xx rejections still fail; Feishu retains its existing delivery retries. No capacity or bot-binding changes.

Validation:

• Parsar: all 85 tests pass; the new regression fails against the original implementation.
• Live Web follow-up: HTTP 200 after 30.4 seconds, then completed with 40,000 files intact and one execution marker; no execution retry.
• Independent full-diff review: no remaining in-scope findings.
• Native Linux helper: go test, go vet and build pass.
• Live suspension: 40,000 files produced 13.1 MiB filesystem state; capture, restore, file/context verification and a second suspension passed. Capacity remains 3/14.

The snapshot budget applies when a VM starts. Deployment must replace the adapter-owned SDK config alongside the helper; an existing running VM retains its original budget.