v0.0.1

The first full release. Everything before it was published as a prerelease.

The version number moves down, from the 0.1.0 the earlier archives declared
to 0.0.1, because that number described a release that was never cut. Nothing
was removed from the tool surface to justify it.

What this is

54 MCP tools — 40 bounded read, 14 change-control — over HPE Juniper Security
Director Cloud. Every mutation is reachable only through
prepare → independent approval → apply; there is no direct deploy tool and no
unauthenticated write path. A wildcard token scope grants no write tool.

Built with Rust 1.98.0 (MSRV 1.88), with the six shared mecmcp crates pinned
at v0.21.0.

Assets

rustsdcmcp_0.0.1.20260828.c5438e80471b_amd64.tar.gz is commit-addressed to
c5438e80471bec552a26e13aa3397e013c1cbe79 and built by CI, not locally. Verify
it against the sibling .sha256, taking the expected value from this page:

edae795543b3abe4753238fa5ec99edf9d3d49c12d813b23213d9aa1caaa57e2  rustsdcmcp_0.0.1.20260828.c5438e80471b_amd64.tar.gz

A linux/amd64 container image is published for this tag to
ghcr.io/fastrevmd-lab/rustsdcmcp:0.0.1.

Upgrading from a v0.1.0-lab.N archive

The packaging assertions are exact-match, so this is not a drop-in swap:

• the archive drops its -lab. infix — rustsdcmcp_0.0.1.<date>.<sha12>_amd64.tar.gz
• BUILD-INFO carries version=0.0.1 and release_status=release, and
  packaging/lxc/install.sh asserts both. An older archive will not install
  under this installer, and this archive will not install under an older one.
• scripts/build-lab-package.sh is now scripts/build-package.sh, with no shim

--lab-mode is a security control, not release framing, and is unchanged.

Full detail in CHANGELOG.md.