What

The vcpkg overlay port for kcenon-thread-system currently references a commit SHA as REF and uses a placeholder SHA512 hash (0). For official vcpkg registry submission, a stable release tag and valid SHA512 hash are required.

Why

• vcpkg PR review checklist (c000005) requires versioned archives — tags, not branch HEADs or arbitrary commits
• SHA512 placeholder 0 blocks actual port installation
• Downstream ports (logger_system, monitoring_system, network_system) need a stable reference point
• IEC 62304 SOUP traceability requires pinned, auditable release versions

Where

• monitoring_system/vcpkg-ports/kcenon-thread-system/portfile.cmake — REF and SHA512 fields
• Repository root — git tag creation

How

1. Ensure all pending changes (including fix(build): Link kcenon::common_system target in ThreadSystemDependencies.cmake for vcpkg find_package support #569 CMake fix) are merged to main
2. Update version in CMakeLists.txt and vcpkg.json if needed
3. Create annotated tag: git tag -a v0.3.0 -m "Release v0.3.0"
4. Push tag: git push origin v0.3.0
5. Create GitHub Release: gh release create v0.3.0 --generate-notes
6. Obtain SHA512: attempt vcpkg install with SHA512 0, copy correct hash from error
7. Update portfile.cmake REF to v0.3.0 and SHA512 to the actual hash

Acceptance Criteria

• Annotated git tag v0.3.0 exists on main branch
• GitHub Release created with changelog
• portfile.cmake REF updated from commit SHA to tag
• portfile.cmake SHA512 updated from placeholder to actual hash
• vcpkg install with overlay port succeeds with correct hash

Context

• Depends on: fix(build): Link kcenon::common_system target in ThreadSystemDependencies.cmake for vcpkg find_package support #569 (CMake linking fix must be merged first)
• Related: monitoring_system#279, common_system#378 (semantic version tags initiative)