Context

Part of #684. Derived from the 2026-06-13 analysis: every ecosystem-coherence gate (conformance_lint.py #693, version-drift, port-sync, ecosystem-cross-build) lives ONLY in common_system and was never propagated — the structural reason cross-system drift goes uncaught. The one cross-build that exists validates against stale main while all work is on develop.

Approach (staged, non-blocking-first to avoid red-walling 5/8 repos)

1. Copy per-repo gates (conformance + its script; a local version-drift + its script) into all 8 repos as advisory (warning-only) + a per-repo tracking issue
2. Remediate each repo to green
3. Flip to required ONLY after that repo exits 0 on develop HEAD
4. Keep ecosystem orchestrators (port-sync, ecosystem-cross-build) single-homed in common; fire downstream via repository_dispatch; pin siblings to a last-green ecosystem-lock SHA, not bare develop

Status — 2026-06-14

Step 1 (advisory conformance propagation) DONE for all 7 downstream repos. The conformance linter (scripts/conformance_lint.py) was copied verbatim from common_system and wired as an advisory (warning-only, exit 0 via || echo ::warning::) Conformance workflow, so each repo surfaces its structural/metadata deviations without red-walling. All 7 PRs CI-green and squash-merged to develop.

Remaining: per-repo remediation to green (step 2) -> flip required (step 3); plus version-drift propagation, option-spelling standardization, tag-reality gate, and the cross-build retarget (below).

Per-repo checklist (conformance linter)

• common_system (source of truth; conformance/version-drift already here — cross-build retarget off stale main still pending)
• thread_system — advisory conformance (PR fix(error): classify positive codes as Invalid not Success #703)
• logger_system — advisory conformance (PR docs(release): document automated portfile SHA512 sync flow #649)
• container_system — advisory conformance (PR build(deps): bump google/osv-scanner-action from 2.3.3 to 2.3.5 #553)
• monitoring_system — advisory conformance (PR chore(release): cut signed v1.0.0 tag + tag-reality gate (release-merge develop into main) #700)
• database_system — advisory conformance (PR [P2][Ecosystem] Standardize Features documentation template for vcpkg ports #603)
• network_system — advisory conformance (PR #1166)
• pacs_system — advisory conformance (PR #1194)
• Standardize the sibling-enable option spelling into one KCENON_WITH_<DEP> namespace via compatibility shims (currently 5 spellings: BUILD_WITH_/MONITORING_WITH_/PACS_WITH_/USE_/LOGGER_USE_)
• Add a "tag-reality" gate (tag resolves AND == release-merge HEAD AND portfile SHA512 matches) to each repo

Follow-up tracks (not yet started)

• version-drift gate propagation to the 7 repos (its check_version_drift.py takes repo-specific args; sequenced after conformance)
• Remediate each repo's advisory conformance deviations to zero, then flip the gate to enforcing/required
• Standardize option spelling + tag-reality gate (above)