The only root entry point immediately redirects to mockup/index.html, which identifies itself as a sample-data design mockup. The requested Vite/React/TypeScript implementation and deployable dist/ export are absent: there is no package.json, src/, public/, scripts/snapshot-launches.mjs, or test suite.

Consequently this checkout cannot deliver or verify the commissioned phase-1 site, including the generated launches snapshot, configurable in-progress banner, and exported cast function. This is a delivery defect, not evidence of prohibited hosting content.

The served landing also hardcodes the network counters to 1,045 / 52 / 6 (mockup/index.html:272-275), makes no /swarm request, renders three sample paid placements instead of only the open slot, and exposes simulated Builder/Launch/Hook/My hooks screens instead of the requested later-job placeholders.

The permissions table uses long unbreakable callback names in Press Start 2P and a two-column layout without a narrow-screen wrapping or stacking rule. At 320 CSS pixels the table extends to x=434.25 and the document scrollWidth is 434, so the explanatory column lies outside the viewport and outside its bordered panel. This violates the explicit Store/Learn no-horizontal-scroll requirement and makes the reference difficult to read on phones.

The same 434 px document width was reproduced at a 390 px viewport.

matchesQuery builds its searchable text from the name, symbol, short summary, block labels and chain, but omits h.req. Section 3.1 requires all search words to match across those fields and the request text. A hook cannot be discovered by requirements that appear only in its original request.

Submitting the landing describe form calls save(), which writes hooks-store:mockup-draft:v3 rather than the specified hooks-store:draft:v2. Although the prompt appears in this mockup Builder, the agreed storage interface for the later Builder job is empty, so submitted descriptions will not carry into that implementation.

The search form is allowed to shrink to zero while the brand, navigation, chain pill and Connect button keep widths whose sum exceeds a small desktop viewport. The mobile layout starts only at 820 px. At 821 px the search form has width 0 and Connect extends to x=959, making these primary controls unusable without horizontal scrolling.

Section 3.0 requires search to retain at least 120 px and the top bar to fit above 820 px.

The empty-state reset clears the search and group/chain checkboxes but does not reset filters.status or the selected status radio. The action therefore does not restore the full catalog as its label promises.

The ticker sets pointer-events: none, which is inherited by the dynamically inserted animate-the-pond button. No button rule restores pointer events. The still frame correctly honors reduced motion, but the advertised per-visit opt-in cannot be used with a mouse or touch.

The WHAT DOES IT COST? answer says a featured placement costs 0.1 IMD for 7 days. SPEC.md sections 3.1, 6.3 and 6.6 specify 24 hours, and both the Store strip and My hooks repeat 24 hours. This leaves contradictory pricing terms in the required Learn content.

The explicit design-mockup disclaimer and absence of live purchasing make this an advisory copy defect rather than a deceptive-sale hosting blocker.

Now: The full-width .landing-copy box receives pointer events throughout its 120px bottom padding on phones, covering visibly empty water above the water-trigger button. Taps there produce neither a splash nor a cast.

Change to: Add pointer-events: none to .landing-copy and pointer-events: auto to .landing-copy > *, so its text, form and links retain their interaction while uncovered gaps and padding pass through to .water-trigger.

Why: SPEC §3.1 and §9 require clicking the water to cast and splash; decorative layout padding should not swallow that interaction.