Publish 'FileMaker Data API: VS Code vs Postman' comparison post

[deffenda]

Postman + myFMbutler collections is the dominant existing workflow for hitting the FileMaker Data API. Direct comparison post targets the exact long-tail Google query FM devs use when evaluating alternatives, demonstrates FileMaker-native advantages (.fmp12-aware schema, layout/script auto-complete, native types) over a generic REST client, and converts the largest addressable audience already paying a switching cost.

{
  "scope": [
    "Create docs/COMPARISON_POSTMAN.md (1200-1800 words",
    "SEO targeting 'FileMaker Data API VS Code'",
    "'FileMaker Data API Postman alternative'",
    "'FileMaker REST client'). Sections: (1) TL;DR comparison table (auth/session",
    "layout-aware autocomplete",
    "script/container handling",
    "env management",
    "team sharing",
    "cost); (2) Side-by-side Find workflow — Postman steps vs extension steps with screenshots; (3) Where Postman is still better (generic REST",
    "mock servers); (4) Migration section pointing to importer ticket; (5) CTA to marketplace listing. Add 'Compare to Postman' section anchor in README.md. Open GitHub Discussions thread 'FileMaker Data API: VS Code vs Postman — when to use which' with same content (or 300-word excerpt + link). Post technical answer on Claris Community linking canonical doc. Capture both URLs in PR description."
  ],
  "depends_on": [],
  "done_when": [
    "PR merged adding docs/COMPARISON_POSTMAN.md + README link; PR description contains live URLs to (a) GitHub Discussions thread and (b) Claris Community post, both pointing back to canonical doc."
  ],
  "validation": {
    "local": [],
    "review": []
  },
  "references": [],
  "surfaces": [],
  "artifact_expectations": [],
  "review_points": []
}