Fix compile: escape backticks in bootstrap template

The gh-aw compiler treats backticks as reserved characters. Use
chr(96) to construct them at runtime in the Python pre-step so
they don't appear as literals in the workflow source.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: mrjf

workflows/autoloop.md

@@ -77,44 +77,47 @@ steps:
       # Bootstrap: create programs directory and template if missing
       if not os.path.isdir(programs_dir):
           os.makedirs(programs_dir, exist_ok=True)
+          bt = chr(96)  # backtick — avoid literal backticks that break gh-aw compiler
+          template = "\n".join([
+              "<!-- AUTOLOOP:UNCONFIGURED -->",
+              "<!-- Remove the line above once you have filled in your program. -->",
+              "<!-- Autoloop will NOT run until you do. -->",
+              "",
+              "# Autoloop Program",
+              "",
+              "<!-- Rename this file to something meaningful (e.g. training.md, coverage.md).",
+              "     The filename (minus .md) becomes the program name used in issues, PRs,",
+              "     and slash commands. Want multiple loops? Add more .md files here. -->",
+              "",
+              "## Goal",
+              "",
+              "<!-- Describe what you want to optimize. Be specific about what 'better' means. -->",
+              "",
+              "REPLACE THIS with your optimization goal.",
+              "",
+              "## Target",
+              "",
+              "<!-- List files Autoloop may modify. Everything else is off-limits. -->",
+              "",
+              "Only modify these files:",
+              f"- {bt}REPLACE_WITH_FILE{bt} -- (describe what this file does)",
+              "",
+              "Do NOT modify:",
+              "- (list files that must not be touched)",
+              "",
+              "## Evaluation",
+              "",
+              "<!-- Provide a command and the metric to extract. -->",
+              "",
+              f"{bt}{bt}{bt}bash",
+              "REPLACE_WITH_YOUR_EVALUATION_COMMAND",
+              f"{bt}{bt}{bt}",
+              "",
+              f"The metric is {bt}REPLACE_WITH_METRIC_NAME{bt}. **Lower/Higher is better.** (pick one)",
+              "",
+          ])
           with open(template_file, "w") as f:
-              f.write("""\
-<!-- AUTOLOOP:UNCONFIGURED -->
-<!-- Remove the line above once you have filled in your program. -->
-<!-- Autoloop will NOT run until you do. -->
-
-# Autoloop Program
-
-<!-- Rename this file to something meaningful (e.g. training.md, coverage.md).
-     The filename (minus .md) becomes the program name used in issues, PRs,
-     and slash commands. Want multiple loops? Add more .md files here. -->
-
-## Goal
-
-<!-- Describe what you want to optimize. Be specific about what "better" means. -->
-
-REPLACE THIS with your optimization goal.
-
-## Target
-
-<!-- List files Autoloop may modify. Everything else is off-limits. -->
-
-Only modify these files:
-- `REPLACE_WITH_FILE` — (describe what this file does)
-
-Do NOT modify:
-- (list files that must not be touched)
-
-## Evaluation
-
-<!-- Provide a command and the metric to extract. -->
-
-```bash
-REPLACE_WITH_YOUR_EVALUATION_COMMAND
-```
-
-The metric is `REPLACE_WITH_METRIC_NAME`. **Lower/Higher is better.** (pick one)
-""")
+              f.write(template)
           # Commit the template so the user can see and edit it
           os.system(f'git add "{template_file}"')
           os.system('git commit -m "[Autoloop] Bootstrap: add program template for configuration"')