feat(compile): add target: job and target: stage for ADO template output (#519)

* feat(compile): add target: job and target: stage for ADO template output

Add two new compile targets that produce reusable ADO YAML templates
for embedding agentic stages into existing pipelines:

- target: job — generates a job-level template (jobs: at root) that can
  be included in a flat pipeline or inside a user-defined stage
- target: stage — generates a stage-level template (stages: wrapping
  jobs) for direct inclusion in multi-stage pipelines

Key design decisions:
- Pool is baked in from front matter (not a template parameter)
- dependsOn and condition are set natively at the ADO call site
- Job names are prefixed with PascalCase agent name for uniqueness
  (e.g., DailyReview_Agent, DailyReview_Detection, DailyReview_Execution)
- Triggers (on:) are ignored with a warning in template targets
- Template parameters only include clearMemory and user-defined params

New files:
- src/compile/job.rs — JobCompiler implementing the Compiler trait
- src/compile/stage.rs — StageCompiler implementing the Compiler trait
- src/data/job-base.yml — job-level template derived from base.yml
- src/data/stage-base.yml — stage-level template wrapping jobs in stage

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* fix(compile): implement review suggestions for job/stage template targets

Agent-Logs-Url: https://github.com/githubnext/ado-aw/sessions/fa2ca612-1703-4107-87c3-2b2ec35429b8

Co-authored-by: jamesadevine <4742697+jamesadevine@users.noreply.github.com>

* fix(compile): use 'template' label for job/stage targets and fix header paths

- CLI now prints 'Generated job template:' and 'Generated stage template:'
  instead of 'Generated job pipeline:' / 'Generated stage pipeline:' since
  these targets produce reusable ADO templates, not standalone pipelines.
- Header comments in generated job/stage templates now reference the actual
  output path instead of deriving a path from the input file, fixing
  incorrect inclusion examples (e.g. showing ./agents/x.lock.yml when the
  output was at ./x.lock.yml).

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

---------

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>

Author: 3 people

src/compile/common.rs

@@ -2861,11 +2861,11 @@ pub async fn compile_shared(
 ///
 /// Handles the full setup — collecting extensions, building the compile context,
 /// generating the stage prefix and template parameters, computing AWF/MCPG
-/// values — and delegates to [`compile_shared`].  The caller supplies:
+/// values — and delegates to [`compile_shared`]. The caller supplies:
 ///
 /// - `cfg`: target-specific settings (template string, integrity / debug flags).
 /// - `header_fn`: a function that generates the leading comment block prepended
-///   to the compiled YAML.  The two template compilers use different header
+///   to the compiled YAML. The two template compilers use different header
 ///   layouts, so this lets each compiler keep its own generator while sharing
 ///   all of the boilerplate setup.
 ///
@@ -2927,9 +2927,15 @@ pub async fn compile_template_target(
     };
 
     let yaml = compile_shared(
-        input_path, output_path, front_matter, markdown_body,
-        &extensions, &ctx, config,
-    ).await?;
+        input_path,
+        output_path,
+        front_matter,
+        markdown_body,
+        &extensions,
+        &ctx,
+        config,
+    )
+    .await?;
 
     let header = header_fn(input_path, output_path, front_matter);
     Ok(format!("{}{}", header, yaml))

src/compile/job.rs

@@ -14,8 +14,7 @@ use std::path::Path;
 
 use super::Compiler;
 use super::common::{
-    compile_template_target, TemplateTargetConfig,
-    generate_header_comment,
+    compile_template_target, generate_header_comment, TemplateTargetConfig,
 };
 use super::types::FrontMatter;
 
@@ -52,16 +51,15 @@ impl Compiler for JobCompiler {
                 debug_pipeline,
             },
             generate_job_header,
-        ).await
+        )
+        .await
     }
 }
 
 /// Generate the header comment block for job-level templates.
 fn generate_job_header(input_path: &Path, output_path: &Path, front_matter: &FrontMatter) -> String {
     let base_header = generate_header_comment(input_path);
-    let mut lock_path = output_path
-        .to_string_lossy()
-        .replace('\\', "/");
+    let mut lock_path = output_path.to_string_lossy().replace('\\', "/");
     // Strip redundant leading "./" (same normalization as generate_header_comment)
     while lock_path.starts_with("./") {
         lock_path = lock_path[2..].to_string();
@@ -102,7 +100,6 @@ fn generate_job_header(input_path: &Path, output_path: &Path, front_matter: &Fro
 
 #[cfg(test)]
 mod tests {
-    use super::*;
     use crate::compile::common::generate_stage_prefix;
 
     #[test]

src/compile/stage.rs

@@ -22,8 +22,7 @@ use std::path::Path;
 
 use super::Compiler;
 use super::common::{
-    compile_template_target, TemplateTargetConfig,
-    generate_header_comment,
+    compile_template_target, generate_header_comment, TemplateTargetConfig,
 };
 use super::types::FrontMatter;
 
@@ -60,16 +59,15 @@ impl Compiler for StageCompiler {
                 debug_pipeline,
             },
             generate_stage_header,
-        ).await
+        )
+        .await
     }
 }
 
 /// Generate the header comment block for stage-level templates.
 fn generate_stage_header(input_path: &Path, output_path: &Path, front_matter: &FrontMatter) -> String {
     let base_header = generate_header_comment(input_path);
-    let mut lock_path = output_path
-        .to_string_lossy()
-        .replace('\\', "/");
+    let mut lock_path = output_path.to_string_lossy().replace('\\', "/");
     while lock_path.starts_with("./") {
         lock_path = lock_path[2..].to_string();
     }