docs: finalize CHANGELOG.md for v2.0.0 release

[alfredo1996]

Summary

• Update CHANGELOG header from [Unreleased] — v1.0.0 Community Launch to [2.0.0] — 2026-05-02
• Add missing entries for PRs feat: NeoDash migration P0+P1 — settings mapping + conversion notes #626, refactor(app): decompose widget-editor-modal into sub-components (#573) #627, test(app): add widget-editor sub-component tests (#578) #628, fix(build): resolve pg/tls client bundle error breaking E2E tests #629, chore(demo): add circle-packing and choropleth to chart gallery (#570) #630, fix(types): resolve pre-existing type errors on release/2.0 #632, feat(connectors): database selector + per-card write toggle (#568) #633
• Add release comparison link at the bottom

Closes #637

🤖 Generated with Claude Code

Summary by CodeRabbit

• New Features

  • Database selector override capability
  • Per-card write toggle functionality
  • Circle packing and choropleth gallery demos
  • NeoDash migration documentation

• Changed

  • Business logic extracted to reusable library files
  • Widget editor sub-component architecture improved

• Bug Fixes

  • PostgreSQL/TLS client bundle errors resolved
  • Type errors corrected on release branch

[coderabbitai]

Walkthrough

The changelog transitions from an "Unreleased — v1.0.0 Community Launch" placeholder to a finalized "## [2.0.0] — 2026-05-02" release section. New entries document added features (database selector, per-card write toggle, gallery demos, NeoDash migration notes, widget editor tests), changes (license terms, state sync, business logic extraction, widget decomposition), and fixes (pg/tls bundle errors, type errors), with a corresponding release link reference appended.

Changes

v2.0.0 Release Documentation

Layer / File(s)	Summary
Release Header & Metadata CHANGELOG.md (lines 7–8, 139–140)	Converts "Unreleased" header to [2.0.0] — 2026-05-02 and appends the corresponding comparison link reference at the bottom.
Added Features CHANGELOG.md (lines 19–29)	Documents new functionality: database selector override, per-card write toggle, Circle packing/choropleth gallery demos, NeoDash migration tooling, and widget editor sub-component unit tests.
Changed Behavior CHANGELOG.md (lines 30–35)	Lists updates to Elastic License 2.0 AI training restriction, widget editor state synchronization removal, extraction of business logic into lib/ files, and widget editor sub-component decomposition.
Fixed Issues CHANGELOG.md (lines 45–46)	Adds E2E test-blocking pg/tls client bundle resolution and pre-existing type error notes on release/2.0 branch.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• chore: CHANGELOG and release automation workflow (#215) #228: Modifies CHANGELOG.md for release/versioning changes as part of the same release cycle.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the primary change: finalizing the CHANGELOG.md file for v2.0.0 release, which matches the changeset.
Linked Issues check	✅ Passed	The PR fulfills all acceptance criteria from issue #637: renamed to [2.0.0] with release date, added missing changelog entries from linked PRs, includes major features (database selector, widget decomposition, chart gallery), follows Keep a Changelog format, and adds comparison links.
Out of Scope Changes check	✅ Passed	All changes are directly related to CHANGELOG.md updates for v2.0.0 release as specified in issue #637; no out-of-scope modifications detected.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/issue-637-changelog-v2

---

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

_{Review rate limit: 0/1 reviews remaining, refill in 60 minutes.}

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

[coderabbitai]

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@CHANGELOG.md`:
- Around line 139-140: Update the link target for the markdown reference
"[2.0.0]" in CHANGELOG.md so it points to the GitHub comparison URL for the
range that ends at the v2.0.0 tag (i.e., use a /compare/<previous-tag>...v2.0.0
style URL) instead of the current release tag page; locate the "[2.0.0]"
reference and replace its href with the proper compare-range URL that spans from
the prior version tag to v2.0.0.
- Line 46: The changelog entry under the "### Fixed" section currently reads
like a status note ("Pre-existing type errors on release/2.0 branch (`#632`)");
update that line to explicitly state the resolution, e.g. change it to a
past-tense fix description such as "Resolved pre-existing type errors on
release/2.0 branch (`#632`)", so it clearly reads as an item in the Fixed list
rather than a status note.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 90a85507-a548-4dbc-a916-0a766b55cdf6

📥 Commits

Reviewing files that changed from the base of the PR and between f42125e and 2161d60.

📒 Files selected for processing (1)

• CHANGELOG.md

[coderabbitai]

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Clarify the fix wording on Line 46.
In a ### Fixed section, this line reads like a status note rather than a resolved change.

Proposed wording tweak

-- Pre-existing type errors on release/2.0 branch (`#632`)
+- Resolved pre-existing type errors on release/2.0 branch (`#632`)

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	- Pre-existing type errors on release/2.0 branch (#632)
	- Resolved pre-existing type errors on release/2.0 branch (`#632`)

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@CHANGELOG.md` at line 46, The changelog entry under the "### Fixed" section
currently reads like a status note ("Pre-existing type errors on release/2.0
branch (`#632`)"); update that line to explicitly state the resolution, e.g.
change it to a past-tense fix description such as "Resolved pre-existing type
errors on release/2.0 branch (`#632`)", so it clearly reads as an item in the
Fixed list rather than a status note.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Use a comparison URL for [2.0.0] on Line 140.
The current link targets the release tag page, not a version comparison. Keep a Changelog-style links should point to compare ranges.

Proposed link fix

-[2.0.0]: https://github.com/alfredo1996/neoboard/releases/tag/v2.0.0
+[2.0.0]: https://github.com/alfredo1996/neoboard/compare/v0.9.1...v2.0.0

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	[2.0.0]: https://github.com/alfredo1996/neoboard/releases/tag/v2.0.0
	[2.0.0]: https://github.com/alfredo1996/neoboard/compare/v0.9.1...v2.0.0

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@CHANGELOG.md` around lines 139 - 140, Update the link target for the markdown
reference "[2.0.0]" in CHANGELOG.md so it points to the GitHub comparison URL
for the range that ends at the v2.0.0 tag (i.e., use a
/compare/<previous-tag>...v2.0.0 style URL) instead of the current release tag
page; locate the "[2.0.0]" reference and replace its href with the proper
compare-range URL that spans from the prior version tag to v2.0.0.