docs: promote CHANGELOG to v0.1.0 (closes #92)

[bradjin8]

Summary

• Promote CHANGELOG.md [Unreleased] → [0.1.0] - 2026-06-04 and add an empty [Unreleased] section for post-release work
• Fix changelog structure after Lazy-load chat histories and serve lightweight list summaries (avoid full global index scan on every page load) #84: initial ship items (Web UI, export formats, CLI, packaging, etc.) were incorrectly nested under ### Deprecated; restore proper ### Added / ### Changed / ### Deprecated / ### Fixed grouping
• Add #87 / #89 resolver test coverage under ### Added (shipped on master, previously missing from the changelog)
• Update Keep a Changelog compare links: [Unreleased] → v0.1.0...HEAD, [0.1.0] → release tag

Closes #92

Motivation

Release infrastructure was already in place (pyproject.toml version = "0.1.0", README semver policy, docs/API_DEPRECATION.md) but no tagged release existed. Consumers could not pin to a known-good state. Remaining work is mechanical: finalize the changelog entry, merge, then tag and publish the GitHub release.

Verified (no code changes in this PR)

Item	Status
pyproject.toml version = "0.1.0"	Already set — unchanged
docs/API_DEPRECATION.md	Already documents deprecation lifecycle — unchanged
README Versioning section	Already documents pre-1.0 semver — unchanged

Post-merge (maintainer)

Do not tag from the PR branch. After this PR merges to master:

git checkout master && git pull
git tag -a v0.1.0 -m "v0.1.0"
git push origin v0.1.0
gh release create v0.1.0 --title "v0.1.0" --notes-file -

<!-- This is an auto-generated comment: release notes by coderabbit.ai -->

## Summary by CodeRabbit

* **Documentation**
  * Updated CHANGELOG with initial v0.1.0 release entry
  * Reorganized feature and change section listings
  * Updated deprecated section guidance regarding UI usage patterns
  * Refreshed version reference links

<!-- end of auto-generated comment: release notes by coderabbit.ai -->

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 9d315882-7099-4c3f-9c29-07f20845437f

📥 Commits

Reviewing files that changed from the base of the PR and between 08667a5 and 501e0d2.

📒 Files selected for processing (1)

• CHANGELOG.md

---

📝 Walkthrough

Walkthrough

CHANGELOG.md is updated to promote the [Unreleased] section to a first stable release [0.1.0] dated 2026-06-04, documenting Web UI, export formats, CLI features, desktop packaging, type-safe models, infrastructure, and deprecation guidance. Version reference links are adjusted to reflect the new release boundary.

Changes

Release v0.1.0 Documentation

Layer / File(s)	Summary
Release v0.1.0 documentation CHANGELOG.md	Version header ## [0.1.0] - 2026-06-04 is added. ### Added section lists UI, export capabilities (web and CLI), agent sessions, desktop packaging, typed models, CI infrastructure, optional exclusions, full-text search, test coverage, and utility improvements. ### Changed section documents shared validation helper extraction and mypy strict-optional enablement. ### Deprecated section records guidance to use ?summary=1 for lazy tab fetching over direct workspace tab loading.
Version reference link updates CHANGELOG.md	Markdown reference link for [Unreleased] is changed from commits/HEAD to compare/v0.1.0...HEAD, and [0.1.0] release reference is added.

🎯 1 (Trivial) | ⏱️ ~3 minutes

Suggested reviewers

• timon0305
• wpak-ai

🐰 A version is born, 0.1.0 takes the stage,
Features logged, changes penned upon the page,
Deprecated paths now clearly marked with care,
The first release flies through the April air! ✨

🚥 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 'docs: promote CHANGELOG to v0.1.0' clearly and directly describes the main change, which is promoting the CHANGELOG for version 0.1.0.
Linked Issues check	✅ Passed	The PR fulfills the core coding requirements from #92: promoting [Unreleased] to [0.1.0], reorganizing sections, and updating comparison links. Note: git tagging and GitHub release creation are post-merge maintainer tasks outside code review scope.
Out of Scope Changes check	✅ Passed	All changes are directly within scope—only CHANGELOG.md was modified to promote version and reorganize sections, with no unrelated alterations.
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 doc/release-v0.1.0

---

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

[clean6378-max-it]

Review: approve — changelog-only; no code findings.

This PR correctly completes the changelog portion of #92: promotes [Unreleased] → [0.1.0] - 2026-06-04, fixes the malformed section layout on master, and updates footer compare/release links. pyproject.toml is already 0.1.0; no code changes needed.

Note for merge: this does not finish #92 by itself. After merge to master, still required on the merge commit:

git tag v0.1.0 && git push origin v0.1.0
gh release create v0.1.0 --title "v0.1.0" --notes-file CHANGELOG.md (or equivalent)
Until then, the [0.1.0] release link in CHANGELOG.md will 404 — expected briefly; avoid leaving master in that state for long.

Tag order: merge this PR first, then tag master. Do not tag before merge (tagged commit would lack the promoted changelog).

[bradjin8]

Review: approve — changelog-only; no code findings.

This PR correctly completes the changelog portion of #92: promotes [Unreleased] → [0.1.0] - 2026-06-04, fixes the malformed section layout on master, and updates footer compare/release links. pyproject.toml is already 0.1.0; no code changes needed.

Note for merge: this does not finish #92 by itself. After merge to master, still required on the merge commit:

git tag v0.1.0 && git push origin v0.1.0 gh release create v0.1.0 --title "v0.1.0" --notes-file CHANGELOG.md (or equivalent) Until then, the [0.1.0] release link in CHANGELOG.md will 404 — expected briefly; avoid leaving master in that state for long.

Tag order: merge this PR first, then tag master. Do not tag before merge (tagged commit would lack the promoted changelog).

Yes, I'll do it once all the pending PRs are merged.