enforce dimOS usage

[paul-nechifor]

Always use dimOS in docs (never DimOS)

[mintlify]

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

Project	Status	Preview	Updated (UTC)
dimensional	🟢 Ready	View Preview	Aug 20, 2026, 12:53 AM

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

[greptile-apps]

Greptile Summary

This change updates the Boston Dynamics Spot documentation to use the dimOS brand spelling and adds a check that prevents the deprecated DimOS spelling from being added to Markdown and MDX documentation. The check passed across the current documentation tree, and it correctly failed with the file and line number after a temporary MDX document containing the deprecated spelling was introduced.

Confidence Score: 5/5

The documentation update and its enforcement check behaved as intended in the exercised documentation flows.

The current documentation scan completed without deprecated brand references, and a temporary invalid MDX file reliably triggered the new assertion with its precise location.

Files Needing Attention: No files require follow-up.

T-Rex Logs

What T-Rex did

• Ran the branding reproduction script against the current documentation tree, and the scanner reported zero deprecated brand references with the assertion passing.
• Created a temporary DimOS MDX fixture to test branding; the assertion failed at docs/trex-branding-fixture.mdx line 2, and the fixture was subsequently removed.
• Reproduced the branding checks using the reproduction script to capture baseline and injected runs; the baseline run exited 0, the injected run exited 1 and was treated as expected by the harness, whose overall exit was 0.
• When attempting to run the tests with pytest directly, the run failed to collect due to a missing dotenv package, so the workflow used the narrow reproduction script instead.

_{Ran code and verified through T-Rex}

_{Reviews (1): Last reviewed commit: "enforce dimOS" | Re-trigger Greptile}

[codecov]

Codecov Report

❌ Patch coverage is 73.68421% with 5 lines in your changes missing coverage. Please review.
✅ All tests successful. No failed tests found.

Files with missing lines	Patch %	Lines
dimos/codebase_checks/test_docs_branding.py	73.68%	3 Missing and 2 partials ⚠️

@@            Coverage Diff             @@
##             main    #3561      +/-   ##
==========================================
- Coverage   76.40%   76.40%   -0.01%     
==========================================
  Files        1244     1245       +1     
  Lines      120503   120522      +19     
  Branches    10737    10742       +5     
==========================================
+ Hits        92069    92083      +14     
- Misses      25333    25336       +3     
- Partials     3101     3103       +2     

Flag	Coverage Δ
OS-ubuntu-24.04-arm	70.88% <73.68%> (+<0.01%)	⬆️
OS-ubuntu-latest	72.64% <73.68%> (+<0.01%)	⬆️
Py-3.10	72.64% <73.68%> (+<0.01%)	⬆️
Py-3.11	72.63% <73.68%> (-0.01%)	⬇️
Py-3.12	72.63% <73.68%> (+<0.01%)	⬆️
Py-3.13	72.63% <73.68%> (-0.01%)	⬇️
Py-3.14	72.64% <73.68%> (+<0.01%)	⬆️
Py-3.14t	72.63% <73.68%> (-0.01%)	⬇️
SelfHosted-Large	29.80% <26.31%> (-0.01%)	⬇️
SelfHosted-Linux	35.78% <26.31%> (-0.02%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
dimos/codebase_checks/test_docs_branding.py	73.68% <73.68%> (ø)

... and 2 files with indirect coverage changes

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.