rubydoc: undo temporary yard fix

[GunniBusch]

---

• Have you followed the guidelines in our Contributing document?
• Have you checked to ensure there aren't other open Pull Requests for the same change?
• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you written new tests (excluding integration tests) for your changes? Here's an example.
• Have you successfully run brew lgtm (style, typechecking and tests) with your changes locally?

---

• AI was used to generate or assist with generating this PR. Please specify below how you used AI to help you, and what steps you have taken to manually verify the changes.

---

Undo the temporary change made by #21589. The issue was solved by lsegal/yard@ae63056

Edit:

Of course it also bumps yard.

[Copilot]

Pull request overview

Removes the temporary Homebrew-side YARD JavaScript workaround now that the underlying issue has been fixed upstream in YARD, and updates the locked YARD version accordingly.

Changes:

• Bump yard from 0.9.38 to 0.9.39 in Library/Homebrew/Gemfile.lock.
• Remove the temporary app.js patch file and the workflow step that applied it.
• Drop the locally-vendored app.js override under Library/Homebrew/yard/templates/....

Reviewed changes

Copilot reviewed 3 out of 4 changed files in this pull request and generated no comments.

File	Description
Library/Homebrew/yard/templates/default/fulldoc/html/js/app.js.patch	Removes the now-unneeded patch that modified YARD’s app.js.
Library/Homebrew/yard/templates/default/fulldoc/html/js/app.js	Removes the local JS override so upstream YARD’s template JS is used.
Library/Homebrew/Gemfile.lock	Updates the locked YARD version to include the upstream fix.
.github/workflows/docs.yml	Stops applying the patch during docs builds since it’s no longer needed.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[MikeMcQuaid]

Thanks again @GunniBusch!

[GunniBusch]

Thanks again @GunniBusch!

Thank you and your team for maintaining the best package manager!