v0.1.2

What's new

change_method_signature — change parameter types (param_types)

The signature refactoring now accepts a param_types option to substitute
parameter types without removing or adding parameters:

• param_types alone applies type changes to the declaration only
  (e.g. int → long).
• Combined with paramOrder, the type substitutions are woven into the
  reordered parameter text, so both axes compose.
• Overloaded-target disambiguation also landed: identical tool descriptions
  across operations were tightened, and remove_param now cross-references
  change_method_signature for the "change type without removal" case.

CLI: --param-types option added to ChangeMethodSignatureCommand.

widen_visibility option for pull-up and move refactorings

Five refactorings that move members across class/package boundaries gain a
boolean widen_visibility option (default true):

• pull_up_field / pull_up_method: private → protected in the superclass
• move_method: private → package-private (same package) or public (cross-package)
• move_static_member: same minimum-required visibility logic
• move_class: package-private class → public when crossing packages

Existing call signatures are unchanged (they delegate with true). Ten new
approval tests cover the true/false pair per refactoring.

Full Changelog: v0.1.1...v0.1.2