[Paulo Lacerda (placerda)]

Purpose

Post-release DOCUMENTATION maintenance for the already published orchestrator v5.2.1. This is not preparation or publication of a new runtime release.

The coordinating human authorized a one-task direct-main documentation exception after the final whole-set review and focused source review cleared all findings. The existing release/5.2.1 branch was advanced normally from its published release ancestry to stable main plus this reviewed documentation commit. No develop branch was pushed.

Exactly four approved files:

• README.md
• docs/runtime.md
• evaluations/README.md
• infra/README.md

The concise README links to the canonical Azure/AI-Landing-Zones main documentation. The runtime guide documents shipped configuration, identity, retrieval, optional-ingestion boundaries, classic and hosted behavior, TLS limitations, build defaults, classic MCP, Work IQ, generic MCP source schema/credentials/trust, and dashboard Entra setup.

Frozen base: 27f952f.
Reviewed head: a63e043.
Diff: four Markdown files, +564 / -549.

No runtime, configuration, tests, VERSION, CHANGELOG.md, policies, tags, images, packages, GitHub Releases or Azure deployments are changed or published.

⚠️ Important: All pull requests must target the develop branch, not main. PRs targeting main will be automatically blocked.

Task-specific exception: The template notice describes the default contribution route. This human-authorized current-version documentation maintenance PR uses the genuine existing release/5.2.1 branch and targets main. The unchanged source gate must pass. No policy is modified or bypassed.

Contributing guidelines

Please see Contributing Guidelines before creating your Pull Request.

Type of change

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Documentation content changes
• Other... Please describe:

Related Backlog Item or Issue

Coordinating maintainer-authorized documentation audit and publication task. No backlog issue URL was supplied.

Is this change disruptive or does it break existing applications?

No runtime or deployment behavior changes. The published runtime tag remains unchanged.

• Yes
• No

Cross-Repository Dependencies

No runtime or merge-order dependency. Companion ingestion documentation is coordinated independently. The parent task owns central, root, UI and agentic documentation work, none of which is included here.

• agent-landing-zone
• agent-app-orchestrator
• agent-app-ingestion
• agent-app-ui

Does this require changes to project documentation?

Yes. This PR is the reviewed component documentation correction. No new functionality is introduced.

• Yes
• No

Documentation Link

Reviewed runtime guide: https://github.com/Azure/agent-app-orchestrator/blob/a63e043d6c544373eb3b0f43f355aace9414d204/docs/runtime.md

Canonical central source: https://github.com/Azure/AI-Landing-Zones/tree/main/docs/agent-landing-zone

Code quality checklist

• I verified the changes locally to ensure they work as expected
• I have tested the new functionality and ensured existing features still work
• I have updated the CHANGELOG.md file to document these changes
• I have reviewed the code for readability, maintainability, and adherence to project conventions
• I have added at least two reviewers to the Pull Request

Validation and checklist applicability

• Offline relative links, local anchors, fences, punctuation, whitespace and approved-file scope checks passed.
• The documented generic MCP JSON and all four credential metadata forms passed validation against the standalone pinned schema without network or credential operations.
• Source citations, exact approved content, current baseline, release ancestry and active protection were verified.
• The coordinating parent reports whole-set and focused review approval plus scope/style/privacy/fence/whitespace/strict MkDocs checks.
• Fresh required CI must pass for this exact head: quality-gate, tests and frontend build. The block-pr source gate must also pass before normal protected merge.
• Runtime tests were not executed locally. CI supplies the required fresh tests and frontend evidence.
• The new-functionality checkbox is not applicable to this docs-only change. CHANGELOG.md is deliberately unchanged under the explicit maintenance scope.
• No two GitHub reviewer requests were added because no reviewer identities were supplied. The checklist is left unchecked rather than claiming requests were made. Coordinating human review has cleared the documentation, and configured PR protection remains in force.
• No Azure access, deployment, image build/publication, tag or release workflow is requested.