Why

thread_system EPIC kcenon/thread_system#683 standardized the public include layout under <kcenon/thread/...>. The legacy install path <thread_system/...> is preserved as a forwarding header marked [[deprecated]] for backward compatibility; it will be removed in the next minor release of thread_system.

Static audit performed against thread_system develop (post sub-issues #684, #685, #686) found one legacy include in this repository.

What

Migrate the following include from the legacy vcpkg-installed path to the canonical <kcenon/thread/...> path:

The legacy path resolves to a forwarding header that emits a #pragma GCC warning "utilities/include/formatter.h is deprecated; include <kcenon/thread/utils/formatter.h> instead" at compile time.

Where

• integration_tests/vcpkg_consumer/main.cpp

Acceptance Criteria

• No #include statements use the legacy <thread_system/...> path
• The vcpkg consumer integration test still finds and links kcenon-thread-system correctly
• Build emits zero deprecation warnings originating from thread_system forwarding headers

Notes

• The legacy install destination (thread_system/utilities/) is set up by cmake/thread_system_install.cmake in thread_system and is scheduled for removal alongside the forwarding headers.
• Reference: thread_system PR chore(release): verify SHA512 against actual archive (#687) #688 introduced the forwarding-header strategy.