Daniel Samson be04ebe954 build: delete module_homes — imports resolve through the declared zon ... The module-to-domain table in build-support duplicated what each domain's build.zig already states with its addModule exports. userBinary now resolves each named import by searching the packages the binary declared in its own build.zig.zon (b.available_deps), which also makes the zon the literal include path: an import can only be satisfied by a domain the binary claims, and naming a module whose domain is missing fails the build graph with the domain to declare. build-support is down to the recipe alone. All build variants green; manifest unchanged.		2026-07-30 07:49:19 +01:00
..
acpi	build: delete module_homes — imports resolve through the declared zon	2026-07-30 07:49:19 +01:00
device-manager	build: delete module_homes — imports resolve through the declared zon	2026-07-30 07:49:19 +01:00
display	build: delete module_homes — imports resolve through the declared zon	2026-07-30 07:49:19 +01:00
display-demo	build: delete module_homes — imports resolve through the declared zon	2026-07-30 07:49:19 +01:00
fat	build: delete module_homes — imports resolve through the declared zon	2026-07-30 07:49:19 +01:00
fdt	build: delete module_homes — imports resolve through the declared zon	2026-07-30 07:49:19 +01:00
init	build: delete module_homes — imports resolve through the declared zon	2026-07-30 07:49:19 +01:00
input	build: delete module_homes — imports resolve through the declared zon	2026-07-30 07:49:19 +01:00
logger	build: exact per-binary imports — the pre-wired default set is gone	2026-07-30 06:42:31 +01:00