chore(main): release 0.2.0

[e2b-generated-code-auto-fixer]

🤖 I have created a release beep boop

0.2.0 (2026-09-16)

Features

• container: self-hostable container image with runtime configuration (#528) (f7b85de)

---

This PR was generated with Release Please. See documentation.

[claude]

LGTM, straightforward automated release version bump with no code changes.

What was reviewed: the version bump in .release-please-manifest.json and package.json (0.1.0 to 0.2.0), and the new CHANGELOG.md entry documenting the container feature (#528). Confirmed no application source files are touched by this diff.

Extended reasoning...

Overview

This is a release-please automated release PR. The diff touches exactly three files: .release-please-manifest.json and package.json (both bump the version string from 0.1.0 to 0.2.0), and a new CHANGELOG.md file documenting a single "container" feature entry referencing PR #528. No application source code, configuration, dependencies, or build scripts changed.

Security risks

None. There is no code execution path affected — only a version string and a markdown changelog file. The pre-existing merge-conflict-marker-looking script key ("<<<<<<< Next.js") in package.json is unrelated to this diff (it exists in both the base and head versions, confirmed by the diff only touching the version line in that file) and is out of scope for this review.

Level of scrutiny

Minimal scrutiny is appropriate here: this is a mechanical, bot-generated release commit of the kind release-please produces routinely, with no ambiguity in intent and no security- or logic-sensitive code touched.

Other factors

No CLAUDE.md conventions are implicated (no code comments in any changed file). No prior review conversation or outstanding objections were found in the timeline. The bug hunter reported no findings, consistent with the trivial nature of the change.

[e2b-generated-code-auto-fixer]

🤖 Created releases:

• v0.2.0

🌻