One Context, One Registry, and Knowing When to Stop

Last post, the first runtime and adapter were alive. The type system had been fighting back — declaration merging across packages, build tool swaps — but honestly? I kind of forgot about that problem. It is still there, just not blocking anything right now. Sometimes you move forward and the old fight waits. 😄 The units existed. They could register. But the plumbing between "units declared in a config file" and "units actually running" did not exist yet. That changed. This round of work is quieter than the last, but it touches everything: config resolution, a shared base context, a working expose-and-query system, and a few small utilities to keep the registry sane. First Things First: Loading the Units Before anything else can work, the Kernel needs to know what units it is dealing with. That is what config.resolve.units does — it takes the flat list of units from your config file and resolves them into something the Kernel can actually use. The units go in as references — strings, fa