Rebuild the 0.3.0 changelog from the code, and fix what blocks the release on main (#1001)

* Point the 0.3.0 release policy at the last migration, 0075_individual_check_ins

The policy was written before the personal edition added 0075_individual_check_ins, so the
publish workflow's --validate-policy step would refuse the release before building anything.

* Rebuild the changelog from the code before cutting a release

Entries added to Unreleased since the last release are claims. The release procedure now starts by
checking every change since the last tag in its diff and writing the notes from what the code
shows.

* Rebuild the 0.3.0 changelog from the code

Every change merged since v0.2.0, #998 included, was checked in its diff and in the code as it
stands, and Unreleased is written from that rather than from the entries added along the way.
Entries the code does not support are dropped, ones it contradicts are rewritten, fixes to things
that never shipped are folded into the feature they fixed, and changes nobody described now have
entries. The section is about 89,000 characters, well under GitHub's 125,000-character limit for a
release body, which the previous section would have crossed.

The redaction entry that merged after v0.2.0 but sat under the 0.2.0 heading moves to 0.3.0, and
the 0.1.0 Before upgrading count, changed to Eight by a merge, is Six again, matching its list.

* Build the release policy test's fixture from the committed policy's migrations

The fixture's last migration was written out as 0074_single_user_identity, the value the policy
held when the test was added, so moving the policy to 0075_individual_check_ins failed five tests
that check something else. The fixture now uses the migrations the committed policy names.

* Check the Recorder's release notes in everything written since 0.2.0

The test read only ## Unreleased, which is empty on the release commit once the release workflow
promotes it, so the checks that gate the publish would have failed. It also required 1.79.1,
which main never pinned: the runtime went from 1.77.0 to 1.83.0. It now reads the notes from
## Unreleased to ## 0.2.0 and requires the runtime version server/package.json pins.

* Add the harness conversation fixes to the 0.3.0 changelog, from their diffs

Claude Agent SDK, Agno, Google ADK, LangGraph and Mastra Bots now answer from the whole
conversation in their role. Checked against v0.2.0 and the code on main: the Antigravity fix is
folded into its entry because that harness is new in this release, the components entry no longer
says the Claude Agent SDK harness drops the standing role, and the macOS signing fixes change only
CI, so they have no entry.

* Point the 0.3.0 release policy at the last migration, 0077_channel_opening

Main added 0076_model_selection and 0077_channel_opening. Create release PR moves only the
policy's version within a release, so the database transition has to be right on main before the
first candidate is cut, or publishing refuses it.

* Add the changes merged since #1012 to the 0.3.0 changelog, from their diffs

The standalone Desktop with local Intelligence, signed installers at fixed links, Intelligence in
the Helm chart, the model picker, the always-ask refinements, the question drawer and Strands are
checked against v0.2.0 and the code on main. Sections they change are rewritten in place, and
links to Admin → Enterprise controls point at the pages that replaced it.

* State the Intelligence version the Helm chart bundles: 0.16.0-rc.4

#1033 moved the chart's Intelligence dependency from 0.16.0-rc.3 to 0.16.0-rc.4 (Chart.yaml and
Chart.lock); the changelog names it once.

* State the Intelligence release the chart and Desktop bundle: 0.16.0-rc.5

#1034 moved the chart's Intelligence dependency to 0.16.0-rc.5 and pinned Desktop's CLI to the
copilotkit preview built from Intelligence commit 256cc68, whose default local release is
0.16.0-rc.5 (checked in the published package). The Desktop entry no longer says the installer
carries whatever CLI was current.

Author: davidmckayv