[Bug Report]: Standalone Tarko CLI --version reports 1.0.0 instead of package version

Version

0.3.0

Issue Type

• Other: standalone Tarko CLI (@tarko/agent-cli)

Model Provider

Not applicable; the failure occurs before any model is used.

Problem Description

The standalone tarko binary reports a version that does not match its published package version.

Reproduction on Windows 11 with Node.js 24.14.1 (the package requires Node.js >= 22.15.0):

> npm exec --yes --package=@tarko/[email protected] -- tarko --version
tarko/1.0.0 win32-x64 node-v24.14.1

Expected: the output reports tarko/0.3.0, matching @tarko/agent-cli 0.3.0.

Actual: the output reports tarko/1.0.0.

The same mismatch is present on current main (c2ad42e3eb9b27830db41a3e6f51ca7179d9b168). multimodal/tarko/agent-cli/bin/cli.js reads the package version but passes it as a top-level version option, while AgentCLI reads versionInfo.version and therefore keeps its default 1.0.0 value.

This can mislead users and automation that use --version to verify the installed CLI release.

Error Logs

No error is emitted; the incorrect version string is the observable failure shown above.