hap-api-doc-updater

To keep OpenAPI documentation in sync across English and Chinese versions, you apply a disciplined workflow that propagates endpoint additions, updates, and deletions to maintain bilingual parity.

The best way to update organization-level and application-level API endpoints bilingually is to enforce OpenAPI 3.0 structure and consistent file layouts while propagating changes across language versions.

Yes, you can use this workflow to add and delete API endpoints while ensuring structural parity by enforcing OpenAPI 3.0 structure and updating paths, descriptions, and schemas consistently.

Synchronizing bilingual OpenAPI docs does not require updating paths and schemas manually across languages; the workflow automates propagation to ensure consistent descriptions, parameters, and schemas.

You need to reconcile changes between en/openapi.yaml and zh-Hans/openapi.yaml whenever APIs evolve and endpoint definitions diverge, requiring you to review diffs and commit updated docs to restore bilingual parity.