Audit E: the eight built screens nobody has compared

[maximsan]

Part of #337 · Feeds the checklist #365

The first divergence audit covered the four tabs, Dictionary home, term detail, module screens, the lesson player and Settings. These built screens were never compared with the prototype:

onboarding (Welcome / Loading / Goal / Brewer / Name) · card detail · course completion · lesson completion · module summary · Saved shelf (shipped as #328) · streak screen · mini-game intro · mini-game player.

Same method and severities as the existing register. Note that the v1 Readiness Audit defers the goal/brewer question flow to v2 — audit them, but flag findings there as possibly moot pending #370.

[maximsan]

This was generated by AI during triage.

Audit E — the eight built screens nobody has compared

Method and severities are the first register's (docs/research/design-divergence-register.md, #344). Every prototype claim cites a file and line in prototype/; every app claim a file and line in lib/. SDK claims were read from the installed Flutter at /opt/homebrew/share/flutter, not recalled. naming is added as a fourth severity per this ticket.

Nothing here repeats #344. Where a finding touches something that register already named — the unset TextTheme slots (§7), the lesson player's progress (§9.4), the stock-AppBar-instead-of-SubScreenHeader shape (§9.1, §9.2) — it is marked as extending it at a screen that register did not cover, never restating it.

Counts: 88 divergences — 7 breaks-a-ruling, 50 structural, 20 cosmetic, 11 naming.

Screen	breaks	structural	cosmetic	naming	total
Lesson completion	–	10	1	1	12
Welcome	3	4	1	3	11
Goal / Brewer / Name †	1	6	2	1	10
Module summary	1	7	–	1	9
Saved shelf	–	3	5	1	9
Card detail	1	6	1	–	8
Streak	–	3	4	1	8
Course completion	–	3	2	1	6
Mini-game player	–	3	2	1	6
Mini-game intro	–	3	1	1	5
Across all eight	1	1	–	–	2
Loading	–	1	1	–	2

† Possibly moot pending #370 — the whole Goal / Brewer / Name section, per prototype/v1 Readiness Audit.html:270-271.

---

0. Across all eight — two systemic faults

#	Severity	Divergence	Prototype / ruling
1	breaks-a-ruling	Every CTA on these screens is a stadium pill. The app ships PrimaryButton, a correct .btn-primary port at AppRadii.editorial (primary_button.dart:36-47) — and uses it only in onboarding. Everywhere else a bare Material FilledButton resolves to the SDK default shape: StadiumBorder() (filled_button.dart:367), because app_theme.dart declares no button theme at all. Fully rounded where the design is 2px and sharp, and 40px tall where PrimaryButton is 52. Call sites in scope: course_completion_screen.dart:165, module_summary_screen.dart:88, lesson_completion_body.dart:56, streak_screen.dart:179, mini_game_intro_screen.dart:172, mini_game_results_view.dart:103.	AppRadii names buttons editorial in as many words (app_radii.dart:17-19), from docs/design/03-design-system.md:63.
2	structural	RoastBean does not exist in the app. A grep across lib/ returns nothing. It is the design's single progress mark — one bean that darkens as the run roasts — used on the lesson player, the mini-game player, Duel and the flashcard bar. In its place the app has invented two different controls on two players: a LinearProgressIndicator on the lesson player (already §9.4) and a segment strip on the mini-game player (#83 below). Extends §9.4 rather than repeating it: the point here is that the shared mark is absent app-wide, so each player invents its own.	flavor-wheel.jsx:77-93; used at lesson.jsx:195, lesson.jsx:1603, duel.jsx:449, dictionary-extras.jsx:80

---

1. Welcome — lib/features/onboarding/presentation/welcome/welcome_screen.dart

The design has two screens here and the readiness audit keeps both in v1: "The Welcome + Meet Roasty intro is v1" (v1 Readiness Audit.html:271). The app has one.

#	Severity	Divergence	Prototype
3	structural	Welcome and Meet Roasty are collapsed into one screen. The design ships OnboardingWelcome (video, brand, tap to advance) and then OnboardingRoasty (the mascot, the promise, the CTA) as separate states. AppRoutes has welcome and no meet (app_routes.dart:24).	screens.jsx:11-95 and :98-136; routed app.jsx:1202-1213
4	breaks-a-ruling	Roasty is on the Welcome screen. The design's own comment on that screen: "Introduces the app and the living coffee tree (the engagement metaphor). No Roasty here. Tapping anywhere advances." The mascot's first appearance is the entire point of the next screen. The app perches one bottom-right inside the video frame (welcome_screen.dart:147-153).	screens.jsx:9-10
5	structural	No tap-anywhere. The design's whole .screen is the target (onClick={advance}, cursor: pointer) and it says so with a .tap-cue: TAP ANYWHERE TO CONTINUE. The app requires hitting a button.	screens.jsx:32-34, :87-89; .tap-cue at index.html:1111
6	structural	The video's sound toggle is gone. The design ships a 44px scrim-backed mute/unmute button over the frame, with speaker-on and speaker-off glyphs, and mutes on mount and before advancing so audio never bleeds into the next screen. The app hardcodes setVolume(0) with no control (welcome_screen.dart:107) — the audio track is unreachable.	screens.jsx:46-68, :14-30
7	structural	A dead control ships on the first screen a new user sees. LinkButton('Already have progress? Restore', onPressed: () {}), commented "placeholder per plan" (welcome_screen.dart:72-77). No design counterpart on either screen.	—
8	breaks-a-ruling	static const double _heroFrameRadius = 4 (welcome_screen.dart:22) is a bare off-token literal. The design's media frame takes var(--r) = 14 = AppRadii.chrome, and AppRadii names media frames as chrome in its own doc (app_radii.dart:21-22). CLAUDE.md: a deliberately off-token value "goes in the OffTokens register with its reason, never as a bare literal" — it is not in the register (off_token.dart:89-94).	screens.jsx:40; index.html:52
9	breaks-a-ruling	context.go('/onboarding/goal') (welcome_screen.dart:70) is a hardcoded path. CLAUDE.md: "Navigate by route name (context.goNamed('welcome')), never by hardcoded path strings."	—
10	naming	Headline is 'Plant your tree.\nGrow with every cup.' (:57-60). The design's is Learn coffee. / Grow a tree., and the body copy under it differs word for word too.	screens.jsx:79, :84-86
11	naming	The eyebrow is a third string in neither screen. The design's Welcome eyebrow is BREWPATH in accent; Meet Roasty's is YOUR COMPANION in accent. The app prints BREWPATH in the default ink-mute above the video (:40) and a merged ROASTY · YOUR COMPANION below it (:55).	screens.jsx:74, :107-109
12	naming	CTA reads 'Plant your seed' (:69). The design's v1 CTA — the one this screen is standing in for — is Start learning.	screens.jsx:127
13	cosmetic	The media frame is square (AspectRatio(aspectRatio: 1), :43); the design's is 4/3.	screens.jsx:39

---

2. Loading — lib/features/onboarding/presentation/loading/loading_screen.dart

The closest port in this audit. Phases and their durations, the caption copy and its italic Fraunces, the 170px mascot, the 56px caption gap, and the three 5px accent dots at 6px gaps on a 1.4s stagger all match (roasty.jsx:602, :663-706 vs loading_screen.dart:33-34, :120-125 and pulsing_dots.dart:20-26). Two things do not.

#	Severity	Divergence	Prototype
14	structural	The tap-to-skip is never advertised. The design's brand mark swaps to TAP ANYWHERE TO CONTINUE once the first cycle completes, which is how a waiting learner learns the screen is skippable. The app always prints BREWPATH (loading_screen.dart:138) while onTap silently skips (:105).	roasty.jsx:708-710
15	cosmetic	The wordmark sits 24px off the bottom (_wordmarkInset = 24, :35); the design pins it at 80.	roasty.jsx:684-686

---

3. Goal / Brewer / Name — ⚠️ possibly moot pending #370

goal_screen.dart, brewer_screen.dart, name_screen.dart. The readiness audit defers "the personalization questions only — goal, brewer, level, reminders" to v2, pinned to the Standard four-question depth (v1 Readiness Audit.html:270-271; app.jsx:1216-1218). Every finding in this section is therefore possibly moot pending #370 and is recorded so that whoever builds v2 does not rediscover it.

The option prose itself is a faithful transcription and should not be touched: both screens' three titles and descriptions match onboarding.jsx:22-35 word for word.

#	Severity	Divergence	Prototype
16	structural	No progress bar, no Skip, no back. The design gives every question screen an OnbHeader: a back chevron, a 6px accent progress bar on a surface-2 track, and a Skip link, over a rule hairline. The app's three screens have none of the three — a learner who enters onboarding cannot go back a step and cannot get out.	onboarding.jsx:145-174
17	structural	Roasty is absent from the questions. The default direction is guided, in which "Roasty is present on every question, speaking in a bubble" — the prompt is the speech. The app renders the prompt as a bare AppText.title (goal_screen.dart:89-92).	onboarding.jsx:6-7, :190-199, :96-142
18	structural	The depth is wrong. The design's Standard depth — what v2 will ship — is goal, brewer, commitment, experience. The app ships goal, brewer, name: two of the design's four are missing and one is invented.	onboarding.jsx:82; app.jsx:1216-1218
19	structural	The Name screen has no counterpart anywhere in the design. Onboarding contains no text input at all (zero <input> in onboarding.jsx), and the greeting Hello, {name}. is filled from an account — email plus initial on the Account and sync screen — not from a typed nickname. The app has substituted an onboarding question for an account.	screens.jsx:668, :2570; settings.jsx:357-370; data.jsx:3098
20	structural	Both bookends are missing. OnbExpectation — Roasty promising "Just {n} quick questions, then your first lesson" — and OnbClosing — "You're all set." over "Your first lesson is brewing. Plant the seed and let's grow your tree.", preceded by a RoastyMoment send-off.	onboarding.jsx:233-246, :249-267, :332-335
21	structural	The Name screen's stock TextField + OutlineInputBorder + maxLength counter (name_screen.dart:85-98) uses vocabulary the design has nowhere in this flow.	—
22	breaks-a-ruling	context.go('/onboarding/brewer') (goal_screen.dart:56) — hardcoded path, same rule as #9.	—
23	naming	The kicker format. Design: QUESTION 01 / 04 · GOAL — zero-padded, carrying the question's own topic. App: ONBOARDING · 1 OF 3 (goal_screen.dart:87, brewer_screen.dart:92, name_screen.dart:73).	onboarding.jsx:202-204
24	cosmetic	PickCard invents a 28px radio indicator (pick_card.dart:65, :74-105). The design's .pick-card renders only the title/description column — its second grid track is empty — and selection is carried by an accent border plus box-shadow: inset 0 0 0 1px var(--accent), i.e. a doubled edge. The app changes border colour alone, so a selected card reads as one hairline lighter.	index.html:519-535; onboarding.jsx:219-225
25	cosmetic	Pick-card padding is 16 (pick_card.dart:41-44); the design's is 20.	index.html:524

---

4. Card detail — lib/features/cards/presentation/card_detail_screen.dart

#	Severity	Divergence	Prototype
26	structural	The design has no card-detail screen. A card opens as a bottom sheet over the Cards tab — handle, backdrop, .sheet-content — so the learner never leaves the grid. The app pushes a full route under a bare, title-less AppBar() (card_detail_screen.dart:26). The app already builds one design sheet correctly (showVisualGuideSheet), so the vocabulary exists.	CardSheet, screens.jsx:2458-2541; mounted app.jsx:1685
27	structural	The FACT block is missing — and the data for it is already loaded. The design closes every card with a FACT smallcaps label over the fact set in Fraunces at the heading step. CoffeeCardModel.fact is assembled (content_assembly.dart:106) and documented as "the keepsake line the reward carries under its summary" (coffee_card_model.dart:27-28), and a grep for .fact across lib/ finds it rendered only in the visual-guide sheet. The card's own keepsake line never reaches the card.	screens.jsx:2524-2532
28	structural	No artwork. The design gives each card kind its own drawn CardArt on a per-kind tinted 150px well. The app draws one Material Icon from moduleIcon() at 96px in accent (card_detail_screen.dart:62-68).	screens.jsx:2484-2506; the CardArt* family at screens.jsx:1676-1824
29	structural	The meta spec rows are absent — smallcaps key ↔ mono tabular-nums accent value, one grid row each. The app's model carries no meta either, so this is a content-pipeline gap as much as a layout one.	screens.jsx:2515-2523
30	structural	TriedSeal is absent: the design stamps a completed Brew Challenge onto the card's header.	screens.jsx:2474-2476
31	structural	The app prints card.moduleTag under the title (:77). The design's sheet prints no category line at all — only VISUAL GUIDE, and only for that one kind.	screens.jsx:2469-2470
32	breaks-a-ruling	The tap-in is a hardcoded path: context.go('/cards/${item.card.id}') (card_grid_item_widget.dart:30). Same rule as #9.	—
33	cosmetic	The title is headlineSmall + w700 (:70-75); the design's is Fraunces at the display step, line-height 1.05, -0.02em.	screens.jsx:2471-2474

✅ Not a divergence — checked and cleared: locked cards are not tappable (card_grid_item_widget.dart:30), which matches the design opening the sheet only for earned cards. And CardStampSection is a correct port, mounted in the same slot the design mounts it (card_detail_screen.dart:80 vs screens.jsx:2534-2536).

---

5. Course completion — lib/features/learn/presentation/course_completion_screen.dart

#	Severity	Divergence	Prototype
34	structural	The app shows an eyebrow the design deliberately deleted — and the prototype names this screen as the drift. In full: "No eyebrow, deliberately: the headline carries the verb, so a COURSE COMPLETE label above it said the same thing twice. Recorded drift from the shipped screen (which shows both)." The app shows both (course_completion_screen.dart:116-120).	rewards.jsx:513-515
35	structural	Roasty's line is missing. The design puts a surface/rule bubble with a rotated tail above a 190px Roasty, carrying "Beans to brew — you did the whole thing." The app's CompanionCelebration draws a bubble, but fills it from the generic authored companion lines — this screen's own sentence is nowhere.	rewards.jsx:505-511
36	structural	The stat rows are the wrong element. Design: .smallcaps key ↔ a mono, tabular-nums, --t-lead, w500 value, separated by rule hairlines, capped at 320px. App: bodyLarge on both sides, value in w700, no hairlines, no mono, no tabular figures — so the three numbers do not align in their column (course_completion_screen.dart:177-206).	rewards.jsx:520-528
37	cosmetic	The CTA is a bare FilledButton → stadium pill (see #1), where the design has .btn-primary on a sticky footer under a linear-gradient(to top, var(--bg) 74%, transparent) fade that lets content scroll beneath it.	rewards.jsx:530-531
38	cosmetic	The entrance stagger is absent: three 520ms rises at 0 / 180 / 360ms, with an explicit prefers-reduced-motion kill.	rewards.jsx:497-501
39	naming	Headline is 'You finished Beginner Foundations' (:125); the design's is You finished Foundations.	rewards.jsx:517

✅ Not a divergence — checked and cleared: the three stat rows, their labels and their order match exactly (rewards.jsx:490-494). Holding the screen on a loading state rather than painting 0 lessons (course_completion_screen.dart:74-78) is an app improvement at no design cost.

---

6. Lesson completion — lesson_completion_screen.dart + lesson_completion_body.dart

The worst screen in the audit. The design's completion is where the tree grows, the score lands and the freeze is introduced; the app's is a badge, a headline and a points number.

#	Severity	Divergence	Prototype
40	structural	The tree is missing. The design centres AnimatedTree fromStage→toStage size={240} — this screen is where the living-tree metaphor that the Welcome screen sells actually pays off. The app shows a celebrating companion and never mentions the tree (lesson_completion_body.dart:84).	rewards.jsx:76-78
41	structural	And with it the still-tree line: when no stage was crossed the design prints {n} lessons to the next stage in mono, for the stated reason "Most completions do not cross a stage threshold. Say how far the next one is, so a still tree reads as progress rather than nothing."	rewards.jsx:79-86
42	structural	The lesson is never named. Design: LESSON COMPLETE smallcaps over the lesson title as a Fraunces --t-title h1. App: 'Lesson complete!' is the headline and the lesson's title appears nowhere on the screen (lesson_completion_body.dart:86-92).	rewards.jsx:50-56
43	structural	The score is missing on a first completion. The design prints {correct} / {total} in mono tabular whenever there is a result. The app prints a score only on a replay ('Best score: N / M', :138-145), so the run that mattered most reports nothing.	rewards.jsx:57-73
44	structural	No mastery chip. The design gives a needs-practice run an accent-tinted pill, and says why: "Only Needs Practice earns a chip … It wears the action colour, because it is an invitation to replay, never a failure red."	rewards.jsx:11-15, :63-70
45	structural	No "Practice this lesson again". The design pairs that chip with a ghost CTA tinted accent. Without both, the weak-run invitation the design built has no surface in the app at all.	rewards.jsx:167-175
46	structural	FREEZE EARNED never appears at the moment it is earned. The design puts the row here and states the reason: "Keeping the streak finally pays out something concrete. This is the first time most users meet the word 'freeze' — before they ever need one, not at the moment they're told they lost a day." The app surfaces freeze only as the save notice on Learn (learn_list_view.dart:78) — precisely the inverse. A grep for freeze across lib/features/lessons/ returns nothing.	rewards.jsx:97-99, row at :100-114
47	structural	The reward rail is dismantled. Design: one bordered surface card, radius 16, hairline-divided, each row a 34px accent-tinted well + a mono micro accent kicker (+N PTS / FREEZE EARNED / NEW CARD UNLOCKED) + a sans-500 support line — and the card row is tappable, opening a full RewardCard preview behind a blurred veil. App: a floating accent +N PTS, then loose Material Cards with no kicker, not tappable, no preview (lesson_completion_body.dart:94-120, :190-234).	rewards.jsx:87-137, :180-206
48	structural	No close. The design keeps the lesson-topbar X on this screen. The app's Scaffold has no appBar and no back affordance (lesson_completion_screen.dart:87-94).	rewards.jsx:40-45
49	structural	No RoastyMoment opener. The design opens on a full-screen beat whose title varies with the run — Perfect run! / Mastered it. / Good start. / Nice work. — then reveals the content.	rewards.jsx:31-35
50	cosmetic	'Module complete!' is added as a second headline line (:105-112) where the design instead routes to its own module screen.	rewards.jsx:210+
51	naming	The CTA. Design: Next lesson when one is playable, Back to Path otherwise, with ghost Back to Path / Duel a friend beside it. App: one Continue (lesson_completion_body.dart:56-59).	rewards.jsx:153, :154-166

---

7. Module summary — lib/features/learn/presentation/module_summary_screen.dart

Prototype counterparts: ModuleCompleteScreen (rewards.jsx:210-347) and ModuleRewardCardScreen (rewards.jsx:356-402).

#	Severity	Divergence	Prototype
52	structural	The tree is missing again — AnimatedTree fromStage→toStage size={250} is the centre of the design's module close.	rewards.jsx:271
53	structural	The card flip is gone. The design turns the whole screen over on a 3D Y-rotation (820ms, perspective: 1800, perspectiveOrigin: 50% 42%): front is the celebration, back is the reward. It is driven by a Turn it over CTA with a flip glyph, set up by the line "A reward card is waiting on the other side." The app stacks everything in one scroll.	rewards.jsx:236-241, :290-303, :310-345
54	structural	The reward is not a RewardCard. The design's card is the module's guide — badge, title, summary, spec rows, memorable fact — and "deliberately no points total: points are paid per lesson and reported by the completion chip." The app draws IconBadge.circle + a title + a 'Reward unlocked' caption (module_summary_screen.dart:100-143).	rewards.jsx:404-407; rendered :336, :385
55	structural	No RoastyMoment opener — MODULE COMPLETE over "Look how far you've come.", held 2200ms.	rewards.jsx:224-225
56	structural	The hierarchy is inverted. Design: MODULE COMPLETE smallcaps in accent, then the module title as a Fraunces display h1. App: 'Module complete!' is the headline in headlineSmall w700 and the module's own title is demoted to a muted titleMedium subtitle (module_summary_screen.dart:62-76).	rewards.jsx:261-268
57	structural	The earned-cards Wrap of icon badges (module_summary_screen.dart:83-86, :146-168) has no design counterpart — the design's module close shows the module reward and nothing else.	rewards.jsx:257-306
58	structural	No close, and no accent radial glow behind the celebration (radial-gradient(circle at 50% 40%, …accent 14%…)).	rewards.jsx:247-253
59	breaks-a-ruling	context.go('/learn') (module_summary_screen.dart:89) — hardcoded path, same rule as #9.	—
60	naming	CTA is always 'Continue'. The design's is Begin next module when one follows, Back to Path otherwise.	rewards.jsx:340, :396

✅ Not a divergence — checked and cleared: the missing +{earned} PTS pill (rewards.jsx:275-286). The app omits it under its own ruling — "No points line. The module pays nothing (§5.1, #16)" (module_summary_screen.dart:77-78). Recorded, not re-litigated.

---

8. Saved shelf — lib/features/saved/presentation/ (shipped as #328)

The domain layer is a faithful port and should not be touched: group order and labels (saved_shelf.dart:62-74 vs library.jsx:146-161), the cap of five (saved_cap.dart:10 vs the readiness audit's amendment at v1 Readiness Audit.html:158), all three count-line strings (saved_cap.dart:118-122 vs library.jsx:170-174), and the empty-state copy word for word (saved_empty_view.dart:15-17 vs library.jsx:207-209). The divergences are all in the drawing.

#	Severity	Divergence	Prototype
61	structural	No page h1. The design gives the shelf a collapsing SubScreenHeader and a Fraunces display h1 in the scroll, with the count line under it. The app has a stock AppBar(title: Text('Saved')) and no h1 (saved_screen.dart:67). Same shape as §9.1/§9.2 of the first register, at a screen it did not cover.	library.jsx:165, :168; SubScreenHeader at settings.jsx:272-289
62	structural	The flashcards row is missing. When any term is saved, the design offers "Study N terms as flashcards" — an accent-tinted row with a flashcard glyph and an accent chevron, directly under the count. Flashcards are v1 free-tier per the readiness audit ("Free keeps all of Module 1 … plus Flashcards and Guess the Term"), so this is in scope, not deferred.	library.jsx:188-201; v1 Readiness Audit.html:158
63	structural	Rows have no glyph and no hairline. The design's SavedRow is a 24px 1fr auto grid led by a per-kind SavedIcon — FlavorWheel for a lesson, CatGlyph for a term, TuneMark for a guide — with 13px vertical padding on a rule bottom border. The app's row has no leading glyph, 8px padding and no divider (saved_row.dart:26-51).	library.jsx:85-108, :112-126
64	cosmetic	The row's over-line is the wrong face and the wrong step: the design's is ff-mono at the micro step (9.5) with 0.14em; the app's is SmallcapsLabel — Plex Sans 500 at the label step (11) (saved_row.dart:34).	library.jsx:120
65	cosmetic	The bookmark is a stock Material IconButton with Icons.bookmark_outline / Icons.bookmark (saved_bookmark_button.dart:74-86). The design's FavButton is a 34px round control with a rule→accent hairline border, drawing the design's own bookmark path.	library.jsx:44-60, used :127
66	cosmetic	The count line is the wrong face: design ff-mono, label step, 0.08em, uppercase; app labelMedium — one of the TextTheme slots §7 found unset, so Roboto 12 (saved_screen.dart:111-116). Cited as a call site of §7, not as a new systemic finding.	library.jsx:169-175
67	cosmetic	The upgrade row flattens the design's emphasis: the design sets the offer phrase in ink at 500 inside an otherwise muted sentence, so the actionable half stands out. The app renders the whole sentence in inkMute (saved_upgrade_row.dart:42-47).	library.jsx:182-184
68	cosmetic	The empty state uses Icons.bookmark_outline at 48 (saved_empty_view.dart:29-33); the design uses its own Bookmark mark at 44 with 0.55 opacity.	library.jsx:206
69	naming	The offer says "Unlock Plus" (saved_upgrade_row.dart:17-19); the design's says "Unlock Foundations", which is what the readiness audit renamed the single v1 product to: "v1 sells one product: Foundations, a one-time purchase at $19.99." Flagged, not decided — the product-name question belongs to #55 and CONTEXT.md:142-145, and this register records rather than rules.	library.jsx:183; v1 Readiness Audit.html:158

✅ Not a divergence — checked and cleared: the screen's name. The app calls it "Saved", once, with the reason written down (saved_screen.dart:24-28) against a prototype that calls the same screen both "Saved" and "Favorites" two lines apart (library.jsx:165, :168). The app is resolving a prototype inconsistency, not drifting from it.

---

9. Streak — lib/features/progress/presentation/streak_screen.dart

#	Severity	Divergence	Prototype
70	structural	The insight card is missing. The design closes the screen with a surface/rule card (radius 14) carrying a ProfileBean and "Showing up daily is how tasting notes start to stick. You've brewed knowledge N days running." — the count set in accent inside the sentence. It is the only place the streak is given a meaning rather than a number.	screens.jsx:321-327
71	structural	There is no primary CTA. The design pairs a .btn-primary Continue with a .btn-ghost Share your streak. The app has only a borderless TextButton('Share your streak') (streak_screen.dart:250-253) — the screen offers no way forward of its own, and share is demoted to a text link.	screens.jsx:334-335
72	structural	The share preview is gone. The design's ShareStreakSheet previews the shareable card in-app under a SHARE eyebrow and a Your N-day streak h2, then offers four destinations and a Maybe later ghost. The app renders the PNG offscreen and hands it straight to the OS share sheet (streak_screen.dart:67-80). The native sheet is a fair platform substitution for the four destinations; the preview is not substituted by anything — the learner never sees what they are sending.	screens.jsx:362-436
73	cosmetic	The SteamMark is missing from inside the ring. The design stacks SteamMark → hero mono count → DAY STREAK smallcaps; the app drops the glyph (streak_screen.dart:223-230).	screens.jsx:294-296
74	cosmetic	The ring is smaller and half the weight. App: diameter 176, strokeWidth 6, track mood.rule (milestone_ring.dart:23-26, streak_screen.dart:219-221). Design: a 208 box, r = 84, strokeWidth 12, track var(--surface-2), round cap, filling on entry over 1100ms — MilestoneRing is static by design (milestone_ring.dart:6-8).	screens.jsx:285-291
75	cosmetic	The badge line is the wrong rung and the wrong colour: AppText.micro = mono at 9.5, ink-mute, mixed case (streak_screen.dart:234-238). The design sets it at the label step, 0.12em, uppercase, in var(--accent) — the accent is what makes it read as progress rather than as a caption.	screens.jsx:302-304
76	cosmetic	The freeze line loses its state colour. The design sets it mono / micro / uppercase and turns it accent when a freeze actually covered a day, ink-mute otherwise — the colour carries the news. The app uses AppText.support (Plex Sans 13) in one colour always (streak_screen.dart:244-248).	screens.jsx:315-317
77	naming	The header's dismissal is a back arrow (Icons.arrow_back, streak_screen.dart:95-98); the design passes icon="close". The title matches ✅.	screens.jsx:279

✅ Not a divergence — checked and cleared: freezeStatusLine's three branches and their exact wording match the design's (freeze_status_line.dart:36-44 vs screens.jsx:268-276). And the milestone beat: the app gates it on a milestone being due and acks it (streak_screen.dart:48-63) where the design replays it once per session (screens.jsx:241-243) — a deliberate app ruling, recorded against #26 / #232 / #236 in the code.

---

10. Mini-game intro — lib/features/mini_games/presentation/mini_game_intro_screen.dart

#	Severity	Divergence	Prototype
78	structural	The icon well is missing. The design pairs the game's per-kind ReplayIcon at 34px inside a 68×68 surface-2 well — radius 20, rule border — beside the Fraunces title. The app shows no artwork at all, so every mini-game intro looks identical.	screens.jsx:3040-3052
79	structural	The meta line is missing. The design prints {game.meta} · N ROUNDS — or ROUNDS IN AUTHORING — in mono at the label step, 0.14em uppercase, under the blurb. The app never tells the learner how long the game is.	screens.jsx:3058-3067
80	structural	The eyebrow and the screen title swap slots. Design: a MINI-GAME smallcaps eyebrow above the title, on a title-less transparent topbar carrying only the close X. App: 'Mini-game' is the AppBar title (mini_game_intro_screen.dart:30) and format.topic becomes the eyebrow (:84-89) — so the word the design puts in the body is in the chrome, and vice versa.	screens.jsx:3029-3039
81	cosmetic	Step numbers. Design: zero-padded mono 01, 02, 03 at the label step, 0.1em, in accent, baseline-aligned with the step text. App: '1' in labelLarge accent, top-aligned in a fixed 24px box (mini_game_intro_screen.dart:135-143).	screens.jsx:3070-3079
82	naming	The disabled CTA reads 'Not playable yet' (:179); the design's reads Rounds in authoring — a statement about the content, not about the build.	screens.jsx:3085

---

11. Mini-game player — mini_game_player_screen.dart + mini_game_results_view.dart

#	Severity	Divergence	Prototype
83	structural	The counter is gone. The design's topbar centres the RoastBean mark plus a zero-padded mono 01 / 12 at the label step, 0.12em. The app shows a RoundProgressStrip of filled pill segments and no number at all (mini_game_player_screen.dart:101-106; round_progress_strip.dart:36-49) — so a learner mid-run cannot say which round they are on except by counting shapes. This is the mini-game player, not the lesson player of §9.4; see #2 for why the two also diverge from each other.	lesson.jsx:1594-1608
84	structural	The results screen never names the game. The design puts the game title in .smallcaps directly above the score, so a result is attributable. The app shows a score with no title anywhere (mini_game_results_view.dart:57-86).	lesson.jsx:1623
85	structural	The topbar disappears on results. The design keeps it and shows the run completed as NN / NN; the app nulls the AppBar title once the run ends (mini_game_player_screen.dart:102-104).	lesson.jsx:1605, :1617
86	cosmetic	The score's split is gone. The design sets the numerator at the Fraunces display step and the / N smaller — at the title step, in ink-mute — so the score dominates its own denominator. The app sets the whole N / M in displaySmall w700 (mini_game_results_view.dart:71-77).	lesson.jsx:1624-1626
87	cosmetic	Done is a borderless TextButton (mini_game_results_view.dart:111); the design's is a .btn-ghost — bordered, full-width, the same footprint as the primary above it.	lesson.jsx:1633
88	naming	None of the encouragement copy matches. Design, three thresholds: "Sharp palate. You know this one cold." / "Solid round — run it back to sharpen up." / "Worth another pass. Try again?". App: five branches, none of those words (mini_game_run.dart:82-90).	lesson.jsx:1627-1629

✅ Not a divergence — checked and cleared: the 80% celebration threshold (mini_game_run.dart:11 vs lesson.jsx:1614), and the Play again / Done labels and their order (lesson.jsx:1632-1633).

---

12. Worst offenders, and what they cost

1. Lesson completion (12). The screen a learner meets more often than any other in this set, and the one furthest from the design. Missing: the tree, the score on a first run, the lesson's own name, the mastery chip, the replay invitation and the freeze introduction. The freeze one is sharpest — the design says in as many words that this is where a learner should first meet the word, and the app only ever shows freeze at the moment of loss.
2. Welcome (11), and the Meet Roasty screen that does not exist. Three ruling breaches on the app's first screen, plus a dead "Restore" link. The mascot appears on the one screen whose design comment reads "No Roasty here."
3. Module summary (9). The 3D card flip — the design's single most distinctive moment — is gone, along with the tree, and RewardCard is replaced by an icon badge.
4. Card detail (8). A pushed screen where the design has a sheet, and CoffeeCardModel.fact is assembled, documented as the keepsake line, and rendered nowhere.
5. The two systemic faults (Feature/migration to proper linter setup #1, ci: run workflow from repo root after restructure #2). One NavigationBarTheme-shaped fix each. PrimaryButton already exists and is correct — six call sites need to use it instead of a bare FilledButton; and one RoastBean widget would replace two invented progress controls.

Cheapest high-value fixes, in order: swap the six FilledButtons for PrimaryButton (#1); fix the five hardcoded path strings (#9, #22, #32, #59, plus module_card_widget.dart:30); render CoffeeCardModel.fact on card detail (#27); delete the course-completion eyebrow the design already recorded as drift (#34); turn the eyebrow/title hierarchy the right way up on lesson and module completion (#42, #56).

---

13. Open questions for the owner

• Streak freeze parameters: what ships of the cap, the automatic spend, and the re-earn #69, "Unlock Plus" vs "Unlock Foundations". The readiness audit renames the single v1 product to Foundations; CONTEXT.md:142-145 and Offers, plans and the paywall pitch #55 own the Plus vocabulary. The two now disagree on the shelf, and this register does not decide it.
• Lesson mastery gauge, and the {correct, total} storage it needs (#46 Part B) #72, share. Is the design's in-app ShareStreakSheet preview wanted, or does the native share sheet supersede it? The four destinations plainly do not survive to a platform sheet; the preview is a separate question.
• Document ComingSoonPath in the overview, and sweep for sibling omissions #19, the Name screen. The design takes the greeting name from an account, which v1 does not have. If Name stays, it is an app-original screen and deserves to be recorded as one, rather than sitting inside a flow Scope conflicts with the v1 Readiness Audit: the free tier, and the onboarding flow — both settled #370 may delete around it.