Revise Arcade validation links in README.md

[ViktorHofer]

Updated links for Arcade validation policy and process.

To double check:

• The right tests are in and the right validation has happened. Guidance: https://github.com/dotnet/arcade/blob/main/Documentation/Validation.md

[Copilot]

Pull request overview

Updates the repository README’s “Validation & Dependency Flow Status” section to point to newer Maestro “latest build” pages, aiming to keep validation-related references current and discoverable for contributors.

Changes:

• Updated the two Maestro links for “Current Version of Arcade…” and “Latest Version of Arcade Being Validated” to .../channel/.../build/latest URLs.
• Removed the README link to the Arcade validation policy/process documentation.
• Removed the “Arcade Validation” build status badge row from the Build Statuses table.

Show a summary per file

File	Description
README.md	Updates Maestro links and adjusts validation/build-status references in the README.

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

• Files reviewed: 1/1 changed files
• Comments generated: 3

[Copilot]

Copilot's findings

Comments suppressed due to low confidence (1)

README.md:12

• The README removed the validation-policy link, and the table column header now says “BarViz Link” but the URLs point to Maestro “build/latest” pages rather than a BarViz graph. Consider restoring a validation-doc link and renaming the column header to match the new link type.

|Flow|BarViz Link|
|---|---|
|Current Version of Arcade in `.NET Eng - Latest`|[Link](https://maestro.dot.net/channel/2/azdo:dnceng:internal:dotnet-arcade/build/latest)|
|Latest Version of Arcade Being Validated|[Link](https://maestro.dot.net/channel/9/azdo:dnceng:internal:dotnet-arcade/build/latest)|

• Files reviewed: 2/2 changed files
• Comments generated: 1

[Copilot]

Copilot's findings

Comments suppressed due to low confidence (2)

README.md:12

• The validation policy/process link was removed here, but the repo has a current doc at Documentation/Validation.md. Consider restoring a link to that doc above this status table (and update the column header to match the new maestro “build/latest” URLs, which no longer look like BarViz graph links).

|Flow|BarViz Link|
|---|---|
|Current Version of Arcade in `.NET Eng - Latest`|[Link](https://maestro.dot.net/channel/2/azdo:dnceng:internal:dotnet-arcade/build/latest)|
|Latest Version of Arcade Being Validated|[Link](https://maestro.dot.net/channel/9/azdo:dnceng:internal:dotnet-arcade/build/latest)|

Documentation/Policy/TestingMSBuildGuidance.md:23

• This link uses an anchor into ../Darc.md, but Darc.md in this repo is a redirect stub and does not include the “#updating-dependencies-in-your-local-repository” section, so the anchor won’t resolve. Link to Darc.md without the anchor (or directly to the target doc that contains the section).

    Your private build of Arcade will be pushed to that feed when you publish it to the `General Testing` channel.
5. Using darc, run `update-dependencies` ([update-dependencies documentation](../Darc.md#updating-dependencies-in-your-local-repository)) on your branch to use the build of Arcade you just created in the previous steps. 
6. Build your project and run the project's unit tests locally, and/or build your branch with your project's Azure DevOps pipeline. Ensure that the build pipeline executes any tests (unit, integration, scenario, et cetera).

• Files reviewed: 2/2 changed files
• Comments generated: 1

[Copilot]

Copilot's findings

Comments suppressed due to low confidence (2)

README.md:10

• The README’s validation section no longer links to the validation policy/process doc. The previous link targeted Documentation/Validation/Overview.md (which doesn’t exist), but we should keep a discoverable link by updating it to Documentation/Validation.md instead of removing it entirely.

## Validation & Dependency Flow Status

|Flow|BarViz Link|
|---|---|

Documentation/Policy/TestingMSBuildGuidance.md:22

• This link includes a fragment to ../Darc.md, but Documentation/Darc.md is a redirect stub without headings, so the #updating-dependencies-in-your-local-repository anchor won’t resolve. Link directly to the arcade-services Darc docs (which the stub points to) with the fragment.

5. Using darc, run `update-dependencies` ([update-dependencies documentation](../Darc.md#updating-dependencies-in-your-local-repository)) on your branch to use the build of Arcade you just created in the previous steps. 

• Files reviewed: 7/7 changed files
• Comments generated: 1

[Copilot]

Copilot's findings

Comments suppressed due to low confidence (4)

README.md:9

• The README no longer links to the validation policy/process, even though the PR description calls out updating that guidance. Also, the column header says "BarViz Link" but the new URLs point to Maestro channel "build/latest" pages (not BarViz graphs). Consider adding a link to Documentation/Validation.md here and renaming the column header accordingly.

## Validation & Dependency Flow Status

|Flow|BarViz Link|

Documentation/Policy/TestingMSBuildGuidance.md:22

• This link uses an anchor on ../Darc.md, but Documentation/Darc.md in this repo is a redirect stub and does not define anchors, so the fragment won’t resolve. Link directly to the arcade-services Darc docs (where the content lives) instead.

5. Using darc, run `update-dependencies` ([update-dependencies documentation](../Darc.md#updating-dependencies-in-your-local-repository)) on your branch to use the build of Arcade you just created in the previous steps. 

Documentation/Policy/ArcadeServicing.md:76

• This Darc link uses an anchor on ../Darc.md, but Documentation/Darc.md in this repo is a redirect stub and does not define anchors, so the fragment won’t resolve. Link directly to the arcade-services Darc docs instead.

3. [Add new channels](../Darc.md#add-channel)

Documentation/Policy/ArcadeServicing.md:88

• This Darc link uses an anchor on ../Darc.md, but Documentation/Darc.md in this repo is a redirect stub and does not define anchors, so the fragment won’t resolve. Link directly to the arcade-services Darc docs instead.

4. [Add default channel associations](../Darc.md#add-default-channel)

• Files reviewed: 7/7 changed files
• Comments generated: 2

[Copilot]

Copilot's findings

Comments suppressed due to low confidence (3)

README.md:11

• The README no longer links to the validation policy/process docs, and the table column header still says "BarViz Link" even though the links now go to the Maestro "build/latest" page (not a BarViz graph). Consider restoring a validation doc link and updating the header to match the new URL type.

## Validation & Dependency Flow Status

|Flow|BarViz Link|
|---|---|
|Current Version of Arcade in `.NET Eng - Latest`|[Link](https://maestro.dot.net/channel/2/azdo:dnceng:internal:dotnet-arcade/build/latest)|

Documentation/Policy/ArcadeServicing.md:76

• This link includes a section anchor, but Documentation/Darc.md is a redirect stub (no headings), so #add-channel won’t resolve. Use an un-anchored link (or link directly to the new Darc docs location).

3. [Add new channels](../Darc.md#add-channel)

Documentation/Policy/ArcadeServicing.md:88

• This link includes a section anchor, but Documentation/Darc.md is a redirect stub (no headings), so #add-default-channel won’t resolve. Use an un-anchored link (or link directly to the new Darc docs location).

4. [Add default channel associations](../Darc.md#add-default-channel)

• Files reviewed: 7/7 changed files
• Comments generated: 1