rig-build: -j12, and a deps image that has wxInspector

Raises the bound from -j8 to -j12: the incident dump measured 1.17 GB average per cc1plus,
so 12 in flight is ~14 GB typical, well inside the 40 GB cgroup ceiling that is the real
guarantee. Keeps the file byte-identical to snaporca's copy, which the header requires.

Dockerfile.deps builds the deps with -j 12 for the same reason, and symlinks
deps/build/destdir -> deps/build/OrcaSlicer_dep: this tree installs under the latter name
while the orcacad_buildcache volume has the former baked as absolute paths in its CMakeCache.
Same tree, two names — without the link, one directory rename costs a full cold rebuild.

scripts/rig-build.sh

@@ -42,13 +42,13 @@ fi
 # build produced a single object. The bounds, weakest to strongest:
 #   flock    — the lock path is shared by both forks on purpose, so they SERIALISE instead of
 #              summing. Peak is one build's worth no matter who else starts one.
-#   -j8      — ~8 TUs in flight, ~10-20 GB, and the box stays usable while it compiles.
-#              JOBS=n overrides for a machine with more headroom.
+#   -j12     — measured 1.17 GB average per cc1plus in the incident dump, so 12 in flight
+#              is ~14 GB typical and leaves the box usable. JOBS=n overrides.
 #   --memory — the actual guarantee. A runaway build hits its own cgroup limit and dies alone;
 #              the host never reaches global OOM again, whatever -j or flock do.
 #              --memory-swap equal to --memory forbids swap, which is what made ssh hang.
-JOBS="${JOBS:-8}"
-MEM="${MEM:-32g}"
+JOBS="${JOBS:-12}"
+MEM="${MEM:-40g}"
 LOCK=/tmp/orca-rig-build.lock
 
 exec 9>"$LOCK"