Correct 0.2 archive minimum-release mapping to the activation version 0.29.0

[eXamadeus]

Why

The held CLI activation changeset (#462) projects agent-facets@0.29.0, not 0.31.0. When the linked changeset group was decoupled (#464), agent-facets began versioning off its own 0.28.0 baseline plus one minor, rather than tracking protocol's higher version line.

The archive-format compatibility table still named 0.31.0 as the first 0.2-supporting release (set provisionally during the 16.4 readiness work). An older, pre-0.2 CLI encountering a 0.2 archive would be told to Update agent-facets to 0.31.0 or later — a version that skips the actual first 0.2 release.

Change

• MINIMUM_RELEASE_FOR_FORMAT['0.2']: 0.31.0 → 0.29.0
• Its unit test assertion updated to match.

Sequencing

This must land on main before #462 is versioned/released, so the shipped 0.29.0 binary carries the correct self-referential mapping. It is intentionally separate from the held changeset PR (#462), which stays changeset-only.

---

Note

Low Risk
Only changes upgrade guidance text for unsupported archive formats; no runtime behavior or security impact.

Overview
Corrects the archive format compatibility mapping so pre-0.2 CLIs are told to upgrade to 0.29.0 or later, not 0.31.0, when they hit a 0.2 archive.

Updates MINIMUM_RELEASE_FOR_FORMAT['0.2'] in archive-compatibility.ts and the matching unit test expectation.

^{Reviewed by Cursor Bugbot for commit 748ce77. Bugbot is set up for automated code reviews on this repo. Configure here.}

[changeset-bot]

⚠️ No Changeset found

Latest commit: 748ce77

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Warning

Review limit reached

@eXamadeus, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 28 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 69457fd8-4799-4dd0-a331-e0ce0fba24e5

📥 Commits

Reviewing files that changed from the base of the PR and between 2e67efd and 748ce77.

📒 Files selected for processing (2)

• packages/cli/src/util/__tests__/archive-compatibility.test.ts
• packages/cli/src/util/archive-compatibility.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch julian/fix-archive-compat-0-29

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[greptile-apps]

Greptile Summary

This PR corrects a single version string in the archive-format compatibility table, changing the minimum agent-facets release for the 0.2 format from 0.31.0 to 0.29.0. The fix is necessary to prevent pre-0.2 CLIs from being directed to a version that doesn't yet exist when the actual first 0.2-supporting release ships as 0.29.0.

• MINIMUM_RELEASE_FOR_FORMAT['0.2'] in archive-compatibility.ts is corrected from 0.31.0 → 0.29.0, matching the actual planned release baseline.
• The corresponding test assertion in archive-compatibility.test.ts is updated to match.

Confidence Score: 5/5

Safe to merge — both the implementation and its test are updated atomically, the change is a single version string correction with no logic changes.

The only change is correcting a version constant from 0.31.0 to 0.29.0 and updating the matching test assertion. The surrounding logic for the compatibility table is untouched, and the test suite exercises exactly the path that uses this constant.

No files require special attention.

_{Reviews (1): Last reviewed commit: "Correct 0.2 archive minimum-release mapp..." | Re-trigger Greptile}