docs: fix CI-absolute paths in prompt files

[github-actions]

Agent Documentation Update

Findings

Area	Issue	File(s)
accuracy	All three prompt files contain hardcoded absolute CI paths (/home/runner/work/ado-aw/ado-aw/...) that fail in every environment except the specific CI runner that generated them	prompts/create-ado-agentic-workflow.md, prompts/update-ado-agentic-workflow.md, prompts/debug-ado-agentic-workflow.md

Root Cause

A previous Copilot agent run (commit 316de97) created these prompt files while running on a GitHub Actions runner, and used the runner's absolute filesystem path for the prompt-contract.md reference and the docs/ References sections. These paths are:

• Invalid in consumer repos (where agents fetch the prompts via raw GitHub URL)
• Invalid in any other CI environment
• Invalid for local development on non-runner machines

Applied Fixes

• Replace Apply \/home/runner/work/ado-aw/ado-aw/prompts/prompt-contract.md`→Apply `./prompt-contract.md`` in all three prompts
• Replace /home/runner/work/ado-aw/ado-aw/docs/ references → ../docs/ relative paths in all three prompts

Notes

Verified against git diff --name-only — only the three prompts/*.md files changed. No source code, YAML, or other documentation was modified.

The relative paths (./prompt-contract.md, ../docs/*.md) work correctly when:

• An agent reads the prompt in the context of the ado-aw repository (file system access)
• An agent resolves relative references from the raw GitHub URL base

---

Created by the agent-documentation maintainer workflow.

Generated by Agent Documentation Maintainer · 162.2 AIC · ⌖ 12.3 AIC · ⊞ 8.7K · ◷

[azure-pipelines]

Azure Pipelines:
2 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.