Build and publish SWARM ALPHA, a beginner-friendly directory of IdentityMD projects. Use real public data, not invented projects or metrics. Keep the name easy to change.

BRANDING: Use the attached Pepe image as our logo beside the Comic Sans MS brand title. Preserve its appearance, remove any checkerboard background and use a transparent image. Use its face as the favicon. If the attachment is unavailable, request it instead of inventing a replacement. Use a readable font elsewhere. No video.

DESIGN: Clean light theme with white cards, light grey background, dark text and blue accents. Add a visible light/dark toggle that remembers the choice. Rounded cards, generous spacing, clear search, responsive mobile layout and keyboard accessibility. Avoid clutter and repeated sections.

HOME: Show a short introduction and an empty search bar with placeholder “Search by project name, website URL or NFT number”. Search the whole directory by project name, URL/domain, contract address, NFT number and agent ID. Normalize URLs: pepe2pepe, pepe2pepe.fun and https://pepe2pepe.fun/ must find the same entry.

Each project gets a separate card showing its authentic logo (neutral initials if unavailable), name, short purpose, category, status, builder NFT profile links and last checked date. Add separate “Project details” and “Open website” buttons. Include category/status filters, sorting and pagination for all results.

DETAILS: Put important information near the top in clear panels:

1. Purpose, status, official website, source code and documentation.
2. Confirmed contract addresses, roles, networks, copy buttons and explorer links. Distinguish mainnet/testnet; label unknown addresses.
3. Builder, reviewer, verifier and publisher NFTs/agents prominently near the top. Show NFT numbers, avatars, roles, public profiles, work records and confirmed owner information with source/time. Distinguish owners, agents and automated services.
4. Promises versus delivery: each promise, Delivered/Partial/Pending/Broken/Unverified status, evidence, delivery date, last check and remaining gaps.
5. Timeline: request, work milestones, first delivery, publication and updates. Calculate elapsed time only from confirmed timestamps. Show promised deadlines only when documented; do not invent deadlines or assume first publication fulfilled every promise.
6. Documented risks, missing information, sources and expandable original request/version history. Add quick section navigation.

DATA: Use api.imd.fun, explorer.imd.fun, relevant repositories and confirmed onchain records. Collect all available sites, jobs and workflows using supported pagination; do not stop at the first 100 records. Reconcile records. Merge only explicitly linked versions into one project, preserving history and old links. Do not merge by similar names.

Include HIVE and https://pepe2pepe.fun/. Connect confirmed contracts and agents; otherwise mark verification pending. Never invent facts, logos, owners or scores.

BOTTOM: Add a searchable “IdentityMD Site Directory” listing all discovered site records with website/detail links and labels for old versions, removed sites and user submissions. Distinguish records from unique active projects. Show freshness and coverage limitations.

EVIDENCE: Label project claims separately from facts. Distinguish publication recorded, link reachable, feature tested and unverified claim. Explain exactly what “Verified” means. Publication or build acceptance does not prove every feature works or financial safety. Any score needs transparent rules and an insufficient-data state. Check links where feasible and offer IPFS alternatives.

DELIVERY: Functional React site, source code and production build. Use relative assets and hash routing for IPFS subpaths. Use live data where available and timestamped snapshot fallback; failures must not replace valid data with zeroes. No frontend secrets, login or wallet required.

TEST: Themes, mobile, keyboard, all search formats, Pepe2Pepe results, detail navigation, prominent agents, correct contract networks, evidence/timeline accuracy, pagination, directory coverage, version grouping and missing-data handling. Pass type checking/build. Publish and provide the repository and working website URL.