fix: require conventional commits in Mintlify workflow instructions

.mintlify/workflows/update-api-reference.md

@@ -32,3 +32,4 @@ If new endpoint tags (groups) are introduced, add corresponding entries to the A
 - If no API changes were introduced, do nothing.
 - Do not include private repository file paths, directory structures, code snippets, or any other internal implementation details in PR titles, descriptions, or commit messages. The PR body should only describe the user-facing change in terms of the API behavior.
 - Do not modify any files other than `api-reference/openapi.json` and `config/navigation.json`.
+- PR titles and commit messages must follow the conventional commits format described in CLAUDE.md. Use `docs:` as the type.

.mintlify/workflows/update-changelog.md

@@ -40,3 +40,5 @@ For each change, describe what changed and what it means for users. Organize ent
 If unsure about the structure, review recent changelog updates and follow that style and format.
 
 Be polite and terse. The changelog must be skimmable and quick to read. Include relevant links to docs pages.
+
+PR titles and commit messages must follow the conventional commits format described in CLAUDE.md. Use `docs:` as the type.

.mintlify/workflows/update-terraform-reference.md

@@ -28,3 +28,5 @@ When creating or updating pages:
 - Include example usage, schema (required/optional/read-only), and import instructions where applicable.
 
 Do not modify changelog/index.mdx — that is handled by the "Update changelog" workflow.
+
+PR titles and commit messages must follow the conventional commits format described in CLAUDE.md. Use `docs:` as the type.