fix: stop Statement::Variable from consuming sibling args in list context

[toddr-bot]

Summary

PPI::Statement::Variable was too greedy when appearing inside a function call's argument list. For example, in open(my $fh, ">", $filename), the Variable statement consumed all three arguments (my $fh, ">", $filename) instead of just the declaration (my $fh).

The fix adds a termination check in _lex_statement that ends a Variable statement at a comma when the declaration is in simple form (keyword + symbol). Parenthesized declarations (my ($a, $b)) and top-level initializers (my $x = 1;) are unaffected.

Fixes #25

Changes

• Add comma-termination logic for PPI::Statement::Variable in simple form inside Lexer::_lex_statement
• Add tests for variable declarations inside function call argument lists (open(my $fh, ...), foo(our $x, ...), etc.)
• Add regression tests ensuring top-level declarations with initializers are unchanged

Test plan

• New tests verify Variable statement contains only the declaration tokens when inside list context
• All four declaration types tested: my, our, local, state
• Assignment inside list tested: foo(my $x = 1, $y) correctly keeps my $x = 1
• Regression tests confirm my $x = 1; and my ($a, $b) = (1, 2); are unaffected
• Full test suite (53121 tests across 69 files) passes with zero failures

---

Generated by Kōan /fix

---

Quality Report

Changes: 2 files changed, 83 insertions(+), 1 deletion(-)

Code scan: clean

Tests: skipped

Branch hygiene: clean

Generated by Kōan post-mission quality pipeline