Todor nia update

[todorarabadzhiev]

No description provided.

[Copilot]

Pull request overview

This PR updates the Native Blazor Report Viewer documentation to better describe Report Server for .NET integration (token-based auth), improves the introductory guidance, and makes the referenced Telerik UI for Blazor version configurable via site variables.

Changes:

• Expanded the “Using with Report Server for .NET” article with token-auth context, security guidance, and troubleshooting; also switched the UI dependency version to {{site.blazoruiversion}}.
• Enhanced the “Using Native Blazor Report Viewer” landing article with an overview section, integration options, updated prerequisites, and additional See Also links.
• Updated .gitignore to exclude local/agent-related directories.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
embedding-reports/display-reports-in-applications/web-application/native-blazor-report-viewer/how-to-use-with-report-server-net.md	Adds token-auth-focused setup guidance plus troubleshooting; uses {{site.blazoruiversion}} for UI dependency version.
embedding-reports/display-reports-in-applications/web-application/native-blazor-report-viewer/how-to-use-native-blazor-report-viewer.md	Expands the intro and adds integration option guidance; updates dependency version reference and See Also links.
.gitignore	Ignores /.github/agents and /.nia.

Comments suppressed due to low confidence (1)

embedding-reports/display-reports-in-applications/web-application/native-blazor-report-viewer/how-to-use-with-report-server-net.md:55

• File extensions are inconsistently capitalized here (.RAZOR, RAZOR, RAZOR.CS). Elsewhere in this article and throughout the docs, Razor files are referenced as .razor / .razor.cs. Using the correct casing/extension makes the instructions clearer and avoids suggesting non-existent file types.

	For Blazor WebAssembly applications where the server is not available, the token can be injected on the `.RAZOR` page at build-time. Use `appsettings.{Environment}.json` files (they are bundled at build time) and read the token from the configuration.

	> important Never hardcode tokens directly in client-side code. Always retrieve them from a secure server endpoint or build-time configuration. Store tokens as environment variables or in secure configuration stores, and ensure the token endpoint is properly secured with authentication and authorization.

1. Configure an `HttpClient` in the `Program.cs` file that will be injected on the `.RAZOR` page on the next step when we make an HTTP request to get the token from the server.

---

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