chore: remove git lfs asset tracking

Author: NathanFlurry

.claude/reference/content-frontmatter.md

@@ -23,3 +23,5 @@ Required fields:
 Optional fields:
 
 - `keywords` (string array)
+- `image` (`true` or `{ format: string }`) — hero image flag. Presence means the post has a hero image in R2 at `website/blog/{post-slug}/image.{format}`; use `image: true` for the default `image.png` or `image: { format: "gif" }` for another extension. The URL is derived from the slug and dimensions are fixed (2:1), so do not write `src`, `width`, or `height`. Resolved by `website/src/lib/postImage.ts`.
+- `unpublished` (boolean)

.gitattributes

@@ -1,12 +1,15 @@
+# Do not add Git LFS filters here. jj can snapshot raw working-tree bytes
+# without running Git LFS clean filters, so large public assets belong in R2.
+
 * text eol=lf
 *.png binary
 *.jpg binary
 *.jpeg binary
-*.gif filter=lfs diff=lfs merge=lfs -text
-*.tar filter=lfs diff=lfs merge=lfs -text
-*.tar.gz filter=lfs diff=lfs merge=lfs -text
-*.tgz filter=lfs diff=lfs merge=lfs -text
-engine/packages/test-snapshot-gen/snapshots/** filter=lfs diff=lfs merge=lfs -text
+*.gif binary
+*.tar binary
+*.tar.gz binary
+*.tgz binary
+*.sst binary
 
 **/Cargo.lock linguist-generated=true