[JarryShaw]

Please follow the guide below

• You will be asked some questions, please read them carefully and answer honestly

• Put an x into all the boxes [ ] relevant to your pull request (like that [x])

• Use Preview tab to see how your pull request will actually look like

• Searched for similar pull requests

• Followed the coding style (make pylint, make mypy, make isort)

• make test passes, and a test case covers the change. Narrow runs only, listed below.

• Added a changelog entry under docs/source/changelog/ and regenerated CHANGELOG.md, if the change is user-visible: N/A — centralised in docs(changelog): shared 1.5.0 changelog — long-lived, merges last (#610, #616, #617, #618, #620) #657

What is the purpose of your pull request?

Tick the commit type your subject line carries.

• fix — corrects a defect
• feat — adds a feature
• perf — changes performance, not behaviour
• refactor — changes neither behaviour nor performance
• test — tests only
• docs — documentation only
• ci — workflows or build tooling
• release — bumps the version or rolls up a distribution
• chore — anything else

---

Counted numbers:

• Drop counts from workflow comments, the release-notes and coverage
  configs, README, CONTRIBUTING, MANIFEST.in, the Makefile, pyproject.toml
  comments, util/ docstrings, and the examples' docstrings and READMEs.
• Replace lint.yml's finding tables with why the header keeps none; the
  measurements that justify a design choice stay, stated as measurements.
• Keep the edits to line-cited files line-neutral, so the citations hold.

Accuracy:

• lint.yml: pcap-ct is also absent, so it is an import-error source too.
• release.yml: dependencies PRs come from pyup and Dependabot, feat and
  fix never overlap each other, and the category is "Fixes".
• CONTRIBUTING: which _OPT_Option siblings stay documented.
• legacy.py's frame-range comments, _engine_support.py's engine claim and
  cron-conda.yml's stale create-release.yml line citation.

Non-prose check: ast.dump is unchanged once docstrings are blanked; any workflow, TOML or script edits are comment-only (parsed and compared). Narrow test runs are green (tests/project and the tests that read edited files).

Refs #1103

[JarryShaw]

Verdict: NEEDS CHANGES at 0232dd812 (merged as 91c4772ae). A Sonnet cross-review (author: Opus) confirmed:

• each generalised create-release.yml comment against the jobs it describes;
• the release.yml claims: dependency PRs come from pyup and Dependabot, and no PR carries both feat and fix;
• pcap-ct as a lint import-error source;
• the legacy.py frame ranges, by regenerating the capture;
• line neutrality for every file:line citation in the repo;
• the YAML, TOML and AST equivalence. It also ran the workflow tests: test_release_gates (125) and the others, all passing.

Two blocking defects, both re-checked on main. In each, a removed count became a false "every":

• create-release.yml:151 "only for every job below to skip": vendor_update, version_check and release_status do not skip, only the publishers do;
• unit-tests.yml:685-686 "loops over every interpreter … every Python times every engine": the same comment excludes 3.7-3.9.

These are workflow files, so the fix goes in a follow-up PR.