Plan next CPAN ports and bundled providers from dependant ranking

[fglock]

Objective

Use dev/design/cpan-port-prioritization.md to turn CPAN dependency impact into the next PerlOnJava porting and bundling plan.

Required work

1. Recreate the dependant ranking with dev/tools/cpan_port_priorities.pl and record the command, report revision, cache scope, and truncation status.
2. Validate a representative sample against targeted MetaCPAN reverse-dependency queries and system Perl.
3. For the highest-impact candidates, decide whether the correct action is a compiler/runtime fix, pure-Perl port, bundled Java provider, compatibility shim, or explicit deferment.
4. Create implementation issues for the selected ports/providers, including dependant counts, failure evidence, owners, and acceptance gates.
5. Define the provider manifest that will be shared by CPAN resolution, bundled-module documentation, and the prioritization tool.
6. Design the scheduled report refresh and upgrade-proposal workflow, with throttling, isolated worktrees, conformance testing, and rollback.

Acceptance criteria

• A reviewed, ranked queue of next porting/bundling targets exists.
• Each selected target has a documented rationale and system-Perl comparison.
• Provider inventory and shadowing policy are specified for bundled modules.
• The automation plan produces reviewable upgrade proposals rather than silently merging upgrades.
• Progress and open questions are updated in the design document.