feat(workflows): expand template library from 9 to 22 + multiline string cleanup (#36)

* feat(workflows): add 13 workflow templates across engineering, business, and productivity

Engineering:
- bug-triage: reproduce path → root cause → fix plan
- api-design: resource model → endpoints → OpenAPI spec
- incident-postmortem: timeline → RCA → full postmortem report
- test-generation: code analysis → edge cases → full test suite
- refactor-plan: smell analysis → prioritised opportunities → migration plan

Business:
- competitor-analysis: profiles → SWOT → strategy report
- product-spec: problem definition → user stories → full PRD
- market-research: landscape → segments → research report

Productivity/Thinking:
- meeting-summary: raw notes → structured summary → follow-up email
- decision-matrix: criteria → weighted scoring → recommendation memo
- learning-plan: gap analysis → roadmap → week-1 day-by-day plan
- job-application: job analysis → tailored resume → cover letter → interview prep
- blog-post: research → outline → draft → SEO optimisation

Closes #1912 on librefang/librefang

* fix(workflows): overhaul existing 9 templates

- data-pipeline: redesigned — original 'extract from URL' step was
  broken (LLMs cannot fetch URLs); replaced with paste-data approach
  (profile → clean_transform → analyse) with analysis_goal parameter
- translate-polish: added target_language and register parameters;
  added back-translation step for accuracy verification
- weekly-report: added team/audience parameters, richer extraction
  step, added Metrics and Notes sections
- content-pipeline: added audience/tone parameters, added outline step
  between research and writing
- content-review: fix category 'content' → 'creation'
- customer-support: fix category 'support' → 'business'

* style(workflows): convert all prompt_template strings to TOML multiline syntax

Replace \n escape sequences with real newlines using triple-quote
multiline strings ("""...""") across all 22 workflow templates.
No content changes — formatting only.

* style(hands): replace \n escape in reddit writer format example with multiline code block

workflows/bug-triage.toml

@@ -0,0 +1,67 @@
+id = "bug-triage"
+name = "Bug Triage & Fix Plan"
+description = "Analyse a bug report, reproduce the failure path, identify root cause, and produce a prioritised fix plan with test cases."
+category = "engineering"
+tags = ["bug", "debugging", "triage", "engineering"]
+
+[i18n.zh]
+name = "Bug 分析与修复计划"
+description = "分析 Bug 报告，还原失败路径，定位根因，输出优先级排序的修复计划与测试用例。"
+
+[[parameters]]
+name = "bug_report"
+description = "The bug report, error message, or stack trace"
+param_type = "string"
+required = true
+
+[[parameters]]
+name = "codebase_context"
+description = "Relevant code snippets or architecture description"
+param_type = "string"
+required = false
+default = ""
+
+[[steps]]
+name = "reproduce_path"
+prompt_template = """
+You are a senior engineer doing bug triage. Given the bug report below, reconstruct the exact failure path:
+1. Preconditions that must be true
+2. Step-by-step sequence that triggers the bug
+3. What the system does vs. what it should do
+4. Affected components and data flow
+
+Bug report:
+{{bug_report}}
+
+Codebase context:
+{{codebase_context}}
+"""
+
+[[steps]]
+name = "root_cause"
+prompt_template = """
+You are a debugging expert. Based on the failure path analysis, identify the root cause:
+1. Immediate cause (the direct code/logic fault)
+2. Contributing factors (environment, race condition, assumption violation)
+3. Why this was not caught earlier (missing test, wrong assumption)
+4. Blast radius — what else could be affected
+
+Failure path:
+{{reproduce_path}}
+"""
+depends_on = ["reproduce_path"]
+
+[[steps]]
+name = "fix_plan"
+prompt_template = """
+You are a tech lead. Produce a concrete fix plan:
+1. **Recommended fix** — specific code change with rationale
+2. **Alternative approaches** — trade-offs of each
+3. **Test cases to add** — unit, integration, regression
+4. **Rollout recommendation** — hotfix vs. normal release, feature flag needed?
+5. **Prevention** — process or tooling changes to prevent recurrence
+
+Root cause analysis:
+{{root_cause}}
+"""
+depends_on = ["root_cause"]