[Mikola Lysenko (mikolalysenko)]

What this is

The CHANGELOG.md entries for #2052, written into the existing ## [5.1.0] section at the owner's request (5.1.0 is stamped on main and not tagged yet).

They are on a release/v* branch because AGENTS.md lets only a release branch edit CHANGELOG.md. The same text was first pushed as part of #2052; a repository routine restored the file there, as the rule says to, so the notes travel here instead.

Merge after #2052. The entries describe code that lands there. Nothing but CHANGELOG.md changes in this PR.

What it adds

82 entries inside ## [5.1.0], in its existing headings and ecosystem groups (Cargo and Composer groups are new under ### Changed); no existing entry, heading or date is touched, and scripts/release-lint.sh passes.

Heading	Entries
Added	4
Changed	24
Fixed	48
Performance	5
Maintenance	1

Each entry was written from the commit messages and the CLI_CONTRACT.md diff of #2052, cites (#2052), and states in full any exit code it changes, any statement vex no longer makes, any file the tool now writes and any new refusal, so the changelog is also the list to review for compatibility.

---

Generated by Claude Code

[cursor]

PR Summary

Low Risk
Documentation-only change to CHANGELOG.md; release risk comes from the described #2052 behavior, not from this PR’s diff.

Overview
Documents 5.1.0 in CHANGELOG.md only—no runtime code changes. The PR fills in 82 new bullets under the existing ## [5.1.0] section, grouped under Added, Changed, Fixed, Performance, and Maintenance, and adds ecosystem groupings (e.g. Cargo/Composer under Changed).

The text captures behavioral and compatibility notes from #2052: hosted Ruby gem install refresh, monorepo-wide scan/list/rollback, stricter patch API error handling, manifest/blob/sidecar failures, child-process env stripping, ecosystem-specific vex and hosted-mode rules, vendor ledger safety, transactional hosted/agent writes, telemetry/help UX, and related performance wins. Entries cite (#2052) and spell out exit codes, new warnings, and attestations where they change.

Merge after #2052 so the changelog matches landed code; release-lint is expected to pass.

^{Reviewed by Cursor Bugbot for commit a3715f4. Configure here.}

[Mikola Lysenko (mikolalysenko)]

Ready for review (burn-down agent)

• Head: a3715f4c941b004dc46010c0c5bc03305cb9f13e
• CI: 31/31 checks passed on this head (19 skipped). No main-wide failures.
• Mergeable: yes. This is a release PR on a release/v* branch, so changing CHANGELOG.md is allowed.
• Bugbot: reviewed this head with no findings and no open threads.
• For reviewers: only CHANGELOG.md changes (82 entries under [5.1.0]). Merge after Fix the defects found by the 5.1.0 full review: do no harm, Bundler hosted mode, VEX, monorepo scans #2052.

---

Generated by Claude Code

[Mikola Lysenko (mikolalysenko)]

Final review brief: #2053

What it does: adds 82 CHANGELOG.md entries for #2052 inside the existing ## [5.1.0] section. 5.1.0 is stamped on main but not tagged yet. Nothing else changes. The entries are on a release/v* branch because AGENTS.md allows changelog edits only there.

Risk: low. It is documentation only. The one thing that matters is order: merge it after #2052, because the entries describe code that lands there.

Look here:

• Changed: exit-code and refusal changes users will notice, e.g. repair --offline exits 1 and redirect_workspace_lockfile_elsewhere
• Fixed (48 entries)
• Added: hosted gem install refresh

Verified:

• scripts/release-lint.sh 5.1.0 passes on the head.
• The branch is up to date with main, and CHANGELOG.md is the only file changed.
• All 62 warning, refusal and error codes the new entries name, and every --flag and SOCKET_* variable they mention, exist in Fix the defects found by the 5.1.0 full review: do no harm, Bundler hosted mode, VEX, monorepo scans #2052's code.
• CI is 31/31 green on a3715f4, ci-ok and clippy included. Bugbot summary: low risk.

Open questions: #2052 got two more review fixes in f16ca61: the gem \ continuation, and a bare rollback that went below --cwd when the mode was ambiguous. These notes don't mention them. The release agent can add them, or you can leave them out as fixes to unreleased code.

Auto-merge is not armed yet: I'll arm it once #2052 is merged or in the merge queue, so an approval here can't merge it first.

---

Generated by Claude Code