Define an strategy to avoid having two different copilot-instructions.md

[vhvb1989]

In PR#5557 , we introduced a new sub-folder .github/copilot-instructions.md for cli/azd.
This will make us maintain 2 different instructions, one for the top level folder (used by the github coding agent) and one inside cli/azd (for when devs open the azd folder only with VSCode).

Ideas:

• Have the copilot instructions in one single folder and have a README there with a process to promote instructions from there to the top and subfolder.
• Create a script that runs and updated top folder and sub-folder instructions. This script could handle paths and placeholders.

[tg-msft]

VS Code doesn't walk up to the git root when searching for these? Might be worth filing a bug on them if they're not doing that today.

[vhvb1989]

I don't think VSCode can even do this @tg-msft. When you open a folder in VSCode, you authorize VSCode to read that path. I wouldn't expect VSCode looking/exploring parent directories.

What you can do is adding two sibling folders into a VSCode workspace. So you can add ./.github/ and ./cli/azd . However, any path in the .github-folder instructions would have things like cli/azd/... which would not be expected on the context of the workspace not having that file structure.

[rajeshkamal5050]

Resolved. The repo now uses a single AGENTS.md at cli/azd/ as the source of truth, with root .github/copilot-instructions.md pointing to it. Root AGENTS.md is an identical copy. The two-file maintenance concern is handled.