@jenga-ai/agent 1.0.1 → 1.1.0

package/skills/strategy/SKILL.md

@@ -0,0 +1,312 @@
+---
+name: strategy
+description: Walk through a guided conversation to capture or update docs/STRATEGY.md — covering Vision, Value Proposition, Scope, and Target Audience — one section at a time.
+metadata:
+  prefered_agent: developer
+keywords:
+  - strategy
+  - strategic brief
+  - vision
+  - value proposition
+  - target audience
+examples:
+  - "/strategy"
+  - "let's capture the strategy"
+  - "update the strategy brief"
+  - "write the strategy doc"
+---
+
+# Strategy — Guided Capture of docs/STRATEGY.md
+
+## Entry Point
+
+Check whether `docs/STRATEGY.md` exists before proceeding.
+
+- If the file does **not** exist → run **Phase A — New Capture Flow** below.
+- If the file **does** exist → run **Phase B — Update Existing File** below.
+
+---
+
+## Phase A — New Capture Flow
+
+Walk the user through four sections in order. Ask **one focused question per section**. Do not present a list of questions up front. Wait for the user's answer before moving to the next section.
+
+### Step 1 — Vision
+
+Ask the user exactly:
+
+> "What is the long-term direction or ambition for this project? Describe where you want it to be in 3–5 years, or what success ultimately looks like."
+
+Wait for the answer. Record it as the **Vision** content.
+
+### Step 2 — Value Proposition
+
+Ask the user exactly:
+
+> "What makes this project uniquely valuable? What would users or teams miss most if it didn't exist?"
+
+Wait for the answer. Record it as the **Value Proposition** content.
+
+### Step 3 — Scope: In Scope
+
+Ask the user exactly:
+
+> "What does this project explicitly cover? List the main capabilities or areas of responsibility."
+
+Wait for the answer. Record it as the **In Scope** content.
+
+### Step 4 — Scope: Out of Scope
+
+Ask the user exactly:
+
+> "What does this project explicitly NOT cover? (Do not include revenue models, pricing, or competitive analysis — those are always out of scope.)"
+
+Wait for the answer. Record it as the **Out of Scope** content. The model must also always append to the Out of Scope section (regardless of whether the user mentions them):
+
+- Revenue model, pricing strategy, or monetisation plans
+- Competitive analysis or feature comparison with other tools
+
+Do not ask the user for these — include them silently.
+
+### Step 5 — Target Audience
+
+Ask the user exactly:
+
+> "Who is this built for? Describe the primary user personas or teams."
+
+Wait for the answer. Record it as the **Target Audience** content.
+
+---
+
+## Pre-Write Summary and Confirmation
+
+After collecting all five pieces of content (Vision, Value Proposition, In Scope, Out of Scope, Target Audience), surface a formatted summary. Use exactly this shape:
+
+```
+Here is what will be written to docs/STRATEGY.md:
+
+## Vision
+<vision content>
+
+## Value Proposition
+<value proposition content>
+
+## Scope
+
+### In Scope
+<in-scope content>
+
+### Out of Scope
+<out-of-scope content (user answer + always-excluded items)>
+
+## Target Audience
+<target audience content>
+
+---
+
+Does this look right? Type **yes** to write `docs/STRATEGY.md`, or tell me what to change.
+```
+
+- If the user says **yes** (or any clear affirmative) → proceed to the Write step.
+- If the user requests a change → re-ask the relevant question(s) using the same prompts from Phase A, collect the updated answer(s), then loop back to this summary step. Do not write the file until the user explicitly confirms.
+
+---
+
+## Write the File
+
+Generate `docs/STRATEGY.md` using **only the content collected in the conversation**. Do not invent facts, add filler text, or leave any placeholder text in the output.
+
+The file must follow this exact structure:
+
+```markdown
+# Strategy Brief
+
+> **Audience:** Investors and strategic partners. This document does not include revenue models, pricing, or competitive analysis.
+
+---
+
+## Vision
+
+<vision content>
+
+---
+
+## Value Proposition
+
+<value proposition content>
+
+---
+
+## Scope
+
+### In Scope
+
+<in-scope content>
+
+### Out of Scope
+
+<out-of-scope content>
+
+---
+
+## Target Audience
+
+<target audience content>
+```
+
+Write the file to `docs/STRATEGY.md`. After writing, print exactly:
+
+```
+Written to `docs/STRATEGY.md` — captured Vision, Value Proposition, Scope, and Target Audience.
+```
+
+---
+
+## Phase B — Update Existing File
+
+`docs/STRATEGY.md` already exists. Do **not** run the new-capture flow. Instead, walk the user through each section so they can decide what to keep and what to replace.
+
+### Step 1 — Read the Existing File
+
+Read `docs/STRATEGY.md` in full. Parse out the content under each of the four sections:
+
+- **Vision** — content under `## Vision`
+- **Value Proposition** — content under `## Value Proposition`
+- **In Scope** — content under `### In Scope`
+- **Out of Scope** — content under `### Out of Scope`
+- **Target Audience** — content under `## Target Audience`
+
+Store these as the current values for each section. They will be used as defaults unless the user explicitly chooses to update them.
+
+### Step 2 — Surface Each Section One at a Time
+
+Work through the sections in this order: Vision, Value Proposition, Scope (In + Out together), Target Audience.
+
+For **Vision**, present exactly:
+
+> "Here is the current Vision:
+>
+> ---
+> <existing vision content>
+> ---
+>
+> Do you want to keep this or update it? (keep / update)"
+
+- If "keep" → store the existing Vision content unchanged and move on.
+- If "update" → ask exactly:
+  > "What is the long-term direction or ambition for this project? Describe where you want it to be in 3–5 years, or what success ultimately looks like."
+  Wait for the answer. Store it as the new Vision content.
+
+For **Value Proposition**, present exactly:
+
+> "Here is the current Value Proposition:
+>
+> ---
+> <existing value proposition content>
+> ---
+>
+> Do you want to keep this or update it? (keep / update)"
+
+- If "keep" → store the existing Value Proposition content unchanged and move on.
+- If "update" → ask exactly:
+  > "What makes this project uniquely valuable? What would users or teams miss most if it didn't exist?"
+  Wait for the answer. Store it as the new Value Proposition content.
+
+For **Scope**, present the In Scope and Out of Scope content together:
+
+> "Here is the current Scope:
+>
+> **In Scope**
+> ---
+> <existing in-scope content>
+> ---
+>
+> **Out of Scope**
+> ---
+> <existing out-of-scope content>
+> ---
+>
+> Do you want to keep this or update it? (keep / update)"
+
+- If "keep" → store the existing In Scope and Out of Scope content unchanged and move on.
+- If "update" → ask the two focused scope questions from Phase A in sequence:
+  1. > "What does this project explicitly cover? List the main capabilities or areas of responsibility."
+     Wait for the answer. Store as the new In Scope content.
+  2. > "What does this project explicitly NOT cover? (Do not include revenue models, pricing, or competitive analysis — those are always out of scope.)"
+     Wait for the answer. Store as the new Out of Scope content. Silently append the always-excluded items (revenue model, pricing strategy, competitive analysis) as in Phase A — do not ask the user for these.
+
+For **Target Audience**, present exactly:
+
+> "Here is the current Target Audience:
+>
+> ---
+> <existing target audience content>
+> ---
+>
+> Do you want to keep this or update it? (keep / update)"
+
+- If "keep" → store the existing Target Audience content unchanged and move on.
+- If "update" → ask exactly:
+  > "Who is this built for? Describe the primary user personas or teams."
+  Wait for the answer. Store it as the new Target Audience content.
+
+### Step 3 — Pre-Write Summary and Confirmation
+
+After all four sections have been decided (either kept or updated), surface a full formatted preview of the final document. Use exactly this shape:
+
+```
+Here is what will be written to docs/STRATEGY.md:
+
+## Vision
+<vision content>
+
+## Value Proposition
+<value proposition content>
+
+## Scope
+
+### In Scope
+<in-scope content>
+
+### Out of Scope
+<out-of-scope content>
+
+## Target Audience
+<target audience content>
+
+---
+
+Does this look right? Type **yes** to overwrite `docs/STRATEGY.md`, or tell me what to change.
+```
+
+- If the user says **yes** (or any clear affirmative) → proceed to the Write step.
+- If the user requests a change → re-surface only the relevant section(s) using the same keep/update flow above, collect the updated answer(s), then loop back to this preview step. Do not write the file until the user explicitly confirms.
+
+### Step 4 — Write the File
+
+Overwrite `docs/STRATEGY.md` using exactly the same format as Phase A output — only real content from the conversation, no placeholder text. Apply all hard constraints from the Hard Constraints block below.
+
+After writing, print exactly:
+
+```
+Written to `docs/STRATEGY.md` — updated Vision, Value Proposition, Scope, and Target Audience.
+```
+
+If some sections were kept unchanged and others were updated, list only the updated sections:
+
+```
+Written to `docs/STRATEGY.md` — updated <list of updated sections>.
+```
+
+---
+
+## Hard Constraints
+
+Enforce these rules throughout the entire skill session — at every step, in every question, and in the written output:
+
+1. **Never ask about** revenue model, pricing, monetisation, competitive analysis, market positioning, financial projections, or any topic outside Vision, Value Proposition, Scope, and Target Audience.
+2. **Never write the file** without receiving explicit user confirmation ("yes" or a clear affirmative) at the pre-write summary step.
+3. **Never include placeholder text** in the written output. Every section must contain real content from the conversation.
+4. **Never add sections** beyond the four defined ones (Vision, Value Proposition, Scope, Target Audience) and their required sub-sections.
+5. **Always include** the audience callout block at the top of the written file, verbatim.
+6. **Always include** the always-excluded Out of Scope items (revenue model, pricing, competitive analysis) even if the user omits them.

package/templates/SCRUM_BOARD_SCHEMA.md

@@ -86,6 +86,7 @@ dates_previously_completed:  # comma-separated list, e.g. 2026-01-15, 2026-03-22
 reopened_on:                 # comma-separated list, e.g. 2026-02-01, 2026-04-10
 reopened_reason:             # comma-separated list, e.g. "Scope expanded", "Bug found post-release"
 docs: []                     # optional list of repo-relative documentation paths, e.g. ["README.md", "docs/API.md"]
+epic_scope_approval: false     # set to true by the human operator only when any task in this epic has execution_scope: epic
 stories:
   - E##_S##
   - E##_S##
@@ -101,6 +102,8 @@ stories:
 - <Concrete, testable criterion>
 ```
 
+> **`epic_scope_approval`** — This field is **set by the human operator only**. Neither the scrum-master nor the developer agent may set it to `true`. It must be `true` before any task with `execution_scope: epic` can be executed. Its absence is equivalent to `false`.
+
 ### Story — `E##_S##_<slug>.md`
 
 ```markdown
@@ -150,6 +153,12 @@ reopened_on:                 # comma-separated list, e.g. 2026-02-01, 2026-04-10
 reopened_reason:             # comma-separated list, e.g. "Scope expanded", "Bug found post-release"
 assigned_to: developer | tester | scrum-master
 docs: []                     # optional list of repo-relative documentation paths, e.g. ["README.md", "docs/API.md"]
+execution_scope: task          # task | story | epic | inline; omit for legacy tasks (defaults to task)
+needs_docs: true               # boolean; omit for legacy tasks (defaults to true)
+scope_rationale: ""            # required when execution_scope is set; must contain a numeric/file-count claim
+jenga_assigned: true           # boolean; true = machine-assigned, false = human override
+override_justification: ""     # required when jenga_assigned: false
+epic_scope_approval: false     # required (as true) when execution_scope: epic; set by human operator only
 ---
 
 # Task: <Title>
@@ -164,6 +173,8 @@ docs: []                     # optional list of repo-relative documentation path
 - [ ] <Verifiable criterion>
 ```
 
+> **Backward compatibility:** Tasks that omit all six new fields (`execution_scope`, `needs_docs`, `scope_rationale`, `jenga_assigned`, `override_justification`, `epic_scope_approval`) are treated as `execution_scope: task` / `needs_docs: true` and are processed without error. Agents must not reject board files that lack these fields.
+
 ---
 
 ## Story Format Standards
@@ -181,6 +192,44 @@ docs: []                     # optional list of repo-relative documentation path
 - Optionality: existing board files remain valid when `docs` is omitted.
 - Format: use a YAML list. Inline (`docs: ["README.md"]`) and expanded list styles are both valid.
 
+## Execution Scope Fields (Task)
+
+These six fields control the execution footprint of a task within the `/jenga` and `/do` workflows. They are **optional** — omitting all six is valid and equivalent to `execution_scope: task` / `needs_docs: true`.
+
+**`execution_scope`**
+- Valid values: `task` | `story` | `epic` | `inline`
+- When required: optional; omit for legacy tasks (runtime default: `task`)
+- Description: defines how broadly this task's implementation touches the codebase.
+  - `task` — standard single-task scope (default)
+  - `story` — task may touch files across multiple tasks in the same story
+  - `epic` — task may touch files across stories; requires `epic_scope_approval: true` on the parent epic
+  - `inline` — trivial change (e.g. config tweak, comment, schema doc); no execution plan or summary document is needed
+
+**`needs_docs`**
+- Valid values: `true` | `false`
+- When required: optional; omit for legacy tasks (runtime default: `true`)
+- Description: when `false`, the developer agent skips writing an execution plan and execution summary for this task. Automatically implied as `false` when `execution_scope: inline`.
+
+**`scope_rationale`**
+- Valid values: any non-empty string; must include a measurable claim (e.g. a file count or line count)
+- When required: required when `execution_scope` is explicitly set to any value
+- Description: a brief justification explaining why the chosen scope is appropriate. Validators reject a blank value when `execution_scope` is present.
+
+**`jenga_assigned`**
+- Valid values: `true` | `false`
+- When required: optional; omit for legacy tasks (runtime default: `true`)
+- Description: indicates whether the execution scope was assigned by the `/jenga` orchestrator (`true`) or overridden by a human (`false`). When `false`, `override_justification` is required.
+
+**`override_justification`**
+- Valid values: any non-empty string
+- When required: required when `jenga_assigned: false`
+- Description: explains why the human operator overrode the machine-assigned scope. Must be non-empty when present.
+
+**`epic_scope_approval`**
+- Valid values: `true` | `false`
+- When required: required on the **epic** frontmatter (as `true`) before any task with `execution_scope: epic` may be executed; the task frontmatter carries this field for reference only
+- Description: the authoritative value is always read from the **epic** frontmatter, not the task. This field is **set by the human operator only** — neither the scrum-master nor the developer agent may set it to `true`. Its absence on the epic is equivalent to `false`.
+
 These rules apply to every story file written or amended by the **Scrum Master**. They are enforced at write time by `scripts/validate-story-format.sh`.
 
 ### Acceptance Criteria (`## Acceptance Criteria`)

package/skills/train/SKILL.md

@@ -1,116 +0,0 @@
----
-name: train
-description: Scaffold and run ML training jobs. Use `new <type> <job-name>` to scaffold a job from a template, or `run <job-dir>` to execute the two-phase validate → train pipeline on an existing job.
-keywords:
-  - train
-  - ml training
-  - model training
-  - machine learning
-  - fine-tune
-examples:
-  - "scaffold a new training job"
-  - "train a classifier model"
----
-
-# Train — ML Training Job Orchestrator
-
-## Usage
-
-```
-python skills/train/train_cli.py <subcommand> [args]
-
-Subcommands:
-  new <type> <job-name>   Scaffold a new training job from a template
-  run <job-dir>           Execute validate → train pipeline on an existing job
-
-Types: classifiers, transformers, nlp
-```
-
-If an unrecognised subcommand is given, argparse prints the usage message above and
-exits with a non-zero code.
-
-## Subcommands
-
-### `/train new <type> <job-name>`
-Scaffold a new training job from the appropriate template (positional / scriptable mode).
-
-**Supported types:** `classifiers`, `transformers`, `nlp`
-
-**Optional flags:**
-- `--model <value>` — Override the model name/type in `config.yaml`
-- `--epochs <n>` — Override the number of training epochs/iterations
-- `--batch-size <n>` — Override the batch size
-
-**Steps:**
-1. Validate `<type>` is one of: `classifiers`, `transformers`, `nlp`
-2. Copy the template directory from `.training/template/<type>/` to `jobs/<job-name>/`
-   - If `jobs/<job-name>/` already exists, auto-suffix: `jobs/<job-name>-1/`, `jobs/<job-name>-2/`, etc.
-3. Apply any CLI flag overrides to the scaffolded `config.yaml`
-4. Generate `start.sh` in the job directory (executable)
-5. Read the `workflow:` block from `config.yaml` and print next-step instructions
-6. Print: `✅ Scaffolded job '<job-name>' from template '<type>' at jobs/<job-name>/`
-
-### `/train new --interactive [--full]`
-Launch a guided wizard that scaffolds the job **and** configures `config.yaml` interactively.
-
-**Flags:**
-- `--interactive` / `-i` — Enable the wizard. Job name and type are collected via prompts.
-- `--full` — Expand the wizard to prompt for **every** configurable field (not just the critical ones).
-
-**Wizard flow:**
-1. Prompt for job name (freeform, used as directory name under `jobs/`)
-2. Prompt for job type (`classifiers`, `transformers`, or `nlp`)
-3. Scaffold the job directory from the template
-4. Prompt for critical config fields (2–3 key model params + data path per type):
-   - **classifiers**: train file, target column, model algorithm, n_estimators, test split
-   - **transformers**: model name, task, train file, epochs, learning rate
-   - **nlp**: model name, task, train file, iterations, learning rate
-5. With `--full`: additionally prompt for every remaining field in `config.yaml`
-6. Write user responses back into the scaffolded `config.yaml`
-
-Each prompt shows the field name, its current default, and an inline description hint.
-
-**Ctrl+C handling:**
-Pressing `Ctrl+C` at any point during the wizard interrupts cleanly. If a scaffold directory has already been created, the user is asked:
-```
-Delete scaffolded directory '<path>'? [y/N]
-```
-Answering `y` removes the directory; `N` (or Enter) keeps it.
-
-### `/train run <job-dir>`
-Execute the two-phase pre-flight → smoke test pipeline on an existing job directory.
-
-**Steps:**
-
-#### Phase A — Pre-flight validation
-1. Print: `[pre-flight] Running validate.py in <job-dir>...`
-2. Run `validate.py` as a subprocess inside `<job-dir>`:
-   ```bash
-   cd <job-dir> && python validate.py
-   ```
-3. Stream all stdout/stderr output to the terminal in real time.
-4. If `validate.py` exits non-zero:
-   - Print: `❌ [pre-flight] FAILED — halting before smoke test.`
-   - Surface the full error output.
-   - **Stop here. Do not proceed to Phase B.**
-5. If `validate.py` exits zero:
-   - Print: `✅ [pre-flight] Passed.`
-
-#### Phase B — Smoke test
-1. Print: `[smoke test] Running train.py --smoke in <job-dir>...`
-2. Run `train.py --smoke` as a subprocess inside `<job-dir>`:
-   ```bash
-   cd <job-dir> && python train.py --smoke
-   ```
-3. Stream all stdout/stderr output to the terminal in real time.
-4. If `train.py` exits non-zero:
-   - Print: `❌ [smoke test] FAILED.`
-   - Surface the full error output.
-5. If `train.py` exits zero:
-   - Print: `✅ [smoke test] Passed. Job '<job-dir>' completed successfully.`
-
-## Notes
-- `train.py` and `validate.py` must have no awareness of each other — the `/train` skill owns the gate.
-- Both subprocess calls must stream output (not buffer) so the user sees progress in real time.
-- Phase B is **never** invoked if Phase A fails.
-- The `--interactive` wizard requires `pyyaml` (`pip install pyyaml`) to patch `config.yaml`.

package/skills/train/assets/dashboard-templates/classifiers.html

@@ -1,106 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-<head>
-  <meta charset="UTF-8" />
-  <meta name="viewport" content="width=device-width, initial-scale=1.0" />
-  <title>Classifier Training Dashboard — {{job_name}}</title>
-  <style>
-    *, *::before, *::after { box-sizing: border-box; margin: 0; padding: 0; }
-    body { font-family: system-ui, -apple-system, sans-serif; background: #f5f7fa; color: #1a1a2e; padding: 2rem; }
-    header { margin-bottom: 2rem; }
-    header h1 { font-size: 1.6rem; font-weight: 700; }
-    header p { color: #555; margin-top: .25rem; font-size: .9rem; }
-    .card { background: #fff; border-radius: 10px; box-shadow: 0 2px 8px rgba(0,0,0,.08); padding: 1.5rem; margin-bottom: 1.5rem; }
-    .card h2 { font-size: 1rem; font-weight: 600; color: #333; margin-bottom: 1rem; text-transform: uppercase; letter-spacing: .05em; }
-    .metrics-grid { display: grid; grid-template-columns: repeat(auto-fit, minmax(150px, 1fr)); gap: 1rem; }
-    .metric-box { background: #f0f4ff; border-radius: 8px; padding: 1rem; text-align: center; }
-    .metric-box .value { font-size: 2rem; font-weight: 700; color: #3b5bdb; }
-    .metric-box .label { font-size: .8rem; color: #666; margin-top: .25rem; }
-    .bar-chart { display: flex; flex-direction: column; gap: .6rem; }
-    .bar-row { display: flex; align-items: center; gap .5rem; }
-    .bar-label { width: 100px; font-size: .85rem; color: #444; flex-shrink: 0; }
-    .bar-track { flex: 1; background: #e9ecef; border-radius: 4px; height: 20px; position: relative; }
-    .bar-fill { height: 100%; border-radius: 4px; background: #3b5bdb; transition: width .4s; }
-    .bar-val { width: 50px; text-align: right; font-size: .8rem; color: #444; }
-    table { width: 100%; border-collapse: collapse; }
-    th, td { padding: .6rem 1rem; text-align: left; font-size: .9rem; border-bottom: 1px solid #eee; }
-    th { background: #f8f9fa; font-weight: 600; color: #555; }
-    footer { text-align: center; font-size: .75rem; color: #999; margin-top: 2rem; }
-  </style>
-</head>
-<body>
-
-<header>
-  <h1>🤖 Classifier Training Dashboard</h1>
-  <p>Job: <strong>{{job_name}}</strong> &nbsp;|&nbsp; Model: <strong>{{model_type}}</strong></p>
-</header>
-
-<div class="card">
-  <h2>Key Metrics</h2>
-  <div class="metrics-grid">
-    <div class="metric-box">
-      <div class="value">{{accuracy}}</div>
-      <div class="label">Accuracy</div>
-    </div>
-    <div class="metric-box">
-      <div class="value">{{f1_score}}</div>
-      <div class="label">F1 Score</div>
-    </div>
-    <div class="metric-box">
-      <div class="value">{{precision}}</div>
-      <div class="label">Precision</div>
-    </div>
-    <div class="metric-box">
-      <div class="value">{{recall}}</div>
-      <div class="label">Recall</div>
-    </div>
-  </div>
-</div>
-
-<div class="card">
-  <h2>Metric Comparison</h2>
-  <div class="bar-chart">
-    <div class="bar-row">
-      <span class="bar-label">Accuracy</span>
-      <div class="bar-track"><div class="bar-fill" style="width: calc({{accuracy}} * 100%)"></div></div>
-      <span class="bar-val">{{accuracy}}</span>
-    </div>
-    <div class="bar-row">
-      <span class="bar-label">F1 Score</span>
-      <div class="bar-track"><div class="bar-fill" style="width: calc({{f1_score}} * 100%)"></div></div>
-      <span class="bar-val">{{f1_score}}</span>
-    </div>
-    <div class="bar-row">
-      <span class="bar-label">Precision</span>
-      <div class="bar-track"><div class="bar-fill" style="width: calc({{precision}} * 100%)"></div></div>
-      <span class="bar-val">{{precision}}</span>
-    </div>
-    <div class="bar-row">
-      <span class="bar-label">Recall</span>
-      <div class="bar-track"><div class="bar-fill" style="width: calc({{recall}} * 100%)"></div></div>
-      <span class="bar-val">{{recall}}</span>
-    </div>
-  </div>
-</div>
-
-<div class="card">
-  <h2>Summary Table</h2>
-  <table>
-    <thead>
-      <tr><th>Metric</th><th>Value</th></tr>
-    </thead>
-    <tbody>
-      <tr><td>Accuracy</td><td>{{accuracy}}</td></tr>
-      <tr><td>F1 Score</td><td>{{f1_score}}</td></tr>
-      <tr><td>Precision</td><td>{{precision}}</td></tr>
-      <tr><td>Recall</td><td>{{recall}}</td></tr>
-      <tr><td>Model Type</td><td>{{model_type}}</td></tr>
-      <tr><td>Job Name</td><td>{{job_name}}</td></tr>
-    </tbody>
-  </table>
-</div>
-
-<footer>Generated by JengaAgent /train skill &nbsp;|&nbsp; {{job_name}}</footer>
-
-</body>
-</html>