Document image caching, linting, and dynamic type in README and showcase

Add decision-table rows and showcase cards for expo-image caching,
ESLint/Prettier gates, and capped dynamic type so the docs match the
shipped implementation.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Author: jnrahme

README.md

@@ -167,6 +167,9 @@ flowchart LR
 | Zod at the mock API boundary                | Mock data is treated like real backend data: it is validated before reaching the UI, and TypeScript types are inferred from the schemas.                        | [schema.ts](src/domain/orders/schema.ts), [ordersApi.ts](src/services/ordersApi.ts)                                                              |
 | FlashList for the timeline                  | Order history is a list surface that can grow. Virtualization is included now so the implementation scales beyond seed data.                                    | [OrdersListScreen.tsx](src/features/orders/OrdersListScreen.tsx)                                                                                 |
 | Native share with web fallback              | The primary experience is mobile. Web preview still behaves reasonably through `navigator.share` or clipboard fallback.                                         | [calendar.ts](src/domain/orders/calendar.ts), [shareCalendar.ts](src/services/shareCalendar.ts)                                                  |
+| expo-image for cached artwork               | Remote event images are the heaviest content. A shared wrapper adds memory/disk caching, a blurhash placeholder, and a fade so cards never flash blank.         | [CachedImageBackground.tsx](src/components/CachedImageBackground.tsx)                                                                            |
+| Capped dynamic type on display text         | Large headings cap their font multiplier so big accessibility text sizes do not break fixed layouts, while body text scales freely.                             | [tokens.ts](src/theme/tokens.ts)                                                                                                                 |
+| ESLint and Prettier as quality gates        | Linting and formatting run locally and in CI so style and common bugs are caught before review, not during it.                                                  | [eslint.config.js](eslint.config.js), [.prettierrc.json](.prettierrc.json)                                                                       |
 
 ## AI-Assisted Delivery Model
 

docs/index.html

@@ -995,6 +995,23 @@ <h3>FlashList anticipates real order volume.</h3>
                   ready for larger data sets without changing the screen API.
                 </p>
               </article>
+              <article class="card">
+                <h3>expo-image for cached artwork.</h3>
+                <p>
+                  Remote event images load through a shared
+                  CachedImageBackground: memory and disk caching, a blurhash
+                  placeholder, and a short fade. The heaviest content on the
+                  screen never re-downloads or flashes blank on scroll.
+                </p>
+              </article>
+              <article class="card">
+                <h3>Dynamic type without broken layouts.</h3>
+                <p>
+                  Large display text is capped with a maximum font multiplier so
+                  big accessibility text sizes never overflow fixed layouts,
+                  while body text stays free to scale.
+                </p>
+              </article>
               <article class="card">
                 <h3>Native screenshots prove the surface.</h3>
                 <p>
@@ -1064,6 +1081,14 @@ <h3>Tests target behavior, not snapshots.</h3>
                   validation, share fallbacks, and list/detail interactions.
                 </p>
               </article>
+              <article class="card">
+                <h3>Linting and formatting are enforced.</h3>
+                <p>
+                  ESLint (expo config) and Prettier run locally and in CI.
+                  `npm run verify` chains strict typing, linting, and tests, and
+                  CI fails on any unformatted file.
+                </p>
+              </article>
               <article class="card">
                 <h3>Runtime schemas protect the boundaries.</h3>
                 <p>
@@ -1076,8 +1101,8 @@ <h3>Runtime schemas protect the boundaries.</h3>
                 <h3>Expo compatibility is verified.</h3>
                 <p>
                   Node 22, Expo SDK 56, React Native 0.85, React Navigation,
-                  TanStack Query, FlashList, and SDK-matched packages are encoded
-                  in the repo and checked before push.
+                  TanStack Query, FlashList, expo-image, and SDK-matched packages
+                  are encoded in the repo and checked before push.
                 </p>
               </article>
               <article class="card">
@@ -1090,6 +1115,7 @@ <h3>Mobile resilience is built in.</h3>
               </article>
             </div>
             <pre class="code-strip" aria-label="Verification commands"><code><b>$</b> nvm use
+<b>$</b> npm run format
 <b>$</b> make verify
 <b>$</b> make expo-check</code></pre>
           </div>