What

Verify that all four downstream consumers of thread_system build cleanly against the standardized layout produced by sub-issues A and B. Acceptable outcome: at most [[deprecated]] warnings from forwarding headers; zero hard failures.

Part of #683. Depends on sub-issues A and B.

Why

thread_system sits at Tier 1 of the ecosystem and is consumed by:

If any of them break after the layout change, the EPIC has not actually delivered the intended standardization — it has just moved the problem downstream. This issue makes that breakage observable before declaring #683 done.

Note: the EPIC body lists "pacs" as a consumer; the active downstream set above is what currently depends on thread_system and should be verified.

How

For each consumer, in the matching repo on the working machine:

1. Pull latest develop of thread_system and the consumer.
2. Update the consumer's thread_system pin (vcpkg manifest, CMake submodule, or find_package) to the post-EPIC commit.
3. Run the consumer's standard build:
   • logger_system: cmake --preset debug && cmake --build --preset debug && ctest --test-dir build-debug
   • monitoring_system: same.
   • network_system: same.
   • database_system: same.
4. Capture build logs. Categorize any warning as either:
   • Acceptable — [[deprecated]] from forwarding headers (action: open follow-up issue in consumer repo to migrate to new include path)
   • Blocking — hard error, missing symbol, incompatible signature (action: stop and reopen sub-issue A or B)
5. Summarize findings in this issue's comment thread.

Acceptance Criteria

• logger_system builds clean (deprecation warnings allowed)
• monitoring_system builds clean
• network_system builds clean
• database_system builds clean
• All deprecation warnings have follow-up issues filed in the consumer repos
• No blocking errors

Where

External repos (verification only — no PR opened in this issue):

• kcenon/logger_system
• kcenon/monitoring_system
• kcenon/network_system
• kcenon/database_system

Local paths under /project/ (logger_system, monitoring_system, network_system, database_system) for build verification.