feat(templates): use {{ agent_display_name }} in all four base templates

docs/template-markers.md

@@ -133,11 +133,17 @@ For an agent named `My "special": agent`, this expands to:
   displayName: "My \"special\": agent"
 ```
 
-Used in `src/data/1es-base.yml` (1ES stage display name) and
-`src/data/stage-base.yml` (stage-target stage display name). The marker
-deliberately does **not** include the `-$(BuildID)` suffix that
-[`{{ pipeline_agent_name }}`](#-pipeline_agent_name-) carries — stage labels are
-static and don't need per-run uniqueness.
+Used in all four base templates as the top-most user-facing
+`displayName:`:
+
+- `src/data/base.yml` — standalone Agent job display name.
+- `src/data/job-base.yml` — job-target Agent job display name.
+- `src/data/1es-base.yml` — 1ES Agent stage display name.
+- `src/data/stage-base.yml` — stage-target Agent stage display name.
+
+The marker deliberately does **not** include the `-$(BuildID)` suffix
+that [`{{ pipeline_agent_name }}`](#-pipeline_agent_name-) carries —
+stage and job labels are static and don't need per-run uniqueness.
 
 ## {{ pipeline_agent_name }}
 

site/src/content/docs/reference/template-markers.mdx

@@ -106,7 +106,7 @@ Example: `name: Daily safe-output smoke: "noop" @nightly` → `Daily safe-output
 
 ## `{{ agent_display_name }}`
 
-Replaced with the raw `name:` front matter value as a YAML double-quoted scalar (e.g., `"Daily Code Review"`). Used in the `displayName:` property of the outermost stage block in `target: stage` pipelines, and in the 1ES template's `templateContext.buildJob.displayName` property.
+Replaced with the raw `name:` front matter value as a YAML double-quoted scalar (e.g., `"Daily Code Review"`). Used as the top-most user-facing `displayName:` in all four base templates: the Agent job displayName in `target: standalone` and `target: job` pipelines, and the Agent stage displayName in `target: stage` and 1ES pipelines.
 
 Always quoted to handle names that contain characters (such as `:`) that ADO would otherwise misparse as YAML mapping indicators.
 
@@ -514,7 +514,7 @@ Should be replaced with the domain the AWF-sandboxed agent uses to reach MCPG on
 
 The 1ES target uses the same template markers as standalone, plus the 1ES-specific `extends:` / `stages:` / `templateContext` wrapping. The 1ES template includes `templateContext.type: buildJob` for all jobs, and the pool is specified at the top-level `parameters.pool` rather than per-job.
 
-Both targets share the same execution model (Copilot CLI + AWF + MCPG) and the same set of template markers. The 1ES template additionally uses `{{ agent_display_name }}` for the `templateContext.buildJob.displayName` property (see above).
+Both targets share the same execution model (Copilot CLI + AWF + MCPG) and the same set of template markers, including `{{ agent_display_name }}` (used in all four base templates — see above).
 
 ## Job/Stage Template Markers
 

src/data/base.yml

@@ -16,7 +16,7 @@ resources:
 jobs:
   {{ setup_job }}
   - job: Agent
-    displayName: "Agent"
+    displayName: {{ agent_display_name }}
     {{ agentic_depends_on }}
     {{ job_timeout }}
     pool:

src/data/job-base.yml

@@ -3,7 +3,7 @@
 jobs:
   {{ setup_job }}
   - job: {{ stage_prefix }}_Agent
-    displayName: "Agent"
+    displayName: {{ agent_display_name }}
     {{ agentic_depends_on }}
     {{ job_timeout }}
     pool: