chore(LLMs): add LLMsDocsGenerator tool

[ArgoZhang]

Link issues

fixes #8135

Summary By Copilot

Regression?

• Yes
• No

Risk

• High
• Medium
• Low

Verification

• Manual (required)
• Automated

Packaging changes reviewed?

• Yes
• No
• N/A

☑️ Self Check before Merge

⚠️ Please check all items below before review. ⚠️

• Doc is updated/provided or not needed
• Demo is updated/provided or not needed
• Merge the latest code from the main branch

Summary by Sourcery

Build:

• Register the LLMsDocsGenerator as a local .NET tool in dotnet-tools.json and configure its usage in the build pipeline.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Adds a new dotnet tool and build target wiring for an LLMsDocsGenerator utility, integrating it into the server project’s tooling/build pipeline.

File-Level Changes

Change	Details	Files
Register LLMsDocsGenerator as a .NET local tool and configure its basic usage.	Add a new tool entry for the LLMsDocsGenerator to the dotnet-tools manifest so it can be restored and invoked via dotnet tool commands Set or update tool version and command alias to match project conventions for other documentation-related tools	dotnet-tools.json
Wire the LLMsDocsGenerator into the server build targets so it can be invoked as part of the build/docs workflow.	Add or update an MSBuild target in the server Directory.Build.targets to invoke the LLMsDocsGenerator tool Configure target conditions (e.g., only on certain configurations or when specific properties are set) and outputs to avoid unnecessary runs Align the new target with existing documentation-generation targets (ordering, dependencies, and properties)	src/BootstrapBlazor.Server/Directory.Build.targets

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've left some high level feedback:

• Consider pinning the LLMsDocsGenerator tool to a specific, non-floating version in dotnet-tools.json to avoid unexpected build behavior when new versions are released.
• If this tool is invoked in Directory.Build.targets, ensure its execution is conditioned (e.g., on a property or target) so local builds and CI can opt out when the tool is not available or needed.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Consider pinning the LLMsDocsGenerator tool to a specific, non-floating version in dotnet-tools.json to avoid unexpected build behavior when new versions are released.
- If this tool is invoked in Directory.Build.targets, ensure its execution is conditioned (e.g., on a property or target) so local builds and CI can opt out when the tool is not available or needed.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[bb-auto]

Auto approved by bb-auto

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (4165b93) to head (7cbb16d).

Additional details and impacted files

@@            Coverage Diff            @@
##              main     #8136   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          766       766           
  Lines        34213     34213           
  Branches      4696      4696           
=========================================
  Hits         34213     34213           

Flag	Coverage Δ
BB	100.00% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.