Links to dispatch-agents.wave.online (host serves nothing) and developer.wave.online/dispatch 404; agent-card missing

[yakimoto]

Summary

dispatch.wave.online links a sibling host that does not exist and a developer-portal path that 404s. A dead-link sweep across all 58 WAVE hosts attributes 3 dead internal links to this host after auth-walled routes were correctly excluded.

This is a small, contained finding — worth recording because two of the three point at a hostname that is not in the 58-host surface inventory at all.

Receipts

$ for u in https://dispatch-agents.wave.online/ \
           https://dispatch-agents.wave.online/mcp \
           https://developer.wave.online/dispatch; do
    printf "%-46s " "$u"; curl -s -o /dev/null -w "%{http_code}\n" "$u"; done
https://dispatch-agents.wave.online/           404
https://dispatch-agents.wave.online/mcp        404
https://developer.wave.online/dispatch         404

dispatch-agents.wave.online does not appear in the surface inventory. The host resolves and terminates TLS — it is inside the zone — but serves nothing, so the links read as a rename or a plan that was never built.

The host's own surfaces are healthy, and its authenticated routes are correctly excluded from this count:

$ curl -s https://dispatch.wave.online/portal
{"error":"unauthorized — Authorization: Bearer <license-key>"}

That 401 names the credential it wants, which means the route exists. An earlier run of the probe counted /portal and /account as dead; that was a verdict bug in the checker and is fixed separately in wave-conformance. They are not defects here.

One further note from the same sweep, not counted against this host: dispatch.wave.online serves /.well-known/agent-card.json as a 404 while serving /llms.txt as 200. Agent-card is how an agent identifies the surface, so it is worth serving alongside the llms.txt that is already there.

$ curl -s -o /dev/null -w "%{http_code} agent-card\n" https://dispatch.wave.online/.well-known/agent-card.json
404 agent-card
$ curl -s -o /dev/null -w "%{http_code} llms.txt\n" https://dispatch.wave.online/llms.txt
200 llms.txt

Suggested fix

Point the two dispatch-agents.wave.online links at whatever host actually serves that surface today, or remove them if the capability folded back into dispatch.wave.online. Correct the developer.wave.online/dispatch link to the page that exists.

Serve /.well-known/agent-card.json so the discovery set matches the /llms.txt already published.

Verification

$ node link-check.mjs   # wave-av/wave-conformance, daily T0 probe

dispatch.wave.online should drop to zero internal dead links. Current: 3.

Found by the docs-completeness and dead-link sweep, 2026-09-03.