git:20261012.3e9b678 to git:20261015.13d6774

6 added, 2 removed. Audit A to A.

# MuseDraw repository conventions

- - Keep the project positioning broad: a professional drawing assistant. Only publish

- capabilities that have a usable workflow; architecture is the first workflow.

+ - Keep the project positioning broad: a professional drawing assistant for research,

+ office work, teaching and engineering. Only publish capabilities with a usable workflow.

+ - New gallery cases: a folder with `scene.json` and `prompt.md`; render with

+ `npm run gallery`, open the PNG, and fix every `checks.json` warning before review.

- Preserve user facts and unchanged diagram content during style-only revisions.

+ - Use the project's configured contributor identity for commits. Do not add

+ model names, generated-by signatures or model co-author trailers to code or commits.

- Use `feat/`, `fix/`, `docs/`, `test/`, `refactor/` or `chore/` for task branches.

Branch names must not contain `codex`, case-insensitively. This does not prohibit

accurate documentation of the actual Codex client.

- Run `python scripts/check.py` before proposing a contribution. Browser rendering

is a separate check, not implied by offline test success.

- Community examples must be original or explicitly licensed for distribution.

Public visibility does not grant permission to copy templates or screenshots.

- Never include credentials, private user artifacts or local absolute paths in

published examples. Do not claim universal accuracy or token savings without a

reproducible, fair experiment.