Historical record, labelled October 19, 2026. This check ran on October 1, 2026, before Practical Picks adopted its research-only method (October 3, 2026). It is kept as dated, bounded evidence about the versions named below. We no longer run product checks, and this record did not decide the current Pick. The October 19, 2026 article no longer names AuditAPI. Practical Picks PP-252 local check, October 1, 2026 Date: 2026-10-01 UTC Environment: Linux x86_64; Node 22.23.3; npm 10.9.9. Scope: static lint of one fictional OpenAPI 3.0.3 file and a repaired control. Fixtures: /assets/pp252/bad.yaml and /assets/pp252/clean.yaml The bad file omits a definition for path parameter {taskId}. The clean file defines it. The clean file deliberately has no security declaration, license, global tag entry, or example data. Those omissions can activate style policy; they do not make the path parameter invalid. Spectral CLI 6.16.3, with a local ruleset file containing only extends: spectral:oas Command: spectral lint bad.yaml --ruleset .spectral.yaml --format stylish Result: exit 1; 1 error, 6 warnings. Error: path-params at 7:9, "Operation must define parameter {taskId} as expected by path /tasks/{taskId}." Clean control: exit 0; one operation-tag-defined warning. With --fail-severity warn, the same clean control exits 1. Redocly CLI 2.57.0 Command: redocly lint bad.yaml --format=stylish Result: exit 1; 3 errors, 3 warnings. Errors: no-empty-servers, path-parameters-defined at 7:5, security-defined. The path error says the operation does not define {taskId} expected by /tasks/{taskId}. Clean control on default recommended rules: exit 1 on security-defined; one info-license warning. That is a default governance preference. Command: redocly lint bad.yaml --extends=spec --format=stylish Result: exit 1; one path-parameters-defined error, no other findings. Clean control with --extends=spec: exit 0, no findings. Vacuum 0.30.6, downloaded Linux x86_64 release binary Archive SHA-256: 179f038a71cd88721738d6c739dd07fbeebc905b48301935f2416e66aead95c6 The digest matched the release checksums.txt. Command: vacuum lint bad.yaml --details Result: exit 1; 3 errors, 7 warnings. Errors include missing path parameter, info description and operation ID. Clean control: exit 0; 6 warnings for missing global tag, examples and schema description. With --fail-severity warn, the clean control exits 1. New entrant: AuditAPI 1.2.0 Command: auditapi audit bad.yaml --json Result: exit 1, grade F, 17 findings including path-params. Clean control: exit 1, grade F, 11 findings. Fatal errors require security declaration and prohibit inline parameter schemas for this public/no-auth API. It was not suitable for this first merge gate; no Rising Star awarded. No remote references, large files, custom rules, published documentation, real CI runner, timing benchmark, package security, or service reliability was tested. The files are local and no listener was started.