chore(release): v1.0.1 — packaging patch (vcpkg + Conan)

[danielPoloWork]

Summary

Release PR for v1.0.1 — a packaging patch over the frozen v1.0.0 API. It bundles the post-1.0 packaging additions (the M7.8 vcpkg port + the M7.9 Conan recipe) into a tagged release. Cut by maintainer request.

Why a PATCH (1.0.1), not a MINOR (1.1.0)

The changes since v1.0.0 are additive in Keep-a-Changelog terms, but the shipped library is byte-identical to v1.0.0 — no source, public-API, ABI, or behaviour change; only repository-side packaging metadata (ports/, conan/) was added. So 1.0.1 is defensible, and it keeps the Milestone 8 close targeted at v1.1.0. (If you'd rather ship this as 1.1.0, say so and I'll re-cut.)

Changes

• version.hpp → 1.0.1; the pool_smoke version-check TEST_CASE asserts the new components (verified locally — pool_smoke passes).
• CHANGELOG.md [Unreleased] (M7.8 + M7.9) rolled into ## [1.0.1] — 2026-06-14 with a packaging-patch headline; fresh empty [Unreleased]; link references rewritten.
• docs/releases/v1.0.1.md — the release notes release.yml uses as the GitHub Release body.
• README status badge (v1.0.0 → v1.0.1) + a one-paragraph patch note.
• ROADMAP session checkpoint for the patch.

Verification

• pool_smoke built and run locally (MSVC 19.51 + Ninja) — the 1.0.1 version assertions pass; CMake configured project(... VERSION 1.0.1).
• No library code changed — the static archive is identical to v1.0.0.
• markdownlint clean; the [1.0.1] anchor follows the v1.0.0 precedent.

Documentation Impact

• README.md — badge + patch note.
• ROADMAP.md — session checkpoint (not a numbered item; ad-hoc patch).
• ADR — N/A (the packaging ADRs 0030/0031 already landed).
• Spec — N/A.
• CHANGELOG.md — sealed [1.0.1] block.

After merge

The agent tags v1.0.1 from master (ADR-0008); release.yml builds the per-platform tarballs + SHA256SUMS and drafts the Release from docs/releases/v1.0.1.md; the maintainer clicks Publish.