# Constructor arguments the .pyi marks omittable that the binding requires, and
# that doppler cannot fix on its own. Both faces are jm-generated, so there is
# no local change that makes them agree — only the upstream one. Each entry is
# `Class.param`, and check_init_param_optionality.py reports an entry that has
# stopped diverging, so this list cannot quietly outlive its reason.
#
# EMPTY as of just-makeit 0.53.1. `MemoryCapture.clock` and `Capture.clock`
# were the last two, and the fix arrived on the STUB side, not the binding:
# gh-845 made the module-aggregated .pyi producer test capsule-ness directly
# instead of inferring it from the manifest's `required` flag, so the stub now
# renders `clock: object | None` — a required positional, which is what the
# binding has always demanded. The argument is still not omittable, and that
# is now stated honestly on both faces rather than being a divergence.
#
# Worth keeping in mind if this list ever refills: the two axes are separate.
# `clock=None` being ACCEPTED (gh-805 §H, 0.53.0) and `clock` being OMITTABLE
# are different questions, and only the first was ever in play here.
