What
Define and wire explicit sanitizer/stress verification gates for thread_system and its highest-risk consumers.
Part of kcenon/common_system#684.
Why
thread_system underpins monitoring_system, network_system, database_system, and pacs_system. The 2026-05-21 analysis found that concurrency-heavy surfaces include lock-free queues, typed thread pools, DAG scheduling, cancellation, autoscaling, and downstream integrations. A normal build passing is not enough signal for this layer.
Existing issue #687 verified downstream builds after layout changes. This issue is narrower and stricter: sanitizer and stress gates for runtime concurrency regressions.
Where
.github/workflows/**
CMakePresets.json
tests/stress/**
tests/integration_tests/**
tests/unit/lockfree_test/**
tests/unit/thread_pool_test/**
- Downstream consumer workflows or documented verification commands for
network_system and pacs_system
How
Approach
- Inventory current ASAN, TSAN, UBSAN, stress, and integration presets/workflows.
- Define the minimum required gate set for release branches.
- Include at least one downstream verification path for
network_system and pacs_system, because they exercise the most integration-heavy thread usage.
- Document tolerated warnings/flakes, retry policy, and failure triage rules.
- Wire missing gates into CI or document why they must remain manual.
Acceptance Criteria
Verification
What
Define and wire explicit sanitizer/stress verification gates for
thread_systemand its highest-risk consumers.Part of kcenon/common_system#684.
Why
thread_systemunderpinsmonitoring_system,network_system,database_system, andpacs_system. The 2026-05-21 analysis found that concurrency-heavy surfaces include lock-free queues, typed thread pools, DAG scheduling, cancellation, autoscaling, and downstream integrations. A normal build passing is not enough signal for this layer.Existing issue #687 verified downstream builds after layout changes. This issue is narrower and stricter: sanitizer and stress gates for runtime concurrency regressions.
Where
.github/workflows/**CMakePresets.jsontests/stress/**tests/integration_tests/**tests/unit/lockfree_test/**tests/unit/thread_pool_test/**network_systemandpacs_systemHow
Approach
network_systemandpacs_system, because they exercise the most integration-heavy thread usage.Acceptance Criteria
network_systemandpacs_systemverification commands/workflows are documentedVerification
cmake --preset asan && cmake --build --preset asansucceeds or equivalent workflow is greencmake --preset tsan && cmake --build --preset tsansucceeds or equivalent workflow is greencmake --preset ubsan && cmake --build --preset ubsansucceeds or equivalent workflow is green