Gallery & before/after — high-level pointers

furfrou tells you what is wrong with a gallery page. The detailed, current naming convention, upload workflow, and resize policy — the file-naming pattern that makes before/after pairing reliable, the shrinkita/sigilyph handoff steps, and how to handle a case found mid-transfer — lives in the team wiki (set OUTLINE + OUTLINE_API_URL and the report links them directly). This file is the minimal high-level fallback for when the wiki isn’t configured: direction only, deliberately not step-by-step, so there’s no detailed content to drift out of sync with the wiki.

• Broken images — a decode failure (naturalWidth === 0) is a real defect; re-upload or re-point the asset.
• Unpaired before/after — a half-uploaded case; find and upload the missing partner rather than leaving the single image live.
• Naming for pairing — name before/after files identically except for the token (before/after, pre/post) so the pairing check — and the person after you — can match them.
• Missing alt text — route to sigilyph to write it; don’t leave gallery images without an accessible name.
• Oversized originals — route to shrinkita to resize before upload, not after a complaint about page weight.
• Stretched or over-cropped cards — preserve the source case ratio unless a different crop was explicitly reviewed. Width-only responsive rules must pair with height:auto; fixed-ratio cards should own the ratio on the wrapper and use width:100%; height:100%; object-fit:cover on the image.
• Lazy loading — on a long gallery, images below the fold should be lazy-loaded; eager-loading the whole gallery is unnecessary page weight up front.
• Verifying a case after upload — re-run the audit after adding a case; “uploaded” and “rendered” are not the same claim.

Full playbook → the team wiki’s gallery & before/after case-photo standards.