Release Hygiene for the ranges nobody read

Field notes

The audit starts with Composer manifests, covering both require and require-dev entries, and tests each constraint against a published version list rather than only the current lockfile. It also converts ranges into intervals and checks subset and intersection relationships, which lets the service identify declarations that quietly constrain a dependency tree. The page names composer/semver as its implementation basis and limits the advertised engagement to one repository and five packages. A CI check is described as the final handoff, while the full four-step sequence is only partly visible in the extract.