[jerelvelarde]

The problem

## Unreleased is the release notes, and docs/releasing.md trusts none of it as written: before a cut, every change since the last tag is checked against its diff and the section is rewritten from what the code shows. 1.0.0 is cut by running Create release PR with major, which promotes ## Unreleased to ## 1.0.0 exactly as it stands. Since v0.3.1, fifteen PRs have landed, and #1065 (the kite) is about to.

As written, four of those fifteen had no entry. Several over- or understated what changes for an existing deployment. And one, #1055, renames a tenant id in a way that stops an existing personal edition from starting, with nothing in the notes to say so.

The approach

This rebuilds ## Unreleased the way #1045 did for 0.3.1. Every change since v0.3.1 (47cc61d and before), plus #1065, is checked against its diff. An entry stays only where the code proves it, gets rewritten where it misstates the change, and is added where nothing mentioned one. #1049, #1052, #1053 and #1057 gain entries. #1025 changes only the README, so it has none. #1061 and #1062 become one section. #1047 splits into the Intelligence rc.7 changes and the CopilotKit runtime changes.

Before upgrading comes first, as in 0.3.1. There are no migrations: the newest file in server/drizzle/ is still 0077_channel_opening, and #1056's Learning queue Job runs in the bundled Intelligence's own PostgreSQL, which the notes now say. Six things change for an existing deployment. OpenBot Desktop becomes the personal edition on its next Start, with what that turns off, and the tenant id moves (both #1055). Every Bot gets every skill once in the personal edition (#1032). A Helm upgrade replaces the bundled Intelligence's PostgreSQL pod, and the Learning queue Job's longer deadline is lost under --reuse-values (#1047, #1056). The Learning model moves to config.learning.model (#1051). With telemetry on, the new CopilotKit runtime forwards each run's analytics context (#1047).

The tenant id is the one to read before cutting. #1055 changed examples/personal/brand.yaml's tenant id from personal to openbot, so a Desktop install keeps its Bots when it switches packages. A personal edition already running on examples/personal still has the Personal Assistant owned by the package under the old id. On this release the package sync refuses to adopt it, and the server stops at start with Tenant package agent "personal-assistant" collides with a user-created agent. This was reproduced on a scratch Postgres by syncing v0.3.1's package and then this one. The notes give the one-line UPDATE that renames the package row; it was tested. Desktop, moving from fintech to personal, syncs fine. Fixing this in code before the cut is the better outcome, and if that happens, that bullet should go.

Only CHANGELOG.md changes. package.json, the chart and the Cargo files are left alone: the release action writes them, and it refuses to run when package.json names a version that was never tagged.

What is not covered

• No recording: this changes notes, not the product.
• Intelligence rc.7's fixes come from the descriptions of Intelligence #2250, #2252 and #2254, not from code in this repo. That rc.5 to rc.7 replaces the PostgreSQL pod follows the chart README and Give Learning's queue migration time to wait out Intelligence's database restart #1056; there was no Helm here to watch it happen.
• The CopilotKit canary's Stop and lock behaviour was read in the installed runtime, not run.
• The app and Desktop weren't run for this. Wording was checked against the source.
• A database holding both an openbot and a personal package row would hit the unique constraint on the rename. The notes don't cover that case.
• release-policy.json isn't here. As 8d0ea17 did for 0.3.1, it's a commit on the release PR the action opens; the draft is under Merge notes.

Verification

• bun run format:check: clean.
• bun test scripts/release-prepare.test.ts scripts/release-version.test.ts: 29 pass, 0 fail.
• bun scripts/release-prepare.ts major stable on a scratch copy of the release files printed version=1.0.0 and base=main. It promoted Unreleased to ## 1.0.0 under a fresh empty Unreleased, and moved package.json, the chart's appVersion and both Cargo files to 1.0.0.
• The draft policy below, in a scratch clone with tags: VERSION=v1.0.0 bun scripts/release-manifest.ts --validate-policy describes v1.0.0, and tests/release-policy.test.ts passes 18 of 18.

Merge notes

This is stacked on #1065. Its own change is the last commit: compare. Merge #1065 first. Anything else that lands on main before the cut needs its entry checked the same way.

After this merges, run Create release PR from main with bump: major and kind: stable. Then add this release-policy.json to the PR the action opens. It lists both v0.3.0 and v0.3.1, because Desktop refuses to move an install whose release isn't listed, and a Mac app still on 0.3.0 goes straight to Latest. Both releases end at 0077_channel_opening.

{
  "$schema": "./shared/release-policy.schema.json",
  "version": "v1.0.0",
  "compatibility": {
    "launcherApi": 1,
    "configSchema": 1,
    "extensionApi": 1,
    "database": {
      "from": ["0077_channel_opening"],
      "to": "0077_channel_opening",
      "rollbackCompatible": false
    },
    "intelligenceCapabilities": []
  },
  "upgrade": {
    "fromVersions": ["v0.3.0", "v0.3.1"],
    "requiresDowntime": true,
    "recovery": "restore-backup"
  }
}

Changelog

• This is the changelog.