docs: fix hardcoded absolute runner paths in workflow-authoring prompts

[github-actions]

Agent Documentation Update

Findings

Area	Issue	File(s)
accuracy	Apply directive and References sections used hardcoded CI runner absolute paths (/home/runner/work/ado-aw/ado-aw/...) that do not exist outside the GitHub Actions runner environment	prompts/create-ado-agentic-workflow.md, prompts/update-ado-agentic-workflow.md, prompts/debug-ado-agentic-workflow.md

Root Cause

All three workflow-authoring prompts had paths like:

Apply `/home/runner/work/ado-aw/ado-aw/prompts/prompt-contract.md` before executing this prompt.

and

- `/home/runner/work/ado-aw/ado-aw/docs/front-matter.md`

These prompts are served via versioned GitHub raw URLs (e.g. https://raw.githubusercontent.com/githubnext/ado-aw/v0.45.1/prompts/create-ado-agentic-workflow.md) and consumed by agents in consumer repositories — contexts where /home/runner/work/ado-aw/ado-aw/ does not exist. The Apply directive in particular would silently fail to load the prompt-contract in those contexts.

Applied Fixes

• Replaced /home/runner/work/ado-aw/ado-aw/prompts/prompt-contract.md → prompts/prompt-contract.md in all three prompts
• Replaced all /home/runner/work/ado-aw/ado-aw/docs/... references → docs/... relative paths in all three prompts' References sections

Verification

• Confirmed grep home/runner prompts/*.md returns no matches after the fix
• Only prompts/ files modified — no Rust, YAML, or other source files touched
• All three prompt files render as valid Markdown

Notes

Relative paths (prompts/prompt-contract.md, docs/front-matter.md) work correctly in the ado-aw repository context (where this workflow runs) and are portable hints for agents in other contexts. The key fix is removing the hardcoded CI runner prefix that made the paths non-portable.

---

Created by the agent-documentation maintainer workflow.

Generated by Agent Documentation Maintainer · 98.3 AIC · ⌖ 12.4 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.

[jamesadevine]

Closing as superseded by #1703, which fixed the hardcoded /home/runner/work/ado-aw/ado-aw/ paths introduced by #1687. Note: replacing them with repo-root-relative paths (as this PR does) is not correct — prompts/*.md are fetched over HTTP by remote agents via raw.githubusercontent.com (see .github/skills/ado-aw/SKILL.md and README.md), so a relative path would resolve against the consumer's repo. #1703 uses raw GitHub URLs, matching the existing README convention.