Repair Zoo Code changelog and Changesets release workflow #33

Context

During the Zoo Code marketplace publishing setup, we started a fresh Zoo Code changelog at the top of CHANGELOG.md and preserved the upstream Roo Code history under an archive section.

The repo already has a Changesets-based release flow (pnpm changeset:version), but the current workspace is not fully aligned with it:

• .changeset/config.json still needed package identity cleanup from the old extension package name.
• pnpm changeset status reported changed packages without changesets.
• It also reported an existing workspace dependency mismatch for @roo-code/web-roo-code depending on @roo-code/types as ^1.108.0 while the current package version is 0.0.1.
• CHANGELOG.md and src/CHANGELOG.md can drift unless the release flow is made authoritative and documented.

Goal

Make changelog and version management boring and explicit for Zoo Code stable releases.

Suggested scope

• Decide whether Zoo Code should use Keep a Changelog manually, Changesets-generated changelogs, or a hybrid policy.
• Make pnpm changeset status clean on the default branch.
• Ensure pnpm changeset:version is the single documented way to bump stable release versions, if Changesets remains the chosen tool.
• Keep active Zoo Code release notes separate from archived Roo Code history.
• Ensure CHANGELOG.md and src/CHANGELOG.md are synchronized intentionally.
• Document how prerelease/nightly versions should be handled, especially because VS Code Marketplace supports prerelease channels but Open VSX does not.

Acceptance criteria

• A contributor can follow docs/scripts to add a release note and bump a stable version without hand-editing multiple files.
• pnpm changeset status exits cleanly when no release notes are missing.
• The publish workflow can extract release notes for the current stable version reliably.
• Archived Roo Code history remains preserved but is not confused with active Zoo Code releases.