[Paulo Lacerda (placerda)]

Purpose

Correct the short README's deployment guidance for the shipped v4.3.0 behavior:

• Link to accurate first-deployment guides instead of presenting generic azd up as the full deployment procedure.
• Explain that the orchestrator agent runs in Microsoft Foundry by default, with the classic Container Apps topology still available.
• Distinguish the optional ingestion Container App and native Foundry IQ Blob ingestion from chat attachment uploads, while noting that existing environments retain their ingestion selection.
• Direct users to select a custom app-definition.json before the first provision.

This is docs-only post-release maintenance of the existing v4.3.0 release, not a new release. The complete root diff is README.md only (+7/-5). No runtime code, component pins, versions, tags, application images, configuration, workflows, or diagrams change.

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: N/A

Related Backlog Item or Issue

If applicable, provide a link to the relevant backlog item or issue.

N/A - coordinated documentation-accuracy maintenance.

Is this change disruptive or does it break existing applications?

If deploying this change could impact existing applications, please specify.

• Yes
• No

N/A - documentation only; no application or deployment behavior changes.

Cross-Repository Dependencies

If this change depends on pull requests in other repositories within the solution, provide the links below.

• agent-app-orchestrator
• agent-app-ingestion
• agent-app-ui

N/A for runtime-component changes. The coordinated 35-document accuracy and plain-English audit is already published in the central documentation at Azure/AI-Landing-Zones commit ace06d7.

Does this require changes to project documentation?

If the changes add new functionality, update the documentation accordingly.

• Yes
• No

The README now agrees with the already-published central documentation. No new functionality is introduced.

Documentation Link

If this change adds a new functionality, provide a link to its documentation.

N/A for new functionality. Relevant existing guides:

• Deploy full stack
• Deploy infrastructure only
• Ingestion selection
• Custom applications

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 reviewed the code for readability, maintainability, and adherence to project conventions
• I have added at least two reviewers to the Pull Request

Functionality testing is N/A for this docs-only change. Reviewer assignment is N/A for this bounded PR-creation handoff; no reviewers have been added.

Validation

• Approved root head: 4c2a1b148c8fc4b34b5f8a63784a8ef6624b0e01; verified against main at 574a3f732ce25248d693ed2753950cee07ebea1b with only README.md changed (+7/-5).
• Root git diff --check origin/main...HEAD passed; worktree is clean.
• The coordinated audit passed final 35-document style, privacy, code-fence, and whitespace checks, plus a strict MkDocs build.
• The final whole-set rubber-duck review completed before publication; all three findings were corrected and verified.
• No Azure, live-authentication, or deployment tests were run. CI and SHA-guarded normal merge remain with the coordinating maintainer.