fix: transitive closure was not testing correctness

[Becheler]

Before submitting

• This PR targets the develop branch.
• I searched for an existing PR or issue covering the same change.
• My contribution is licensed under the Boost Software License 1.0.

Type of change

• Bug fix
• New feature or API addition
• Refactor (no behavior change)
• Documentation
• Build, CI, or tooling
• Other (specify below)

Does this PR introduce a breaking change?

• Yes (describe migration impact below)
• No

What this PR does

• Folds a print-only test into transitive closure test, and actually test it
• Modernize the test file by bringing BOOST_TEST in
• Refactor to limit verbosity and complexity

Motivation

Flickering CI coverage, and untested test files are not great.

Testing

Checklist

• Existing tests pass (b2 in the test/ directory).
• New behavior is covered by a test, or this is a docs / build / refactor change.
• Documentation was updated if user-facing behavior changed.
• No new compiler warnings on the platforms I built against.

[github-actions]

Boost dependency footprint vs develop (auto-generated).
PR run 31467881423 vs develop run 31467777307 (09646e7664).

Header-inclusion weights (graph files pulling each direct dependency in):

No header-inclusion-weight changes.

Transitive Boost modules: 68 → 68 (0)

[github-actions]

Compiler-warning counts vs develop (auto-generated).
PR run 31467881369 vs develop run 31467777283 (09646e7664).

Job	Baseline	After	Delta
macos (clang, 14)	681	676	-5
macos (clang, 17)	641	636	-5
macos (clang, 20)	641	636	-5
ubuntu (clang-19, 14)	681	676	-5
ubuntu (clang-19, 17)	641	636	-5
ubuntu (clang-19, 20)	641	636	-5
ubuntu (clang-19, 23)	641	636	-5
ubuntu (gcc-14, 14)	827	823	-4
ubuntu (gcc-14, 17)	949	945	-4
ubuntu (gcc-14, 20)	949	945	-4
ubuntu (gcc-14, 23)	949	945	-4
windows_msvc_14_3 (msvc-14.3)	962	962	0

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.