appstore-precheck 1.7.0 → 1.9.0

package/CHANGELOG.md

@@ -5,6 +5,82 @@ All notable changes to this project are documented here. Versioning follows
 
 ## [Unreleased]
 
+## [1.9.0] - 2026-07-02
+
+Smarter analysis (roadmap #2a): **screenshot vision**, in two layers.
+
+**Layer 1 (deterministic, offline, zero-dependency).** The static scanner now
+reads each in-repo screenshot's file format and, for PNGs, its pixel dimensions —
+a new `screenshot-dimensions` check (catalog vector 42) under guideline 2.3.3. It
+WARNs on a file whose content does not match its extension, a truncated PNG, or a
+PNG whose dimensions match no known App Store screenshot size (either orientation).
+WARN-only: it never forces a RED verdict, and the offline scan stays
+byte-identical on inputs without real screenshots. Parsing uses only `bash`+`od`+
+`awk` — no new runtime dependency.
+
+**Layer 2 (agent-mode, non-blocking).** A dedicated structured screenshot vision
+review that uses the host model's vision capability to check screenshots for
+placeholder / dev-debug / empty-state content, text overflow / truncation, wrong
+device frame / aspect, misleading marketing (2.3.3 "show the app in use" / 2.3.10),
+and metadata mismatches. Like Pierre deep-review it is advisory (`REVIEW-FINDING`)
+and never changes the GREEN/YELLOW/RED verdict. It runs only in agent-skill mode
+(host vision model), never in the CLI / npx / GitHub-Action path.
+
+### Added
+- **`skills/appstore-precheck/scripts/image-dims.sh`** — zero-dependency PNG
+  magic-byte + IHDR pixel-dimension parser (pure `bash`+`od`+`awk`) and the Apple
+  accepted-screenshot-size table (verified against Apple's screenshot
+  specifications page).
+- **`scan.sh` §7b** — screenshot format + PNG-dimension validation (rule
+  `screenshot-dimensions`, catalog vector 42), WARN-only.
+- **`skills/appstore-precheck/references/screenshot-vision-review.md`** — agent-mode
+  structured screenshot vision checklist (5 checks), non-blocking, wired into
+  Pierre deep-review check #8 and SKILL.md Phase 4.
+- Tests: `tests/test-image-dims.sh` (parser unit tests) and
+  `tests/fixtures/screenshots-app/` (end-to-end fixture); `tests/make-png.py`
+  fixture generator.
+
+### Changed
+- Advertised deterministic rejection-vector count **41 → 42** (the new
+  screenshot-dimensions check) across README, SKILL.md, and methodology.
+- Existing screenshot test fixtures: replaced 1-byte placeholders with real
+  accepted-size PNGs (scan output byte-identical).
+
+### Notes
+- JPEG dimensions are not parsed in this release; JPEGs are format-validated
+  (magic bytes) and counted only.
+
+## [1.8.0] - 2026-07-02
+
+Smarter analysis (roadmap #2c): a deterministic **semantic guideline-drift**
+detector. Beyond the existing section-number check, the tool now fingerprints the
+*text* of every guideline section our checks depend on and reports when Apple
+rewrites a section's meaning (even if its number is unchanged), naming the
+affected check(s). It is a maintainer/CI tool — network-using (`curl`), never
+sourced by `scan.sh`, never in the offline user scan path. Zero new runtime
+dependency for the distributed scanner; default scan output stays byte-identical.
+
+### Added
+- **`scripts/guideline-drift.sh`** (maintainer/CI): fetches the full live App
+  Store Review Guidelines and reports section-number drift AND text drift of
+  covered sections, deriving the affected check(s) from `scan.sh`'s `set_rule`
+  blocks. Non-blocking (WARN lines, always exits 0); the parse/diff logic is
+  unit-tested offline via `--html`. `--reconcile` regenerates the fingerprint
+  baseline (a deliberate human step) and skips/ WARNs on sections Apple has
+  removed rather than writing empty placeholders.
+- **`skills/appstore-precheck/guidelines-fingerprints.json`** — human-reconciled
+  per-covered-section text fingerprints (57 sections).
+- A non-blocking scheduled + manual GitHub workflow (`guideline-drift.yml`) that
+  surfaces drift; it never gates a PR.
+
+### Changed
+- **Baseline reconciled to Apple's current guidelines** (the drift tool's first
+  run caught real drift): Apple consolidated section 5.6 to end at **5.6.4** —
+  the removed **5.6.5–5.6.7** were dropped from the baseline and Pierre
+  deep-review check 28 (rating/review-manipulation) was remapped to the surviving
+  **5.6.1 / 5.6.3**. Six sub-sections a prior truncated fetch had missed
+  (2.5.7, 2.5.10, 4.2.4, 4.2.5, 4.4.3, 4.6) were added to `all_sections`.
+
 ## [1.7.0] - 2026-07-02
 
 Smarter analysis (roadmap #2b): the scanner now resolves the iOS source directory

package/README.md

@@ -44,7 +44,7 @@ each, divided by horizontal rules), not one compressed sentence. The breakdown b
 
 ## What it checks
 
-41 rejection vectors across code, fastlane metadata, screenshots, `PrivacyInfo.xcprivacy`, and the paywall:
+42 rejection vectors across code, fastlane metadata, screenshots, `PrivacyInfo.xcprivacy`, and the paywall:
 
 | Guideline | Check |
 |-----------|-------|
@@ -56,6 +56,7 @@ each, divided by horizontal rules), not one compressed sentence. The breakdown b
 | **2.3.1** | Metadata length limits (name, subtitle, keywords, promo, description) |
 | **2.3.1** | Misleading marketing claims (iOS virus / malware scanners, fake speed boosters) in metadata |
 | **2.3.3** | At least one screenshot per locale |
+| **2.3.3** | Screenshot format + PNG dimensions match a known App Store screenshot size *(advisory, WARN-only)* |
 | **2.3.7** | Localized metadata parity across every locale |
 | **2.3.8** | "For Kids" / "For Children" wording outside the Kids Category |
 | **2.3.10** | No other-platform / competitor names in metadata |
@@ -132,7 +133,7 @@ signals with a higher false-positive rate; Pierre prefers `not applicable` when
 | **5.2.1–5.2.3** | Obvious third-party trademark or brand misuse in metadata or UI copy |
 | **5.3.1–5.3.3** | Contest / sweepstakes copy includes official rules and eligibility |
 | **5.6.2–5.6.3** | Developer identity consistent (app name, support URL content, domains) |
-| **5.6.4–5.6.7** † | Rating / review manipulation dark patterns (withhold features until 5 stars, write-review links without `requestReview`) |
+| **5.6.1 / 5.6.3** † | Rating / review manipulation dark patterns (withhold features until 5 stars, write-review links without `requestReview`) |
 
 Pierre runs **all 28 every time** and reports each as `REVIEW-PASS:` or `REVIEW-FINDING:`. When the
 static scan already flagged a guideline, the deep check adds semantic context the scanner could not see.
@@ -146,7 +147,7 @@ how the app is built:
 
 | App type | Coverage |
 |----------|----------|
-| 🟢 **Native Swift / SwiftUI** | **Full.** All 41 vectors apply. |
+| 🟢 **Native Swift / SwiftUI** | **Full.** All 42 vectors apply. |
 | 🟡 **React Native / Flutter** | Metadata, privacy manifest, screenshots, and export compliance apply in full. The Swift-source checks (ATT, paywall links, private API, SDK detection, navigation) **under-detect rather than misfire**: that logic lives in JS/Dart, so they stay quiet instead of blocking. |
 
 ## Quick start
@@ -268,7 +269,7 @@ a RED verdict. No App Store Connect credentials are needed; the action runs the
 | Phase | Step |
 |-------|------|
 | **0** | **Guideline drift**: diff the live App Store Review Guidelines against a tracked baseline. Never blocks. |
-| **1** | **Static scan**: `scan.sh` over the 41 vectors above. |
+| **1** | **Static scan**: `scan.sh` over the 42 vectors above. |
 | **2** | **`fastlane precheck`**: Apple's own metadata rule engine. |
 | **3** | **Pierre commentary**: explains **every** FAIL and WARN from Phases 0–2 in 2–3 sentences each. |
 | **4** | **Pierre deep review**: 28 semantic checks (22 Tier A + 6 Tier B v1 heuristic). Advisory only. |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "appstore-precheck",
-  "version": "1.7.0",
+  "version": "1.9.0",
   "description": "Read-only iOS App Store pre-submission check, packaged as a portable Agent Skill with native Claude Code, Cursor, and Codex plugins, plus an npx CLI.",
   "license": "MIT",
   "author": "Berkay Turk (https://github.com/berkayturk)",

package/skills/appstore-precheck/SKILL.md

@@ -1,10 +1,10 @@
 ---
 name: appstore-precheck
-description: Read-only pre-submission check for an iOS app before App Store review. Scans Swift code, fastlane metadata, screenshots, PrivacyInfo.xcprivacy, and the paywall for 41 rejection vectors, wraps Apple's official `fastlane precheck`, watches for live App Store Review Guideline drift, has Pierre explain every FAIL and WARN, then runs 22 semantic deep-review checks (Tier A) plus 6 heuristic checks (Tier B v1) — 28 total. Emits a GREEN/YELLOW/RED verdict and a `.precheck-pass` token an upload guard can gate on. Use when preparing an iOS App Store submission (before Archive, before "Submit for Review", before TestFlight, or before any `fastlane deliver/pilot/release`), or when the user mentions App Store rejection, app review, or fastlane upload.
+description: Read-only pre-submission check for an iOS app before App Store review. Scans Swift code, fastlane metadata, screenshots, PrivacyInfo.xcprivacy, and the paywall for 42 rejection vectors, wraps Apple's official `fastlane precheck`, watches for live App Store Review Guideline drift, has Pierre explain every FAIL and WARN, then runs 22 semantic deep-review checks (Tier A) plus 6 heuristic checks (Tier B v1) — 28 total. Emits a GREEN/YELLOW/RED verdict and a `.precheck-pass` token an upload guard can gate on. Use when preparing an iOS App Store submission (before Archive, before "Submit for Review", before TestFlight, or before any `fastlane deliver/pilot/release`), or when the user mentions App Store rejection, app review, or fastlane upload.
 license: MIT
 metadata:
   author: Berkay Turk
-  version: 1.7.0
+  version: 1.9.0
 allowed-tools: Bash Read Grep Glob WebFetch
 ---
 
@@ -104,13 +104,19 @@ two-pass technique; the exact prompts and the reconciliation procedure are in
 [`references/methodology.md`](references/methodology.md#phase-0-guideline-drift-check). The
 baseline is **never auto-updated**. Reconciliation is a deliberate human step.
 
+The deterministic, full-page drift detector is `scripts/guideline-drift.sh` (maintainer/CI;
+curl-based, so it also covers the 5.5–5.6.x tail that `WebFetch` truncates). It reports
+section-number drift AND text (semantic) drift of covered sections, naming the affected
+check(s). It is non-blocking and never runs in the offline user scan; the fingerprint baseline
+(`guidelines-fingerprints.json`) is human-reconciled via `guideline-drift.sh --reconcile`.
+
 ### Phase 1: Static scan
 
 ```bash
 bash skills/appstore-precheck/scripts/scan.sh
 ```
 
-Emits `FAIL:` / `WARN:` / `PASS:` lines covering 41 rejection vectors: Privacy Manifest /
+Emits `FAIL:` / `WARN:` / `PASS:` lines covering 42 rejection vectors: Privacy Manifest /
 Required Reason API parity (5.1.1), purpose strings (5.1.1), ATT (5.1.2), other-platform mentions
 (2.3.10), metadata limits (2.3.1), localized parity (2.3.7), screenshots (2.3.3), trial &
 auto-renew disclosures (3.1.2), Restore/Terms/Privacy links (3.1.2), private API (2.5.1), minimum
@@ -127,9 +133,10 @@ NetworkExtension usage (5.4), a demo account for a login-gated app (2.1), execut
 / native hot-patching (2.5.2), unused background modes (2.5.4), cryptocurrency wallet/mining
 (3.1.5(a)), thin WKWebView wrappers (4.2.3), remote-desktop apps (4.2.7), Safari extensions
 (4.4.2), account creation without in-app deletion (5.1.1(v) Account Sign-In), kids audience with
-third-party ads/analytics (5.1.4), real-money gambling copy (5.3.4), and MDM signals (5.5). The
-IAP checks (8–10) are skipped automatically when no in-app-purchase signals are present, and the
-signal-gated advisory checks (16–41) stay silent unless their triggering signal is found. The
+third-party ads/analytics (5.1.4), real-money gambling copy (5.3.4), MDM signals (5.5), and
+screenshot format/dimension mismatches (2.3.3). The IAP checks (8–10) are skipped automatically
+when no in-app-purchase signals are present, and the signal-gated advisory checks (16–42) stay
+silent unless their triggering signal is found. The
 full check table is in
 [`references/methodology.md`](references/methodology.md#phase-1-rejection-vectors).
 
@@ -220,7 +227,9 @@ After Phase 3, Pierre runs the **Review Simulator**: 28 read-only, evidence-base
 static scanner cannot fully judge (**22 Tier A** + **6 Tier B v1** heuristic — marked † below).
 The full checklist, per-check procedure, and output format live in
 [`references/pierre-deep-review.md`](references/pierre-deep-review.md) — read it before starting
-Phase 4.
+Phase 4. When screenshots are present, also run the structured screenshot vision review in
+[`references/screenshot-vision-review.md`](references/screenshot-vision-review.md) (non-blocking;
+host vision model; never changes the verdict).
 
 **What Pierre does:** read Swift, metadata, entitlements, xcstrings, paywall views, review notes,
 screenshot/preview assets; fetch privacy and support URLs; cross-check claims vs code, policy vs
@@ -265,7 +274,7 @@ SDK usage, screenshots vs features, and paywall disclosure quality.
 | 25 | **5.2.1–5.2.3** | Obvious trademark/brand misuse in metadata or UI? |
 | 26 | **5.3.1–5.3.3** | Contest/sweepstakes copy includes official rules? |
 | 27 | **5.6.2–5.6.3** | Developer identity consistent (support URL, domains, app name)? |
-| 28 † | **5.6.4–5.6.7** | Rating manipulation dark patterns beyond scan §25? |
+| 28 † | **5.6.1 / 5.6.3** | Rating manipulation dark patterns beyond scan §25? |
 
 Use this prompt after Phase 3:
 

package/skills/appstore-precheck/guidelines-baseline.json

@@ -1,8 +1,8 @@
 {
   "_doc": "Baseline of Apple App Store Review Guidelines section numbers, for drift detection. Phase 0 fetches the live guidelines page and diffs its section numbers against `all_sections`; any NEW/REMOVED number => WARN: guideline-drift. This file is updated ONLY by deliberate human reconciliation (see SKILL.md Phase 0), NEVER auto-edited by the skill, otherwise the warning would be silently swallowed.",
   "source_url": "https://developer.apple.com/app-store/review/guidelines/",
-  "reconciled_on": "2026-06-30",
-  "apple_last_updated_seen": "Last Updated: June 8, 2026 (now exposed at the page footer); drift signal remains the set of section numbers",
+  "reconciled_on": "2026-07-02",
+  "apple_last_updated_seen": "Last Updated: June 8, 2026 (now exposed at the page footer); drift signal remains the set of section numbers. 2026-07-02: confirmed 5.6 now ends at 5.6.4 (5.6.1 App Store Reviews, 5.6.2 Developer Identity, 5.6.3 Discovery Fraud, 5.6.4 App Quality) — 5.6.5/5.6.6/5.6.7 (rating/review manipulation) were removed/consolidated; that content now lives under 5.6.1 and 5.6.3.",
   "drift_check_coverage": "Reliable for Sections 1-4 + 5.1-5.4 (high-churn regions: 2.5.x, 3.1.x, 4.7, 5.1.x). The 5.5-5.6.x tail can't be fetched (the page truncates ~5.4) and is structurally stable; review it by hand at reconciliation.",
   "covered_by_scan": [
     "1.2", "1.5", "1.6",
@@ -21,7 +21,7 @@
     "5.1.1", "5.1.2", "5.1.3", "5.1.4", "5.4",
     "5.2.1", "5.2.2", "5.2.3",
     "5.3.1", "5.3.2", "5.3.3",
-    "5.6.2", "5.6.3", "5.6.4", "5.6.5", "5.6.6", "5.6.7"
+    "5.6.1", "5.6.2", "5.6.3", "5.6.4"
   ],
   "all_sections": [
     "1.1", "1.1.1", "1.1.2", "1.1.3", "1.1.4", "1.1.5", "1.1.6", "1.1.7",
@@ -30,18 +30,19 @@
     "2.1", "2.2", "2.3", "2.3.1", "2.3.2", "2.3.3", "2.3.4", "2.3.5", "2.3.6",
     "2.3.7", "2.3.8", "2.3.9", "2.3.10", "2.3.11", "2.3.12", "2.3.13",
     "2.4", "2.4.1", "2.4.2", "2.4.3", "2.4.4", "2.4.5",
-    "2.5", "2.5.1", "2.5.2", "2.5.3", "2.5.4", "2.5.5", "2.5.6", "2.5.8", "2.5.9",
-    "2.5.11", "2.5.12", "2.5.13", "2.5.14", "2.5.15", "2.5.16", "2.5.17", "2.5.18",
+    "2.5", "2.5.1", "2.5.2", "2.5.3", "2.5.4", "2.5.5", "2.5.6", "2.5.7", "2.5.8", "2.5.9",
+    "2.5.10", "2.5.11", "2.5.12", "2.5.13", "2.5.14", "2.5.15", "2.5.16", "2.5.17", "2.5.18",
     "3.1", "3.1.1", "3.1.2", "3.1.3", "3.1.4", "3.1.5",
     "3.2", "3.2.1", "3.2.2",
-    "4.1", "4.2", "4.2.1", "4.2.2", "4.2.3", "4.2.6", "4.2.7",
-    "4.3", "4.4", "4.4.1", "4.4.2",
+    "4.1", "4.2", "4.2.1", "4.2.2", "4.2.3", "4.2.4", "4.2.5", "4.2.6", "4.2.7",
+    "4.3", "4.4", "4.4.1", "4.4.2", "4.4.3",
     "4.5", "4.5.1", "4.5.2", "4.5.3", "4.5.4", "4.5.5", "4.5.6",
+    "4.6",
     "4.7", "4.7.1", "4.7.2", "4.7.3", "4.7.4", "4.7.5",
     "4.8", "4.9", "4.10",
     "5.1", "5.1.1", "5.1.2", "5.1.3", "5.1.4", "5.1.5",
     "5.2", "5.2.1", "5.2.2", "5.2.3", "5.2.4", "5.2.5",
     "5.3", "5.3.1", "5.3.2", "5.3.3", "5.3.4",
-    "5.4", "5.5", "5.6", "5.6.1", "5.6.2", "5.6.3", "5.6.4", "5.6.5", "5.6.6", "5.6.7"
+    "5.4", "5.5", "5.6", "5.6.1", "5.6.2", "5.6.3", "5.6.4"
   ]
 }

package/skills/appstore-precheck/guidelines-fingerprints.json

@@ -0,0 +1,233 @@
+{
+  "sections": {
+    "1.2": {
+      "fingerprint": "ce18f5618681eafe5b4010d3162e0cdfe026aed127295d1762a1fe0c23f68026",
+      "snapshot": "1.2 user-generated content apps with user-generated content present particular challenges, ranging from intellectual property infringement to anonymous bullying"
+    },
+    "1.2.1": {
+      "fingerprint": "ffadee3ecbf75b6cf5b293fa2d9f59b2d68c1ba61e6e4c0cb33852324081e84b",
+      "snapshot": "1.2.1 creator content apps which feature content from a specific community of users called “creators” are a great opportunity if properly moderated. these apps "
+    },
+    "1.4.1": {
+      "fingerprint": "30045ffe09e8c2fe50923eb5f718ddec394b048bef67c6b7959abadb178c8406",
+      "snapshot": "1.4.1 medical apps that could provide inaccurate data or information, or that could be used for diagnosing or treating patients may be reviewed with greater scr"
+    },
+    "1.5": {
+      "fingerprint": "5553347bd97263487f23eae8b7577d036a875ba0934bbde44ac4216218fe85fa",
+      "snapshot": "1.5 developer information people need to know how to reach you with questions and support issues. make sure your app and its support url include an easy way to "
+    },
+    "1.6": {
+      "fingerprint": "0620b0807840c795dfcdf546b4a9e648564a192b48a995e3b507f60f26ee690f",
+      "snapshot": "1.6 data security apps should implement appropriate security measures to ensure proper handling of user information collected pursuant to the apple developer pr"
+    },
+    "2.1": {
+      "fingerprint": "f5cd98793df128268b4fe5b3b31b006776b0678f6d79d0b88d0d9b3986ea5fd4",
+      "snapshot": "2.1 app completeness (a) submissions to app review, including apps you make available for pre-order, should be final versions with all necessary metadata and fu"
+    },
+    "2.2": {
+      "fingerprint": "5df8bc50bf6ef5ce31be95dc03f8bc4ece4cd107055a5124add9336b49471a0d",
+      "snapshot": "2.2 beta testing demos, betas, and trial versions of your app don’t belong on the app store – use testflight instead. any app submitted for beta distribution vi"
+    },
+    "2.3": {
+      "fingerprint": "f7b9c31377de7f721ecb9f203a2f107d3600c464ce0633e0d79dd5318250d4df",
+      "snapshot": "2.3 accurate metadata customers should know what they’re getting when they download or buy your app, so make sure all your app metadata, including privacy infor"
+    },
+    "2.3.1": {
+      "fingerprint": "4745cb96a6e7665103163daa8a6f07dfc08008288116132a1f3c668d621c61b3",
+      "snapshot": "2.3.1 (a) don’t include any hidden, dormant, or undocumented features in your app; your app’s functionality should be clear to end users and app review. all new"
+    },
+    "2.3.10": {
+      "fingerprint": "a770ee4d270784e3bfa0784aab62563acccae50f02e4d85c4bb65bda14a4133d",
+      "snapshot": "2.3.10 make sure your app is focused on the experience of the apple platforms it supports, and don’t include names, icons, or imagery of other mobile platforms "
+    },
+    "2.3.11": {
+      "fingerprint": "393e4075d4b403ff201771e040768963299b7df6f01693317ea87c208276b63a",
+      "snapshot": "2.3.11 apps you submit for pre-order on the app store must be complete and deliverable as submitted. ensure that the app you ultimately release is not materiall"
+    },
+    "2.3.12": {
+      "fingerprint": "c4fe778434d20e2157b2093ceab8e780d6a98f85c05c57823507992f58de54a3",
+      "snapshot": "2.3.12 apps must clearly describe new features and product changes in their “what’s new” text. simple bug fixes, security updates, and performance improvements "
+    },
+    "2.3.13": {
+      "fingerprint": "40d66f89efc57625525782e40afc24aabd8a4cbe2a745eca725a7a2d6324f742",
+      "snapshot": "2.3.13 in-app events are timely events that happen within your app. to feature your event on the app store, it must fall within an event type provided in app st"
+    },
+    "2.3.2": {
+      "fingerprint": "e070f3780bbbbf41f191f71ef396904f9d42d531ab782f6f35b4e0c9b95dbf0a",
+      "snapshot": "2.3.2 if your app includes in-app purchases, make sure your app description, screenshots, and previews clearly indicate whether any featured items, levels, subs"
+    },
+    "2.3.3": {
+      "fingerprint": "599fcbd06e68d93bab64101dc412f5c6ffb13eb76e8490c7e93d95d95e4dafae",
+      "snapshot": "2.3.3 screenshots should show the app in use, and not merely the title art, login page, or splash screen. they may also include text and image overlays (e.g. to"
+    },
+    "2.3.4": {
+      "fingerprint": "581fe91e7677d96de480c0edca7761023e5606f5d6cd39ae42a06d29081ab393",
+      "snapshot": "2.3.4 previews are a great way for customers to see what your app looks like and what it does. to ensure people understand what they’ll be getting with your app"
+    },
+    "2.3.5": {
+      "fingerprint": "b4fb364fef12344219399d477daa73bca645261f6feee1a67dc88916a417c5c5",
+      "snapshot": "2.3.5 select the most appropriate category for your app, and check out the app store category definitions if you need help. if you’re way off base, we may chang"
+    },
+    "2.3.6": {
+      "fingerprint": "a6804ee336bd78da1ddc44613ea6fe131b5dcf4cbe482b8cb696ef3720435c3d",
+      "snapshot": "2.3.6 answer the age rating questions in app store connect honestly so that your app aligns properly with parental controls. if your app is mis-rated, customers"
+    },
+    "2.3.7": {
+      "fingerprint": "3493119147fdb0b4735ce6760d2a0186a4941531ff209e4198879f0a1c201a2c",
+      "snapshot": "2.3.7 choose a unique app name, assign keywords that accurately describe your app, and don’t try to pack any of your metadata with trademarked terms, popular ap"
+    },
+    "2.3.8": {
+      "fingerprint": "9c1bc1fbee57f292a14e4b6cfa465021ad0f7acb79691337b2a0f5c2e41392bb",
+      "snapshot": "2.3.8 metadata should be appropriate for all audiences, so make sure your app and in-app purchase icons, screenshots, and previews adhere to a 4+ age rating eve"
+    },
+    "2.3.9": {
+      "fingerprint": "5161fcd6aaa9dfd7b3cfff5f32912448dc937083d095fe9049cef0f80a09fa32",
+      "snapshot": "2.3.9 you are responsible for securing the rights to use all materials in your app icons, screenshots, and previews, and you should display fictional account in"
+    },
+    "2.5.1": {
+      "fingerprint": "7b055c4d2438faeaee3b1b77f5ce9b9cec38e713466ea0c85d31117d6484ba8b",
+      "snapshot": "2.5.1 apps may only use public apis and must run on the currently shipping os. learn more about public apis . keep your apps up-to-date and make sure you phase "
+    },
+    "2.5.2": {
+      "fingerprint": "353ebb9358966707a33b8b1b29575e44c1a2db44e8a42c013bcd48ca296fec44",
+      "snapshot": "2.5.2 apps should be self-contained in their bundles, and may not read or write data outside the designated container area, nor may they download, install, or e"
+    },
+    "2.5.4": {
+      "fingerprint": "9695ae52e1472dc7f5d977a88287c590b468401dd6a1fb30ddbe252029c59c81",
+      "snapshot": "2.5.4 multitasking apps may only use background services for their intended purposes: voip, audio playback, location, task completion, local notifications, etc."
+    },
+    "3.1.1": {
+      "fingerprint": "16d14be80e2243e9456be40bbc6c8dfb2cb6e90c6e98e5c36ba6e7f7147a61e8",
+      "snapshot": "3.1.1 in-app purchase: if you want to unlock features or functionality within your app, (by way of example: subscriptions, in-game currencies, game levels, acce"
+    },
+    "3.1.2": {
+      "fingerprint": "015f5baa628e085d550f8bc6d47f0cc33508915a5dced6d8b238e6a52616690a",
+      "snapshot": "3.1.2 subscriptions: apps may offer auto-renewable in-app purchase subscriptions, regardless of category on the app store. when incorporating auto-renewable sub"
+    },
+    "3.1.5": {
+      "fingerprint": "ff34b24b578bec14defe707f1333593160535ab927d03676f1e533b4d9ef03bb",
+      "snapshot": "3.1.5 cryptocurrencies: (i) wallets: apps may facilitate virtual currency storage, provided they are offered by developers enrolled as an organization. (ii) min"
+    },
+    "4.2": {
+      "fingerprint": "381768384e5d58de6c2c75ccfae3524279669ea710b29bd12994561ba002e9d6",
+      "snapshot": "4.2 minimum functionality your app should include features, content, and ui that elevate it beyond a repackaged website. if your app is not particularly useful,"
+    },
+    "4.2.1": {
+      "fingerprint": "186350931d2f6ae6faf4fab30b4ad0000cb386890f59dfc1f0d55904e0d31ebc",
+      "snapshot": "4.2.1 apps using arkit should provide rich and integrated augmented reality experiences; merely dropping a model into an ar view or replaying animation is not e"
+    },
+    "4.2.2": {
+      "fingerprint": "504f8404893912593ded8f89748de71a847897cc0cf7f987e475323edef8650a",
+      "snapshot": "4.2.2 other than catalogs, apps shouldn’t primarily be marketing materials, advertisements, web clippings, content aggregators, or a collection of links."
+    },
+    "4.2.3": {
+      "fingerprint": "60bde0e85a028024660dd1b6da7a487083fea5c8e346e1f9d4ef287e6bce7829",
+      "snapshot": "4.2.3 (i) your app should work on its own without requiring installation of another app to function. (ii) if your app needs to download additional resources in "
+    },
+    "4.2.7": {
+      "fingerprint": "debd395643a03b8dec28d32aed55ec883b91ce24df156ed8365846245a56d436",
+      "snapshot": "4.2.7 remote desktop clients: if your remote desktop app acts as a mirror of specific software or services rather than a generic mirror of the host device, it m"
+    },
+    "4.4.1": {
+      "fingerprint": "520a1ac7a5d13b54061b05bdc57a851e7d5f541a352144623b16c52ae578e5c6",
+      "snapshot": "4.4.1 keyboard extensions have some additional rules. they must: provide keyboard input functionality (e.g. typed characters); follow sticker guidelines if the "
+    },
+    "4.4.2": {
+      "fingerprint": "6b7f6bde5787ba828a1f18833340140d858d1cc520430b0519f487a7d86dc54c",
+      "snapshot": "4.4.2 safari extensions must run on the current version of safari on the relevant apple operating system. they may not interfere with system or safari ui elemen"
+    },
+    "4.5.1": {
+      "fingerprint": "9a82e38f4117ddc59f65993ff1ba5c8fba392fb91f7aad3936725e289d348b38",
+      "snapshot": "4.5.1 apps may use approved apple rss feeds such as the itunes store rss feed, but may not scrape any information from apple sites (e.g. apple.com, the itunes s"
+    },
+    "4.5.2": {
+      "fingerprint": "285371a2e18e84a6b20f61f4b9e4f342c2890debecfaf527c57051d4e15c48b4",
+      "snapshot": "4.5.2 apple music (i) musickit on ios lets users play apple music and their local music library natively from your apps and games. when a user provides permissi"
+    },
+    "4.5.3": {
+      "fingerprint": "66dcdc8015b616f09d2dc81e96567f1e003d3c71d8549e89d911ff1a7a3a528e",
+      "snapshot": "4.5.3 do not use apple services to spam, phish, or send unsolicited messages to customers, including game center, push notifications, live activities, etc. do n"
+    },
+    "4.8": {
+      "fingerprint": "4d97c6a408a925e9209c7f01ca4377b17c52eeb837a15023ac776b198f3f203e",
+      "snapshot": "4.8 login services apps that use a third-party or social login service (such as facebook login, google sign-in, log in with x, sign in with linkedin, login with"
+    },
+    "4.9": {
+      "fingerprint": "6ac6eb5bc1047758fde6986c12411e5ccd0901ae38c71facf71076dab9a8f671",
+      "snapshot": "4.9 apple pay apps using apple pay must provide all material purchase information to the user prior to sale of any good or service and must use apple pay brandi"
+    },
+    "5.1.1": {
+      "fingerprint": "fed9edf9021681ed9f27139e162f963bf4823e95775d6efad1156c59e9bd7baf",
+      "snapshot": "5.1.1 data collection and storage (i) privacy policies: all apps must include a link to their privacy policy in the app store connect metadata field and within "
+    },
+    "5.1.2": {
+      "fingerprint": "9817b825aa227ee7959bdecde672a78dffa147ce2ded3e3bcc0c0a4b3010f80c",
+      "snapshot": "5.1.2 data use and sharing (i) unless otherwise permitted by law, you may not use, transmit, or share someone’s personal data without first obtaining their perm"
+    },
+    "5.1.3": {
+      "fingerprint": "12a61190ea01b69c11d8d029b473777b5e9590739fd3043afa25f4f0f05c114a",
+      "snapshot": "5.1.3 health and health research health, fitness, and medical data are especially sensitive and apps in this space have some additional rules to make sure custo"
+    },
+    "5.1.4": {
+      "fingerprint": "43671205363120d06dd34eb1971c4751e8582fb8f7dfe69abbcadf2cd36195ea",
+      "snapshot": "5.1.4 kids (a) for many reasons, it is critical to use care when dealing with personal data from kids, and we encourage you to carefully review all the requirem"
+    },
+    "5.1.5": {
+      "fingerprint": "07911be837521693da654a46f08e84c9ca2ec3cf9ad87c65f54ae9624d157b3e",
+      "snapshot": "5.1.5 location services use location services in your app only when it is directly relevant to the features and services provided by the app. location-based api"
+    },
+    "5.2.1": {
+      "fingerprint": "358d2d81a7b375d308077bbb71b07989235f5667d2cda7fffb14ac1b006c7ae8",
+      "snapshot": "5.2.1 generally: don’t use protected third-party material such as trademarks, copyrighted works, or patented ideas in your app without permission, and don’t inc"
+    },
+    "5.2.2": {
+      "fingerprint": "b7e091540eb347bfa61de6c24a960913e95e67bfe4b40197a464d56b21c45424",
+      "snapshot": "5.2.2 third-party sites/services: if your app uses, accesses, monetizes access to, or displays content from a third-party service, ensure that you are specifica"
+    },
+    "5.2.3": {
+      "fingerprint": "af448918a1af7645066c9cce2be68952a841908a49efe143123b5641e8cf2215",
+      "snapshot": "5.2.3 audio/video downloading: apps should not facilitate illegal file sharing or include the ability to save, convert, or download media from third-party sourc"
+    },
+    "5.3.1": {
+      "fingerprint": "b1b9f19d97e0303c2b658f1b7d9d0db70dc417bdff7ce826c1e5b93b4a35ca55",
+      "snapshot": "5.3.1 sweepstakes and contests must be sponsored by the developer of the app."
+    },
+    "5.3.2": {
+      "fingerprint": "49577a0affde1ea6a425b47803c251eaede1565ee4a92676587bda910b5f0632",
+      "snapshot": "5.3.2 official rules for sweepstakes, contests, and raffles must be presented in the app and make clear that apple is not a sponsor or involved in the activity "
+    },
+    "5.3.3": {
+      "fingerprint": "7770603fbb406eeaa5d1320ca6baa5f57a72ee680200d82373bbc9dd6e41b8fe",
+      "snapshot": "5.3.3 apps may not use in-app purchase to purchase credit or currency for use in conjunction with real money gaming of any kind."
+    },
+    "5.3.4": {
+      "fingerprint": "aaca06600d77f4c3d63ffd9c6c3f5eef979135c2ce3f1263bb5349420d036387",
+      "snapshot": "5.3.4 apps that offer real money gaming (e.g. sports betting, poker, casino games, horse racing) or lotteries must have necessary licensing and permissions in t"
+    },
+    "5.4": {
+      "fingerprint": "3d639b21b98c7d15167fdfbd71559a91a5de51a7b5c22f300203e5f341af8616",
+      "snapshot": "5.4 vpn apps apps offering vpn services must utilize the nevpnmanager api and may only be offered by developers enrolled as an organization. you must make a cle"
+    },
+    "5.5": {
+      "fingerprint": "f8c3db6e7237d7c5a5002a507e20296153e906118b7ce05c537d1873e2adeab0",
+      "snapshot": "5.5 mobile device management mobile device management apps that offer mobile device management (mdm) services must request this capability from apple. such apps"
+    },
+    "5.6.1": {
+      "fingerprint": "17224df537dcc818fd69678e5f067156127cc8513cb0188ad6e3431641673172",
+      "snapshot": "5.6.1 app store reviews app store customer reviews can be an integral part of the app experience, so you should treat customers with respect when responding to "
+    },
+    "5.6.2": {
+      "fingerprint": "960f0c0dab8442a42b03926ae1123ffabbc676ecd4dc1890d31fd58c3ba9cf36",
+      "snapshot": "5.6.2 developer identity providing verifiable information to apple and customers is critical to customer trust. your representation of yourself, your business, "
+    },
+    "5.6.3": {
+      "fingerprint": "1d9e3acfb31ec0ba65a77d09e230f5a3c408bc4438343437aa8dc3bd17d5967b",
+      "snapshot": "5.6.3 discovery fraud participating in the app store requires integrity and a commitment to building and maintaining customer trust. manipulating any element of"
+    },
+    "5.6.4": {
+      "fingerprint": "2f63efa4160b309b6ef4d1280e3d16a06165676f1421c3c36f6dbe305ca1291a",
+      "snapshot": "5.6.4 app quality customers expect the highest quality from the app store, and maintaining high quality content, services, and experiences promotes customer tru"
+    }
+  },
+  "reconciled_on": "2026-07-02"
+}

package/skills/appstore-precheck/references/methodology.md

@@ -52,6 +52,13 @@ number is unchanged but whose *text* changed is not caught here, but is partly c
 Phase 2 (Apple's own rule engine) and Phase 3 (Pierre explains every FAIL/WARN). Apple does not expose a
 machine-readable "last updated" date in the page DOM, so the section-number set is the signal.
 
+**Automated detector:** `scripts/guideline-drift.sh` is the deterministic, curl-based counterpart
+to the two-pass technique above — it runs unattended in CI (see
+`.github/workflows/guideline-drift.yml`, scheduled + `workflow_dispatch`, always non-blocking) and
+also covers text (semantic) drift of covered sections via `guidelines-fingerprints.json`, naming
+the affected check(s) when a section's fingerprint no longer matches. Reconcile the fingerprint
+baseline the same deliberate way, with `guideline-drift.sh --reconcile`.
+
 ---
 
 ## Phase 1: Rejection vectors
@@ -101,11 +108,31 @@ machine-readable "last updated" date in the page DOM, so the section-number set
 | 39 | **5.1.4 Kids** *(advisory)* | Metadata targets a child audience **and** a third-party ads/analytics SDK is linked; Kids Category apps may not include third-party ads/analytics and need a parental gate |
 | 40 | **5.3.4 Gambling** *(advisory)* | Real-money gaming language in metadata (casino, sportsbook, real money, wager); real-money gambling needs licensing, geo-restriction, and must be free on the store |
 | 41 | **5.5 MDM** *(advisory)* | A Mobile Device Management signal (`DeviceManagement`, managed-app-config, `com.apple.mdm`); MDM apps need a commercial enterprise/education entity and purpose-limited data use |
+| 42 | **2.3.3 Screenshot format/dimensions** *(advisory)* | Reads each in-repo screenshot's magic bytes and, for PNGs, its IHDR pixel dimensions; WARNs on a file whose content does not match its extension, a truncated PNG, or a PNG whose size matches no known App Store screenshot size (either orientation). JPEG dimensions are not parsed (format-checked only). WARN-only — never forces a RED verdict. |
 
 Vectors 8–10 only run when in-app-purchase signals are detected (StoreKit / RevenueCat import,
-or a paywall view). Otherwise the scanner emits a single PASS and skips them. Vectors 16–41 are
+or a paywall view). Otherwise the scanner emits a single PASS and skips them. Vectors 16–42 are
 signal-gated advisory WARNs: each emits nothing unless its triggering signal is present.
 
+### Screenshot format + dimensions (§7b, 2.3.3)
+
+Vector 7 (above) checks that every locale has at least one screenshot. §7b goes one layer deeper,
+purely with zero-dependency byte reads (`image-dims.sh`, pure bash + `od`/`awk`): for every
+in-repo screenshot it reads the file's magic bytes to confirm the content actually matches its
+extension (`.png`/`.jpg`/`.jpeg`), and for PNGs it also parses the IHDR chunk for pixel width and
+height and checks that pair against a table of known App Store screenshot sizes (tried in both
+orientations, sourced from Apple's [screenshot specifications
+page](https://developer.apple.com/help/app-store-connect/reference/screenshot-specifications/)).
+JPEG dimensions are not parsed — JPEGs are format-checked only (magic-byte match), not size-checked.
+
+This is **WARN-only, never FAIL**: the accepted-size table can drift as Apple adds device sizes,
+and the scanner has no way to know which display slot (iPhone 6.9", iPad 13", …) a given file is
+meant to target, so a size that matches nothing in the table is a prompt to verify against the
+current spec, not proof of a rejection. A mismatched-format file (e.g. a renamed JPEG saved as
+`.png`) or an unreadable/truncated PNG WARNs the same way. Findings surface under
+`rule_id == "screenshot-dimensions"` (catalog vector 42) with messages beginning
+`WARN: 2.3.3 Screenshot …`.
+
 **Scope by app type.** The metadata, privacy-manifest, screenshots, and export-compliance checks
 apply to any iOS app regardless of how it is built. The code-level checks grep the app's Swift
 source (`*.swift`, plus `*.m`/`*.h` and `*.entitlements` where relevant), so they are most accurate
@@ -147,7 +174,7 @@ finds; Pierre explains.
 After Phase 3, Pierre runs the **Review Simulator**: 28 evidence-based checks the static scanner
 cannot fully judge — **22 Tier A** (high-confidence) plus **6 Tier B v1** heuristic checks (items
 **4, 5, 7, 10, 15, 28** in the checklist: 2.1 review notes, 2.2, 2.3.4, 2.3.9, 4.5.1–4.5.3,
-5.6.4–5.6.7). Full procedure, output format, and per-check steps are in
+5.6.1/5.6.3). Full procedure, output format, and per-check steps are in
 [`pierre-deep-review.md`](pierre-deep-review.md).
 
 **Verdict impact:** none. Phase 4 emits `REVIEW-PASS:` or `REVIEW-FINDING: <guideline> WARN — …`.

package/skills/appstore-precheck/references/pierre-deep-review.md

@@ -87,7 +87,7 @@ REVIEW-PASS: <guideline> — not applicable (<reason>)
 | 25 | **5.2.1–5.2.3** | Obvious third-party trademark/brand misuse in metadata, assets, or UI copy? | metadata, asset filenames, Swift strings |
 | 26 | **5.3.1–5.3.3** | Contest/sweepstakes/lottery copy → official rules/eligibility/disclosure present in metadata? | description, keywords, in-app contest UI |
 | 27 | **5.6.2–5.6.3** | Developer identity consistent: app name, support URL content, bundle/marketing domain match? | fetch support URL, metadata, legal/footer copy |
-| 28 | **5.6.4–5.6.7** | Rating/review manipulation dark patterns (withhold features until 5 stars, direct write-review links without `requestReview`)? | Swift, metadata, §25 scan context |
+| 28 | **5.6.1 / 5.6.3** | Rating/review manipulation dark patterns (withhold features until 5 stars, direct write-review links without `requestReview`)? | Swift, metadata, §25 scan context |
 
 ---
 
@@ -147,6 +147,9 @@ REVIEW-PASS: <guideline> — not applicable (<reason>)
 1. Open ≥1 screenshot per primary locale.
 2. List visible features (tabs, paywall, login, maps, etc.).
 3. Flag screenshots showing features absent from the build or metadata.
+4. For the full structured screenshot vision review (placeholder/empty-state, text overflow,
+   wrong device frame, misleading marketing, metadata mismatch), follow
+   `references/screenshot-vision-review.md`.
 
 ### 9 — 2.3.6 Pricing language
 
@@ -253,7 +256,7 @@ REVIEW-PASS: <guideline> — not applicable (<reason>)
 2. Compare app name, support domain, and privacy policy domain for consistency.
 3. Flag placeholder support pages or identity mismatch.
 
-### 28 — 5.6.4–5.6.7 Rating manipulation *(Tier B v1)*
+### 28 — 5.6.1 / 5.6.3 Rating/review manipulation *(Tier B v1)*
 
 1. Grep Swift and metadata for: `itms-apps://` write-review URLs, `apps.apple.com/.../write-review`,
    "rate 5 stars", "only enable after review", custom star-rating UI tied to App Store review.

package/skills/appstore-precheck/references/screenshot-vision-review.md

@@ -0,0 +1,69 @@
+# Screenshot vision review (agent-mode, non-blocking)
+
+Deepens Pierre deep-review check #8 (2.3.5) into a dedicated, structured screenshot review.
+This is the **vision layer** of the Review Simulator: the host model reads the actual screenshot
+images and cross-checks their content against the metadata and the shipped app.
+
+**Identity:** this runs ONLY in agent-skill mode (Claude Code / Codex / …), using the host LLM's
+vision capability — exactly like Pierre reads code and the drift phase fetches URLs. It is NOT a
+bundled dependency and does NOT run in the offline CLI / npx / GitHub-Action path.
+
+**This phase does not change the GREEN/YELLOW/RED verdict** (verdict comes only from scan
+`FAIL:`/`WARN:` counts). It emits `REVIEW-PASS:` / `REVIEW-FINDING: … WARN` lines, like Pierre
+deep-review.
+
+## Rules
+
+- Read-only. Never modify project files.
+- Evidence-based: cite the screenshot **filename** (and locale) for every finding. If you cannot
+  read an image, say so — do not invent findings.
+- Read at least one screenshot per primary locale; when several are present, scan them all.
+- All five checks, every run: report each as `REVIEW-PASS:` or `REVIEW-FINDING: … WARN`.
+- If there are no in-repo screenshots, report each check as
+  `REVIEW-PASS: <guideline> — not applicable (no in-repo screenshots; managed in App Store Connect)`.
+- Severity is always WARN (advisory). Cautious language ("may trigger review questions").
+- Write Pierre's 2–3 sentence explanations in the user's conversation language.
+
+## The 5 checks
+
+| # | Guideline | Question |
+|---|-----------|----------|
+| S1 | 2.3.3 / 2.3.7 | Placeholder / dev-debug / empty-state content: Lorem ipsum, debug overlays or logs, visible TODO/FIXME, empty lists or skeleton loaders shown as content, simulator status bar with placeholder carrier/time. |
+| S2 | 2.3.3 | Text overflow / truncation / clipping: clipped or overlapping labels, cut-off buttons, text running off-screen. |
+| S3 | 2.3.5 | Wrong device frame / aspect: an iPad screenshot in an iPhone slot (or vice-versa), letterboxing, obviously stretched/squished aspect. |
+| S4 | 2.3.3 / 2.3.10 | Misleading marketing: 2.3.3 "show the app in use" — the shot is a splash/title/logo/pure marketing art, not actual app UI; 2.3.10 — a feature is depicted that the app does not ship. |
+| S5 | 2.3.5 | Metadata ↔ screenshot claim mismatch: visible UI text/features contradict the description, keywords, or promo text. |
+
+## Per-check procedure
+
+### S1 — Placeholder / dev-debug / empty-state
+1. Open each screenshot; read visible text and UI state.
+2. Flag Lorem ipsum, debug HUDs, log text, "TODO"/"FIXME", empty/skeleton content presented as real, or a simulator status bar with placeholder carrier/time.
+3. Cite the filename. Not applicable if no screenshots.
+
+### S2 — Text overflow / truncation
+1. Inspect labels, buttons, and headings for clipping, overlap, or off-screen text.
+2. Flag any truncation that suggests an unfinished or broken layout.
+
+### S3 — Wrong device frame / aspect
+1. Compare each screenshot's aspect to its locale/slot (iPhone vs iPad).
+2. Flag an iPad-aspect image in an iPhone slot (or vice-versa), letterboxing, or stretched aspect.
+
+### S4 — Misleading marketing
+1. Determine whether each screenshot shows the app actually in use (real UI) vs pure title/splash/logo art.
+2. Flag shots that are marketing art rather than the app in use (2.3.3), or that depict a feature absent from the build (2.3.10).
+
+### S5 — Metadata ↔ screenshot mismatch
+1. Read the visible UI text/features and compare to the description, keywords, and promo text.
+2. Flag direct contradictions (a feature/claim in the screenshot not in metadata, or vice-versa).
+
+## Output format
+
+```
+REVIEW-PASS: <guideline> — <one-line why it looks OK, with screenshot filename>
+```
+or
+```
+REVIEW-FINDING: <guideline> WARN — <one-line concrete issue, with screenshot filename>
+Pierre: <2–3 sentences: why Apple cares, what you saw, what to fix or verify>
+```

package/skills/appstore-precheck/scripts/findings.sh

@@ -26,7 +26,8 @@ rule_slug() {
     35) echo webview-wrapper ;;                36) echo remote-desktop ;;
     37) echo safari-extension ;;               38) echo account-no-delete ;;
     39) echo kids-ads-analytics ;;             40) echo realmoney-gambling ;;
-    41) echo mdm ;;                            *) echo "" ;;
+    41) echo mdm ;;                            42) echo screenshot-dimensions ;;
+    *) echo "" ;;
   esac
 }
 

package/skills/appstore-precheck/scripts/image-dims.sh

@@ -0,0 +1,76 @@
+#!/usr/bin/env bash
+# image-dims.sh — zero-dependency image format + PNG dimension helpers for scan.sh.
+# Pure bash + od + awk; bash 3.2 compatible; sourced, no side effects, no output on load.
+
+# img_format <file> -> "png" | "jpeg" | "unknown"
+img_format() {
+  local f="$1" sig
+  [[ -r "$f" ]] || { echo unknown; return; }
+  sig="$(od -An -tx1 -N8 "$f" 2>/dev/null | tr -d ' \n')"
+  case "$sig" in
+    89504e470d0a1a0a*) echo png ;;
+    ffd8ff*)           echo jpeg ;;
+    *)                 echo unknown ;;
+  esac
+}
+
+# png_dims <file> -> "W H" (decimal) and return 0, or return 1 with no output.
+# IHDR width = big-endian bytes 16-19, height = 20-23 (8-byte signature + 4-byte
+# length + "IHDR" tag precede the 8 dimension bytes at offset 16).
+png_dims() {
+  local f="$1"
+  [[ "$(img_format "$f")" == png ]] || return 1
+  local b
+  read -r -a b < <(od -An -tu1 -j16 -N8 "$f" 2>/dev/null)
+  [[ "${#b[@]}" -ge 8 ]] || return 1
+  local w=$(( b[0]*16777216 + b[1]*65536 + b[2]*256 + b[3] ))
+  local h=$(( b[4]*16777216 + b[5]*65536 + b[6]*256 + b[7] ))
+  printf '%s %s\n' "$w" "$h"
+}
+
+# ACCEPTED_SIZES — Apple App Store screenshot pixel sizes (portrait "W H").
+# The matcher tries both orientations. This table is intentionally generous
+# (includes current + legacy device sizes) because this check is WARN-only.
+# Verified against Apple's official page:
+# https://developer.apple.com/help/app-store-connect/reference/screenshot-specifications/
+ACCEPTED_SIZES="
+1260 2736
+1290 2796
+1320 2868
+1284 2778
+1242 2688
+1179 2556
+1206 2622
+1170 2532
+1125 2436
+1080 2340
+1242 2208
+750 1334
+640 1096
+640 1136
+640 920
+640 960
+2064 2752
+2048 2732
+1488 2266
+1668 2420
+1668 2388
+1640 2360
+1668 2224
+1536 2008
+1536 2048
+768 1004
+768 1024
+"
+
+# dims_match_accepted <W> <H> -> return 0 if W×H or H×W is an accepted size.
+dims_match_accepted() {
+  local w="$1" h="$2" aw ah
+  while read -r aw ah; do
+    [[ -z "$aw" ]] && continue
+    if { [[ "$w" == "$aw" && "$h" == "$ah" ]]; } || { [[ "$w" == "$ah" && "$h" == "$aw" ]]; }; then
+      return 0
+    fi
+  done <<< "$ACCEPTED_SIZES"
+  return 1
+}

package/skills/appstore-precheck/scripts/scan.sh

@@ -15,6 +15,7 @@ cd "$ROOT" || { echo "FAIL: repo-root — could not enter repository root"; exit
 source "$(dirname "${BASH_SOURCE[0]}")/findings.sh"
 source "$(dirname "${BASH_SOURCE[0]}")/suppress.sh"
 source "$(dirname "${BASH_SOURCE[0]}")/project-model.sh"
+source "$(dirname "${BASH_SOURCE[0]}")/image-dims.sh"
 FINDINGS_TMP="$(mktemp)"; export FINDINGS_TMP
 trap 'rm -f "$FINDINGS_TMP"' EXIT
 FORMAT="text"
@@ -395,6 +396,42 @@ else
   pass "2.3.3 Screenshots — no in-repo screenshots dir; assumed managed in App Store Connect (set .screenshotsDir to check in-repo)"
 fi
 
+# ===================================================================
+# §7b — 2.3.3 Screenshot format + PNG dimensions (deterministic; PNG dims,
+# JPEG format only). WARN-only: the accepted-size table can drift, and we
+# cannot know which display slot a file targets, so mismatches never FAIL.
+# ===================================================================
+if [[ -n "$SCREEN_DIR" && -d "$SCREEN_DIR" ]]; then
+  set_rule "screenshot-dimensions"
+  while IFS= read -r img; do
+    [[ -z "$img" ]] && continue
+    fmt="$(img_format "$img")"
+    case "$img" in
+      *.png)
+        if [[ "$fmt" != png ]]; then
+          warn "2.3.3 Screenshot $img is not a valid PNG (file content does not match .png extension)" "$img"
+          continue
+        fi
+        dims="$(png_dims "$img")"
+        if [[ -z "$dims" ]]; then
+          warn "2.3.3 Screenshot $img — could not read PNG dimensions (possibly truncated)" "$img"
+        else
+          w="${dims% *}"; h="${dims#* }"
+          if ! dims_match_accepted "$w" "$h"; then
+            warn "2.3.3 Screenshot $img is ${w}x${h}, which matches no known App Store screenshot size — verify against the current spec" "$img"
+          fi
+        fi
+        ;;
+      *.jpg|*.jpeg)
+        if [[ "$fmt" != jpeg ]]; then
+          warn "2.3.3 Screenshot $img is not a valid JPEG (file content does not match extension)" "$img"
+        fi
+        ;;
+    esac
+  done < <(find "$SCREEN_DIR" -maxdepth 3 -type f \( -name '*.png' -o -name '*.jpg' -o -name '*.jpeg' \) 2>/dev/null | sort)
+  set_rule ""
+fi
+
 # ===================================================================
 # In-app purchase gate — only run 3.1.2 checks if IAP signals exist
 # ===================================================================
@@ -403,7 +440,7 @@ grep -rqE 'SKPaymentQueue|SKProduct|SKMutablePayment|Product\.products|Product\(
 [[ -n "$SUB_VIEW" ]] && iap_detected=1
 
 if [[ -z "$iap_detected" ]]; then
-  # Not one of the 41 catalog sections — clear the rule_id so this PASS doesn't
+  # Not one of the 42 catalog sections — clear the rule_id so this PASS doesn't
   # inherit §7's "screenshots-per-locale" slug in the JSON output.
   set_rule ""
   pass "3.1.2 IAP — no in-app purchase / subscription signals detected, skipping paywall checks"