fix(docs): resolve heading anchors the way Mintlify publishes them

[datlechin]

main has failed Validate docs since #2988:

FAIL features/sql-editor.mdx:93 links to /databases/oracle#pl%2Fsql, but that heading does not exist

The link is right and the checker is wrong. docs/scripts/check-links.py turned a heading into an anchor with [^a-z0-9]+ -> -, so it expected #pl-sql. Mintlify publishes the ## PL/SQL heading as id="pl/sql" (and ## SSL/TLS as ssl/tls), so a #pl-sql link would have passed CI and been broken on the live site.

Changes

• heading_anchor follows the rule Mintlify publishes. I checked it against every heading on docs.tablepro.app: 1257 of 1257 ids match. A slash, &, @, _, … and curly apostrophes stay. Brackets, :, ,, ;, ?, ~ and backticks are dropped. A full stop separates words the way a space does. Mintlify also curls straight quotes, and which way it curls one depends on text outside the heading, so quote characters compare as one character on both sides.
• Link anchors are percent-decoded before the lookup, so #pl%2Fsql and #pl/sql both resolve.
• verify.sh docs now runs check-links.py too. It ran the other two docs checks only, which is why this passed locally and failed in CI. With the old checker put back, verify.sh docs now reports the same FAIL CI did.
• verify.sh gets DEVELOPER_DIR from xcode-select -p when that is a full Xcode, then falls back to Xcode.app, then Xcode-beta.app. It used to try Xcode-beta.app first, and that app is no longer installed. The fix-issue references no longer hard-code that path. They also said TablePro targets macOS 14, but project.yml sets deploymentTarget to 13.0, so API availability advice was off by one release.

No CHANGELOG entry: tooling and docs checks only.

[mintlify]

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

Project	Status	Preview	Updated
TablePro	🟢 Ready	View Preview	Sep 18, 2026, 6:40 PM

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