release: v0.3.1

[brettdavies]

Summary

Releases v0.3.1, an artifact-set release: ships x86_64-unknown-linux-musl and aarch64-unknown-linux-musl static
binaries on every release. No source change versus v0.3.0: the binary is identical; only the artifact set is wider.

Consolidates one dev commit:

• feat(release): opt into linux-musl artifacts via shared workflow #48, feat(release): opt into linux-musl artifacts via shared workflow: passes linux_musl_required: true and
  linux_musl_verify_alpine: true to the shared rust-release.yml@main (those inputs landed in
  release: linux-musl matrix rows + RELEASES.md backport .github#18). Bundled with the inputs change is a RELEASES.md polish: 5 → 7 target table update plus a
  separate cliff.toml chore-skip + "never hand-written" rule that was pre-existing dirty in the working tree.

Triple-diff verification before opening: A is exactly the 6 expected ship-surface files; B contains only release-prep
files (Cargo.toml, Cargo.lock, CHANGELOG.md) plus the always-divergent completions/; no guarded engineering-doc paths
leaked.

Changelog

Added

• Ship x86_64- and aarch64-unknown-linux-musl static binaries on every release. Statically linked against musl libc,
  so they run on Alpine and other musl-libc-host distros without glibc, and on every glibc distro too.

Documentation

• Document the cliff.toml chore-skip footgun and the "CHANGELOG is generated, never hand-written" rule in
  RELEASES.md under Releasing dev to main.
• Update the release-pipeline target table from 5 → 7 targets, naming the two musl rows and the two opt-in inputs
  (linux_musl_required, linux_musl_verify_alpine).

Type of Change

• feat: New feature (non-breaking change which adds functionality)

Related Issues/Stories

• Story: n/a
• Issue: n/a
• Architecture: n/a
• Related PRs: feat(release): opt into linux-musl artifacts via shared workflow #48 (this release's only consolidated dev commit), feat(rust-release): add linux-musl matrix rows with soft-fail and alpine-verify inputs .github#17 (shared-workflow musl matrix
  rows + soft-fail), release: linux-musl matrix rows + RELEASES.md backport .github#18 (release of refactor: enforce check_x → CheckStatus convention + toolchain supply-chain pin #17 to main)

Testing

• Manual testing completed
• All tests passing

Test Summary:

• Unit tests: pass on dev as part of feat(release): opt into linux-musl artifacts via shared workflow #48 CI (fmt, clippy, test, audit, package check, drift-check)
• Integration tests: n/a (no source change vs v0.3.0)
• Coverage: unchanged

End-to-end musl validation completed pre-merge in the throwaway spike/musl-build workflow:

• cross build --release --locked --target x86_64-unknown-linux-musl: green, statically linked
• cross build --release --locked --target aarch64-unknown-linux-musl: green, statically linked
• file target/.../release/anc matched statically linked for both arches
• x86_64 host smoke test (anc --version): anc 0.3.0
• Belt-and-suspenders: docker run --rm --pull always -v ".../release:/musl-bin:ro" alpine:latest /musl-bin/anc --version: anc 0.3.0

The release pipeline (now 7 targets) re-runs all of the above on the v0.3.1 tag push, so the binaries shipped to the
GitHub Release will be the freshly-built ones, not the spike's.

Files Modified

Modified:

• .github/workflows/release.yml: passes the two new shared-workflow inputs.
• Cargo.toml: version 0.3.0 → 0.3.1.
• Cargo.lock: cargo update -p agentnative regen.
• CHANGELOG.md: scripts/generate-changelog.sh extracted feat(release): opt into linux-musl artifacts via shared workflow #48's ## Changelog section into a v0.3.1 entry.
  Cross-checked: cliff.toml chore-skip didn't drop anything (commit subject was feat, not chore).
• RELEASES.md: release-pipeline table 5 → 7 targets + bundled cliff.toml/never-hand-written documentation.
• src/skill_install/skill.json: fixture refresh from upstream agentnative-site dev (caught by drift-check on feat(release): opt into linux-musl artifacts via shared workflow #48;
  brought along here).

Created:

• None.

Renamed:

• None.

Deleted:

• None.

Breaking Changes

• No breaking changes

The binary surface is unchanged. New consumers on Alpine gain an install path; existing consumers see no difference.

Deployment Notes

After this PR squash-merges to main:

git checkout main && git pull
git tag -a -m "Release v0.3.1" v0.3.1
git push origin main --tags

The tag push triggers the now-7-target release pipeline. After the GitHub Release reaches published (homebrew dispatch
and finalize-release flip), backport per the new convention:

./scripts/sync-dev-after-release.sh v0.3.1
git push origin dev

The throwaway spike/musl-build branch (local + remote) can be pruned any time after this PR opens; it served its
purpose.

Checklist

• Code follows project conventions and style guidelines
• Commit messages follow Conventional Commits
• Self-review of code completed (PR feat(release): opt into linux-musl artifacts via shared workflow #48 review applies; release-prep commits are
  bump/completions/CHANGELOG/skill-fixture as scripted)
• Tests added/updated and passing (validated via spike + feat(release): opt into linux-musl artifacts via shared workflow #48 CI)
• No new warnings or errors introduced
• Changes are backward compatible