diff --git a/tasks/in-progress/35-the-site-reads-on-a-phone.md b/tasks/review/35-the-site-reads-on-a-phone.md
similarity index 50%
rename from tasks/in-progress/35-the-site-reads-on-a-phone.md
rename to tasks/review/35-the-site-reads-on-a-phone.md
index ab079bc..460c7bd 100644
--- a/tasks/in-progress/35-the-site-reads-on-a-phone.md
+++ b/tasks/review/35-the-site-reads-on-a-phone.md
@@ -1,6 +1,6 @@
 # 35 — Make the site read on a phone
 
-**Status:** In Progress
+**Status:** Review
 **Assignee:** istos
 **Priority:** Medium — a public URL gets opened on phones whatever the
 design was drawn at
@@ -71,3 +71,23 @@ the desktop design.
 
 Do this in the templates and stylesheet, with container queries or plain
 media queries — nothing here justifies a script.
+
+
+---
+
+## Work report — 2026-07-31 14:58 (Piper)
+
+contents gutter goes and its strip appears, tables become their own scrollers, and an unbreakable token in running text breaks. At 760px the sidebar goes and its menu appears, the type scale steps down (`--t-hero` 52→36, `--t-title` 40→30, and again at 480px to 31/26; `--display` stays Zilla Slab at every width), and everything a finger has to hit gets `min-height: var(--tap)` — a new 44px token. At 480px the padding tightens, the masthead and footer spacers drop so the rows wrap, body text goes 15→16px, and the hero buttons go full width.
+- **`tests/test_site_responsive.py`** — new, 22 tests, four groups: every media query is a `max-width` below the design and the strips are `display:none` in the base sheet; the step that hides a column is the step that shows its strip, and the strips in the *built* pages carry the same links as the columns; a table scrolls inside itself with a `local`/`scroll` edge shadow and a long token stays inside its `pre`; and the site still ships no `.js` and no `<script>`.
+- **`site/README.md`** — a "Below the design's width" section documenting the three steps and the two consequences an editor of `article.html` needs to know.
+
+### For the reviewer, first
+
+1. **`site/static/site.css:397`, the lede rule.** The contents strip is a sibling between the `<h1>` and the body's first paragraph even where it is `display:none`, so `.prose h1 + p` alone would silently demote the lede on every article page at desktop width. The selector now names `.menu-contents + p` too, and a test pins it. This is the one place the change could have altered the 1180px rendering.
+2. **`site/static/site.css:413`, the table rule.** `display:block` is what makes a `<table>` a scroll container without a wrapper element (which would have meant changing `site/build.py`, and the card scoped this to the templates and stylesheet). It has a real cost, noted in the comment: below 1080px a table *narrower* than its column no longer stretches to fill it. No page slices a table today, so this is a rule waiting for content rather than a visible change.
+
+### To know, not to act on
+
+- The acceptance criteria about pixel widths (390 / 768 / 1280, no horizontal body scroll) were verified by construction and by reading, not by a browser: this environment has no headless browser, and the tests assert stylesheet and markup structure instead. Someone with `npx wrangler@4 dev --config site/wrangler.jsonc` in front of them should give the three widths a look before merge — particularly the landing page's terminal at 390px and the folded nav on `/concepts/pull-requests/`.
+- `.menu-contents:not(:has(a))` hides the contents strip on a page whose body has no `<h2>`s. In a browser without `:has()` support the rule is dropped and such a page would show an empty strip; every current article page has `<h2>`s, so this is only a guard for future content.
+- Out of scope and untouched, as the card asked: no night theme, no desktop redesign, no navigation product beyond the one menu.