Co-Authored-By: Claude Opus 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_01P5YBdwj33XByFVTvu9bfci
7.8 KiB
/auto — James-eye review
Reviewed 7 Nov 2026 (round 3 walk), walked moving at 1470x801 and 375x812 (Playwright, wheel steps of 400px every 700ms, rest shots, hover/press/click on every control, 8 lone reloads for hydration).
Verdict: 7/10 Ready: 8 Nov, held up next to /api and /affiliate (James's new bar, no score). After the 17:13 rebuild (server-final hero with no hydration diff, "Restart the pod" in the race strip on the first screen at both widths, full-bleed tracks, the drag canvas in place of the empty figures room, two-column index), this pass made the connector board, text links and the band's repo chip answer hover under (hover: hover), (pointer: none); the prompt's Copy already inverts on "Copied" and reduced motion leaves 0 running animations in main at 3 s (375x667). taste/unique/parity OK (text 53/53, links 4/4); 0 console errors, no overflow at 1470 and 375. Left alone (shared): the Finale repo chip's own hover sits under (hover: hover) only in Launch.css (overridden on this page). copycheck missing 0 of 26 (8 Nov).
First complaint: "The one thing that proves it, restarting the pod, is sitting under the fold, and then that black figures room is mostly empty with a box that never finishes drawing. It's clean, but it looks like the /automations page again."
The 11 answers
- Sells in 5 seconds, moves within 1 second? Yes. "Hanzo Auto", the AUTO.HANZO.AI caption, the lede and "Open Auto" read at once; the two-lane race is already stepping at 1.0 s (record step 2/5, goroutine step 2/5) and by 2.0 s the "POD RESCHEDULED" line cuts across and the goroutine lane drops to step 1/5. But at 1470x801 the editor's bottom bar with the "Restart the pod" button sits at y 793-837 (phone: 786-830), so the control that makes the point is off the first screen on both sizes, and about 360px of the first screen is h1/lede/asks before the editor starts.
- One in, one out? Mostly. Hero race, then the six-row index with one row open running its own mini, then the pinned black figures room, the connectors on quiet grey, the black band. The index reads like an FAQ accordion: one big open row and five grey 26px rows, with a ~250px empty left column under the open row's three-line body.
- A real object in every section? Yes: the flow editor, a live mini in every opened row (record ticks, run log from two triggers, draft vs published), the figures plus the container drawing, the numbered connector chain, the agent prompt card. The figures room is the weakest: four words on hairlines and the container outline, with ~200px of empty black above and ~250px below.
- One ask, sticky after the hero? Yes. "Open Auto" is the only solid in the hero and in the band; the header carries "Try Hanzo" (shared). Nothing floats over content. Scale rhythm is good: h1 52px, section heads 26px, the open index row grows to ~44px and the others stay 26px, figures at 64px Air. The figures room has four equal 64px words in four equal columns, which is "everything the same size" for that screen.
- Every hover and press answers? Yes. Open Auto: ink to rgb(44,44,46) and scale .98 on press. Documentation: transparent to #f5f5f5 and a 1px press. Restart: white to ink fill, the icon turns, the lane restarts. Index rows: title grey to ink, plus button fills, the row opens and its mini starts. Connector rows: fill #e4e4e7, a number badge, and the left chain re-flows (Notion pressed: chain became Stripe, Airtable, Notion). The editor leans with the pointer. Copy puts exactly the displayed prompt on the clipboard, but the confirmation is only a tiny tick squeezed next to the copy icon; the label never changes.
- Overlap, font swap, layout shift? CLS 0.0002 desktop, 0 phone; no horizontal overflow at either size; no font swap seen; nothing overlaps. But a hydration error on this page's own element reproduces: "Hydration failed...
<motion.p className="l2-lede" initial={{opacity:0,y:16}}>" atcomponents/pages/apps/Auto.jsx (143-144) @ Hero, with the red "1 Issue" badge. Seen on both walk loads and in 2 of 7 lone desktop reloads (0 of 4 lone phone reloads). Also the container outline in the figures room rests with its bottom edge open (desktop) and as two loose stroke fragments (phone, at rest). - Which reference, and is its motion there? apple.com product page: the product as the hero, one pinned scene (the figures room, 210svh) where words cut in. The pinned scene is there but is the thinnest part of the page; no idea changes inside it beyond four words appearing and a box drawing.
- Different from its neighbours? Partly. /automations opens with the same composition: h1 top-left, solid ask on the right, then a wide rounded frame holding a node chain with a pause button bottom-right. The objects differ (a two-lane race here vs connector tiles there), but at a glance the first screens are siblings.
- All 18 parts covered? The card has 18 parts filled. Claims I checked hold: parity 53/53 text, 4/4 links; primary ask bottom at 357px at 375x667; 44px pause controls; no overflow; tilt on the editor. Claims that do not hold: part 13 "0 console errors" and "hyd.js shows 0 on repeat loads" (the hero lede mismatch reproduces, see 6); part 9 "reduced motion renders the settled frame": at 375x667 with reduced motion, 18 animations were still running at 2.5 s (rule:
getAnimations()empty after 3 s; recheck at 3 s). - Banned tells? None of the hard ones: no hue, no gradient text, no eyebrow above a headline (the caption sits under the h1), no floating pill. Soft tells: the three grey "window dots" on the editor chrome; the goroutine lane's finished "done" node is white text on a mid-grey fill (low contrast) at the end of each run.
- Copy untouched? Yes, parity OK 53/53 text, 4/4 links.
Fixes (ordered, most important first)
- Kill the hydration mismatch on the hero lede (
Auto.jsx143-144,motion.p.l2-ledewithinitial={{opacity:0,y:16}}). Server and client must render the same element; render the final state in HTML (noopacity:0start in SSR) or use the samem.pon both. It shows the red badge and contradicts the card. - Get "Restart the pod" onto the first screen at 1470x801 and 375x812. It sits at y 793 (desktop) and 786 (phone). Tighten the hero: the h1 top is 180px; pull the editor up ~100px (h1 near 120-140px, asks beside the lede, not on their own row) or move the restart control into the editor's top bar beside "published" and the pause button.
- Fill or shorten the figures room. About 450px of empty black around four equal words, and the container outline never closes at rest (bottom open on desktop, loose fragments on phone). Close the drawing by the end of the pin, cut the pin height (210svh feels long for four words), and give the screen one big thing: let the word in its moment grow past 64px and the others settle smaller, instead of four equal columns.
- Separate from /automations' first screen. Same h1-left/ask-right/rounded-frame layout. Give /auto its own composition, e.g. the editor as the full-bleed object with the h1 over its top-left, or the race lanes running edge to edge without the framed window (and drop the three window dots).
- Make the index less of an accordion. The open row leaves ~250px of empty left column under a three-line body; put the row's mini beside the title (top-aligned) or let the body column hold the step list, and shorten the closed rows to 56-64px so the open one is clearly the moment.
- Copy confirmation: swap the label to Hanzo's existing confirmation word (or the register's) and the icon to a tick for ~1.5 s; right now a 10px tick crowds the copy icon and "Copy" never changes.
- Contrast of the finished goroutine "done" node (white on mid grey) and reduced motion: confirm
getAnimations()is empty at 3 s at 375x667. - Shared, not this page's fault: the header glass shows a grey smear when a dark object (the index minis) passes under it; worth a request to the header owner.