What

Three satellite projects (pacs_bridge, dicom_viewer, messaging_system) use inconsistent vcpkg configuration compared to the 8 core ecosystem projects. This epic tracks the standardization effort.

Current State

Expected State

All 11 projects use identical vcpkg-configuration.json with:

• Default registry baseline: d90a9b159c08169f39adcd1b0f1ac0ca12c4b96c
• Custom registry: kcenon/vcpkg-registry baseline 77cc46d5ba5e2aef1581f2ec674f83e1ac906b43
• Consistent overrides for shared packages (gtest, benchmark, etc.)

CI Standardization

Additionally, ecosystem CI workflows use 3 different patterns for vcpkg setup:

A reusable composite action will centralize vcpkg bootstrap, pinning, and caching.

Why

• Version drift: Satellite projects resolve different package versions than core projects (no shared overrides), causing build failures when mixing dependencies
• Registry gap: Without vcpkg-configuration.json, satellite projects cannot consume kcenon-* packages from the custom registry
• CI instability: Cloning vcpkg from HEAD means CI builds use different vcpkg versions than declared in baseline, leading to non-reproducible builds
• Maintenance burden: 3 different CI patterns for the same operation across 11 repos

Sub-Issues

• chore(vcpkg): migrate to vcpkg-configuration.json and add ecosystem overrides pacs_bridge#374 — Migrate to vcpkg-configuration.json and add ecosystem overrides
• chore(vcpkg): migrate to vcpkg-configuration.json and add ecosystem overrides dicom_viewer#543 — Migrate to vcpkg-configuration.json and add ecosystem overrides
• chore(vcpkg): add vcpkg-configuration.json and ecosystem overrides messaging_system#238 — Add vcpkg-configuration.json and ecosystem overrides
• chore(ci): create reusable GitHub Actions composite action for ecosystem vcpkg setup #510 — Create reusable GitHub Actions composite action for ecosystem vcpkg setup

Acceptance Criteria

• All 11 projects use identical vcpkg-configuration.json
• All projects that share dependencies use the same override versions
• builtin-baseline field removed from satellite vcpkg.json files (superseded by vcpkg-configuration.json)
• Reusable composite action adopted by at least one project's CI
• Full ecosystem vcpkg install resolves without version conflicts