docs: fix template-markers.md — triggers.pipeline → on.pipeline, agentic_depends_on accuracy (#561)

- {{ pipeline_resources }}: fix stale references to 'triggers.pipeline' field
  name; the unified trigger syntax uses 'on.pipeline' under the 'on:' key.
- {{ agentic_depends_on }}: expand the description to accurately reflect that
  this marker also fires for PR/pipeline runtime filters (not just setup steps),
  and that it emits both 'dependsOn: Setup' and a 'condition:' expression when
  gate steps are present.

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: github-actions[bot]

docs/template-markers.md

@@ -198,9 +198,15 @@ If `post-steps` is empty, this is replaced with an empty string.
 
 ## {{ agentic_depends_on }}
 
-Generates a `dependsOn: Setup` clause for `Agent` if a setup job is configured. The setup job is identified by the job name `Setup`, ensuring the agentic task waits for the setup job to complete.
+Generates job dependency and condition configuration for the `Agent` job. This marker is populated whenever any of the following are true:
 
-If no setup job is configured, this is replaced with an empty string.
+- A **setup job** is configured (`setup:` steps are present)
+- **PR runtime filters** are configured (`on.pr.filters`)
+- **Pipeline runtime filters** are configured (`on.pipeline.filters`)
+
+When a setup job or gate step is needed, this emits `dependsOn: Setup`. When PR or pipeline filter conditions are also present, it additionally emits a `condition:` expression that gates the Agent job on the gate evaluator's output from the Setup job (e.g. `dependencies.Setup.outputs['prGate.SHOULD_RUN'] == 'true'`).
+
+If none of these are configured, this is replaced with an empty string.
 
 ## {{ job_timeout }}
 
@@ -288,9 +294,9 @@ Generates CI trigger configuration. When a schedule or pipeline trigger is confi
 
 ## {{ pipeline_resources }}
 
-Generates pipeline resource YAML when `triggers.pipeline` is configured in the front matter. Creates a pipeline resource with appropriate trigger configuration based on the specified branches. If no branches are specified, the pipeline triggers on any branch.
+Generates pipeline resource YAML when `on.pipeline` is configured in the front matter. Creates a pipeline resource with appropriate trigger configuration based on the specified branches. If no branches are specified, the pipeline triggers on any branch.
 
-Example output when `triggers.pipeline` is configured:
+Example output when `on.pipeline` is configured:
 ```yaml
 resources:
   pipelines: