Public root
Use the domain as a product URL, not as an implementation detail. This makes the site shareable without looking like a health endpoint.
A branded front door for shared sessions, operator visibility, and bundle distribution. The coordination protocol stays ACP underneath. The public surface becomes simpler to share.
The root URL is now a landing page instead of a raw runtime payload. Operational endpoints stay available on explicit paths, so you keep diagnostics without exposing them as the first impression.
Use the domain as a product URL, not as an implementation detail. This makes the site shareable without looking like a health endpoint.
The agent bundle is served by the hub itself, so the landing and the downloadable artifact live behind the same deployment surface.
The runtime snapshot moves to /runtime and health remains at /health. That keeps automation and diagnostics stable.
Pull the packaged ACP agent bundle directly from the hub and keep installation linked to the same branded entrypoint.
The current package is available at /downloads/ACP_AGENT.zip and can be distributed from the same service that powers the dashboard and session coordination.
Use /dashboard for the web UI, /runtime for readiness metadata, and /health for lightweight probes.
If you later want a cleaner separation, the landing can stay on the root domain and the hub API can move behind a subdomain without changing the product identity.