Replace outdated workflow with validation

[bb220]

What changed

Replaced the stale docs updater setup with a focused docs validation workflow.

Removed:

• .github/CODEOWNERS
• .github/workflows/update-docs.yml
• DOCS_UPDATER_SETUP_TODO.md
• The duplicated local validation command block from AGENTS.md

Added:

• .github/workflows/docs-validation.yml

The new workflow runs on pull requests into master and can also be triggered manually. It checks:

jq empty docs.json
jq empty openapi.json
mint broken-links
mint validate

Why

The old GitHub Actions setup was outdated and broken. This keeps PR validation lightweight and docs-focused: JSON syntax checks for the core config/spec files, link checking, and Mintlify build validation. Since these checks now run in CI, the agent review guide no longer needs to ask reviewers to run that command block manually.

Validation

Ran locally:

jq empty docs.json
jq empty openapi.json
mint broken-links
mint validate

All checks passed. mint validate needed access to refresh Mintlify's local cache, then completed successfully.

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
promptlayer	🟢 Ready	View Preview	May 19, 2026, 2:06 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e5c861d495

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Update the remaining updater setup guide

@claude Removing the workflow leaves the tracked DOCS_UPDATER_SETUP_TODO.md instructions pointing at .github/workflows/update-docs.yml as deployed and telling maintainers to run gh workflow run update-docs.yml; with this entrypoint gone, anyone following the setup/test guide will fail to trigger the documented automation. Please either keep a replacement workflow or update/remove that setup guide alongside this deletion.

Useful? React with 👍 / 👎.

[bb220]

@claude remove that setup guide as well