build: make managed Tor opt-in, and ignore upstream's committed build artifacts

Upstream 1.2.19 auto-starts a bundled tor whenever one sits next to the
executable: silent transport change, a spawned process, a new hidden service,
and descriptors going out with meeting_node="rendezvous-pending" -- on nodes
that never asked, against this fork's pinned-relay posture. The behavior moves
behind the explicit /automanagedtor; /managedtor stays as before.

Also ignore build-*.log, __pycache__/ and *.pyc so the five artifacts stripped
from the release merge cannot come back.

1 files changed, 5 insertions, 0 deletions

diff --git a/.gitignore b/.gitignore
index a74295a..b18859f 100644
--- a/.gitignore
+++ b/.gitignore
@@ -20,11 +20,16 @@ SHA256SUMS.asc
 # Runtime data / logs
 debug.log
 db.log
+build-*.log
 *.dat
 wallet.dat
 nostr.key
 btf_enc.key
 
+# Python cache (upstream's release commit accidentally shipped one)
+__pycache__/
+*.pyc
+
 # Third-party build trees (rebuilt by the build scripts)
 RandomX/
 deps/