Update CHANGELOG.json for v0.11.133 [skip ci]

[beastoin]

Auto-generated: consolidates unreleased entries into v0.11.133 and clears the unreleased array.

[greptile-apps]

Greptile Summary

This PR auto-generates a new v0.11.133 release entry in desktop/CHANGELOG.json, inserting it at the top of the releases array. The unreleased array was already empty prior to this change, so no unreleased entries were actually consolidated — the new entry carries only a generic "Bug fixes and improvements" description rather than meaningful changelog notes.

• New v0.11.133 release entry added with date 2026-03-18 and a single generic change string.
• The unreleased array is already [] in the base branch, so the PR description's claim of "consolidates unreleased entries" does not match the actual diff.
• Multiple consecutive releases (0.11.127 through 0.11.133) share the same date (2026-03-18) and identical generic change description, suggesting the auto-generation pipeline is not capturing granular changelog entries.

Confidence Score: 4/5

• This PR is safe to merge — it is a pure JSON data file update with no runtime impact.
• The change is a single JSON entry addition to a changelog file. It carries no code logic, no security surface, and no side effects. The only concern is the auto-generation pipeline producing a generic "Bug fixes and improvements" message when the unreleased array was already empty, which suggests the tooling may not be capturing actual change descriptions. This is a process quality issue, not a merge blocker.
• No files require special attention — the change is limited to a data-only JSON changelog file.

Important Files Changed

Filename	Overview
desktop/CHANGELOG.json	Adds v0.11.133 release entry dated 2026-03-18 with a generic "Bug fixes and improvements" change description; unreleased array was already empty so no entries were actually consolidated.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Auto-generate script triggered] --> B{Unreleased entries exist?}
    B -- Yes --> C[Consolidate entries into new version]
    B -- No --> D[Create version with generic message]
    C --> E[Add release to CHANGELOG.json]
    D --> E
    E --> F[Clear unreleased array]
    F --> G[Commit with skip-ci flag]

Loading

_{Last reviewed commit: "chore: consolidate c..."}

[greptile-apps]

Unreleased array was already empty — no entries were consolidated

The PR description states this commit "consolidates unreleased entries into v0.11.133 and clears the unreleased array," but unreleased is already [] in the base branch. The new release entry therefore carries only the placeholder "Bug fixes and improvements" string rather than actual change notes.

Additionally, versions 0.11.127 through 0.11.133 all share the same date (2026-03-18) and the same generic description, suggesting that the auto-generation script is not populating changelog entries before cutting a release. Consider ensuring that meaningful change descriptions are written to the unreleased array during development so that auto-generated changelogs contain useful information for end users.