[JarryShaw]

• 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
• Added a changelog entry under docs/source/changelog/ and regenerated CHANGELOG.md

What is the purpose of your pull request?

• fix — corrects a defect

---

Description of your pull request and other information

16 of the 24 dict-based pcapkit.vendor crawlers' process(self, data) ignored the data
argument and read the module-level DATA literal instead. Harmless today, since every real
call site passes request()'s own DATA-returning value, so data is DATA always held in
practice — but a caller passing different data would have gotten the module's table back
regardless, with no error.

pcapkit-vendor regenerates pcapkit/const/, not pcapkit/vendor/ itself, so these
hand-written crawlers needed no template fix and no const/ regeneration follows.

New test (tests/vendor/test_vendor_process_uses_passed_data_2429_unit.py) drives each
crawler's count()/process() on a fabricated registry and proves the output now reflects
the argument rather than the module global; confirmed to fail against the unfixed code first.

Closes #2429.

[github-actions]

Coverage: 94.44% (unit tier, Python 3.15, fd12a4c0a, Unit Tests run success)

Package	Statements	Missed	Branches	Partial	Cover
pcapkit (top level)	104	4	20	2	95.16%
pcapkit/const	19609	133	2620	120	98.84%
pcapkit/corekit	2605	74	818	37	96.52%
pcapkit/dumpkit	282	3	102	3	98.44%
pcapkit/foundation	3064	24	1068	26	98.79%
pcapkit/interface	138	4	52	3	96.32%
pcapkit/protocols	17593	193	4678	179	98.32%
pcapkit/toolkit	924	36	334	10	95.55%
pcapkit/utilities	502	7	144	5	98.14%
pcapkit/vendor	4449	1854	1020	167	55.11%

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

[JarryShaw]

Review: NEEDS CHANGES at b2e69d9ec (Sonnet). Code fix itself is correct — every factual claim held, 101 of 118 subtests fail with exactly the 16 sources reverted. Two text-only blockers:

1. Counted numbers in prose, violating the standing no-counted-numbers convention (ruled 2026-10-15, docs/source/contributing/conventions/documentation.rst:228; 1.5.0 is unreleased so this applies): "16 of the 24 dict-based crawlers" in CHANGELOG.md/1.5.0.rst, and in the new test's docstring/comments. The file lists already enumerate the modules — the count adds nothing. Same pattern test(hip): drop counted numbers from the #2394 str-name test #2402 fixed for fix(hip): resolve a str enum name in list-argument makers too #2401.
2. The test docstring says the fabricated mapping "shares the module's codes" but the actual fabricated codes (900001/900002) are described two lines later as "well outside any real range" — contradicts itself.

Non-blocking: test_process_does_not_fall_back_to_the_module_table doesn't actually catch ipv4/tos_ecn (swapping vendor.record between its two calls changes output on its own, independent of the fix) — the sibling test still catches it, so not blocking, but worth tightening. Also: the test only covers the 16 hard-coded modules, so a future crawler could regress unnoticed — acceptable for this PR's scope.

Everything else independently re-verified: AST walk over all 97 process(self, data) methods confirms exactly 16 affected (matching the PR/issue list exactly), confirmed no vendor template writes to pcapkit/vendor/ (only pcapkit/const/ is generated), confirmed harmless-until-now (data is DATA held on every real path, rendered const text byte-identical base vs head), full tests/vendor/const/registry/template suites green, mypy/pylint/isort identical to base.

[JarryShaw]

Review: GOOD TO GO at fd12a4c0a. Verified directly (main thread). Both text-only fixes confirmed: counted numbers removed from CHANGELOG.md/1.5.0.rst/the test file (checked directly — no "16 of"/"of the 24" remains), and the module docstring now correctly says the fabricated codes are "disjoint from the module's own DATA" instead of the self-contradicting "shares the module's codes".

tests/vendor/ suite: 190 passed, 2209 subtests. isort clean; mypy's 13 errors are entirely in tests/_support.py, confirmed pre-existing on main. Code fix content unchanged from the prior round's independent verification.