Package-level declarations

Enumerate the real backing jars for net.minecraft.* at runtime, so the REPL can feed them to the Kotlin compiler as its classpath.

Who put each compile-classpath jar there, for the access-widen overlay to shard by.

Fetching the per-version mapping artifacts RemapCache provisions from: where they live, how to retry a transient failure, and how to verify what came back. Nothing here knows about the cache layout or the masking-loader hop — it hands back files.

The value/output join and the mojmap reverse-mapping of throwables. Pure functions over their arguments — no REPL state. Game loader, so the lane can render without reaching across the masking seam.

Resolve a CodeSource or module-reference location to the real backing jar File, across loaders.

Parses the runtime mappings bundle — tiny v2 (namespace ORDER read from the header, see Parser.parseTinyV2) or forge TSRG2 — into the named->runtime lookups mapClass / mapMethod / mapField, so name strings written in mojmap (REPL scripts that pass class/method names to Patches.onEnter / Patches.onExit, plus the mod's own reflective lookups — auth probe, command compat) can be translated to the runtime namespace on a non-mojmap production runtime.

What Mixin merges into its targets, read off Mixin's own model — the prepared configs and the MixinInfos under them — rather than by applying anything to a class.

The disk side of ModJarCollector: turns a code root with no file behind it into a repacked jar, and decides when that jar is stale.

Enumerate the backing jars of every LOADED mod — including jar-in-jar / nested modules — so a script can import mod APIs (fabric-api, NeoForge/Forge mods, and any mod's bundled libraries) at compile time.

Detects, once at startup, which naming namespace the game runtime actually uses — so the REPL knows whether a compiled (mojmap-named) script must be remapped before it can link against the running MC.

Plugin jars for the compile classpath: whatever the host enumerates (Services.PLATFORM) plus the urls of the loaders behind the plugins. PluginBridge searches those same loaders at runtime, and the two MUST agree — a name the compiler resolves and the snippet loader then misses is a NoClassDefFoundError.

The mojmap<->runtime remap bundle in force: a mappings file, and the symbol dir holding MC_SYMBOLS (plus DEPS_LIST where one was harvested). Private constructor — mappings without symbols leaves scripts compiling against the runtime jar, where no mojmap name resolves, so neither factory below can produce that pair.

First-launch remap-bundle provisioning for a NON-mojmap production runtime. The mod jar carries no per-version mapping data. On a Fabric intermediary runtime with no mcp.remap.* flags set, this downloads the two per-version artifacts that ARE published (Mojang client mappings + fabric intermediary), assembles named<->intermediary, and reverse-remaps the runtime jar into a mojmap symbol jar — caching everything under the mod's cache dir, one subdirectory per MC version. On later launches it's a cache hit.

The => type = value line, for both the single-tick result and every cross-tick McpScope.yield — one function, so the two cannot drift apart.