release(1.6.1): manifest declares only crates.io-published crates, in publish order

[randlee]

Release run 35952487967 for v1.6.1 failed at the first cargo publish: atm-graft-python cannot be published (its Cargo.toml has publish = false). Nothing was uploaded to any channel; the publisher cancelled the run before the GitHub Release job. The v1.6.1 tag exists at 1272d4c and gate-and-tag reuses it.

Cause. The kit's list-publish-plan emits every [[crates]] entry in manifest file order. atm-core's 1.6.0 copy of release_artifacts.py carried a local fix that skipped publish = false crates and sorted by publish_order; the phase-bc kit re-render (b381e09) replaced that copy with upstream, which never had the fix. 1.6.1 is the first release on the re-rendered copy.

Fix (manifest only, no kit file touched). release/publish-artifacts.toml:

• remove the two publish = false [[crates]] entries (atm-graft-python, atm-query-python); they are PyPI-only bridge crates and remain declared under [[python_packages]] / [[python_distributions]], which is what builds and publishes them;
• reorder the remaining [[crates]] blocks to match their publish_order, since the kit publishes in file order.

Verified locally with the pinned kit script: validate-manifest passes, validate-publish-order passes, python-wheel-matrix unchanged, and list-publish-plan output is identical, crate for crate and in order, to the 1.6.0 upload sequence in run 34988409741.

🤖 Generated with Claude Code