docs: add swagger readme

Author: TristanSpeakEasy

swagger/README.md

@@ -0,0 +1,39 @@
+<p align="center">
+  <p align="center">
+    <img  width="200px" alt="Swagger" src="https://github.com/user-attachments/assets/5d00308c-8fda-4b5b-bf39-16b10bccfe6f">
+
+
+  </p>
+  <h1 align="center"><b>Swagger Parser</b></h1>
+  <p align="center">An API for working with Swagger Documents including: read, walk, create, mutate, and validate
+</p>
+  <p align="center">
+     <!-- Built By Speakeasy Badge -->
+     <a href="https://speakeasy.com/"><img alt="Built by Speakeasy" src="https://www.speakeasy.com/assets/badges/built-by-speakeasy.svg" /></a>
+    <a href="https://github.com/speakeasy-api/openapi/releases/latest"><img alt="Release" src="https://img.shields.io/github/release/speakeasy-api/openapi.svg?style=for-the-badge"></a>
+    <a href="https://pkg.go.dev/github.com/speakeasy-api/openapi/swagger?tab=doc"><img alt="Go Doc" src="https://img.shields.io/badge/godoc-reference-blue.svg?style=for-the-badge"></a>
+   <br />
+    <a href="https://github.com/speakeasy-api/openapi/actions/workflows/test.yaml"><img alt="GitHub Action: Test" src="https://img.shields.io/github/actions/workflow/status/speakeasy-api/openapi/test.yaml?style=for-the-badge"></a>
+    <a href="https://goreportcard.com/report/github.com/speakeasy-api/openapi"><img alt="Go Report Card" src="https://goreportcard.com/badge/github.com/speakeasy-api/openapi?style=for-the-badge"></a>
+    <a href="/LICENSE"><img alt="Software License" src="https://img.shields.io/badge/license-MIT-blue.svg?style=for-the-badge"></a>
+  </p>
+</p>
+
+## Contributing
+
+This repository is maintained by Speakeasy, but we welcome and encourage contributions from the community to help improve its capabilities and stability.
+
+### How to Contribute
+
+1. **Open Issues**: Found a bug or have a feature suggestion? Open an issue to describe what you'd like to see changed.
+
+2. **Pull Requests**: We welcome pull requests! If you'd like to contribute code:
+   - Fork the repository
+   - Create a new branch for your feature/fix
+   - Submit a PR with a clear description of the changes and any related issues
+
+3. **Feedback**: Share your experience using the packages or suggest improvements.
+
+All contributions, whether they're bug reports, feature requests, or code changes, help make this project better for everyone.
+
+Please ensure your contributions adhere to our coding standards and include appropriate tests where applicable.