site: rename "finds" superpost collection to "bundles"

Disambiguates the one-letter `find` (item) vs `finds` (roundup) split that
kept causing confusion. Audience-facing now: `/bundles/<slug>/`, "Bundle"
labels in home/footer/search.

Internals: `getCollection('finds')` → `('bundles')`, `Entry.type 'finds'`
→ `'bundle'`, `OgFallback 'finds'` → `'bundles'`, `findListMosaic` →
`bundleMosaic`, `FindsPost` → `Bundle`, `findsReferencing` →
`bundlesReferencing`. Build script + generated mosaic dir follow
(`scripts/build-bundle-mosaics.mjs`, `src/generated/bundle-mosaics/`).

Skills `build-finds` → `build-bundle`, `cluster-finds` →
`cluster-bundles`. The `find` collection (individual items) is unchanged.

No URL redirects: low external-link surface area.

.claude/skills/build-review/SKILL.md

@@ -72,14 +72,34 @@ Edit `src/content/find/<slug>.mdx` frontmatter: add `promotedTo: <review-slug>`.
 
 (Slug usually matches the find's slug, so `promotedTo` and the find's filename match.)
 
-### 6. Verify
+### 6. Register the hero in `src/lib/hero.ts` (REQUIRED if a hero asset exists)
+
+This is the step that has bitten us repeatedly. **The home grid and category cards do NOT auto-discover review hero assets** — they only show a hero if the review's slug is a key in the `heroes` record exported by `src/lib/hero.ts`. Skipping this step ships a review whose grid card is empty.
+
+For a review with a static image hero (`hero.png`, `hero.jpg`, `hero.webp`):
+
+1. Add an `import` line near the top, alphabetically grouped with the other image imports. The variable name is the slug in camelCase. Example for slug `tablepro`:
+   ```ts
+   import tablepro from '../content/reviews/tablepro/hero.png';
+   ```
+2. Add an entry to the `heroes` record, alphabetically by key:
+   ```ts
+   tablepro: { kind: 'image', src: tablepro },
+   ```
+
+For a review with a video hero (`.mp4`), put the import in the second (video) import group and the record entry uses `kind: 'video'`. Match the existing pattern.
+
+If the review legitimately has no hero asset (rare — e.g. text-only reviews like `snewpapers-newspaper-archive`, `sindre-sorhus-older-mac-apps`), explicitly note it in the log entry from step 8 ("no hero asset — text-only review") so the omission is intentional and traceable.
+
+### 7. Verify
 
 - Run `npm run build`. Confirm:
   - `/reviews/<slug>/` exists, shows the source badge and "← First surfaced…" backlink to the find page.
   - `/find/<slug>/` shows the "→ Read the full review" callout pointing to the review.
-  - Any superpost that references the find still renders fine; the find card on the grid remains.
+  - Any bundle that references the find still renders fine; the find card on the grid remains.
+  - Visit `/grid/` (or `/`) and confirm the new review's tile renders with its hero — not blank. **If the tile is empty, step 6 was skipped.**
 
-### 7. Update the log
+### 8. Update the log
 
 Append to `daily-finds.log.md`: