home.nix depends on nix-colors (colorScheme), lazyvim, and walker HM
modules; previously every host wired them by hand via `modules`, which
external consumers couldn't know to do. Inject them in mkSystem so any
host built through it gets them; re-importing from a host is a no-op.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Expose templates.default — a starter flake that consumes OmniXY as an
input (dependency model): omnixy.lib.mkSystem + nixosModules.omnixy +
a placeholder host. Lets adopters track OmniXY with `nix flake update`
instead of forking. See templates/default/README.md.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Extract the reusable core module list into modules/default.nix (single
source of truth) and expose it as nixosModules.omnixy / .default.
configuration.nix now imports ./modules instead of listing each module,
so this repo's hosts and external consumers share one definition. Theme
stays a settings.theme-driven import inside the aggregate. Packs,
dev-env, sops and home-manager remain injected by mkSystem.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Surface mkSystem as a flake output and make its host resolution
non-throwing: internal hosts (this repo's hosts/<name>/) are still
imported automatically, but a consumer using OmniXY as a flake input
can now pass their own host via `modules` instead. First brick of the
dependency-model framework; the core module aggregate (nixosModules)
follows so a consumer's host can import OmniXY core.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The public template should ship the copy-me `example` host and the ISO,
not the maintainer's real machine. bohm's `omnixy` host enables MCP
servers that require secrets (absent in the public tree), so it broke
`nix flake check` on the public branch. It moves to the private
omnixy-private branch (which re-adds it with the real secrets). Forkers
define their own host modeled on `example`.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
