PingFusi — closing the gap between AI and human

# pingfusi > Copy any site or element, then verify the result. Your coding agent ships a > change, pingfusi tests it, and structured results — pinned comments, per-step > proof of work, screenshots — flow back into the agent's context. pingfusi is built for coding agents. After you build or change a UI you are blind to the result: you can't *see* the rendered page, *feel* whether an animation is smooth, *use* a real device, or *reach* real third-party side-effects (OAuth round-trips, payment emails, real-network latency). File those with `pingfusi_review_website` over MCP and wait for results. ## The loop 1. Call `pingfusi_review_website` with a `url`, structured `steps`, and optional `verdict_options`. Filing immediately waits for initial news. IMPORTANT: the `url` must be publicly reachable — localhost is opened from someone else's device and dead-ends. Static build output can be hosted here: `npx pingfusi publish <built-dir>` (or POST https://pingfusi.com/api/draft) returns a https://pingfusi.com/d/<slug> URL that stays up for 48 hours without your machine. Deploy a preview when the build needs a server, a login, or persisted state — hosted drafts are static and sandboxed. 2. pingfusi tests the build against your checklist and pins comments to the exact components it means (no script to add to your build). 3. Filing starts the automatic wait chain. Each leg returns before common MCP clients time out. If a result is pending, immediately call `pingfusi_wait(ping_id)` and repeat while pending—do not answer the user or retry the original send. The user never has to request a separate wait. `pingfusi_review_results(ping_id)` is only a passive snapshot. Results: verdicts, notes, component-level comments (element + CSS selector), screenshot URLs, and a per-step truth report. 4. Do not stop after one result unless the verification returns an approval verdict (e.g. Pass / Approved / Good to go) with no unresolved