Summary

Track the ecosystem hardening work identified during the 2026-05-21 read-only analysis of:

• common_system
• container_system
• thread_system
• logger_system
• monitoring_system
• network_system
• database_system
• pacs_system

The analysis found three follow-up clusters: version/package-contract drift, production-support classification gaps for stub/placeholder areas, and missing explicit release gates for concurrency-heavy or medical/security-sensitive paths.

Why

• network_system and pacs_system both contain visible v1.0 contract language while their package metadata still exposes pre-1.0 versions in at least one place. That confuses downstream consumers and release automation.
• network_system, monitoring_system, and database_system contain placeholder/stub/experimental areas that need an explicit support classification so users can tell production APIs from test scaffolding or future work.
• thread_system sits underneath network/database/monitoring/pacs; sanitizer, stress, and downstream-consumer gates should be explicit enough that concurrency regressions are caught before release.
• pacs_system is medical-imaging and security-sensitive, so DICOM conformance, TLS/ATNA, anonymization, and storage migration checks should be treated as release gates, not ad hoc test runs.

Scope

1. Reconcile version, CMake, README, CHANGELOG, and vcpkg manifest state for top-tier release candidates.
2. Audit all stub/placeholder/experimental markers in the affected repos and classify each as production, experimental, test-only, or remove.
3. Convert the audit findings into narrowly scoped fixes or documentation updates.
4. Make concurrency and PACS domain-specific release gates observable in CI or release checklists.

Child Issues

Acceptance Criteria

• Every child issue below is closed or explicitly superseded
• A final ecosystem matrix is posted here covering version state, package metadata, support classification, and release-gate status for all affected repos
• No v1.0 README/CMake/package version mismatch remains in network_system or pacs_system
• Stub/placeholder/experimental areas in network_system, monitoring_system, and database_system are classified and documented
• thread_system and top-tier consumers have sanitizer/stress/downstream verification gates documented or wired into CI
• pacs_system has explicit release gates for DICOM conformance, security/audit, anonymization, and storage migration

Verification

This issue creation is tracking-only. No build or test verification is expected until the child implementation issues are worked.