Complete the hosted administrative panel after the no-panel preview release

[placerda]

Summary

Complete and validate the optional administrative panel after the first hosted-agent preview ships with DEPLOY_ADMINISTRATIVE_PANEL=false.

Why will we implement this?

• Problem / opportunity: The hosted/no-panel path can ship independently, but the panel still lacks a cross-repository contract for reading Microsoft Foundry managed Conversation history. The current ingestion draft correctly returns 501 Not Implemented rather than fabricating history.
• Business value / outcome: Operators receive a complete, supportable panel for conversation history, feedback, curation, and dashboard workflows without delaying the hosted/no-panel preview.
• Success metrics (how we know it worked): Hosted/panel deploys with exact released pins, retrieves managed Conversation history through an explicit authorized contract, renders the panel frontend, preserves feedback/curation behavior, and passes live panel topology/runtime tests.

What does it do? (Functional Overview)

• Core behavior: Define the managed Conversation history API across UI, orchestrator, ingestion, and Microsoft Foundry. Complete the panel frontend and replace the intentional 501 response with the implemented fail-closed path.
• Data collection / storage needs: Continue using Foundry managed Conversations for hosted chat history and Cosmos DB only for panel feedback/curation data. Do not duplicate protected conversation content into new stores.
• Data analysis / reporting needs: Validate authorization, correlation, error behavior, retention ownership, and telemetry without logging tokens or protected content.
• Nice to have (stretch goals): Automated hosted/panel regression coverage in an approved isolated validation environment.

Components

• **Components (check all that apply):
  • gpt-rag-orchestrator
  • gpt-rag-ingestion
  • gpt-rag-ui
  • gpt-rag-mcp

Acceptance criteria

• The managed Conversation history contract is versioned and documented.
• The panel frontend supports history, feedback, curation, and overview without success-shaped placeholders.
• Missing identity, configuration, or Foundry access fails closed with a controlled error.
• Hosted/panel passes a live deployment and runtime validation with immutable component pins.
• User and operator documentation is updated before the panel is marked supported.

Release relationship

The first hosted-agent preview intentionally supports hosted/no-panel only. Keep DEPLOY_ADMINISTRATIVE_PANEL=false for that release. This issue owns enabling and promoting hosted/panel later.