Add top-level CLI workflows

[Ahmed-Hindy]

Summary

• Add the top-level materials-processor console script with Blender workflow commands and runtime validation commands.
• Add materials-processor blender inspect and route materials-processor blender export-usd through the shared Blender CLI implementation.
• Add texture remap/search options plus policy flags for missing textures and unsupported Blender nodes.
• Add materials-processor runtime validate --dcc blender|maya, including optional material smoke validation.
• Keep CLI failures clean by returning error: ... without Python tracebacks for expected runtime/configuration errors.

Changed-Code Review

• Reviewed the semantic diff before publishing.
• Fixed one review issue: explicit export-usd --graph-json paths now create their parent directory before Blender writes the extraction JSON.
• Removed an unused helper from the Blender CLI module.
• No remaining blocking findings found in the changed-code review.

Validation

• uv --native-tls run ruff check
• uv --native-tls run pytest tests/test_cli.py tests/test_blender_cli.py tests/test_public_imports.py
• uv --native-tls run pytest
• uv --native-tls run materials-processor runtime validate --dcc blender --material-smoke --timeout 120
• uv --native-tls run materials-processor runtime validate --dcc maya --material-smoke --timeout 180
• Real Blender scene inspect against G:\Projects\AYON_PROJECTS\mo_ashraf\Mojar_01\sh_001\work\lighting\mo_sh_001_lighting_v005.blend
• Real Blender scene MaterialX/OpenPBR USD export against the same scene
• Missing texture policy smoke: confirmed --missing-textures error writes the report and exits cleanly with code 1

Known Scene Findings

• The real Blender scene still has unsupported ShaderNodeGroup entries on felt_fabric_03 and old_gold_04.
• The real Blender scene still reports two missing BlenderKit texture paths for Marble.012.

[coderabbitai]

Warning

Review limit reached

@Ahmed-Hindy, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 12 minutes and 35 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: d799e39e-e4b7-4696-8bb1-1127a246976d

📥 Commits

Reviewing files that changed from the base of the PR and between 7e9bb45 and d641279.

📒 Files selected for processing (6)

• pyproject.toml
• src/materials_processor/cli.py
• src/materials_processor/dcc/blender/cli.py
• tests/test_blender_cli.py
• tests/test_cli.py
• tests/test_public_imports.py

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/top-level-cli-workflows

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}