Add comprehensive README.md documentation

[Copilot]

Creates project documentation for the Progress Agentic RAG + Telerik Blazor UI demo application.

Changes

• Overview: Project description highlighting the AI-powered search + Blazor UI integration
• Product Links: Direct links to Progress Agentic RAG and Telerik UI for Blazor
• Architecture: ASCII diagram showing the layered stack (Blazor → Telerik UI → Nuclia SDK → Agentic RAG)
• Demo Pages: Documentation for all 5 routes (/, /ai-search, /finance-analysis, /knowledge-assistant, /value-proposition)
• Getting Started: Setup instructions including:
  • NuGet feed configuration for Telerik packages
  • Progress Agentic RAG credentials in appsettings.json
  • License/trial requirements
• Configuration: Environment variables and user secrets for production/development
• Project Structure: Directory tree reference

Live demo placeholder badge included for future deployment URL.

Original prompt

@workspace create a readme.md file inside the repo.
Explain technical details, how to run the project. What pages does it have.

Add placeholder to a live demo link.

Also explain that this is a A comprehensive demo application showcasing the powerful integration between Progress Agentic RAG AI-powered search capabilities and Telerik Blazor ui components This application demonstrates how to build intelligent, data-driven interfaces that combine enterprise-grade AI retrieval with beautiful, functional user interfaces.

Also specifit link of the products:

https://www.progress.com/agentic-rag
https://www.telerik.com/blazor-ui

Explain the architecture
Getting stareted.
Installing dependencies (license or trial for blazor is needed)

and more.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[telerik-pr-policy-bot]

Hello @copilot-swe-agent,

This Pull Request appears to be missing a reference to a GitHub Project. All Pull Requests must be linked to a Project, either directly or by referencing an Issue.

Please, link to an Issue included in a Project using the closes, fixes, implements or part of keywords. For example, add Implements #<issue number> to the description.

Alternatively, associate this PR with a Project from the panel on the right and edit the PR description to restart the policy check.

Cheers,
Your friendly Policy Bot