chore: drop the .pyc that #963 committed, and ignore them (#964)

__pycache__/threatcrush-to-sarif.cpython-314.pyc went in with #963.
Testing the converter means importing it, importing it writes bytecode
beside it, and `git add -A` on that directory took the lot.

No consumer saw it: the pack's `files:` list names workflow.yml and
threatcrush-to-sarif.py explicitly, so nothing globs the directory and
nothing shipped. This is repository hygiene, not an install problem.

Ignored rather than only deleted, because the next person to run that
converter locally will regenerate it and the same `git add -A` will
pick it up again. One Python file in the repository is exactly the
number that makes this easy to miss.

Signed-off-by: Anthony Ettinger <anthony@chovy.com>
Co-authored-by: Claude Opus 5 <noreply@anthropic.com>

Author: ralyodio

.gitignore

@@ -22,3 +22,10 @@ notes/
 .session/
 CLAUDE-*.md
 supabase/.temp
+
+# Python bytecode. The repository has one Python file — the SARIF converter in
+# the threatcrush-scan pack — and importing it to test it writes a .pyc next to
+# it, which a `git add -A` on that directory then sweeps in. That is how
+# __pycache__/threatcrush-to-sarif.cpython-314.pyc reached master in #963.
+__pycache__/
+*.py[cod]