ChangePackage/ChangeType do not apply to package-info.java Javadoc

[SamBarker]

What version of OpenRewrite are you using?

v8.91.3 (latest)

What is the smallest, simplest way to reproduce the problem?

ChangePackage fails to rewrite {@link} references in a package-info.java file's Javadoc.

Recipe:

new ChangePackage("org.openrewrite", "org.openrewrite.test", true)

Before (package-info.java):

/**
 * See {@link org.openrewrite.Existing}
 */
package com.example;

What did you expect to see?

/**
 * See {@link org.openrewrite.test.Existing}
 */
package com.example;

What did you see instead?

No change — the recipe silently no-ops on the file. The same Javadoc on a class instead of a package declaration is rewritten correctly.

[SamBarker]

I looked at this a bit. package-info.java's leading Javadoc comment doesn't seem to get routed through the Javadoc parser at all for the package declaration — ReloadableJava{17,21,25}ParserVisitor.visitCompilationUnit captures it via a plain format() call rather than the docCommentTable lookup that class/method declarations get, so it ends up as an inert TextComment rather than a structured Javadoc.DocComment.

I poked at wiring that lookup up (keying it to CompilationUnitTree.getPackage()), and got as far as the comment parsing structurally without crashing. But the type resolution for {@link} targets (ReloadableJava{N}JavadocVisitor.visitReference) relies on attr.attribType(ref.qualifierExpression, symbol), which needs a class-scoped symbol registered in javac's Enter.typeEnvs to build an attribution environment — and packages don't have one. At that point it stopped feeling like something I could confidently finish without more experience in this part of the parser, so I backed out my exploratory changes rather than submit something half-working.

Opening this with just a minimal failing test, in case it's useful as a starting point or if someone with more context on the attribution machinery wants to pick it up: #8732