fix: ensure StaticSite uploads html after other assets #6118
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.

Why it matters: CloudFront served a brand-new
index.htmlwhile the referencedapp.[hash].jsfiles were still on their way to S3, so early visitors hit 403s and saw a white screen.What changed: we keep user-defined cache semantics, but split
fileOptionsinto HTML vs. non-HTML buckets so SST always ships hashed assets before HTML.Testing: not run (library change).