ycb_sphinx_pr8035

what a new run launched now would send

Support defining specific `:private-members:` for autodoc
**Is your feature request related to a problem? Please describe.**
Currently, if I'm using autodoc, the `:private-members:` option does not allow specification of which private members to document. The current behavior is to document all private members, but what if I would only like to document 1 or 2?

**Describe the solution you'd like**
For `:private-members:` to take arguments, similarly to how `:members:` currently works

**Describe alternatives you've considered**
The current best way to do this is to explicitly list each class in a module and use `:autoattribute:`

- Some prior discussion: https://github.com/sphinx-doc/sphinx/issues/8009

Work only inside this repository checkout. Make the code change the task
describes, keeping the diff focused — no drive-by refactors.

When you are done, leave your changes committed or in the working tree;
they are collected automatically.

Stay on this snapshot checkout (`task/ycb_sphinx_pr8035`). Never checkout, pull, or rebase onto `main`. That branch is a README-only orphan.
Stay on this HEAD. Do not fetch another default branch. Push only on the Cursor-created `crazy-cursor/…` side branch from this HEAD.

Some past runs of this task were launched with a different prompt (the prompt template changed since, or those runs predate this benchmark's stored prompt). Each run persists the exact prompt it sent at launch — that per-launch record is the audit trail; this page shows only the current one.