Boost review: acceptance conditions and follow-up tracker

[sgerbino]

From the review result:

I recommend that Boost.Capy and Boost.Corosio be conditionally accepted into Boost.

Source: Boost review result (conditional acceptance), Boost mailing list, September 2026.

This issue tracks every condition and discussion item from the review across both repositories. Items are attached as sub-issues.

Documentation (Capy)

• docs: move the coroutine and concurrency introductions out of the main reading path #398 move the coroutine and concurrency introductions out of the main reading path
• docs: add sequence diagrams and up-front mental models #399 add sequence diagrams and up-front mental models
• docs: restore nav sub-entries for the Buffer Sequences section #400 restore nav sub-entries for the Buffer Sequences section
• docs: enable site search #401 enable site search
• docs: link the benchmark suites from the documentation #402 link the benchmark suites from the documentation
• docs: make "Why not std::execution" a peer design page and link the comparison paper #403 make "Why not std::execution" a peer design page and link the comparison paper
• docs: reconcile thread_pool destructor reference wording with the manual #404 reconcile thread_pool destructor reference wording with the manual
• docs: give io_result a page of its own and annotate the early examples #405 give io_result a page of its own and annotate the early examples
• docs: add a lifetime and ownership page for composing coroutines #406 add a lifetime and ownership page for composing coroutines
• docs: add a glossary #407 add a glossary
• docs: add a functionally grouped entry point into the reference #408 add a functionally grouped entry point into the reference
• docs: document quitter and the other toolkit examples in the manual #409 document quitter and the other toolkit examples in the manual

Documentation (Corosio)

• docs: move Quick Start to the front of the navigation corosio#351 move Quick Start to the front of the navigation
• docs: address the remaining mailing-list review feedback corosio#353 address the remaining mailing-list review feedback
• docs: review feedback corosio#324 review feedback on the documentation (pre-existing tracker)

Naming (Capy)

• Capy types need renaming #395 Capy types need renaming (pre-existing)
• docs: explain the buffer archetype underscore convention #410 explain the buffer archetype underscore convention

TLS (Corosio)

• docs: remove stale TLS warnings that contradict the implemented verification corosio#350 remove stale TLS warnings that contradict the implemented verification

Performance and benchmarks

• docs: link the benchmark suites from the documentation #402 (Capy docs linkage, listed above)
• perf: make the published benchmark report reproducible and current corosio#352 make the published benchmark report reproducible and current
• Run performance benchmarks on PRs and report the impact corosio#343 run performance benchmarks on PRs (pre-existing)

Enhancements (Corosio)

• feat: add a generic ip_address type corosio#357 add a generic ip_address type (promoted from discussion)

Discussion items (converted to GitHub Discussions)

• should thread_pool be renamed?
• buffer type naming and concept taxonomy
• io_context and signal handling at the Capy level
• quitter's place in the library

Resolved during or shortly after the review (no open issue)

• Delays and timeouts moved to Corosio as native delay/timeout (Redesign delay/timeout/timer — move to corosio; remove timer/cancel_at/cancel_after #351, corosio#315/Fix broken link #322/Incorrectly assuming operator-> exists #333)
• DynamicBuffer concept and types removed from Capy
• TLS implementation hardened to verify and fail closed (corosio#297, corosio#301)
• std::execution interop: IoAwaitables composable as senders, bridge examples (feat: make IoAwaitables composable as std::execution senders #371)