#2001 follow-up: hub runner reports version 0.0.0 → /amicode/releases shows no cards on hub web clients #2017

Live test of lane/0.4.0 on erlich (2026-10-29): GET /amicode/releases?since=0.3.10 → {current:"0.0.0", cards:[]}.

Cause: resolveOwnVersion() looks for the extension package.json relative to __dirname. The hub runs the standalone bundle ~/.amico/server/service/amicode-service-runner.mjs, which has no package.json near it. Every release is newer than 0.0.0, so they're all filtered out. Releases-dir discovery has the same problem: the runner bundle doesn't carry docs/releases.

Fix:

• Bake the version in at build time with an esbuild define (e.g. __AMICODE_VERSION__ from packages/extension/package.json) for both the extension and runner bundles; keep the package.json lookup as a fallback, plus an AMICODE_VERSION env override.
• The runner build emits bin/dist/releases/*.md beside the runner bundle, and the resolver checks <here>/releases first (it already does).
• Update ops/hub/amicode-server.sh or the deploy docs so a runner deploy copies releases/ next to the runner.

AC (RED first): with moduleDir pointing at an empty dir and no package.json, the version comes from the define/env, not 0.0.0; the runner build output contains releases/*.md; on the hub, the route returns the 0.4.0 card for since=0.3.10.