claude-code-chat-browser: take `app.py` off `0.2.0.dev0` and cut the v0.2.0 tag and Release

[clean6378-max-it]

Sprint Item

is-12 of 13 — Task — Thursday PR 2 of 3 (the release)

Block Relations

Blocked by	is-11 (hard) — the Release notes are copied from the [0.2.0] changelog section
Blocks	— (though is-13 reads better if written after this lands, since it then records what actually happened)
Repo/day	Independent of is-1–is-10

Calendar Day

Thursday, July 30, 2026 (PR 2 of 3)

Planned Effort

1 story point (Task) — sprint item is-12

Problem

app.py declares __version__ = "0.2.0.dev0" (line 3), signalling an unreleased trunk state.

The only existing tag is v0.1.0 from 2026-06-18 (CHANGELOG.md line 9). The Week 30 concurrency, parity and documentation work is merged on master at HEAD, but no v0.2.0 tag or GitHub Release exists.

Goal

The repository's v0.2.0 Release — tag plus notes, since there is no artifact to publish.

Scope

Part A — version bump

• Change app.py __version__ from "0.2.0.dev0" to "0.2.0".
• It is the sole version declaration — there is no pyproject.toml version field.

Part B — catch stale references

• After bumping, grep the repository for 0.2.0.dev0 to catch anything left behind.

Part C — tag and Release

• Push an annotated tag v0.2.0 to origin.
• Publish a GitHub Release with notes from the [0.2.0] CHANGELOG section.

Part D — what this Release is not

There is no npm or PyPI artifact: this is a source-only Flask app, so the Release is tag plus notes. Do not add a publish workflow for it this week.

Out of scope

• MCP server integration — that is the Week 32 feature item (5 pt).

Acceptance Criteria

• app.py __version__ is changed from "0.2.0.dev0" to "0.2.0".
• No stale 0.2.0.dev0 references remain anywhere in the repository.
• An annotated git tag v0.2.0 is pushed to origin.
• A GitHub Release for v0.2.0 is published with notes from the [0.2.0] CHANGELOG section.
• CI green on the release commit.
• PR approved by at least 1 reviewer.

Verification

# from the claude-code-chat-browser checkout root
git grep -n "0.2.0.dev0"
git tag -n v0.2.0
gh release view v0.2.0

• git grep for 0.2.0.dev0 returns nothing.
• The GitHub Release exists as a Release object, not a bare tag.
• The Release notes match the [0.2.0] CHANGELOG section.

Close-out gate (Chen owns this repository)

Column	Status
No Critical/High/Medium-High open	Nothing open — this repo had no surviving issues at any severity
Release cut	This issue — v0.2.0
Actions green	CI green on the release commit
No new Critical/High found Thursday	Fresh re-scan required Thursday — re-run the review tooling against Thursday's HEAD

No owner after Thursday. That is why item is-13 (RELEASING.md) is on the same day: whoever picks this repository up next needs the release ceremony written down.

References

• Sprint: Week 31 (Jul 27–31, 2026) — Chen item is-12 (1 pt, Task)
• Week 31 weekly plan — claude-code-chat-browser
• Week 31 issue descriptions — claude-code-chat-browser, v0.2.0 release
• Eval finding: n/a
• Files: app.py:3; CHANGELOG.md:9; docs/architecture.md
• Companion: Thursday is-11 [0.2.0] changelog, is-13 RELEASING.md
• Success definition: "Documented lock order backed by concurrency tests, diagnosable failures, deployment doc" — v0.2.0