Context
During the 2026-07-02 branch triage on `chore/refresh-unified-chemical-mappings`, `git status` surfaced 126 untracked entries in the working tree. Most were captured by the new `.gitignore` rules in #578 — but ~30 entries need per-file decisions before they can be either committed, deleted, or gitignored.
What still needs a call
New utility modules (no in-repo references — either real work on the wrong branch, or dead scratch)
Scripts at repo root (root-level Python is almost always a one-off)
Unknown directories (peek and decide)
Data / mapping / xref files
Docs
Mappings
Notebooks
Rule of thumb: notebooks with a clear analytical purpose can be committed; `.ipynb_bak`, `_withoutput.ipynb`, `catboost_info/`, and rendered `.html` are now gitignored by #578.
Decision checklist per file
- Is anything in the repo already importing / referencing it? `grep -r 'basename' .` — no hits = not wired in.
- Was it ever tracked? `git log --all --follow -- ` — empty = fresh scratch.
- Would losing it be a problem tomorrow? If not, delete.
Related
Context
During the 2026-07-02 branch triage on `chore/refresh-unified-chemical-mappings`, `git status` surfaced 126 untracked entries in the working tree. Most were captured by the new `.gitignore` rules in #578 — but ~30 entries need per-file decisions before they can be either committed, deleted, or gitignored.
What still needs a call
New utility modules (no in-repo references — either real work on the wrong branch, or dead scratch)
Scripts at repo root (root-level Python is almost always a one-off)
Unknown directories (peek and decide)
Data / mapping / xref files
Docs
Mappings
Notebooks
Rule of thumb: notebooks with a clear analytical purpose can be committed; `.ipynb_bak`, `_withoutput.ipynb`, `catboost_info/`, and rendered `.html` are now gitignored by #578.
Decision checklist per file
Related