GCD-WEB-117 — Start Here

PRESERVE-WHAT-WORKS

PRESERVE FIRST. The auditor is read-only. It is not authorization to redesign, reroute, restyle, replace components, rewrite content, or alter analytics, authentication, checkout, integrations, databases, APIs, accessibility, mobile behavior, SEO, or unrelated working behavior.

• Change: none; analyze supplied metadata evidence.
• Do not change: host design, structure, routes, contracts, or behavior.
• Touch only: separately approved metadata files/templates after review.
• Prerequisite: Node 18+, ESM, evidence, policy, and platform knowledge.
• Checkpoint: back up the site and capture representative rendered metadata.
• Install: extract, run npm test, then import src/index.js.
• Targeted tests: missing, duplicate, invalid URL, robots conflicts, and delivery visibility.
• Regression: routes, server head, social metadata, accessibility, mobile, analytics, and critical journeys.
• Compatibility: no crawler, DOM, index, social cache, or ranking verification.
• Failure/recovery: coded errors; correct input/policy and rerun; no mutation occurs.
• Rollback: remove the import; revert only later approved metadata edits from checkpoint.
• Unverified: production merge order, CDN headers, bot output, indexing, and sharing caches.
• Deploy next: use the existing pipeline and verify production head output.

PRESERVATION CONFLICT / REVIEW REQUIRED: stop if a fix needs structural, route, content-hierarchy, or rendering-boundary changes. Use the smallest metadata-only alternative.

Quick run

npm test\nnode examples/basic.mjs