feat(pipeline): InDesign as a first-class Flavian workflow — agent, skill, CLI, docs (#66)

[PAMulligan]

Sub-issue of #61 — the closes candidate for the epic. Ships the user-facing surface that turns the underlying InDesign pipeline (#62–#65) into something developers actually use.

What's included

Agent — .claude/agents/indesign-to-wordpress.md

Orchestrates parse → map-tokens → generate, then reads the generation report and proposes concrete follow-ups (unmapped frames, font fallbacks to confirm, image alt text to add). Non-destructive: works on a feature branch, never main. PreToolUse theme-location guard + PostToolUse validators (block markup, token audit, security, WPCS). Referenced from CUSTOM-AGENTS-GUIDE.md.

Skill — .claude/skills/indesign-conversion/SKILL.md

When-to-use, prerequisites (exported .idml or PDF), expected outputs, common gotchas (CMYK→sRGB shifts, missing fonts, oversized print images), and a runnable worked example against the committed code fixture. Referenced from skills/README.md.

CLI — bin/flavian.mjs

flavian pipeline indesign <input> [--seed-content] [--output <dir>]

• Honors flavian.config.json (output path, base theme, namespace; CLI flags override) — see flavian.config.example.json
• Emits a machine-readable indesign-pipeline-report.json alongside the Markdown report
• flavian pipeline indesign --help prints documented usage
• Registered as the flavian bin + pnpm flavian script

Documentation

• docs/pipelines/indesign.md — exporting from InDesign (IDML & PDF), expected output, fidelity expectations, troubleshooting
• README Pipelines section now lists InDesign alongside Figma and Canva
• Agent/skill indexes and counts updated; v2.0.0 release-notes draft updated

CI smoke test

scripts/indesign-fse/smoke-test.mjs builds a two-spread brochure fixture in code (no committed binaries), runs the real CLI end-to-end, and asserts the generated theme is valid (theme.json v3, one pattern per spread, indesign-imports category). Wired into pipeline-tests.yml.

Acceptance criteria

• indesign-to-wordpress agent exists, follows the Flavian agent shape, referenced from the agents index
• indesign-conversion SKILL.md exists with a runnable example
• flavian pipeline indesign --help prints documented usage
• docs/pipelines/indesign.md published and linked from the README
• README's Pipelines section lists InDesign
• End-to-end smoke test in CI runs the pipeline against the committed fixture and asserts the theme is valid

Tests

• pnpm --filter @flavian/pipeline test → 100 passing (adds a JSON-report test)
• node scripts/indesign-fse/smoke-test.mjs → ✓ valid theme (2 spreads, theme.json v3)
• Agent/skill config validation passes

Notes

• Builds on [InDesign pipeline] Output generator: FSE block patterns, templates, and theme.json writer #65 (now merged to main).
• Counts in CLAUDE.md / CUSTOM-AGENTS-GUIDE.md reconciled to the actual totals (53 agents, 12 skills).
• When this ships, the InDesign epic Add InDesign-to-WordPress conversion pipeline #61 can be closed.

🤖 Generated with Claude Code