release: v0.6.0-rc1

[alpCaner]

Prepares the v0.6.0-rc1 tag: folds the pending changelog.d/ fragments into a dated release section and moves the three version files onto 0.6.0-rc1.

The number is 0.6.0, not the 0.5.2 the files carried

python/tan/version.py read 0.5.2-rc1.dev0 with a ## [0.5.2] — Unreleased header. That is wrong on three counts:

• The milestone being closed is v0.6.0, with 206 closed issues. No v0.5.2 milestone exists.
• The section carries a ### Removed block — the Rust oracle (crates/tan-core, crates/tan-cli, Cargo.toml, Cargo.lock). Pre-1.0 SemVer puts a removal in the minor, not a patch.
• Latest published is v0.5.1, so 0.5.2 was dev scaffolding nobody re-pointed.

TAN_VERSION (source of truth) : 0.6.0-rc1
python/pyproject.toml         : 0.6.0rc1
npm-shim/package.json         : 0.6.0-rc1
CHANGELOG.md section          : ## [0.6.0-rc1]
git tag                       : v0.6.0-rc1
versions agree

Cargo.toml needs no edit — the release pipeline does not read it.

43 fragments folded

$ python3 python/scripts/assemble_changelog.py --require-empty ; echo rc=$?
rc=0

Only changelog.d/README.md remains, as intended.

A section-hierarchy defect this fold exposed

Seven fragments written this cycle used a ### Fixed — <title> header. changelog.d/README.md specifies the file contains bullets; the category comes from the filename. The fold therefore produced seven stray ### sections where v0.5.1's section has exactly one ### Fixed.

Demoted to #### under the canonical heading. No content changed. The release section now has the same six headings as its predecessors:

### Added, Removed, Changed, Fixed, Security, Added — CI

Gates

Full python/tests, parity included, bound against alp-sdk bd8be484680cf5aa1c1ac0e8b38d84128b5a279d:

5126 passed, 64 skipped, 1 xfailed in 734.38s (0:12:14)

Zero failures. Re-run after merging origin/dev for #749, not carried over from the pre-merge run.

The release-body slice was simulated before tagging and matches:

MATCH: ## [0.6.0-rc1] — 2026-08-14

Ordering note for the next release

assemble_changelog.py only folds into an Unreleased header. Once the header is dated, a late-landing PR cannot be folded by the tool — it refuses with "Refusing to guess where entries belong." #749 landed after the rename here and had to be folded by renaming back, folding, and re-dating. Fold last, date last.

Not in this cut

#58 (feat(model) edge-AI surface) is CONFLICTING and excluded by maintainer direction.

After this merges

release: promote v0.6.0-rc1 to main, then the tag on main — matching how v0.5.0-rc4 and v0.5.1 were cut. The lean release body is written and will be applied the moment the page exists; the auto-slice is 4670 lines.