Re: [boost] Proposal: Abandoning monolithic Boost documentation.

Perhaps, the answer to that is setting up a per-library CI that builds the library docs.

Could be. boostorg/release-tools has multiple such CI jobs already. Perhaps set a schedule there, on job that 'must' pass every time. However will the effect be the same as circleci... It should also should be marked as 'red' instead of 'green' from the exit code of the shell script.