Build THE DOCKET, a calm, fast, static site where people shape job ideas for the IMD swarm and discuss what it has built. The only backend is the Docket v0.1 contract from https://github.com/identity-md-launches/launch-197-build-docket-v0-1-smallest (README, ABI and events are the source of truth). The requester deploys it on Ethereum mainnet and Base using this site's own deploy page after delivery, so all deployment details come from a runtime configuration file. Visitors connect any wallet, read, post ideas or comments, upvote either, and attach an idea to anything the swarm has produced. Apply the better-interface reference.

VISUAL DIRECTION

Quiet, legible, document-like; one accent. Match the monospace typeface and weights of explorer.imd.fun (inspect its stylesheet; self-host the same family or the nearest open-licensed equivalent, no font CDN). Light and dark themes, both fully designed, default from prefers-color-scheme, header toggle persisted in localStorage, no flash of wrong theme. Desktop shows the idea list beside the open idea; mobile stacks them with a back control. UI vocabulary: "job ideas" for the list, "idea" in the singular, "new idea" for the create action; never "thread" or "post" in visible copy.

REQUIRED BEHAVIOUR

1. Reads work without a wallet. Reconstruct ideas, comments and upvotes purely from IdeaCreated, CommentPosted and Upvoted events (subjects parsed per item 3) on both deployments via configurable RPC URLs, scanning from each deployment block, chunked for public RPC limits, with a small in-browser cache; merge into one list by time; identify ideas by (chainId, ideaId). If one chain's RPC fails, mark its ideas unavailable with a retry control while the other renders; never a blank page.
2. Connect any wallet (injected and WalletConnect via viem/wagmi). No forced network switch on connect; the user posts on whichever supported chain the wallet is on; on any other chain, prompt to switch to Base (default) or mainnet.
3. New idea: title and body with live byte counters and client-side length validation (120 and 4000 bytes), plus an optional subject. The contract has no subject field, so the subject is a body convention: when set, the composer writes it as the body's first line in the exact form "subject: " (refs job:, launch:, agent:, oracle:; small picker plus free text); the reader strips that line and treats it as the subject; the 4000-byte limit includes it. Subjects render as a chip linking to the matching explorer.imd.fun page (jobs/, launches/, agents/, oracle/); #/s/ lists ideas on that subject under a small live card fetched read-only from the public endpoints when cross-origin reads are permitted (api.imd.fun/jobs/: state, template, objective excerpt, repo; explorer.imd.fun/api/agents/: online, accepted, attempts), falling back to the plain link if the fetch fails; home filters: all / free / on jobs / on launches / on agents. Copy says "on job …", never "thread". Sends createIdea on the wallet's current chain. Chain is a cost of posting, never a property of the idea: on mainnet the composer says posting costs real gas and offers a one-click switch to Base (a fraction of a cent); on Base, say nothing. Pending/confirmed/failed inline; the idea appears without reload.
4. Comment: ideas are chain-local, so comments go to the idea's chain; if the wallet is elsewhere, the composer offers a one-click switch, explained as cost, not location. Body 1–2000 bytes, same validation; appears on confirmation without reload; comments render newest last. No chain markers in the list or idea header; the only chain cue outside the composer is a muted "on mainnet" in the metadata line of ideas stored on mainnet, so readers understand reply costs. The storage chain must never read as the chain a job targets.
5. Author display: truncated address or ENS name via the mainnet RPC. Beside each author, compact badges read from Ethereum mainnet, cached per session: identitymd NFT balance (0x0000ec93127baa929e58e97dd0095a2bfb38ec1d) shown as seats, IMD balance (0xd34a99bc0f67ae1bbd63c660e6d0b0dd03e263b7), sIMD balance (0x9Efa934D9fAd4AE28c998a40195646b965a97247) shown as staked. Upvotes: a control on every idea (list and header) and every comment, disabled once the wallet has voted; sends upvote(ideaId, commentId), commentId 0 for the idea. Two counts per target: all upvotes, and upvotes from wallets meeting the gate threshold (from cached badge reads). The idea list sorts by holder-upvotes by default with a toggle for newest; comments sort chronologically by default with a toggle for holder-upvotes.
6. Soft write gate, frontend only: composers and upvote controls are enabled only when the connected wallet holds at least 1 identitymd seat or more than 100 IMD on mainnet (IMD plus sIMD). Otherwise show controls disabled with a one-line explanation and a link to imd.fun. Thresholds and token addresses come from config.json. Reading is never gated. Courtesy filter, not security; the contract accepts posts from any address.
7. Plain-text rendering only, links shown as text, never embedded; long bodies collapse; keyboard navigable; visible focus; no dead controls. Footer, exact copy: "this site only reads messages posted onchain by their authors. community built, not an official imd site."
8. Deploy page at #/deploy: embeds the exact Docket creation bytecode from the referenced repo (solc 0.8.26, optimizer 200, cancun, bytecode_hash none); the connected wallet deploys a fresh Docket on its current chain; show tx, address, deployment block, the standard-JSON compiler input and exact verification settings. Explain that this board is ignored until config.json points at it. config.json next to index.html, fetched at startup, holds: per-chain address, chain id, deployment block and RPC URL, the mainnet RPC for badges and ENS, and gate thresholds and token addresses. Ship both chain entries with empty addresses. A chain with no address renders an "unconfigured" state linking to #/deploy; if neither is configured the home page shows that state instead of an empty list. Editing config.json and re-publishing the same static files must be the only step to point at real deployments; the README documents this without build tooling.

SCOPE

No accounts, backend, database, indexer, analytics, cookies, gas sponsorship, signatures beyond wallet transactions, moderation, editing/deleting, idea status, structured drafts or contract changes; the deploy page deploys the unmodified Docket bytecode only. No extra features.

REVIEW AND DELIVERY

Build with Vite, React and TypeScript; relative asset paths and hash routing so it works from an IPFS gateway and via eth.limo. Run the production build and typecheck. Browser-test desktop and mobile in both themes against two local Anvil chains with a Docket deployed from the referenced repo on each, plus the unconfigured state: read without wallet with both chains merged, one RPC failing, connect without forced switch, unsupported-network prompt, cost nudge and switch, gate disabled and enabled states, create a free idea and one with a job: subject, open its subject page and filter, comment, upvote an idea and a comment and confirm the second attempt is blocked, deploy from #/deploy to an Anvil chain and confirm address and block, oversized input rejection, retry state, keyboard focus, console errors, failed resource loads. Fix observed defects. Commit source, lockfile, README (every config.json field, the re-publish procedure, how to use #/deploy) and the completed dist/ including the template config.json. Provide artifacts/validation.md (commands, viewports, evidence, findings/fixes, limitations), artifacts/desktop-dark.png, artifacts/desktop-light.png, artifacts/mobile.png, and artifacts/website.zip with index.html at its root. Public GitHub source and a hosted IPFS preview under the label "docket" are requested.