Description

Fixes #19770 - JavadocTypeCheck incorrectly matches record component @param tags using prefix instead of exact match.

Root Cause

In JavadocTypeCheck.checkComponentParamTag(), the matching logic used indexOf() == 0:

.anyMatch(tag -> tag.getFirstArg().indexOf(recordComponentName) == 0);

This means any @param tag whose argument starts with the component name as a prefix would match. For example, with a record component named john, @param john123 was incorrectly treated as documenting john because john123.indexOf(john) == 0.

Fix

Changed to exact match or space-separated match:

.anyMatch(tag -> {
    final String arg = tag.getFirstArg();
    return arg.equals(recordComponentName)
            || arg.startsWith(recordComponentName + " ");
});

This ensures:

• @param john matches record component john (exact match)
• @param john some description matches record component john (name + space prefix)
• @param john123 does NOT match record component john (different name)

The existing checkUnusedParamTags() already uses extractParamNameFromTag() which properly extracts the param name via regex, so it correctly reports john123 as an unused tag.

Testing

Added InputJavadocTypeRecordComponentPrefixMatch.java test case that reproduces the exact scenario from issue #19770.