[Bug] packages/agent-host states 0.14.6-rc.4, so the release preflight fails on main

[dajiaohuang]

What happened?

packages/agent-host/package.json states 0.14.6-rc.4 while every other version surface states 0.14.6, so the release preflight that guards tagging fails on main.

packages/agent-host was added by c9f7cd86 (feat(agent-host): add the headless Agent Host module (R1)) already carrying the stale 0.14.6-rc.4 version, and it was not advanced by the later chore(release) bumps for v0.14.6-rc.5, v0.14.6-rc.6, or v0.14.6.

Steps to reproduce

git clone https://github.com/vastsa/PI-Desktop && cd PI-Desktop
node scripts/check-release-docs.mjs

Expected behavior

Release documentation is aligned with 0.14.6 (0.14.x line).

Exit code 0, as the rule in release-runbook 4.1 requires.

Actual behavior

Release documentation is not aligned with 0.14.6:
  - packages\agent-host\package.json: version is 0.14.6-rc.4, expected 0.14.6

Exit code 1. Reproduced at 6e6d710e517b567d82dc28f8b01e19f7f81eaf64. The comparison is a plain string equality on each surface, so it is not platform-specific.

Impact

scripts/release.mjs runs check-release-docs.mjs after bumping and refuses to tag while any surface disagrees, and release-runbook 4.1 requires package.json, apps/*/package.json, packages/*/package.json, and docs/package.json to state the same version. Until this is aligned, the documented pre-tag verification is red on main.

This is not currently a release blocker: release.mjs bumps every directory under packages/, so the next chore(release) resets the field. It is a broken invariant and a failing gate in the meantime.

App version

0.14.6

Operating system

Windows

Extra environment

Reproduced on main at 6e6d710e. Any platform reproduces it, because the check only compares version strings.

Proposed fix

Set packages/agent-host/package.json to 0.14.6. The package is "private": true and is consumed as workspace:*, so its version carries no resolution weight: no dependency graph changes, and pnpm-lock.yaml needs no update (pnpm install --frozen-lockfile still passes). A pull request follows.

[vastsa]

Confirmed on current main: packages/agent-host/package.json is still 0.14.6-rc.4 while APP_VERSION / other surfaces are 0.14.6. Open fix: #205.

[vastsa]

Verified on origin/main @ b48c11d1 — the version-surface mismatch is gone.

• packages/agent-host/package.json now reads 0.14.8-native.1, identical to the root package.json, apps/desktop/package.json, docs/package.json, the other workspace packages, Cargo.toml [workspace.package], and APP_VERSION (packages/shared/src/protocol.ts:5).
• The stale 0.14.6-rc.4 was replaced by 42d397eb (chore(release): v0.14.7-beta.1) and advanced again by later release bumps. PR fix(release): align the agent-host package version with 0.14.6 #205 was closed unmerged and was not the fix.
• node scripts/check-release-docs.mjs no longer reports any version-surface mismatch. It does still exit 1 on current main, but only because packages/shared/src/changelog*.ts (8 locales) and changelog.test.ts have no entry for 0.14.8-native.1 — that is the documented prerelease behaviour (.github/workflows/ci.yml intentionally keeps check:release-docs out of CI because it fails on rc/prerelease versions) and is unrelated to this report.

Closing as fixed by the release bumps. The changelog-on-prerelease gap is a separate concern and should get its own issue if it is worth tracking.