chore(release): add release-smoke pre-release gate + fix stale CLI --version

[saucam]

Why

We're prepping the next codeoid release and had no single command to answer "is main releasable?" CI runs lint/typecheck/test/build, but silently skips the real-backend integration suites and never boots the shipped bundle — so a binary that builds but doesn't start, or reports the wrong version, would sail through.

What

bun run smoke (scripts/release-smoke.sh) — a pre-release gate that:

Stage	What it proves	New vs CI?
daemon lint / typecheck / test / build	code + bundle are sound	mirrors CI
version coherence	built codeoid --version == package.json	new
daemon boot probe	the built bundle actually starts + binds its port (isolated XDG_CONFIG_HOME, --no-web --no-telegram)	new
web lint / typecheck / test / build	web app is sound	mirrors CI
integration: backends (opt-in)	create → turn → reply, and cross-backend fork → recall, against a live backend	new

The integration layer is opt-in — CODEOID_SMOKE_INTEGRATION=1 bun run smoke (needs an authed backend; costs tokens). Backends come from CODEOID_SMOKE_BACKENDS (default claude); two authed backends also exercise the cross-backend fork-resume journey. Without opt-in it prints a clear SKIP (never a silent pass). CODEOID_SMOKE_KEEP_GOING=1 runs every stage even after a failure.

The boot probe uses a throwaway config dir, so it never touches your real ~/.codeoid state or a daemon you already have running.

Drive-by fixes the smoke surfaced

• fix(cli): source --version from package.json — codeoid --version was hardcoded to "0.1.0" while the package is 0.2.0. The shipped binary lied about its version. Now sourced from package.json (bun inlines the JSON at build) so it can't drift — and the smoke's version-coherence stage keeps it honest. (Run against unpatched main, the smoke FAILs this stage — which is the point.)
• test:integration pointed at an empty src/integration/ directory (ran zero tests). Repointed at the actual src/tests/*.integration.test.ts suites.

Verification

bun run smoke on this branch — all deterministic stages green:

PASS  daemon: lint / typecheck / test / build
PASS  daemon: version coherence      (0.2.0 == 0.2.0)
PASS  daemon: boot probe             (built bundle boots + accepts a connection)
PASS  web: lint / typecheck / test / build
SKIP  integration: backends          (opt-in)
release-smoke: OK

🤖 Generated with Claude Code

[github-actions]

🤖 Gemini code review

This PR introduces a robust pre-release smoke testing script (scripts/release-smoke.sh) that runs linting, type-checking, unit tests, version coherence checks, and a live daemon boot probe. It also fixes a bug where the CLI was hardcoded to version 0.1.0 instead of dynamically sourcing it from package.json, and corrects the integration test path.

Findings: 🔴 0 · 🟠 0 · 🟡 0 · 🟢 1

---

_{Tokens spent · ⬆️ Input: 3,997 · ⬇️ Output: 274 · Σ Total: 9,820
Total may be higher due to thinking token counts.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 84.90%. Comparing base (f4139b7) to head (cf15e36).
⚠️ Report is 1 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #175   +/-   ##
=======================================
  Coverage   84.90%   84.90%           
=======================================
  Files         106      106           
  Lines       18678    18678           
=======================================
  Hits        15858    15858           
  Misses       2820     2820           

Flag	Coverage Δ
daemon	84.90% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.