Nah, sorry, there's something I'm messing up/not getting 😅
See this paste: https://paste.sr.ht/~x10an14/653ed23dd63ba7166d4da89b315c9cce3c4f92c8
And see the comment.
Here's the error when I try to nix eval .#modules.x10.device-configs:

x10an14@home-desktop ❯ : nix eval .#modules.x10.device-configs
warning: Git tree '/home/x10an14/Documents/sr.ht/nix-parts-conf' is dirty
{ "x10an14@home-desktop" = { homeManager = { entryPoint = «error: attribute 'username' missing»; homeDirectory = «error: attribute 'system' missing»; toplevelBuild = «error: The option `flake.modules.x10.device-configs."x10an14@home-desktop".homeManager.toplevelBuild' was accessed but has no value defined. Try setting the option.»; }; hostname = "home-desktop"; system = "x86_64-linux"; username = "x10an14"; }; "x10an14@nav-x10an14-t14" = { homeManager = { entryPoint = «error: attribute 'username' missing»; homeDirectory = «error: attribute 'system' missing»; toplevelBuild = «error: The option `flake.modules.x10.device-configs."x10an14@nav-x10an14-t14".homeManager.toplevelBuild' was accessed but has no value defined. Try setting the option.»; }; hostname = "nav-x10an14-t14"; system = "x86_64-linux"; username = "x10an14"; }; }

See the errors reporting missing attributes?

I know that, but again, I'm asking here because I don't know what I should be exploring. There's something missing in my mental model, and I'm here asking for a nudge in the right direction^^

Answering your suggestion on using the nix repl directly, how can I in the repl explore what the config attribute w/the comments look like? I only know how to explore evaluated configs/outputs in the repl

          {
            name,
            username, # <- I want access to these, that live under `config.flake.modules.x10.device-configs.<a device>,`
            hostname, # <- I want access to these, that live under `config.flake.modules.x10.device-configs.<a device>,`
            system, # <- I want access to these, that live under `config.flake.modules.x10.device-configs.<a device>,`
            ...
          }:
let
  ihnerit (config.flake.modules.x10.device-config.${name}) username;
in
          {
            options.homeManager = {

          {
            name,
            ...
          }:
let
  ihnerit (config.flake.modules.x10.device-config.${name}) username;
in
          {
            options.homeManager = {

          {
            name,
            ...
          }:
let
  inherit (config.flake.modules.x10.device-config.${name}) username;
in
          {
            options.homeManager = {

Something I'd already tried earlier but discarded due to an unrelated error (that I thought told me I could not do things this way):

{
    type =
      with lib.types;
      attrsOf (
        submodule (
          nixosConfig:
          let
            cfg = nixosConfig.config.nixos;
            inherit (nixosConfig.config) hostname username system;
          in
          {
            options.nixos = builtins.break {
              entryPoint = lib.mkOption {
                type = lib.types.path;
                default = "${repoRoot}/nixos/${username}_at_${hostname}";
              };
              toplevelBuild = lib.mkOption {
                type = lib.types.raw;
                readOnly = true;
              };
            };
            config.nixos.toplevelBuild = lib.mkIf (builtins.pathExists cfg.entryPoint) (
              inputs.nixpkgs.lib.nixosSystem {
                modules = [
                  {
                    nixpkgs.hostPlatform = { inherit system; };
                  }
                  (import cfg.entryPoint (inputs // { inherit repoRoot; }))
                  "${repoRoot}/x10/options/unfree-packages.nix"
                  inputs.nur.modules.nixos.default
                ];
                specialArgs = {
                  inherit inputs hostname repoRoot;
                };
              }
            );
          }
        )
      );
  }

So yeah, the inner config variable of the extending submodule contains the submodule's "sibling" option values.

x10an14: taking the discussion from the beginning …

If you want to declare options specific to one instance, you can do it as follow:

{ lib,  ... }@toplevel:
{
  config.flake.modules.foo.<fooInstance> = {config, ...}@submoduleInstance: {
    options.home-manager = lib.mkOption { ... };
    config.home-manager = ...;
  }
}

If you want to make the home-manager option available to all instances, then your initial example is almost there, you have to redefine the foo option with the submodule that you want to add. Submodule option declarations are merged, see fileSystems option as an example, which is declared in multiple modules.

nbp: Thanks! =D

I got it to work, as described in the previous 2x messages of mine =)
This is how I did it: https://git.sr.ht/~x10an14/nix-parts-conf/tree/main/item/device-configs/home-manager.nix

Any feedback/suggestions welcome!
PS: I urge those who've got feedback/suggestions to consider whether it's too niche for this channel/is maybe better suited for a DM =)