Dist::Zilla::Plugin::TrialVersionComment fails and times out

The issue is in Dist::Zilla::Plugin::TrialVersionComment's integration with PPI under PerlOnJava. Start by examining the plugin's source, particularly the transformation of version assignments. Reproduce the failure using the CPAN test run details. Focus on object lifecycle and refcount issues noted in the repository's PPI support documentation. Create a minimal test case that isolates the problem without modifying upstream tests.

Summary

Dist::Zilla::Plugin::TrialVersionComment-0.007 fails under PerlOnJava in
the CPAN compatibility run.

Evidence

• CPAN run: 20260924-085657-82687

• Failing test: t/01-basic.t

• System Perl oracle: all 15 test files passed, 30 tests total.

• PerlOnJava: the test command exceeded the 300-second runtime limit.

• Before the timeout, the plugin produced:

  our $VERSION = '; # TRIAL
  

  The expected output preserves the version literal:

  our $VERSION = '0.001'; # TRIAL
  

The minimal standalone PPI parse/mutate/serialize operation reproduces the
expected output under PerlOnJava, so this appears to require the
Dist::Zilla/PPI integration path rather than being a generic PPI round-trip
failure.

Investigation notes

The repository's PPI support notes already identify unresolved PerlOnJava
object-lifecycle/refcount/DESTROY problems that may explain both the
corrupted transformed content and the long-running test process. This issue
should be reduced to a project-owned minimal reproducer before implementing a
fix; do not change the upstream test.

Acceptance criteria

• Identify the root cause in the Dist::Zilla/PPI integration or PerlOnJava
  runtime.
• Add a permanent focused regression test that passes under system Perl and
  both PerlOnJava backends where applicable.
• Make the plugin's version assignment transformation preserve the original
  version literal and complete within normal test time.
• Re-run the full Dist::Zilla::Plugin::TrialVersionComment test suite.