Repository navigation
v0.1.1 — More reliable checks, safer exports, easier setup
This update makes the existing Codex-driven workflow more dependable, especially
when something fails or you're getting started on another machine.
Fixes
- Missing work can no longer look finished. Asset audits now require every
expected stage before reporting production readiness. Damaged or incomplete
records are flagged clearly, and existing evidence is preserved. - Failed prop exports stay failed. An old report can no longer make a failed
Blender run look successful. Each compile keeps its own files and logs, checks
that the new FBX and textures match their receipts, and protects existing outputs. - The installed CLI works outside the repository. The Python package now
includes the configuration needed to plan, create and audit asset workspaces. - Setup checks match what you're trying to run. Check just the ledger,
geometry, texturing or Unreal route. Missing optional tools won't block an
unrelated workflow, and JSON output reports failures correctly. - Local checks match CI. Verification now tests the installed package as well
as the source, and includes the same tests, lint and syntax checks on both paths.
Getting started
Update your checkout and reinstall the development dependencies:
.\.venv\Scripts\python.exe -m pip install -e ".[dev]"
.\scripts\workflow_doctor.ps1 -Profile ledger
.\scripts\verify.ps1For ledger-only use, install the attached wheel with python -m pip install <wheel-file> and run rac --help. The full Blender/Unreal pipeline still runs
from the source checkout. Model weights, engines and generated artwork are separate.
Existing work stays put. Use a new asset id when compiling a derivative into
an output directory that already exists. Historical reports remain readable;
this release does not migrate assets or change their approval status.
Validated on Python 3.11 and 3.12, including fresh wheel installs, plus a real
CPU-only Blender export/reimport fixture. No AI inference was needed for this
maintenance release. Visual review and cooked-runtime gates still apply.