Some vendored minitest page cross-references resolve to nonexistent targets

[skatkov]

Summary

A few generated minitest pages still contain local documentation links that do not map to actual emitted files.

This is separate from the Manifest.txt page problem: these are page-to-page cross-references inside otherwise normal generated docs.

Reproduction

1. Run rake vendor:setup:minitest.
2. Run rake vendor:docs:minitest.
3. Open the generated files below and follow the local links.

Examples

• vendor/docs/minitest/Minitest/Reportable.md:4
  • Emits: [Reporter](Reporter.md)
  • There is no generated Reporter.md page in that directory.
  • The generated reporter pages include names like AbstractReporter.md, CompositeReporter.md, ProgressReporter.md, etc.
• vendor/docs/minitest/Minitest/VendoredPathExpander/Minitest/VendoredPathExpander/Minitest/PathExpander.md:38
  • Emits: ../Minitest.md
  • That relative target does not exist from this nested output path.

Actual Result

Some generated minitest cross-references point to markdown files that are not present in the emitted output tree.

Expected Result

Generated page cross-references should resolve to the actual emitted file path for the target page, or remain plain text if there is no unambiguous target.

Notes

This appears to be a path/name resolution problem for certain page references rather than a markdown rendering failure.

[skatkov]

RDoc master comparison note: this looks fixed by upstream master.

Tested with ruby/rdoc master at bc0baee787609f2205e8f1103f3e1d36b923184a. The reported Minitest examples no longer reproduce:

• Minitest/Reportable.md now renders Reporter as plain text, not [Reporter](Reporter.md).
• The duplicated Minitest/VendoredPathExpander/.../PathExpander.md path is no longer emitted.

Remaining Minitest broken links under master are the :include / :exclude examples tracked by #62.