fix(docs): MDX 2 parser kills cost-benchmark page on '<1 pp' prose#62
Merged
Conversation
Same class of bug as PR #58 commit 10c492c (the-team page 404 root cause): MDX 2 (used by Mintlify) treats '<' followed by any non- whitespace character as the start of a JSX opening tag — including digits. Line 101's '**<1 pp**' was parsed as a malformed JSX attempt, the file failed compilation, Mintlify's deploy of PR #60 (commit 6fe485a) failed with "Encountered syntax error(s). Deployment not updated", and the live docs at docs.zerooperators.com stayed on the pre-PR-#60 cached version (still showing the '(pending)' tracking table row instead of the measured '$7.75 / 30%' values). Fix: replace '<1 pp' with 'under 1 pp' — natural prose, preserves semantic meaning, no MDX gotcha. Same fix pattern as PR #58. Repo-wide regex sweep confirmed this is the only remaining unescaped '<digit' or '<letter' pattern in tracked .mdx files outside of code fences and valid Mintlify components (<Note>, <Warning>, <Tabs>, etc). Mintlify will redeploy automatically on merge. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Deploying zero-operators with
|
| Latest commit: |
2b23462
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://02c4b9c9.zero-operators.pages.dev |
| Branch Preview URL: | https://claude-docs-fix-mdx-less-tha.zero-operators.pages.dev |
4 tasks
SamPlvs
added a commit
that referenced
this pull request
Apr 30, 2026
fix(docs): MDX 2 parser kills cost-benchmark page on '<1 pp' prose
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Mintlify's deploy of PR #60 (commit 6fe485a) failed with "Encountered syntax error(s). Deployment not updated" — the live docs at docs.zerooperators.com stayed on the pre-PR-#60 cached version (still showing the `(pending)` tracking table row instead of the measured `$7.75 / 30%` values).
Same class of bug as PR #58 commit 10c492c (the-team page 404 root cause): MDX 2 treats `<` followed by any non-whitespace character — including digits — as the start of a JSX opening tag. Line 101 of `docs/reference/cost-benchmark.mdx` had `<1 pp` in prose. The `<1` was parsed as a malformed JSX attempt, the file failed compilation, Mintlify silently dropped the deploy.
Fix
One-line: replace `<1 pp` with `under 1 pp`. Natural prose, preserves semantic meaning, no MDX gotcha. Same fix pattern as PR #58.
Sweep
Repo-wide regex sweep (`grep -E '<[0-9]|<[a-zA-Z]' docs/**/*.mdx`) confirmed this is the only remaining unescaped `<digit` or `<letter` pattern in tracked `.mdx` files outside of code fences and valid Mintlify components (``, ``, ``, etc.).
Test plan
🤖 Generated with Claude Code