Ruleset: no inline schemas and no sentinel maxLength

[ExtraToast]

What to build

Two structural rules: schemas must be named rather than inlined, and a sentinel maximum length is not a valid constraint.

Inline schemas produce anonymous generated types that are painful to reference from application code, and the sentinel maximum is spec noise that travels into every generated client and into generated validation as a meaningless bound.

Acceptance criteria

• An inline response or request schema fails the check
• A sentinel maximum length fails the check
• Any existing violations are extracted or corrected in this same change
• Both rules are shown to fail against deliberately bad fixtures

Blocked by

• Add vacuum lint inputs and a ruleset requiring operationId
• Stop springdoc emitting a sentinel maxLength for unbounded size constraints