Before the Builder, carry over two fixes from job 1's delivery; both are visible on the live site and both are defined by mockup/index.html.

(1) The top bar must be exactly the mockup's top bar, by the owner's decision (SPEC 14.9): at desktop the hook glyph ʃ at 30 px in VT323 with a 10 px gap, the wordmark at 12 px, nav links padded as in the mockup instead of fixed 48 to 72 px boxes, and the chain pill reading Sepolia · test phase; keep the 820 px wrap rules, the 12-character address rule and the header tests from job 1.

(2) The landing copy must use the mockup's text and faces exactly: the eyebrow UNISWAP V4 HOOKS · BUILT BY THE IMD SWARM in Press Start 2P, uppercase, pine; the lede Describe the hook you want, or stack reviewed blocks. The swarm writes it, tests it, audits it and launches it. You pay 0.5 IMD and gas.

The three live numbers keep their real /swarm names and stay hidden on failure.

(3) The catalog lists only hooks launched through this site (SPEC 3.1 and 14.9): remove scripts/snapshot-launches.mjs, public/launches.json, the unit test for the snapshot and the Public launch snapshot line; job 3 will read this site's launches from chain, so for now the grid shows the empty pond panel from SPEC 3.1 (NOTHING ON THE POND YET, the one line, a DESCRIBE A HOOK button to #builder) with the count 0 hooks, a search or filter shows the no-match state, the featured strip keeps only the open-slot card, and the README's regenerate section goes.

Everything else from job 1 stays as delivered, including the Learn cost answer at 24 hours. The Hooks Store, phase 1 job 2 of 6: the Builder. Implement SPEC.md sections 3.2, 4 (including 4.11) and 5 exactly, matching mockup/index.html.

The canvas reads as three numbered questions: 1 launch type cards A, B, C first; 2 the describe-or-blocks segmented control with the two-card chooser on a first visit; 3 settings. In Describe mode, show the blocks added from the palette as chips with a remove button under the text area, and the one-sentence rule that numbered rules win over the words; the palette stays usable in both modes.

Switching modes keeps both the words and the blocks, which the composer always combines as section 5 says.

Add src/blocks/catalog.json with every block in section 4 (id, group, title, blurb, types, params with defaults, limits and units, short label, sentence template that ends with the exact management functions of 4.11, ownerPower, requires, excludes, replaces, owner, anyone, user, view) and src/lib/compose.ts that produces the description text in the exact order and wording of 5.1 for launch types A, B and C (the owner sentence ends with through the functions named above when there are powers; with words and rules together the sentence says the numbered rule wins on a disagreement; the last line asks to keep the function names) plus the request body of 5.2 (univ4_hook body for A with shape, references, steps, chainId, pairWith, owner, economics and customToken only when true; evm_contracts body for B and C; repoUrl and baseCommit when the own-code fields are filled).

Palette as collapsible groups with added/total counts and the grey state pills that wrap within 96 px and never squeeze the text column. Block cards show the short label, the fields, the Who uses it line from section 4.12 and the after-launch note (On the hook page: owner buttons, anyone can, users get). Blocks not allowed by the launch type are dimmed and excluded.

Preview: the short summary rows, the full description text inside a details disclosure, cost box with amounts in VT323, a disabled free-check button noting it needs the relay, Continue. Enforce every rule in 4.10 and show inline errors. Drafts persist under localStorage hooks-store:draft:v2 and reopen; the landing box text from job 1 lands in the describe editor.

Tests: every catalog block renders its sentence with defaults under each allowed type and the sentence contains its 4.11 function names; the fixtures compose-A.txt, compose-B.txt and compose-C.txt in tests/fixtures are identical; body under 16 KiB; the 5% rule, the swap-fee dependencies and the buy/sell exclusion are enforced; Playwright at 320, 390 and 1440 for choosing a type, choosing a mode, switching modes without loss, adding, reordering and removing blocks, and reload persistence.

Deliver the source, dist/ and the test report files under tests/results. Pool share per SPEC 3.2 and 5.2: no default value; the field starts empty, Continue stays disabled until the user chooses 10 to 90 in steps of 5, and economics is sent only when chosen.

Gameable blocks per SPEC 4.13: a risk field in the catalog, a small yellow warning sign with a hover and focus tooltip (Heads up: this block is easy to work around or needs care, followed by the risk sentence) next to the block name in the palette, on the block card and in the summary list, no red labels, and the Prize pot in its own palette group named Games and lotteries; tests cover the required pool share and that every block with a risk field renders its sign and tooltip.

Tested marks per SPEC 4.14: at load fetch https://raw.githubusercontent.com/the-hook-store/hooks-store-spec/main/evidence/blocks-verified.json and fall back to the bundled public/blocks-verified.json (ship it as an empty array); a block with an entry whose passed is true shows a small tick and the words tested on Sepolia on its card, every other block shows not yet tested on Sepolia in its tooltip; tests cover both states and the fallback.