[qingyun-wu]

What changed, and why

Release proposal for engine v0.13.0. The last engine release is v0.12.0 (2026-08-20). The sparrow-v* tags in this repo belong to the ag2-sparrow package line, so the bump is counted from v* tags only.

This PR contains release artifacts only, no product code:

• CHANGELOG.md: a curated [v0.13.0] section (headline, Added, Fixed, Security, Changed), plus the old [Unreleased] feat(codex): redeem earned reset near weekly exhaustion #4829 entry folded into it. Also adds stub [v0.12.0] and [v0.11.0] sections that link to their GitHub releases, since neither version had a section here.
• CHANGELOG-PENDING.md: its entries are now in the v0.13.0 section, so the file is reset to an empty template.

Proposed version: v0.13.0 (MINOR). The range adds many user-visible capabilities. No commit is marked breaking (!: / BREAKING CHANGE: 0). Changes that need action on some installs either add something or still read the old form, which a 0.x MINOR allows. The upgrade action is listed under Changed.

Candidate SHA: 623c927afb6e3b9bd0b8faf19fb89f0f41fe392d (main at #5979). It contains the s.space connection work (#5966 to #5973, #5977 to #5983, #5996) and the terminal-run move warning (#5971).

Where to look first

CHANGELOG.md, the [v0.13.0] section. In particular, check the "Changed" upgrade-action bullets.

Feature/documentation consistency

The canonical docs for the headline are already current on main, including the terminal-run move section in docs/connections.md (#5971). A public docs-site page for the move is in a separate PR on the docs site. docs/README.md navigation is unchanged.

Release gates (candidate 623c927)

The candidate is current origin/main, 623c927afb6e3b9bd0b8faf19fb89f0f41fe392d. The [v0.13.0] section now lists everything merged since the first cut (#5971, #5976 to #5983, #5990, #5992, #5996, #5998) and counts 1201 PRs. The retired room-doc spelling is gone from CHANGELOG.md.

Gate	Command	Result
Docs audit	python3 skills/release/scripts/docs_audit.py	docs-audit: PASS (56 indexed docs; 59 Markdown files checked), exit 0, at the candidate and on this branch
Retired-spelling lint	python3 scripts/lint-old-collab-literals.py; tests/lint-old-collab-literals.test.py	ok (0 occurrences in 0 files); test exit 0
1. CI green at the candidate	gh api repos/sonichi/sutando/commits/623c927af…/check-runs	22 success, 1 skipped; rest were still queued when read, re-checked below
2. Fresh-clone health check	fresh clone at the candidate, python3 src/health-check.py	exit 1; 2 issues (build_log.md and .env missing) plus warnings an unconfigured clone always shows; no probe crashed. Not a clean pass. Needed an idna package supplied through PYTHONPATH: this host's Python has a broken idna, so detect_secrets fails to import.
3. Headline smoke	tests/connections.test.py, connections-cli, connections-no-cloud-trust, agent-api-connections, runtime-api-connections-view, dotspace, dotspace-literal-guard	all exit 0. Not executed: a live add + promote on a real host, because it rotates a real agent credential. Needs an owner or test-agent run before tagging.
4. Migrations	tests/*migrat*.py (5), tests/*migrat*.sh (10), voice-config-model-migration, conversation-store-migrations, conversation-store-migration-delegation	all pass (TS: 5, 15 and 4 tests); sync-workspace-anchor-migration needs SUTANDO_REPO_DIR set to the clone. There are no new numbered migrations.
5. Upgrade smoke v0.12.0 → candidate	clean clone: bash scripts/sutando-migrate.sh --dry-run at v0.12.0, checkout candidate, run again; import connections + dotspace	dry-run exit 0 at both commits; imports OK; the registry lists ag2.space, dev.ag2.space, s.space and dev.s.space. Not executed: bash src/startup.sh, because it would start bridges against live tokens.

Also on this branch: tests/release-docs-audit.test.py ALL PASS (5 checks); tests/self-upgrade.test.sh 3/3; scripts/review-checks.sh hardcoded-paths and root-artifacts clean.

Before/after evidence

N/A for behavior: this PR only edits the changelog. The before/after is the diff of CHANGELOG.md and CHANGELOG-PENDING.md.

Live path

N/A: no code changes.

Tag and publish (not done here; needs the owner's confirmation of version and SHA)

SHA=<final candidate sha, full 40 chars>
git fetch origin main && git tag -a v0.13.0 "$SHA" -m "engine v0.13.0 — one install, several homeservers, and the move to s.space"
git push origin v0.13.0
gh release create v0.13.0 -R sonichi/sutando --verify-tag \
  --title "v0.13.0 — one install, several homeservers, and the move to s.space" \
  --notes-file release-notes-v0.13.0.md --generate-notes --latest

release-notes-v0.13.0.md is the [v0.13.0] section of CHANGELOG.md. Per docs/release-process.md, the tag does not wait for this PR to merge.

🤖 Generated with Claude Code

[qingyun-wu]

Reviewed at 02236ba. Two blocking findings.

Verified: all 87 PRs cited in the [v0.13.0] section are in v0.12.0..c8aa23a0e. Nothing cited predates v0.12.0, and nothing cited is outside the candidate.

Blocking:

1. CI is red because of this PR. CHANGELOG.md:29 (the Skills bullet) contains the retired spelling "room-doc". lint-old-collab-literals reports CHANGELOG.md: 0 -> 1, which fails both lints + typecheck and python standalone tests (2/9). Say "Room Commons", or drop that word.
2. The candidate is stale. c8aa23a0e is 9 commits behind main. The changelog doesn't cover #5977, #5978, #5980, #5983, #5990 or #5998 (connections and s.space fixes), nor #5992 (automatic bug reports now default OFF, a user-visible change that belongs under Changed). Pick the final SHA, add these, and re-run gates 1 to 3 there, as the body already says will happen when #5971 lands.

Non-blocking:
3. promote wording. The headline (:9) and the Connections bullet (:20) say promote makes the new homeserver primary "then stops and parks" the old one. #5996 (open) makes promote keep the old bridge, with park-legacy as the explicit cutover. Decide whether #5996 is in v0.13.0 and word both lines to match. :46 ("ag2.space keeps working during the transition") is only true for a terminal-run core once #5996 is in.
4. python standalone tests (4/9) fails in tests/skills/worker-pool/pool-restart*.test.py. The same shard passes on main and this PR changes no code, so it looks unrelated. Re-run it.

[github-actions]

@cla-assistant check

[github-actions]

Coverage Gate

✅ No Python changes — nothing to gate (bar: 95% on changed lines).