What

Bring every system in the kcenon ecosystem to a state where it can be installed via vcpkg with a single vcpkg install kcenon-<system> command, backed by version pinning and automated hash updates.

• Current: All systems have vcpkg.json + portfile.cmake, but a few gaps (hash automation, version drift, stubbed subsystems) prevent smooth installs
• Expected: vcpkg install works first-try for every system; release flow updates ports automatically
• Scope: common, container, network, pacs (others already distribution-ready)

Why

• vcpkg is the primary distribution channel for kcenon C++ libraries
• Manual hash updates and doc version drift are the top causes of broken installs
• A consistent release flow unblocks future vcpkg official registry submissions

How

Sub-issues (implementation work)

• chore: automate portfile SHA512 on release #643 — Automate portfile SHA512 on release (template for other systems)
• docs: sync protobuf version reference (README vs CLAUDE.md) container_system#524 — Sync protobuf version reference (fixes doc drift)
• refactor: finish Result<T> migration (75-80% → 100%) network_system#988 — Finish Result<T> migration (blocks v1.0 tag)
• docs: expand Doxygen API coverage pacs_system#1103 — Expand Doxygen API coverage (originally noted as #1102 sibling, now closed)
• Tag pacs_system v1.0.0 once #1101, #1102, #1103 land (#1102, #1103 closed; tracks #1101 progress)
• Submit common_system to vcpkg official registry → tracked in chore(vcpkg): submit kcenon-common-system to microsoft/vcpkg official registry #653

Sub-issues (acceptance gap, opened 2026-04-21)

• docs(ecosystem): document version pins in ECOSYSTEM_OVERVIEW.md #652 — Document version pins in ECOSYSTEM_OVERVIEW.md
• chore(vcpkg): submit kcenon-common-system to microsoft/vcpkg official registry #653 — Submit kcenon-common-system to microsoft/vcpkg official registry

Acceptance Criteria

• vcpkg install kcenon-<system> succeeds for every Tier-0/1/2 system (kcenon vcpkg-registry holds 8 ports; weekly vcpkg-consume-test.yml validates)
• Release workflow auto-updates REF + SHA512 in vcpkg-registry (sync-vcpkg-registry.yml, on-release-sync-registry.yml)
• Version pins documented in ecosystem manifest → tracked in docs(ecosystem): document version pins in ECOSYSTEM_OVERVIEW.md #652
• At least one system accepted into vcpkg official registry → tracked in chore(vcpkg): submit kcenon-common-system to microsoft/vcpkg official registry #653

Verification 2026-04-21: install paths and release automation are in place; consumption is validated weekly. Documentation of version pins and upstream submission remain — see verification comment.