Convert curl commands and Postman collections into OpenAPI (without losing fields)

Two artifacts appear in every API integration: a curl command someone pasted into Slack, and a Postman collection exported from someone's account. Both are presented as "the API docs." Neither is documentation — but both are salvageable as raw material for an OpenAPI spec, as long as you know what each conversion preserves and what it silently destroys. Take a realistic capture: curl -X POST 'https://api.example.com/v1/projects?dry_run=false' \ -H 'authorization: Bearer eyJhbGciOi...' \ -H 'content-type: application/json' \ -H 'idempotency-key: 7b32f1' \ --data '{"name":"Apollo","plan":"TEAM",