[tonytonycoder11]

The release commit for 0.2.0, which holds all of Tier 2 (M15 to M22 and M24) and the pub.dev work (M34 to M36). Merging it tags and publishes nothing: the release workflow starts from a tag, and pushes to main only run CI.

The four packages go to 0.2.0 together, the three adapters now ask for flutwire ^0.2.0, and flutwireVersion and the podspec follow, which version_test checks. The entries under Unreleased are now under [0.2.0] - 2026-10-24, in the order of their milestones, with a fresh empty Unreleased above and the compare links moved on. Each package has its own changelog entry, which is what pub.dev shows. The README says what shipped, names 1.0.0 as next, and lists the new source directories and the interception component in its architecture section.

I checked every number in the notes against the code: ten slowest calls, the latest hundred in the timeline, a pause of two minutes, 1000 messages and a megabyte per conversation, four packages, eight screenshots and four screens in the tour. That caught one wrong claim, which is fixed. The media entry said two diagrams, but the repository has one diagram and a tour of four screens, and only the root README shows the diagram. Apart from that entry, every bullet is word for word what was under Unreleased, and the 0.1.0 section is untouched.

Checked locally on this commit: format, analyze and the four suites; the four flutter pub publish --dry-runs with 0 warnings; the lowest versions of each package; the example for Android, the iOS simulator, macOS and the web; the repository audit, which says "At standard"; and the release workflow's own awk run on the new changelog, which gives a 26 line body from "### Added" to the last Internal entry.

What is not in this PR, and waits for the release itself: the tag v0.2.0 on the merge commit, which starts the workflow (CI, flutwire, the three adapters once the core can be resolved, the GitHub Release from the changelog, the attestation and the storage records); the board, where the items that target 0.2.0 go to Shipped and the Tier 2 milestone closes; the topics, which are re-ranked at each minor release; and a new status update. It will be the first run of the automated publishing, so each of the four packages needs Automated publishing on pub.dev with the tag pattern v{{version}}, which can only be checked there.

The date in the changelog heading and in the anchors of the four package changelogs is the day this was written. If the tag goes out on another day, those five places change.

Targets 0.2.0, Tier 2.

[trueup-by-nacode-studios]

This pull request adds no capability the code did not already have.

_{12 files read · 4166 ms · against 7644e94 · engine 1.4.1}