The Hooks Store, job 14: stopped and failed launches leave the public pond, the Checking pill, and the resilience carry-overs.

Read SPEC.md at its current version (1.56, decision 49) in https://github.com/the-hook-store/hooks-store-spec and the sections "Carry-overs for job 14" and "Carry-overs for a later job 14" of jobs/next-job-carry-overs.md there (raw: https://raw.githubusercontent.com/the-hook-store/hooks-store-spec/main/jobs/next-job-carry-overs.md) for the full wording and tests of every item; every item is in scope, in this order.

(u) Public pond (SPEC 3.1, 3.4, 3.5, 7.3, decision 49), first: the Store's grid lists three test launches of 2026-10-21 that IMD's builders stopped with a question (intake chain 1, requests 0x43921ed5…, 0x4208cbe0…, 0x8c7a2972…, full ids in the carry-over) as REQUESTED cards for good, because the Intake never completes a stopped launch.

A launch is public while it is live, in progress (IMD's record says its job is executing, or completed with the launch not yet live, or the launch is deploying) or requested for less than 24 hours since its Requested log's block time with no record saying it stopped.

Not public: Completed status 1 or 2 (Failed); a job record that is blocked, cancelled, failed or superseded or has a node whose failure reason says needs_input; a launch record parked or failed; or a request 24 hours old or older with no record saying it runs. The age rule needs no relay.

Public surfaces list public launches only: the catalog grid and its count, the search results, the status rail (All = every public launch; Live only; In progress = in progress, checking and young requested), the landing's launch list and casts, and the featured strip's hook lookup.

Not public launches stay in My hooks for the payer (status pill, the Needs attention text, Fix in Builder) and at their direct link #hook//, where one line under the header reads "Not on the pond: IMD stopped this launch" or "Not on the pond: this launch failed"; the page is otherwise unchanged.

Tests: unit tests of the rule for every case listed in the carry-over, with the three stopped launches' real job records as fixtures; Playwright on a pond-shaped fixture set: the grid counts 4 hooks, the three stopped launches are in neither the grid nor a search for their names, all three appear in My hooks for the paying wallet with the Needs attention text, their direct links open with the Not on the pond line, a request younger than 24 hours shows in the grid and leaves it on the next refresh once its job record reads blocked, and the four live hooks still read LIVE and PROVEN.

(v) Checking, not In progress (SPEC 7.3): a live type A launch whose hook code is not yet verified on chain reads "Checking…" (status class status-checking), is public and counts as In progress in the rail, and turns LIVE when the verification completes; it never reads In progress; a unit test on the derivation, Playwright before and after the code read.

(r) Live without IMD's record plane (decision 48): the spec repository now publishes evidence/launch-records.json (raw: https://raw.githubusercontent.com/the-hook-store/hooks-store-spec/main/evidence/launch-records.json, refreshed every six hours by scripts/launch_records.py there, which is not yours to change): {version, generatedAt, launches: [{launchId, launchNumber, chainId, kind, status, parkedReason, createdAt, updatedAt, jobId, jobState, blockedReason, paidBy, objectiveSha256, sourceRepoUrl, sourceCommit, attested, artifacts: [{role, name, address, txHash, blockNumber}], pool}]} for every store launch IMD lists, live or parked. objectiveSha256 is the lowercase hex SHA-256 of the UTF-8 request objective, which the site already decodes from the Requested log's body, so a chain-read request matches its record with no relay call; paidBy must equal the request's payer.

The site fetches the snapshot at load like the proven index, never bundles it, and uses it to resolve addresses, Live (still confirming hook code on chain as today) and the public rule's running and stopped states whenever /intake, /jobs or /launches fail, time out or answer 5xx; the relay stays the first source and the chain scan keeps working for new requests. Ship a fixture of the file.

Playwright: with /jobs and /intake answering 503, the catalog shows the four live hooks as Live from the snapshot.

(s) Log windows and backoff (SPEC 7.2, decision 48): a per-endpoint maximum log range in site-config.json (publicnode: 10,000 blocks), windows split to fit the endpoint in use, a backoff of 2, 4, 8 seconds on 429 before any retry, at most two log scans in flight per chain, and the validation run includes a scan against the real endpoints with the counts of failed calls in the results (zero on a quiet network).

(t) Findings grouped by cause (SPEC 6.7, low): on a hook-only draft with a name typed and no wallet connected the Builder lists seven findings for two causes; the chain finding suppresses the PoolManager and deployer findings that follow from it, and the missing owner raises one finding that also covers the recipient, the body address and the deployer constructor lines, the others appearing only when the owner is set and still wrong; unit tests on the grouping, Playwright asserts two findings on that draft.

Deliver source, dist/ and test results.