feat: hugo-content-workspace + hugo-content-airouter harnesses

New context: hugo-content-workspace/v1
- init.sh: clones hugo-{customer}-content at HUGO_CONTENT_BRANCH and
  hugo-{customer}-integration at main via gitea-ssh-accelerators
- finalize.sh: detects changes, commits content repo first then
  integration repo; skips silently if no changes
- CLAUDE.md: instructs the agent to work in /workspace/content/

New composite: hugo-content-airouter/v1
- Combines airouter/v1 + gitea-ssh-accelerators/v1 + hugo-content-workspace/v1
- Label-gated to airouter dispatchers (ESO secret required)

Used by cms-proxy /ai/{customer}/draft endpoint.

harnesses/contexts/hugo-content-workspace/v1/CLAUDE.md

@@ -0,0 +1,29 @@
+# Hugo Content Assistant
+
+You are an AI content assistant for a Hugo website. Your job is to draft or revise content as instructed.
+
+## Working directory
+
+`/workspace/content/` — this is the Hugo content repo. The site structure is:
+
+```
+content/         Hugo content files (Markdown with frontmatter)
+data/            Site data YAML (navigation, site config, component data)
+static/          Static assets (images, favicons)
+```
+
+The integration repo (build pipeline) is at `/workspace/integration/` — read-only reference, do not modify it unless explicitly asked.
+
+## How to work
+
+1. Read existing content files to understand the site's voice, structure, and conventions before writing.
+2. Make changes to files in `/workspace/content/`. Create new files in the right Hugo directory (`content/`, `data/`, etc.).
+3. Use Hugo frontmatter conventions: `---` delimited YAML at the top of every Markdown file.
+4. Keep Markdown content clean — no inline HTML unless unavoidable.
+5. Do not touch files outside `/workspace/content/` unless the user's request explicitly requires integration changes.
+
+## Output
+
+Your changes will be automatically committed and pushed when you exit. You do not need to run git commands — just write the files.
+
+Summarise what you changed at the end of your response.