docs: fix template-markers.md drift — aliases and schedule variants (#725)

Author: github-actions[bot]

docs/template-markers.md

@@ -76,6 +76,11 @@ Examples of fuzzy schedule → cron conversion:
 - `weekly on monday` → Monday at scattered time (e.g., `"43 5 * * 1"`)
 - `every 2h` → every 2 hours at scattered minute (e.g., `"53 */2 * * *"`)
 - `bi-weekly` → every 14 days (e.g., `"43 5 */14 * *"`)
+- `tri-weekly` → every 21 days (e.g., `"43 5 */21 * *"`)
+- `every 3 days` → every 3 days (e.g., `"43 5 */3 * *"`)
+- `every 2 weeks` → every 14 days (e.g., `"43 5 */14 * *"`)
+
+See [`docs/schedule-syntax.md`](schedule-syntax.md) for the full schedule syntax reference.
 
 ## {{ checkout_self }}
 
@@ -102,6 +107,8 @@ Should be replaced with the human-readable name from the front matter
 no quoting or escaping — front-matter `name` values are free-form and
 have not been validated against YAML scalar rules.
 
+> **Alias:** `{{ agent }}` is registered as a backward-compatible alias for `{{ agent_name }}` and expands to the same unescaped name value. The same safety caveat applies — only safe in non-YAML positions.
+
 > ⚠️ This marker is only safe inside a position that is **not parsed as
 > YAML** (currently only `src/data/threat-analysis.md`, which is a
 > markdown body). YAML positions inside the generated pipelines use
@@ -159,6 +166,8 @@ so the macro passes through untouched.
 Used in `src/data/base.yml` and `src/data/1es-base.yml` only. The
 job- and stage-level templates don't emit a top-level pipeline name.
 
+> **Alias:** `{{ pipeline_name }}` is registered as a backward-compatible alias for `{{ pipeline_agent_name }}` and expands to the same value.
+
 ## {{ engine_install_steps }}
 
 Should be replaced with engine-specific pipeline steps to install the engine binary. Generated by `Engine::install_steps()`. The install strategy is **target-aware**:
@@ -311,6 +320,8 @@ workspace: exp23-a7-nw    # Resolves to $(Build.SourcesDirectory)/exp23-a7-nw
 
 This is used for the `workingDirectory` property of the copilot task.
 
+> **Alias:** `{{ workspace }}` is registered as a backward-compatible alias for `{{ working_directory }}` and expands to the same value. Prefer `{{ working_directory }}` in new templates. For paths that must always resolve to the trigger repo (not the agent workspace), use [`{{ trigger_repo_directory }}`](#-trigger_repo_directory-) instead.
+
 ## {{ source_path }}
 
 Should be replaced with the path to the agent markdown source file for Stage 3 execution. The path is anchored at the **trigger ("self") repository** via `{{ trigger_repo_directory }}` (see below), independent of the user's `workspace:` setting, and mirrors the relative path used at compile time:
@@ -498,7 +509,7 @@ The threat analysis prompt instructs the security analysis agent to check for:
 
 ## {{ agent_description }}
 
-Should be replaced with the description field from the front matter. This is used in display contexts and the threat analysis prompt template.
+Should be replaced with the description field from the front matter. This is used in the threat analysis prompt template (`src/data/threat-analysis.md`) via `{{ threat_analysis_prompt }}`. It is **not** used in any pipeline YAML template (`base.yml`, `1es-base.yml`, `job-base.yml`, `stage-base.yml`) directly.
 
 ## {{ acquire_ado_token }}