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

[beastoin]

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

[greptile-apps]

Greptile Summary

This is a routine, auto-generated changelog consolidation that promotes the single unreleased entry ("Added 'How did you hear about us?' onboarding step for K-factor tracking") into a new v0.11.207 release block dated 2026-04-01 and resets the unreleased array to empty. The change is minimal, follows the existing schema pattern used by all prior releases in desktop/CHANGELOG.json, and carries no functional code risk.

• Moved one changelog entry from unreleased → releases[0] under version 0.11.207
• Set release date to 2026-04-01, consistent with the immediately preceding releases (0.11.206, 0.11.205, etc.)
• unreleased array correctly cleared after consolidation
• No logic, build, or test files were modified

Confidence Score: 5/5

Safe to merge — documentation-only change with no functional impact.

Single-file changelog update that follows the established schema exactly. No code, tests, or configuration were modified. No issues identified.

No files require special attention.

Important Files Changed

Filename	Overview
desktop/CHANGELOG.json	Auto-generated changelog update that moves the "How did you hear about us?" onboarding entry from unreleased into a new v0.11.207 release entry dated 2026-04-01, and clears the unreleased array.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["unreleased[]<br/>(before PR)"] -->|"contains"| B["Added 'How did you hear<br/>about us?' onboarding step"]
    B -->|"auto-consolidated into"| C["releases[0]<br/>v0.11.207 — 2026-04-01"]
    A -->|"cleared to"| D["unreleased: []<br/>(after PR)"]
    C --> E["releases[1]<br/>v0.11.206"]
    E --> F["releases[2]<br/>v0.11.205"]
    F --> G["... older releases ..."]

Loading

_{Reviews (1): Last reviewed commit: "chore: consolidate changelog for v0.11.2..." | Re-trigger Greptile}