{;; Exact pins — the Closure compiler version rides on these two, and the
 ;; committed dist/ must rebuild byte-identical (deploy/check-dist.sh).
 ;;
 ;; THE CLASSPATH LAW (read before adding a node_modules path — the hoisting
 ;; trap): a bot may compile a suite app's or kit's PURE namespaces from
 ;; source by adding "node_modules/<pkg>/…/src" here — but ONLY require-free
 ;; or js-only leaves may enter any build's graph that way. A classpath
 ;; require of a namespace that value-imports libp2p (or any kit internals) BY
 ;; NAME resolves it from the npm root, where peer-kit's libp2p v3 hoists: the
 ;; wrong generation, silently, straight past the two-stack law. The network
 ;; stack reaches the :worker build ONLY through rooms-kit's compiled dist
 ;; ("ardegazu-rooms-kit" / "ardegazu-rooms-kit/…" imports), which carries its
 ;; own nested v2 dependency tree; deploy/check-dist.sh's stack greps are the
 ;; tripwire. bot.git's deps.edn is the worked example of the audit a new
 ;; path owes.
 :paths ["src"]
 :deps {org.clojure/clojurescript {:mvn/version "1.12.134"}
        thheller/shadow-cljs {:mvn/version "3.3.6"}}
 :aliases
 {:dev {:extra-deps {cider/cider-nrepl {:mvn/version "0.59.0"}}}}}