fix: nuke dummy binaries + fingerprints before second cargo build

Touch alone wasn't enough — cargo can still reuse cached fingerprint
state from the dependency-cache layer. Explicitly remove the dummy
binaries and their fingerprint dirs so the second build reproduces
real artifacts unconditionally.

Also drop the obsolete `version: '3.9'` from docker-compose.yml.

Co-Authored-By: OpenClaude <openclaude@gitlawb.com>

Author: kevincodex1

Dockerfile

@@ -29,6 +29,10 @@ RUN mkdir -p crates/gitlawb-core/src crates/gitlawb-node/src crates/gl/src crate
 # and the runtime container exits immediately with code 0.
 COPY crates/ crates/
 RUN find crates -name "*.rs" -exec touch {} + && \
+    rm -f target/release/gitlawb-node target/release/gl target/release/git-remote-gitlawb && \
+    rm -rf target/release/.fingerprint/gitlawb-node-* \
+           target/release/.fingerprint/gl-* \
+           target/release/.fingerprint/git-remote-gitlawb-* && \
     cargo build --release -p gitlawb-node -p gl -p git-remote-gitlawb && \
     strip target/release/gitlawb-node target/release/gl target/release/git-remote-gitlawb
 

docker-compose.yml

@@ -1,5 +1,3 @@
-version: '3.9'
-
 # Run a gitlawb node + Postgres locally. For on-chain PoS operation, supply
 # the operator key + contract addresses via a .env file or shell environment.