max / makenotwork

Disclose founder pricing on /pricing, and compute on it The landing page leads with founder pricing at half of list. /pricing did not mention it anywhere, so a visitor walking landing -> pricing saw the full price and no sign the discount existed. That matters more here than on a page of numbers, because /pricing is the fee calculator rather than a price list. The tier radio's value is what hx-include sends to /pricing/compare, so it is the price the server computes the outcome on. A visitor inside the founder window was being shown what they keep at a price they would not pay. Two parts, both gated on founder_window_open, read from the same config the landing page reads so the two cannot disagree about whether the offer is live: The banner reuses the landing tagline's wording and its .founder-tagline classes. Same offer, so a second phrasing for it would read as a second offer, and the class reuse means no new CSS. The toggle is <mnw-price-mode>, an island over the tier cards. Each card publishes both prices as data-price-std and data-price-founder, so flipping is a local swap with no round trip for the prices; the recompute is the calculator's existing one, re-fired by dispatching change on the checked tier radio, which is what hx-trigger already listens for. Pure logic sits in price-mode.logic.ts under node --test, including the case that made it worth extracting: getAttribute returns "" for a present-but-empty attribute, and writing that into the radio value would send an empty tier price to the calculator. The server renders the founder price as the default, so the flip is the only thing JS is load-bearing for. Without it the page still opens on the price the visitor would actually pay. With the window shut nothing above renders and the page is what it was. The harness gained founder_window_open and with_founder_window_open(), since every existing test runs with it shut and neither surface was otherwise reachable; both states are now asserted.