Repo hygiene: coverage.json (1.6MB) tracked again; .gitignore ends with broken '.json' entry; node_modules/ unignored

Problem

Three repo-hygiene problems verified via git ls-files / git check-ignore:

1. coverage.json (1.6 MB) is tracked by git. It was removed once in a51f1cd5 ("chore: remove coverage.json artifact") but came back in 5720fd84 ("test: 97.5% coverage for command_line modules"). It is a regenerated test artifact and bloats every clone.

2. The last line of .gitignore is literally .json, which only ignores a file named .json — it does not ignore coverage.json (which is why it got re-committed) and was almost certainly a typo for coverage.json. Introduced in f1715e25.

# last lines of .gitignore
.claude/hooks/ts-hooks/dist/

.json        # <-- matches nothing useful

3. node_modules/ (4.6 MB, containing docx/jszip/pako/etc.) sits at the repo root with no ignore entry. It's currently untracked, but nothing prevents an accidental git add . from committing it. There's no package.json at the root either, so it appears to be leftover tooling debris.

Untracked-but-ignored junk also present locally (.coverage at root and code_puppy/.coverage, .DS_Store files) — those are correctly covered by .gitignore lines 12 and 24, no action needed. code_puppy/models_dev_api.json (535 KB) is tracked deliberately as wheel shared-data per pyproject.toml, so it is not flagged here.

Suggested fix

git rm --cached coverage.json

And in .gitignore, replace the trailing .json line:

-.json
+coverage.json
+node_modules/

Filed by Zen Reviewer C (code-puppy-60635a)

Start by inspecting the repository root .gitignore and verify the reported state with git ls-files and git check-ignore. Remove the tracked coverage.json entry and ensure coverage.json and node_modules/ are ignored; done means coverage.json is no longer tracked and both artifact paths are covered by .gitignore.