Documentation Freshness Audit
This audit found the following inconsistencies between code and documentation:
Findings
| Area |
Issue |
File(s) |
| Architecture tree |
dotnet/ runtime directory missing from runtimes/ section |
AGENTS.md |
| Docs index |
docs/runtimes.md entry lists "Lean 4, Python, Node.js" but omits .NET |
AGENTS.md |
| Front matter table |
runtimes field description shows only "lean" |
README.md |
| Workflow authoring prompt |
No runtimes step — agents authoring pipelines have no guidance on runtimes: configuration |
prompts/create-ado-agentic-workflow.md |
Details
src/runtimes/dotnet/ exists in the codebase (with mod.rs and extension.rs) and DotnetRuntimeConfig is a fully documented field in FrontMatter. The runtime is also covered in docs/runtimes.md. However, three other documentation surfaces hadn't been updated:
AGENTS.md architecture tree — The runtimes/ subtree listed only lean/, python/, and node/; dotnet/ was absent.
AGENTS.md docs index — The blurb for docs/runtimes.md said "Lean 4, Python, Node.js" with no mention of .NET.
README.md front matter table — The runtimes row description said only "lean" instead of listing all supported runtimes.
prompts/create-ado-agentic-workflow.md — No "Runtimes" step existed in the workflow creation guide (Steps 1–13 skipped runtimes entirely). AI agents following this guide would never know to configure runtimes: even when the task clearly needs it (e.g., .NET dependency update agent).
Applied Fixes
This pull request was created by the automated documentation freshness check.
To route changes like this to a review issue instead of blocking, configure protected-files: fallback-to-issue in your workflow configuration.
Generated by Documentation Freshness Check · ● 2M · ◷
Documentation Freshness Audit
This audit found the following inconsistencies between code and documentation:
Findings
dotnet/runtime directory missing fromruntimes/sectionAGENTS.mddocs/runtimes.mdentry lists "Lean 4, Python, Node.js" but omits .NETAGENTS.mdruntimesfield description shows only "lean"README.mdruntimes:configurationprompts/create-ado-agentic-workflow.mdDetails
src/runtimes/dotnet/exists in the codebase (withmod.rsandextension.rs) andDotnetRuntimeConfigis a fully documented field inFrontMatter. The runtime is also covered indocs/runtimes.md. However, three other documentation surfaces hadn't been updated:AGENTS.mdarchitecture tree — Theruntimes/subtree listed onlylean/,python/, andnode/;dotnet/was absent.AGENTS.mddocs index — The blurb fordocs/runtimes.mdsaid "Lean 4, Python, Node.js" with no mention of .NET.README.mdfront matter table — Theruntimesrow description said only "lean" instead of listing all supported runtimes.prompts/create-ado-agentic-workflow.md— No "Runtimes" step existed in the workflow creation guide (Steps 1–13 skipped runtimes entirely). AI agents following this guide would never know to configureruntimes:even when the task clearly needs it (e.g., .NET dependency update agent).Applied Fixes
dotnet/subtree to theruntimes/architecture section inAGENTS.mddocs/runtimes.mddocs-index description inAGENTS.mdto include ".NET"runtimesfield description inREADME.mdto listlean,python,node,dotnetprompts/create-ado-agentic-workflow.mdwith YAML examples for all four runtimes (lean, python, node, dotnet) and a note about auto-added bash commands and network domains; renumbered former Step 13 → Step 14 (Network)This pull request was created by the automated documentation freshness check.
Warning
Protected Files
This was originally intended as a pull request, but the patch modifies protected files. These files may affect project dependencies, CI/CD pipelines, or agent behaviour. Please review the changes carefully before creating the pull request.
Click here to create the pull request once you have reviewed the changes
Protected files
AGENTS.mdTo route changes like this to a review issue instead of blocking, configure
protected-files: fallback-to-issuein your workflow configuration.