refactor(output): relocate templates with examples

output/README.md

@@ -8,6 +8,7 @@ This directory houses the post-processing side of ResumeCustomizer. It accepts o
 - `ForRelease/processed/YYYY/MM/DD/HHMM` – timestamped archives of Markdown files that converted successfully.
 - `ForRelease/failed` – holding area for Markdown files that Pandoc could not render.
 - `Docker/` – Dockerfile, compose stack, watcher script, and wrapper used to run the conversion container.
+- `templates/` – default Pandoc assets (`*.example`) the watcher copies into `/tmp` at runtime; copy any `.example` file without the suffix to override it locally (ignored by git).
 
 All `ForRelease` subdirectories include `.gitkeep` and `.gitignore` so artifacts stay local and never reach version control.
 
@@ -23,7 +24,7 @@ The wrapper auto-detects the Docker Compose plugin or legacy `docker-compose`, f
 
 ## Conversion Flow
 1. The watcher polls `ForRelease/inbox` every few seconds for exactly one Markdown resume.
-2. Pandoc renders DOCX and PDF using the shared templates.
+2. Pandoc renders DOCX and PDF using the shared templates (and auto-falls back to the bundled `.example` files if no overrides exist).
 3. Artifacts land in a timestamped folder under `ForRelease/outbox`.
 4. The source Markdown moves into the matching timestamp folder under `ForRelease/processed`.
 5. On Pandoc failure, the Markdown shifts into `ForRelease/failed` for human review before retrying.
@@ -32,7 +33,7 @@ Outbox and processed directories are append-only historical records managed sole
 
 ## Prerequisites
 - Docker Engine with the Compose plugin (`docker compose`) or the standalone `docker-compose` binary.
-- Template assets mounted read-only from `input/templates`.
+- Template assets mounted read-only from `templates/` (copy `.example` files to matching names without the suffix to customize them).
 
 Stop or inspect the stack with: