[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

---

Follow-up to #1830's review (verdict on #1830). Comments and docstrings only.

• create-release.yml: the gate skips only for the publishers, not "every job below", because vendor_update, version_check and release_status run. The version_check == 'success' clause is attributed to tag, pypi and conda, since github lacks it.
• unit-tests.yml: the engine jobs loop over their own interpreters, which excludes 3.7-3.9, not "every interpreter".
• legacy.py: the capture covers a FIN-completed stream and an RST-aborted one. The submit triggers are listed in full: SYN restart, window gap, timeout and end of capture.
• run_unittest_leg.py: drops a test-count ordering claim that no longer holds.
• release.yml: re-wraps an over-long line.

Checks:

• each workflow parses to the same YAML once comment lines are stripped;
• the workflow hunks are line-neutral, so file:line citations hold;
• ast.dump is unchanged with docstrings blanked;
• test_release_gates and the other tests/project files that read these workflows pass.

Refs #1103

[JarryShaw]

Verdict: GOOD TO GO at 20fd20f39. A Sonnet cross-review (author: Opus) parsed create-release.yml and confirmed two things:

• with a non-v* ref and all evidence 'true', only the publishers skip, while release_status and version_check run;
• tag, pypi and conda carry version_check == 'success' and github does not.

It also confirmed:

• util/python_versions.py engine-supported engine-ktlo lists 3.10–3.15 only;
• legacy.py, by tracing TCP.submit on the generated captures: every datagram comes from its own FIN or RST, and a half-closed connection gives a datagram per direction;
• that the list of submit triggers is complete (every call site);
• run_unittest_leg.py's test counts.

YAML is equal, the ASTs are equal, and the workflow hunks are line-neutral; test_release_gates and test_workflows_at_a_glance_1732 pass. Non-blocking: the ~37s for interface in run_unittest_leg.py still differs from the table's 38s.

[github-actions]

Coverage: 90.05% (unit tier, Python 3.15, 20fd20f39, Unit Tests run success)

Package	Statements	Missed	Branches	Partial	Cover
pcapkit (top level)	104	2	20	2	96.77%
pcapkit/const	19595	881	2618	867	92.11%
pcapkit/corekit	2462	69	780	35	96.55%
pcapkit/dumpkit	276	3	100	3	98.40%
pcapkit/foundation	2915	164	1016	34	93.59%
pcapkit/interface	138	7	52	5	93.68%
pcapkit/protocols	17408	224	4580	189	98.10%
pcapkit/toolkit	872	177	298	8	77.18%
pcapkit/utilities	512	2	158	4	99.10%
pcapkit/vendor	4407	2342	1010	157	43.27%

Per-file detail: the coverage-html artifact of this run.