fix(cli,ci): correct relavium --version + release-smoke install path; mark 2.L Done

[cemililik]

Follow-up to PR #49 (2.L · ADR-0051): fixes the two defects that surfaced on the first tag-triggered Release CLI run, plus the 2.L-Done status bookkeeping. Nothing was published — the publish job is gated on the cross-OS smoke, which went red, so relavium is still absent from npm (E404).

55aa3cc — fix(cli,ci): two release-blocking packaging defects

1. relavium --version reported 0.0.0. The version was a hardcoded sentinel, never wired to package.json (the program.ts comment deferred it to "packaging (2.L)", but PR #49 didn't do it). tsup now injects the manifest version at build time via a __RELAVIUM_CLI_VERSION__ esbuild define; program.ts reads it behind a typeof guard and falls back to 0.0.0-dev on a source run (tsx/vitest, no define). Bundled relavium --version → 0.1.0; source → 0.0.0-dev.

2. The cross-OS install-smoke failed on all three runners. npm install -g artifact/relavium-X.tgz — a slash-bearing arg without ./ — is read by npm as a GitHub owner/repo shorthand and git-cloned (Permission denied (publickey)), never as the local tarball. Prefixing with ./ forces the file spec (verified via npm-package-arg: bare → git, ./ → file).

Also adds a relavium --version == package.json assertion to the smoke matrix so a version-wiring regression is caught before publish — the old smoke only ran --help, which is why #1 slipped through.

424b363 — docs(roadmap): mark 2.L Done (PR #49), next pickup 2.S

2.L closed the last Phase-3 go/no-go exit criterion (#7) — the Phase-2 spine is complete and all seven criteria hold. A 4-surface discovery pass audited every status surface; only the live trackers were updated, the static plan views (Mermaid DAGs, wave/dependency tables, exit-criteria definitions) left unchanged per their own "the plan, not a live tracker" framing. ADR-0051's "(today a stub)" aside was left unedited — ADRs are append-only (CLAUDE.md rule 9).

• current.md, phase-2-cli.md, CLAUDE.md, README.md: 2.L → Landed list; next pickup → 2.S (media host-wiring); NPM_TOKEN obligation re-tensed; pickup queue renumbered.
• runbooks/release-a-surface.md: Status draft → partial — CLI (npm) flow complete (2.L).

Validation

turbo lint typecheck test build 20/20 · typecheck:tools · bundled --version 0.1.0 + full smoke exit codes (run 0 / gate 3 / unknown 2) · bundle-closure 15 deps · format:check · release.yml valid YAML · leakwatch 0 across touched files.

After merge (maintainer)

Re-tag to re-run the release (v0.1.0 was never published, so it is reused):

git push --delete origin v0.1.0      # drop the stale tag (points at the pre-fix commit)
git fetch origin
git tag -a v0.1.0 origin/main -m "relavium v0.1.0 — first public CLI release"
git push origin v0.1.0               # Release CLI re-runs → green smoke → npm publish (provenance)

🤖 Generated with Claude Code

Summary by CodeRabbit

• New Features
  • The CLI now reports its real published version, and the packaged install flow is verified across operating systems.
• Bug Fixes
  • Improved version checks during release smoke tests to catch mismatches between the installed CLI and the package version.
• Documentation
  • Updated roadmap and release docs to reflect the completed CLI release milestone and current project status.

[sourcery-ai]

Sorry @cemililik, you have reached your weekly rate limit of 500000 diff characters.

Please try again later or upgrade to continue using Sourcery

[coderabbitai]

Caution

Review failed

Pull request was closed or merged during review

📝 Walkthrough

Walkthrough

The CLI now stamps its package version at build time, falls back to a dev sentinel when run without the injected token, and the release smoke job compares the installed tarball version against apps/cli/package.json. Related roadmap, README, runbook, and CLAUDE text were updated to reflect the packaged CLI milestone.

Changes

CLI release flow and status docs

Layer / File(s)	Summary
Build-time version injection apps/cli/tsup.config.ts, apps/cli/src/program.ts	tsup now reads the CLI package version at build time, injects it as __RELAVIUM_CLI_VERSION__, and CLI_VERSION falls back to 0.0.0-dev when that token is unavailable.
Release smoke version check .github/workflows/release.yml	The smoke step installs the local tarball with a ./-prefixed spec and fails when relavium --version does not match the package version from apps/cli/package.json.
Status docs updates docs/roadmap/current.md, docs/roadmap/phases/phase-2-cli.md, README.md, docs/runbooks/release-a-surface.md, CLAUDE.md	The CLI packaging milestone, Phase 3 status text, next-pickup wording, and release-flow status notes are updated across the project docs.

Sequence Diagram(s)

sequenceDiagram
  participant ".github/workflows/release.yml" as releaseWorkflow
  participant "artifact/*.tgz" as tarball
  participant "relavium" as cli
  participant "apps/cli/package.json" as packageJson
  releaseWorkflow->>tarball: install ./artifact/*.tgz
  releaseWorkflow->>cli: run relavium --version
  releaseWorkflow->>packageJson: read PKG version
  releaseWorkflow->>releaseWorkflow: compare VER to PKG

Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

• HodeTech/Relavium#49: Introduces the CLI packaging/distribution/install verification work that this PR references and extends.

Poem

A bunny hopped through build and smoke,
Found the version string was no joke.
Tarball zipped and numbers matched,
So I nibbled carrots, neatly snatched. 🐇

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title is concise and accurately summarizes the main packaging fixes and the 2.L status update.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch development

---

_{Comment @coderabbitai help to get the list of available commands.}

[gemini-code-assist]

Code Review

This pull request implements CLI packaging, distribution, and install verification (workstream 2.L). It updates the build configuration in tsup.config.ts to read the package version from package.json and inject it into the bundle via __RELAVIUM_CLI_VERSION__ at build time, which is then consumed in program.ts. Various documentation files are also updated to reflect that workstream 2.L has landed, completing the Phase-2 spine and satisfying all Phase-3 exit criteria. There are no review comments, so I have no feedback to provide.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud