release: update container and chart versions

[cdgamarose-nv]

No description provided.

[AjayThorve]

LGTM

[greptile-apps]

Greptile Summary

This PR promotes the AIQ blueprint from a staging release candidate to the official 2.0.0 release by updating container image references, Helm chart names, and related documentation across the repository.

Key changes:

• Container images migrated from nvcr.io/nvstaging/blueprint/ (RC versions) to nvcr.io/nvidia/blueprint/ at 2.0.0; the frontend image is also renamed from aiq-frontend-v2 to aiq-frontend
• Helm chart name updated from aiq-web to aiq2-web, and install examples now use the OCI registry path (oci://nvcr.io/nvidia/blueprint/aiq2-web) rather than a traditional Helm repo reference
• FRAG integration examples in kubernetes.md are updated to use the concrete OCI chart reference
• The helm repo update step is correctly removed from the upgrade guide since OCI-based charts do not require it
• The deepresearch_bench benchmark is removed from the root README.md quick-start
• One issue found: the ## Upgrade section in docs/source/deployment/kubernetes.md hardcodes --version 2.0.0, which will mislead users attempting to upgrade to a future version

Confidence Score: 4/5

• This PR is safe to merge with one minor doc fix recommended before the upgrade guide becomes stale.
• All changes are documentation and reference updates with no code logic changes. The only actionable issue is a hardcoded version in the Upgrade section of kubernetes.md, which doesn't affect the current release but will mislead users in future upgrade scenarios.
• docs/source/deployment/kubernetes.md — the ## Upgrade section hardcodes --version 2.0.0 where a <new-version> placeholder is more appropriate.

Important Files Changed

Filename	Overview
docs/source/deployment/kubernetes.md	Updated chart references, image names, and FRAG examples to use OCI registry and version 2.0.0. The Upgrade section incorrectly hardcodes --version 2.0.0 instead of using a <new-version> placeholder, which could mislead users performing future upgrades.
.secrets.baseline	Updated line number reference for a secret in README.md (304 → 303) and refreshed the generated_at timestamp. Housekeeping change, no issues.
README.md	Removed the deepresearch_bench benchmark install line from the quick-start instructions. Straightforward cleanup.
deploy/compose/README.md	Updated container image references from nvcr.io/nvstaging/blueprint/ (RC versions) to nvcr.io/nvidia/blueprint/ at 2.0.0, and renamed the frontend image from aiq-frontend-v2 to aiq-frontend. No issues.
deploy/compose/docker-compose.yaml	Updated in-file comment examples to reflect the same image name and registry changes as the compose README. No issues.
deploy/helm/README.md	Updated the local .tgz install example to aiq2-web-2.0.0.tgz and the example values in the explanatory text from aiq-web/2603.7.0 to aiq2-web/2.0.0. Option B (install from repo) retains generic <version> placeholders, which is consistent and correct.
docs/source/deployment/docker-compose.md	Mirrors the same container image updates applied to deploy/compose/README.md. No issues.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[User deploys AIQ 2.0.0] --> B{Deployment method?}
    B -->|Docker Compose| C[nvcr.io/nvidia/blueprint/aiq-agent:2.0.0\nnvcr.io/nvidia/blueprint/aiq-frontend:2.0.0]
    B -->|Helm - local .tgz| D[helm pull → aiq2-web-2.0.0.tgz\nhelm upgrade --install aiq aiq2-web-2.0.0.tgz]
    B -->|Helm - OCI registry| E[helm upgrade --install aiq\noci://nvcr.io/nvidia/blueprint/aiq2-web\n--version 2.0.0]
    E --> F{FRAG integration?}
    F -->|Yes - internal cluster| G[--set RAG_SERVER_URL=http://rag-server.svc]
    F -->|Yes - external RAG| H[--set RAG_SERVER_URL=http://rag-host:8081/v1]
    F -->|No| I[Standard deployment]

Loading

_{Last reviewed commit: "update helm chart na..."}