blender-knowledge-workbench

# Blender Knowledge Workbench Run commands from the project root containing `.project-agent.md`. The CLI also resolves that root from its own path. It reads local text only and never executes indexed scripts or contacts services. ## Choose the smallest useful reading pack 1. Run `python3 scripts/blender-knowledge.py check`. If missing/stale, run `build` after the source edits settle, then `check`. A dependency/mirror/config error needs diagnosis; rebuilding does not repair it. 2. For new/changed knowledge or workflow/skill maintenance, follow [knowledge-to-workflow pipeline](references/knowledge-to-workflow.md). Run `python3 scripts/blender-knowledge.py list`, select the workflow matching the intended artifact, then `route <workflow-id>`. Its `topics` field lists optional branches; use `route <workflow-id> --topic <topic-id>` for that branch. A changed topic source requires re-review. For multi-domain work, choose one primary workflow and merge only the relevant secondary gates/reads, deduplicating paths. 3. Read `required` sources not already in context. Three foundations are required for Blender execution. `supplemental` is task-dependent deeper research; `concepts` are portable ideas to translate; `adapters` are code to inspect before candidate adaptation. `related` is a one-hop optional queue, never recursive mandatory loading. 4. Search an unresolved question with `search "joint inertia" --limit 5`. Results include source path, line, hash, use class and known cautions...