[exKAZUu]

Why

Typed parameters lack the name field that defaulted parameters expose, forcing consumers to infer which child represents the name. This addresses the typed-parameter inconsistency reported in tree-sitter/tree-sitter-python#199.

Requirements

• required: Improve our forked grammar repositories, ignoring backward compatibility, with a dedicated PR for each actionable upstream item.
• chosen: Expose the existing typed parameter name or splat pattern through a name field, matching the pattern-valued names already supported by default parameters without changing parameter node kinds.

Customer Summary

Queries can select ordinary, variadic positional, and variadic keyword typed parameter names directly through typed_parameter name:.

Technical Summary

Add a field to the existing typed-parameter alternatives and regenerate the parser and node metadata. Splat names point to their existing pattern nodes. Update corpus field expectations and test querying real parsed declarations through the published WASM API.

Testing

• bun run verify passed; code-gauge reports no violations in changed code.
• bun wb test test/unit/typedParameterNames.test.ts test/unit/corpus.test.ts passed, including all 207 corpus cases.
• The regression query fails on the previous grammar because typed_parameter name: is invalid.
• PR CI passed, including full integration and Rust checks.
• Five automated reviewers completed without findings. The completion revision was reviewed by at least one successful exploration session; full coverage is unverified.