test build

Expose the mobile screenshot to listing cards AND fix excessive left padding on the mobile JUST UPDATED scroll. Worker (jb-creators-worker.txt, hold for paste) + repo (index.html + css/justblt.css, hold for push it).

=== FIX 1: mobile scroll padding too large ===
On mobile, the JUST UPDATED horizontal scroll (.listing-scroll / .listing-scroll-wrap) has too much left padding/inset, pushing the first card inward so it looks off-center with dead space on the left. Reduce the left padding to something reasonable so the first card sits close to flush-left (a small consistent gutter, matching the rest of the mobile layout), with a slice of the next card peeking on the right. Check the .container padding + .listing-scroll padding + any wrap margin stacking up - reduce whatever is making the left inset oversized. Confirm at ~380px the first card is near flush-left with the next card peeking.

=== FIX 2: mobile card uses mobile screenshot ===
WORKER: add "screenshot_mobile_url" to both Airtable field-select lists (/api/listings feed and /api/search), and add screenshot_mobile_url: str(f.screenshot_mobile_url) to publicCard() alongside screenshot_desktop_url. Public-safe.
REPO (index.html): feedToCard exposes both (thumbImg=desktop, thumbImgMobile=mobile). The MOBILE card branch uses thumbImgMobile when present, falling back to thumbImg. Desktop row keeps desktop. If /everything and search render mobile cards, apply the same there.

VERIFICATION (mandatory): at ~380px the JUST UPDATED first card sits near flush-left with the next card peeking (padding reasonable, not oversized); /api/listings and /api/search return screenshot_mobile_url; the mobile card shows the MOBILE (phone-shaped) screenshot; a build with no mobile screenshot falls back to desktop; desktop row still uses desktop. Verify each holds. Self-review. Report what you verified and how. No AI attribution. Worker in .txt (hold), repo held for push it.