bug(build): genie-hook binary missing from standard build + 99MB compile vs 20MB wish gate (#1485 followup)

[namastex888]

Summary

Followup to #1485. Two related issues with the genie-hook thin-client native binary:

1. Missing from standard build artifact — bun run build does not produce dist/genie-hook. Operators must manually run bun build --compile src/hooks/dispatch-client.ts --outfile dist/genie-hook to get it.
2. Compiled size is 99,301,083 bytes (~95MB) — vs the wish's stated gate of <=20MB.

Both make the daemon-mode hook dispatch unusable as a production default: it's not built by default, and the manual build is 5x oversize.

Repro

cd /home/genie/workspace/repos/genie/.worktrees/dogfood-session
bun run build
ls dist/genie-hook   # absent

bun build --compile src/hooks/dispatch-client.ts --outfile dist/genie-hook
ls -la dist/genie-hook
# 99,301,083 bytes

Evidence: /home/genie/workspace/agents/genie/.genie/agents/dog-fooder/state/evidence/batch-2034c4f3

Why this matters

src/hooks/inject.ts (per #1485 commit body): "buildDispatchCommand() now prefers the compiled binary at GENIE_HOOK_BIN, ~/.genie/bin/genie-hook, or repo dist/genie-hook (in that order); falls back to the legacy bun .../genie.ts hook dispatch". Since the binary isn't built, every install falls back to the legacy bun fork. Same outcome as #1490 (UDS not created in detached daemon), from a different angle.

Acceptance

• bun run build produces dist/genie-hook as part of the standard artifact set
• Compiled binary size <= 20MB (per wish gate); investigate why it's currently 99MB (likely full tree-shaking opportunities, or bundling unused subsystems)
• Published npm @automagik/genie package includes dist/genie-hook so end-users get daemon-mode dispatch by default

[namastex888]

Triage @ 2026-04-30 — STILL-OPEN-CONFIRMED

Tested against: chore/pgserve-2.0.2 HEAD 4b5e1820 (chore(version): bump to 4.260429.33)

Evidence:

• Related fix exists at cf7275fd (feat(install): compile genie-hook binary at postinstall (87× hot-path)) but is only on branches dev and feat/genie-hook-binary-install — verified git merge-base --is-ancestor cf7275fd chore/pgserve-2.0.2 → NOT ON pgserve, NOT ON main.
• chore/pgserve-2.0.2 package.json build script is unchanged: bun build src/genie.ts --outdir dist --target bun ... — does not produce dist/genie-hook. postinstall runs only scripts/postinstall-tmux.js; no genie-hook compile step.
• Local dist/genie-hook (built manually) measures 94.7M — confirms AC2 (≤20MB) still violated.
• AC2 is explicitly deferred even on dev: cf7275f commit body states "the binary is ~95MB (bun runtime + bundled JS). The wish ≤20MB target was Rust-sized; bun-compile sets the floor higher. Delivery Best practice for adding language / framework spesific agents? #5 (Rust thin client) drops this to ~3MB while preserving the perf wins."

Verdict: STILL-OPEN-CONFIRMED

Status by AC:

• AC1 (bun run build produces dist/genie-hook): on dev, addressed via postinstall rather than build (binary lives at ~/.genie/bin/genie-hook, not dist/). Not yet on pgserve/main.
• AC2 (size ≤20MB): not met anywhere; bun-compile floor is ~95MB. Requires Delivery Best practice for adding language / framework spesific agents? #5 (Rust thin client → ~3MB).
• AC3 (npm package ships binary by default): on dev, postinstall compiles on user machine (functionally equivalent for end-users); not yet on pgserve/main.

Suggested next step: backport cf7275fd to chore/pgserve-2.0.2 to close AC1/AC3 functionally; keep this issue open against AC2 until Rust thin client (Delivery #5) lands.