feat(windsurf): add Windsurf as converter target provider

[rburnham52]

Summary

• Add --to windsurf support for convert and install CLI commands
• Converts Claude Code plugins to Windsurf format with full component mapping:
  • CLAUDE.md → AGENTS.md at project root (path-rewritten)
  • Agents → .windsurf/workflows/agents/*.md (YAML frontmatter + markdown body)
  • Commands → .windsurf/workflows/commands/*.md (separate subdirectory preserves semantic type)
  • Skills → .windsurf/skills/*/SKILL.md (pass-through with path rewriting)
  • MCP servers → .windsurf/mcp-setup.md (human-readable setup instructions, secrets redacted)
  • Hooks → skipped with warning (no Windsurf equivalent)

Architecture

Follows the established 3-layer target provider pattern:

• src/types/windsurf.ts — WindsurfBundle, WindsurfWorkflow, WindsurfSkillDir
• src/converters/claude-to-windsurf.ts — converter with 4 content transformation rules
• src/targets/windsurf.ts — writer with double-nesting guard and path validation

Testing

• 46 new tests (30 converter, 10 writer, 6 normalizeName)
• 179 total converter/writer tests pass across all targets with 0 regressions
• Covers: content transformation, name normalization/deduplication, 12K char limit warnings, path traversal protection, MCP secret redaction, AGENTS.md backup, empty bundles

Post-Deploy Monitoring & Validation

No additional operational monitoring required: CLI tool with no runtime/server component.

---

🤖 Generated with Claude Code

[rburnham52]

I'm playing around with adding a converter for windsurf. It still needs testing but let me know if this might be useful?

I also have a branch for Devin but because most of the concepts are hosted it's a bit more complex. I added the converter but also addded an sync scripts to import via api key. This process still needs some testing as well but let me know if you think it's useful as well. The windsurf convention was more of a 1 - 1 match.

https://github.com/rburnham52/compound-engineering-plugin/tree/feat/devin-target-provider