fix: Infer parameter type from default value when no explicit type annotation

[danadajian]

Summary

• When a custom command parameter has a default value but no explicit TypeScript type annotation (e.g. input1 = 123), the generated interface previously emitted an untyped optional (input1?), which provided no IntelliSense benefit
• The generator now infers number, string, or boolean from numeric, string, and boolean literals respectively, producing correctly-typed optional parameters in the generated interface
• Parameters that already carry an explicit type annotation are unaffected — the explicit annotation always takes precedence

Changes

• Default argument with no type annotation now resolves to a typed optional in the generated Chainable interface
• Supported literal types: number, string, boolean

Test plan

• export function example(input1 = 123) {} → generates example(input1?: number): Chainable
• export function example(input1 = 'hello') {} → generates example(input1?: string): Chainable
• export function example(input1 = true) {} → generates example(input1?: boolean): Chainable
• Existing behaviour for explicitly-annotated defaults (e.g. input2: number = 0) is unchanged

---

Generated with Claude Code

[github-actions]

🎉 This PR is included in version 2.5.2 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)

Your semantic-release bot 📦🚀