Bring VERSION into scope where the file uses it

`export { VERSION } from "./version.js"` re-exports a name without binding it
locally, so the two bare uses of `VERSION` in this file did not resolve and
`main` stopped typechecking. Importing it and re-exporting separately does
both jobs, and the alias that worked around the first half is no longer
needed.

The re-export landed while those two call sites were on a branch, so neither
change was wrong on its own base and the break only existed once both were on
`main`. A gate that ran on the merged state rather than on each branch would
have caught it.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DTmy4SEXrHXouw5sZbs3f4

Co-Authored-By

Claude Opus 5 (1M context) <noreply@anthropic.com>

Claude-Session

https://claude.ai/code/session_01DTmy4SEXrHXouw5sZbs3f4

Deploy story

What this commit did to the running system — joined from the forge receipt chain, the part a commit page elsewhere cannot show.

Changed files

• modified packages/openagents-cli/src/cli.ts

Diff

1 file changed, +7 -3

import { TerminalSession } from "./terminal-session.js";

// The version lives in `package.json`; see `version.ts`.

export { VERSION } from "./version.js";

import { VERSION as CLI_VERSION } from "./version.js";

import { VERSION } from "./version.js";

// Re-exported because `main.ts` reads it from here, and imported above because

// this module uses it too. A bare `export … from` would do only the first, and

// every use in this file would be an unbound name.

export { VERSION };

const profileFlag = Flag.choice("profile", ["production", "staging", "local"]).pipe(

  Flag.withSchema(Profile),

  ]),

);

export const runCliWith = Command.runWith(openagentsCommand, { version: CLI_VERSION });

export const runCliWith = Command.runWith(openagentsCommand, { version: VERSION });