Files
Claude 07cf81bd47 Handoff layout: new README; build-chat notes moved to docs/build-notes/
- README.md: what this is, how to run and build it, the folder map, how light and dark
  mode work (@hanzo/appearance, @hanzo/design), where every price and checkout link
  lives, scripts, and known differences from live
- docs/build-notes/: status files, request notes, per-page checklists and reviews, plans
- Removed: screenshot galleries, captures of third-party sites used as references,
  the generated status page and its script, editor config, a personal working-rules file
- Code comments point at the new docs paths (no code changes)

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01P5YBdwj33XByFVTvu9bfci
2026-11-08 13:22:36 +00:00

7.8 KiB
Raw Permalink Blame History

/billing — James-eye review

Reviewed 2026-11-07 ~17:00, walked moving at 1470x801 and 375x812 (Playwright, wheel steps of 400px every 700ms, rest pairs 1s apart, hover/press/click on every control in main, the console drawer opened at both sizes). Proof: docs/build-notes/review/billing/desktop-first.jpg, desktop-walk.jpg (the dead white gap after the hero machine releases), phone-first.jpg, phone-walk.jpg (the hero machine running edge to edge with no gutter).

Verdict: 7.5/10 Ready: 8 Nov, copycheck missing 0 of 48 (hanzo.ai live), held up next to /api and /affiliate (James's new bar, no score). Hanzo's example console is back in the page as on hanzo.ai (it had been behind a drawer, so its lines were missing): the projects list, "The service the session above is changing.", Open in the console and its caption sit in the Get started column beside the code and the agent prompt; capability titles and code runs are real text runs. Usable: calculator, code, prompt, Read the docs and console in one place. taste/unique OK; 0 console errors, no overflow at 1470 and 375. Shared, tiny: components/pages/cloud/Frame.jsx code runs wrapped in spans, components/v2/Finale.jsx prompt's api label as a span (Launch.css selector).

First complaint: "Better: it's alive and it makes sense now. But I scroll off the hero and get half a screen of nothing, then the same event, meter, invoice machine shows up a third time at the bottom as three dark boxes in a row. Don't repeat the trick, finish it."

The 11 answers

  1. Sells in 5 seconds, moves within 1 second? Yes. The h1 "Hanzo Billing" (52px) is top-left at y 100 with the mono caption under it and the solid "Read the docs" at y 214. The whole machine is on the first screen at 1470x801: events land every ~0.4 s, the black meter rolls its digits (7, then 9, by 2 s), and the invoice moves Draft → Preview. On the phone the h1, lede and ask fit, and the machine peeks at ~575px.
  2. One in, one out? Mostly. The hero copy scrolls away while the machine pins, then the three chapters pin one invoice that changes (Plans and prices → Meters → Invoices, with a 01/02/03 rail). The joins are where it breaks. Once the hero pin releases there is ~350px of blank white at 1470x801 (the frame's bottom is at y 260 and "The objects you bill with" is at y 608 when scrollY is 800). There are also ~190px of empty black above "What the endpoint gives you" and ~160px of empty white above "Report the use, then charge for it". On the phone, the chapters unpin into three stacked full invoices (~600px each), so the phone reads the same invoice three times, as a document.
  3. A real object in every section? Yes. The hero has the machine. The chapters have the price stack with +/Reset, the 18-cell meter and the Draft/Preview/Issued stepper, all beside the invoice. The history has the cus_abc123 history ledger. Get started has the code pane, the agent prompt and the console drawer. The close has the replay machine.
  4. One ask, sticky after the hero? Scale rhythm? Yes. "Read the docs" is solid in the hero and again in Get started (never two in one viewport); GitHub is a text link; the header keeps "Try Hanzo"; there is no floating bar. Scale has rhythm: h1 52, section heads 26, h3 21/17, figures 64 Air only in their moment (the meter, × 18), mono 12-13 around them.
  5. Every hover and press answers? Nearly. Primary: fill #0a0a0a→#2c2c2e and press scale .98. GitHub greys with its arrow. Pause fills #ededed. "+" and Reset fill and darken their border; "+" disables properly (35% opacity, dashed) once Price 3 exists. The capability items light the matching history row. Copy and "Deploy to Cloud"/"Logs" get underlines. The drawer opens, focus lands on Close, and Esc closes it. Two dead: the 01/02/03 chapter rail buttons show no hover change (click does jump to the chapter), and the history ledger rows do not answer a pointer on their own, only from the left list.
  6. Overlap, font swap, layout shift? No overlap at either size, overflow 0 at both. CLS was 0.0006 desktop and 0.0001 phone over the full walk, all sub-0.001 from the shared header and figure digits. No font swap seen. A hydration-attribute mismatch badge appeared once under shared load. It did not reproduce on 3 solo reloads at each size, so it is not counted.
  7. Which reference, and is its motion there? apple.com product page: the product as the hero, and a pinned scene where one panel (the invoice) changes per chapter. The motion is genuinely there: pinned invoice, the rolling counter, the stepper, the stamp landing on the phone. Motion kinds: idle (hero), time (counts), state (price publish, steps, drawer), pointer (capability highlight), with scroll limited to the pin. That is a good mix.
  8. Different from its neighbours? Its own object (an invoice built from a meter) and its own signature (the invoice building as you scroll). The split hero layout is shared with /telemetry, but the object differs.
  9. All 18 parts covered? The card has 18 of 18 headings filled. Claims I checked hold: the machine is on the first screen, CLS is near 0, the phone stamp no longer overlaps, the drawer opens below the header, Publish has a disabled state, overflow is 0, the h1 is 52/40. One claim is not true: "Every control has hover" fails for the chapter rail buttons. A second claim is weak: "black room enters as a rounded card" (MASTER 3.1) is not done, because both dark rooms enter as hard full-bleed rectangles.
  10. Banned tells? One borderline tell. The closing band's machine is three dark same-height boxes in a row (324 / 421 / 324px wide, 160px tall, joined by dashes), and it reads as "3 equal boxes in a row". Nothing above a headline, no hue, no glow.
  11. Copy untouched? As far as the walk shows, yes. Hanzo's words appear as live, and demo names (cus_abc123, api_requests, price_api_metered) are drawn as objects, not claims. The card reports parity at 0 missing.

Fixes (ordered, most important first)

  • Close the dead air between rooms. Desktop, after the hero pin releases, ~350px of blank white sits between the machine's bottom and "The objects you bill with". Either let the chapter head rise into the machine's exit (40px overlap, one in as one goes out), or shorten the pin's tail. Also trim the ~190px empty top of the black history room and the ~160px empty top of Get started.
  • Don't replay the hero machine as three dark boxes at the close. bl2-fin repeats events → meter → invoice a third time, as three same-height dark tiles in a row (a banned tell). Make the close one object: just the Issued invoice landing once, or the single meter line. It should not be a third copy of the hero.
  • Make the chapter numbers agree. In chapter 02 the left meter read 5 while the invoice read "× 10" in the same frame. In chapter 03 the stepper showed "Issued" while the invoice chip still read "Preview". Drive both from one value so the logic reads true ("logic applied").
  • Phone: give the hero machine its gutter, and don't stack three full invoices. .l2-stage-pin / .bl2-mach sit at left 0, width 375, so the outer frame's rounded border is clipped at both edges. Put them inside the 16px gutter. In stack mode, show the full invoice once and let chapters 02 and 03 show only the line that changes (the × 18 row, then the stamp), instead of three ~600px invoices.
  • Phone code pane wraps mid-token. In the typescript pane at 375, 'default_incomplete', and }], fall onto their own lines. Use horizontal scroll (a labelled tabindex=0 region) with no wrapping inside string literals.
  • Hover on the 01/02/03 chapter rail (a 48x44 button, currently no hover change): darken the segment or lift the number. Also let the history ledger rows answer hover themselves, lighting their matching capability on the left.
  • Dark rooms enter as rounded cards that open to full width (MASTER 3.1). Both bl2-hist and bl2-fin currently cut in as hard rectangles.