python3 scripts/prepare_weekly_docs_update.py --output-dir .docs-update-reports/latest --force

.docs-update-reports/latest/weekly-docs-update.md

You are updating the DialNexa Mintlify docs in /Users/kamat/Documents/projects/api-docs.

Follow AGENTS.md exactly. Do not use em dash or en dash punctuation in docs prose. Keep changes scoped to source behavior changes. Review source diffs bidirectionally: new behavior may need docs added, and removed, renamed, hidden, deprecated, or unsupported behavior may need docs deleted or revised.

First run:

python3 scripts/prepare_weekly_docs_update.py --output-dir .docs-update-reports/latest --force

Read .docs-update-reports/latest/weekly-docs-update.md.

If dashboard-be changed, also read .docs-update-reports/latest/dashboard-be-v1-api-docs-audit.md. For every added v1 route that is not present in OpenAPI, decide whether it is public API, dashboard-only API, provider webhook, or internal API. Public API changes must update api-reference/openapi.json and matching MDX pages. For every removed v1 route that is still present in OpenAPI or still referenced in docs, delete the stale docs operation or reference. Intentionally excluded routes must be listed in the PR body with the reason.

If the dashboard-be diff touches src/modules/mcp/**, the MCP tool catalog may have changed (a tool added, removed, renamed, or its description or parameters edited). Re-sync the generated docs instead of hand-editing them. The prepare script only fetches dashboard-be's origin/master ref for diffing; it does not pull that commit into the sibling worktree, so the checkout on disk can be behind what the report just diffed. Before exporting, run the exporter from the exact origin/master commit in a clean or detached worktree. Do not switch or pull a dashboard-be worktree that has local changes. Then run `npm run mcp:export`, copy the resulting dashboard-be/scripts/output/mcp-tools.raw.json to mcp-tools/_generated/mcp-tools.raw.json in this repo, and run `python3 scripts/build-mcp-tools-from-export.py`. The builder creates one page per tool, group overviews, navigation entries, compatibility redirects, and the tracked manifest. Run `python3 scripts/validate_mcp_tool_docs.py` and review the generated diff. If endpoint, authentication, transport, or common response behavior changed, update the hand-authored MCP overview, quickstart, or error guide.

If all three source repos have 0 new commits, report that no docs update is needed and stop.

For each source repo with new commits:
1. Inspect the changed files listed in the report, including additions, deletions, renames, and behavior removals.
2. Read directly referenced helpers only when needed to understand user-facing behavior.
3. Decide which docs need additions, removals, or edits. Delete stale MDX prose, OpenAPI operations, docs.json navigation entries, screenshots, examples, and changelog links when the current codebase no longer supports them.
4. Update the affected MDX pages, docs.json, images, or api-reference/openapi.json.
5. For dashboard-be API changes, compare added and removed controllers, DTOs, guards, and routes.config entries against api-reference/openapi.json, API MDX pages, docs prose, and the API reference navigation.
6. If dashboard UI changes need screenshots, ask me for the exact screenshots needed and pause before creating a PR.

After I provide screenshots:
1. Add or replace the screenshot assets.
2. Update the affected docs with meaningful alt text.
3. Add a dated changelog entry to the matching monthly page under changelog/.
4. In the monthly changelog summary, use one table row per H3 update. Link each Update cell and each dated H3 update title to the exact destination section, not just the page top. Do not group multiple updates into one summary row.
5. If the changelog month page is new, add it under Changelog > Platform in docs.json.
6. Update DOCS_SOURCE_SNAPSHOT.md to the latest source commits from the report.
7. Run:

npx -y -p node@20 -p mint@latest mint validate
rg -n $'\u2014|\u2013' --glob '!mcp-tools/**' .
git diff --check
python3 -m json.tool api-reference/openapi.json >/dev/null
python3 -m json.tool docs.json >/dev/null
python3 scripts/validate_mcp_tool_docs.py

8. Fix any failures.
9. Commit the changes on a branch named codex/weekly-docs-update-YYYY-MM-DD.
10. Push the branch and open a draft PR for manual review.
11. In the PR body, include the source commit ranges, docs pages changed, screenshots requested or added, dashboard-be v1 API audit outcome, intentionally excluded routes, and validation results.

{
  "date": "2026-05-25",
  "updates": [
    {
      "title": "Batch call validation guidance",
      "body": "Updated recipient upload docs to explain grouped validation errors, failed row handling, and the expected correction flow."
    }
  ]
}

python3 scripts/add_changelog_entry.py --entry-file .docs-update-reports/latest/changelog-entry.json