deps phases 3-4: uberscript bundling + conformance harness

Phase 3 — bundling. `jolt uberscript OUT -m NS` requires NS, uses the loader's
recorded load order (a dep finishes loading before its requirer, so it's
topological) to concatenate the used namespaces into one .clj that runs on a
plain jolt with no deps/jpm. `jolt-deps uberscript` resolves first. The loader
records loaded file paths when ctx env has :loaded-files.

Phase 4 — conformance. deps-conformance-test resolves real pure-cljc git libs
and reports load/run status, gated behind JOLT_CONFORMANCE so CI stays offline.
First run: medley works; cuerdas hits a reader gap (filed); stuartsierra/
dependency uses Long/MAX_VALUE (JVM interop, out of scope).

Tests: uberscript-test, deps-conformance-test (skips without the flag).

doc/building-and-deps.md

@@ -93,5 +93,17 @@ so an unchanged `deps.edn` doesn't re-fetch.
   or fail at a call. Coverage is per-function: a namespace can load with most
   functions working and a few not.
 
-See [`tools-deps.md`](tools-deps.md) for the design rationale and the road to
-compiling used dependency namespaces into the build.
+### Bundling into one file
+
+`jolt uberscript OUT.clj -m NS` (or `jolt-deps uberscript …`, which resolves deps
+first) bundles `NS` and every namespace it requires — your code plus its
+dependencies — into a single `.clj` in dependency order, ending with a call to
+`NS/-main`. The result runs on a plain `jolt` with no `JOLT_PATH`, no deps
+fetched, and no jpm:
+
+```bash
+jolt-deps uberscript app.clj -m myapp.main
+jolt app.clj arg1 arg2
+```
+
+See [`tools-deps.md`](tools-deps.md) for the design rationale.