@celilo/cli 0.24.1 → 0.25.1

package/src/services/network-ensure.ts

@@ -0,0 +1,260 @@
+/**
+ * Ensure every network a module REQUIRES is defined before the deploy proceeds
+ * (openspec/changes/networks-are-declared-not-written/specs/network-declaration/spec.md).
+ *
+ * celilo owns the network namespace. A module names the networks it depends on
+ * under `requires.networks`; it never carries their values. When one of those
+ * networks has no `network.<name>.subnet` in system config, this asks for the
+ * range over the event bus and writes it — celilo asking, celilo writing.
+ *
+ * Two properties matter and both come from WHERE this runs rather than from
+ * anything clever it does:
+ *
+ *   - It runs in the deploy's interview phase, before generation and before any
+ *     hook. So by the time a hook executes, the network is defined — whether the
+ *     consumer reading declared networks captured them eagerly or reads at point
+ *     of use. That is what retires the live-reader mitigation the firewall
+ *     capability carries today (celilo#759).
+ *   - It asks through the generic bus interview, so it is answerable by whatever
+ *     responder is attached — a terminal, `celilo events reply`, an automated
+ *     policy — and behaves identically interactive or headless.
+ *
+ * ── What is asked, and what is merely observed ──
+ *
+ * Not every attribute of a network is a question. The rule is whether celilo can
+ * already SEE the answer:
+ *
+ *   - `subnet` is ASKED. It is an addressing-plan decision that predates every
+ *     module, and nothing in the fleet can be consulted for it. A well-known name
+ *     is offered a suggested range so an operator new to networking is not made to
+ *     invent one — an offer in a question, never a seeded row.
+ *   - `gateway` is OBSERVED, never asked. It is the address a router answers on
+ *     inside that subnet, which celilo already holds: `machine add` catalogues
+ *     every interface of every machine. Asking for it would be asking the operator
+ *     to retype something celilo can look up, which is the same failure this change
+ *     exists to remove, aimed at a different key.
+ *   - `vlan` is ASKED, optional, blank meaning untagged. It is NOT observable —
+ *     a catalogued interface carries `{name, ipAddress, zone}` and no tag — and it
+ *     IS load-bearing: every container-provisioning template reads
+ *     `$system:network.<zone>.vlan` as the Proxmox NIC tag. Leaving it uncollected
+ *     would provision containers untagged onto the wrong VLAN, silently.
+ *
+ * Which attributes a network HAS at all is celilo's answer too, taken from
+ * `schemas/system_config.json`: it declares `gateway`/`vlan` for the routed
+ * segments and omits both for the control-plane VPN, which has neither. So a
+ * module never states which attributes it reads, and asking a nonsense question
+ * is impossible by construction.
+ */
+
+import { subnetContains } from '@celilo/capabilities';
+import { eq } from 'drizzle-orm';
+import type { DbClient } from '../db/client';
+import { machines, moduleConfigs, systemConfig } from '../db/schema';
+import { type ModuleManifest, getRequiredNetworkNames } from '../manifest/schema';
+import { askText } from './bus-interview';
+import { loadSchema } from './system-init';
+
+export interface NetworkEnsureResult {
+  success: boolean;
+  error?: string;
+  /** What this call defined, as `<key> = <value>` lines for the deploy log. */
+  applied: string[];
+}
+
+/** The one piece of I/O here, injectable so the rules are testable without a bus. */
+export type NetworkAsker = (question: {
+  scope: string;
+  key: string;
+  message: string;
+  description: string;
+  defaultValue?: string;
+  placeholder?: string;
+  required: boolean;
+  pattern?: string;
+}) => Promise<string>;
+
+/**
+ * The module's own config, flat, for resolving a `from:` requirement.
+ *
+ * Reads `value_json` in preference to `value`: an array config value is stored
+ * as JSON, and reading the scalar column would yield the string form, which
+ * `getRequiredNetworkNames` would then have to guess at.
+ */
+function loadModuleConfigValues(db: DbClient, moduleId: string): Record<string, unknown> {
+  const values: Record<string, unknown> = {};
+  for (const row of db
+    .select()
+    .from(moduleConfigs)
+    .where(eq(moduleConfigs.moduleId, moduleId))
+    .all()) {
+    values[row.key] = row.valueJson ?? row.value;
+  }
+  return values;
+}
+
+function readSystemConfigValue(db: DbClient, key: string): string | undefined {
+  const row = db.select().from(systemConfig).where(eq(systemConfig.key, key)).get();
+  return row?.value && row.value.length > 0 ? row.value : undefined;
+}
+
+function writeSystemConfigValue(db: DbClient, key: string, value: string): void {
+  db.insert(systemConfig)
+    .values({ key, value })
+    .onConflictDoUpdate({ target: systemConfig.key, set: { value } })
+    .run();
+}
+
+/**
+ * The address a router answers on inside `subnet`, from the machine catalogue.
+ *
+ * Matched by CONTAINMENT rather than by an interface's recorded zone, because on
+ * a fleet that is still being described those are not the same thing: an
+ * interface is classified into a zone by comparing it against declared subnets,
+ * so before the subnet exists the interface has no zone. Containment answers the
+ * moment the operator supplies the range, which is exactly when this runs.
+ *
+ * `role: 'router'` is what distinguishes the gateway from any other host that
+ * happens to sit in the subnet.
+ */
+export function observeGateway(db: DbClient, subnet: string): string | undefined {
+  for (const machine of db.select().from(machines).all()) {
+    if (machine.role !== 'router') continue;
+    for (const iface of machine.interfaces) {
+      if (iface.ipAddress && subnetContains(subnet, iface.ipAddress)) {
+        return iface.ipAddress;
+      }
+    }
+  }
+  return undefined;
+}
+
+/**
+ * Ensure each of `manifest.requires.networks` is defined: a subnet, a vlan tag
+ * where one applies, and a gateway wherever celilo can see one.
+ */
+export async function ensureRequiredNetworks(
+  moduleId: string,
+  manifest: ModuleManifest,
+  db: DbClient,
+  ask: NetworkAsker = askText,
+): Promise<NetworkEnsureResult> {
+  // A `from:` requirement resolves against the module's OWN config, so the
+  // module's values have to be loaded before its required set is even knowable.
+  const names = getRequiredNetworkNames(manifest, loadModuleConfigValues(db, moduleId));
+  if (names.length === 0) return { success: true, applied: [] };
+
+  const schema = loadSchema();
+  const applied: string[] = [];
+
+  for (const name of names) {
+    const subnetKey = `network.${name}.subnet`;
+    const subnetProperty = schema.properties[subnetKey];
+    if (!subnetProperty) {
+      return {
+        success: false,
+        applied,
+        error: [
+          `Module "${moduleId}" requires a network called "${name}", which celilo does not know`,
+          `about: there is no "${subnetKey}" in celilo's system-config schema. Networks are`,
+          "celilo's to define, so a new one is added to schemas/system_config.json — a module",
+          'cannot introduce one.',
+        ].join(' '),
+      };
+    }
+
+    // 1. The subnet — asked, because nothing in the fleet can be consulted for it.
+    //
+    // Whether this network already EXISTED is the fact everything below turns
+    // on: celilo is here to define a network, not to audit one it already holds.
+    let subnet = readSystemConfigValue(db, subnetKey);
+    const defining = subnet === undefined;
+    if (defining) {
+      const answer = (
+        await ask({
+          scope: `network:${name}`,
+          key: 'subnet',
+          message: `Subnet CIDR for the "${name}" network:`,
+          description: [
+            `${moduleId} requires the "${name}" network, and celilo has no subnet for it.`,
+            "This becomes celilo's definition of the network — every module that needs it reads",
+            'this one value.',
+          ].join(' '),
+          defaultValue: subnetProperty.suggested,
+          // A defaultValue MUST have a matching placeholder, or the operator
+          // cannot see what pressing Enter would accept.
+          placeholder: subnetProperty.suggested,
+          required: true,
+          pattern: subnetProperty.pattern,
+        })
+      ).trim();
+
+      if (answer.length === 0) {
+        return {
+          success: false,
+          applied,
+          error: `No subnet supplied for the "${name}" network; ${moduleId} cannot deploy without it.`,
+        };
+      }
+      writeSystemConfigValue(db, subnetKey, answer);
+      applied.push(`${subnetKey} = ${answer}`);
+      subnet = answer;
+    }
+
+    // 2. The VLAN tag — asked, because it cannot be observed: a catalogued
+    //    interface carries no tag. Optional: an untagged segment genuinely has
+    //    none, and a blank answer writes nothing rather than writing "".
+    //
+    //    ONLY when celilo is defining the network. An existing network was
+    //    already defined without a tag — deliberately, or because it is
+    //    untagged — and re-opening that question every time a new module
+    //    requires it is not a question, it is a deploy that stops. Which is
+    //    exactly what happened: `iptables` requires `internal`, whose subnet the
+    //    management install had already recorded and whose vlan nothing ever
+    //    set, so a headless deploy died on `interview.required.network:internal.vlan`
+    //    with no responder to answer it. Absent means untagged; if that is wrong,
+    //    `celilo system config set network.<name>.vlan <tag>` says so once.
+    const vlanKey = `network.${name}.vlan`;
+    if (
+      defining &&
+      schema.properties[vlanKey] &&
+      readSystemConfigValue(db, vlanKey) === undefined
+    ) {
+      const answer = (
+        await ask({
+          scope: `network:${name}`,
+          key: 'vlan',
+          message: `VLAN tag for the "${name}" network (blank if untagged):`,
+          description: [
+            'Container provisioning reads this as the NIC tag, so a tagged fleet that leaves it',
+            'unset puts containers on the wrong VLAN without saying so. Leave it blank if this',
+            'segment is untagged.',
+          ].join(' '),
+          required: false,
+        })
+      ).trim();
+      if (answer.length > 0) {
+        writeSystemConfigValue(db, vlanKey, answer);
+        applied.push(`${vlanKey} = ${answer}`);
+      }
+    }
+
+    // 3. The gateway — OBSERVED. celilo catalogues every machine's interfaces at
+    //    `machine add`, so the router's address inside this subnet is a fact it
+    //    already holds. Absent means no router leg is catalogued there yet, which
+    //    a later `machine add` or firewall deploy resolves; it is not a question.
+    const gatewayKey = `network.${name}.gateway`;
+    if (
+      subnet &&
+      schema.properties[gatewayKey] &&
+      readSystemConfigValue(db, gatewayKey) === undefined
+    ) {
+      const observed = observeGateway(db, subnet);
+      if (observed) {
+        writeSystemConfigValue(db, gatewayKey, observed);
+        applied.push(`${gatewayKey} = ${observed} (observed from the machine catalogue)`);
+      }
+    }
+  }
+
+  return { success: true, applied };
+}

package/src/services/system-init.ts

@@ -15,7 +15,7 @@ import { systemConfig } from '../db/schema';
 /**
  * System configuration schema interface
  */
-interface SystemConfigSchema {
+export interface SystemConfigSchema {
   properties: Record<
     string,
     {
@@ -26,6 +26,17 @@ interface SystemConfigSchema {
       minimum?: number;
       maximum?: number;
       format?: string;
+      /**
+       * A starting offer for an interview, deliberately NOT a `default`.
+       *
+       * `getDefaultConfiguration()` seeds every `default:` it finds at `system
+       * init`, and network addressing is specifically not seeded
+       * (openspec/specs/progressive-zone-disclosure/spec.md). A separate field
+       * is structurally incapable of becoming a row nobody chose: it is only
+       * ever read to pre-fill a question the operator still has to answer
+       * ([[services/network-ensure.ts]]).
+       */
+      suggested?: string;
     }
   >;
 }
@@ -33,7 +44,7 @@ interface SystemConfigSchema {
 /**
  * Load system config schema from JSON file
  */
-function loadSchema(): SystemConfigSchema {
+export function loadSchema(): SystemConfigSchema {
   // Try common locations (relative to this file's directory and cwd)
   const thisDir = dirname(new URL(import.meta.url).pathname);
   const candidates = [
@@ -80,7 +91,7 @@ export function getDefaultConfiguration(): Record<string, string | number> {
  * @param subnet - CIDR notation (e.g., "10.0.10.0/24")
  * @returns Gateway IP (e.g., "10.0.10.1")
  */
-function computeGateway(subnet: string): string {
+export function computeGateway(subnet: string): string {
   const [network, _bits] = subnet.split('/');
   const octets = network.split('.').map(Number);
 

package/src/templates/dns-ingress-ip.test.ts

@@ -0,0 +1,123 @@
+/**
+ * The DNS-ingress allocate-and-reserve guard (ISS-0156).
+ *
+ * This invariant had NO test. Losing it is not a crash: `module generate`
+ * re-allocates a different address on every run, silently moving the address
+ * internal clients use to reach DNS, while every command still reports success.
+ * `module generate` runs repeatedly over a module's life, so "on the second
+ * run" is the normal case, not an edge one.
+ */
+
+import { beforeEach, describe, expect, test } from 'bun:test';
+import type { DbClient } from '../db/client';
+import type { ModuleManifest } from '../manifest/schema';
+import { getModuleConfigValue } from '../services/module-config';
+import { setupTestDatabase } from '../test-utils/database';
+import { ensureDnsIngressIp } from './generator';
+
+let db: DbClient;
+
+/** A manifest that opts in the way a `dns_internal` provider does. */
+const wantsIngress = {
+  variables: { owns: [{ name: 'dns_ingress_ip', source: 'infrastructure' }] },
+} as unknown as ModuleManifest;
+
+/** Same shape, but the variable is operator input rather than infrastructure. */
+const operatorSupplied = {
+  variables: { owns: [{ name: 'dns_ingress_ip', source: 'user_input' }] },
+} as unknown as ModuleManifest;
+
+/**
+ * Typed as `string | undefined` rather than `unknown`: every assertion here is
+ * about an address, and an untyped read pushes a cast onto each one.
+ */
+const storedIp = (moduleId: string): string | undefined => {
+  const value = getModuleConfigValue(moduleId, 'dns_ingress_ip', db)?.value;
+  return typeof value === 'string' ? value : undefined;
+};
+
+beforeEach(async () => {
+  db = await setupTestDatabase();
+  db.$client
+    .prepare('INSERT OR REPLACE INTO system_config (key, value) VALUES (?, ?)')
+    .run('network.internal.subnet', '10.226.1.0/24');
+});
+
+describe('ensureDnsIngressIp', () => {
+  test('allocates an address from the internal subnet on first generate', async () => {
+    const result = await ensureDnsIngressIp('technitium', wantsIngress, db);
+
+    expect(result.success).toBe(true);
+    expect(storedIp('technitium')).toMatch(/^10\.226\.1\.\d+$/);
+  });
+
+  test('REUSES the same address on a second generate', async () => {
+    // The guard itself. Re-allocating here moves the resolver's DNAT ingress
+    // every time the module is regenerated, and nothing reports a problem.
+    await ensureDnsIngressIp('technitium', wantsIngress, db);
+    const first = storedIp('technitium');
+
+    await ensureDnsIngressIp('technitium', wantsIngress, db);
+    const second = storedIp('technitium');
+
+    expect(second).toBe(first);
+  });
+
+  test('stays stable across many generates, not just two', async () => {
+    await ensureDnsIngressIp('technitium', wantsIngress, db);
+    const first = storedIp('technitium');
+
+    for (let i = 0; i < 5; i++) {
+      await ensureDnsIngressIp('technitium', wantsIngress, db);
+    }
+
+    expect(storedIp('technitium')).toBe(first);
+  });
+
+  test('RESERVES the address, so it is never handed out to something else', async () => {
+    // Allocation without reservation is the same bug one step later: a
+    // container gets the resolver's ingress address and DNS goes dark.
+    await ensureDnsIngressIp('technitium', wantsIngress, db);
+    const ip = storedIp('technitium');
+
+    const reserved = db.$client
+      .prepare('SELECT ip_start, reason FROM ip_reservations WHERE ip_start = ?')
+      .get(ip ?? '') as { ip_start: string; reason: string } | undefined;
+
+    expect(reserved?.ip_start).toBe(ip);
+    // The reason names the owner, so an operator reading the table can tell
+    // what an otherwise anonymous held address is for.
+    expect(reserved?.reason).toBe('dns-ingress:technitium');
+  });
+
+  test('two modules get two different addresses', async () => {
+    await ensureDnsIngressIp('technitium', wantsIngress, db);
+    await ensureDnsIngressIp('knot-unbound-internal', wantsIngress, db);
+
+    expect(storedIp('knot-unbound-internal')).not.toBe(storedIp('technitium'));
+  });
+
+  test('does nothing for a module that never asked for one', async () => {
+    const result = await ensureDnsIngressIp('caddy', {} as ModuleManifest, db);
+
+    expect(result.success).toBe(true);
+    expect(storedIp('caddy')).toBeUndefined();
+  });
+
+  test('only `source: infrastructure` opts in', async () => {
+    // A same-named variable the operator supplies is theirs to set; allocating
+    // over it would overwrite an operator's deliberate choice.
+    await ensureDnsIngressIp('technitium', operatorSupplied, db);
+
+    expect(storedIp('technitium')).toBeUndefined();
+  });
+
+  test('fails with an actionable message when the internal subnet is unset', async () => {
+    db.$client.prepare('DELETE FROM system_config WHERE key = ?').run('network.internal.subnet');
+
+    const result = await ensureDnsIngressIp('technitium', wantsIngress, db);
+
+    expect(result.success).toBe(false);
+    expect(result.success === false && result.error).toContain('network.internal.subnet');
+  });
+});

package/src/templates/generator.ts

@@ -653,6 +653,70 @@ celilo module import modules/${moduleId}
  * @param options - Generation options
  * @returns Generation result
  */
+/** Narrower than `GenerateResult`: this step produces no files, only an outcome. */
+export type DnsIngressResult = { success: true } | { success: false; error: string };
+
+/**
+ * Allocate-and-reserve the module's dedicated DNS-ingress IP, ONCE (ISS-0156).
+ *
+ * A `dns_internal` provider deploys into a PROTECTED zone (dmz) so it can see
+ * protected-zone query sources for split-horizon views. `internal` devices have
+ * no route into the 10-net, so they reach the resolver through a firewall DNAT
+ * on a dedicated `internal`-subnet address. A module opts in by declaring a
+ * `dns_ingress_ip` infrastructure variable.
+ *
+ * **Idempotence is the whole point, and it is load-bearing.** `module generate`
+ * runs repeatedly over a module's life. Re-allocating here on the second run
+ * would move the address internal clients use to reach DNS, every time — while
+ * every command still reports success. That is why the stored value is reused
+ * rather than re-derived, and why this is a named function instead of a branch
+ * buried in `generateTemplates`: an invariant nothing can call is an invariant
+ * nothing can test, and this one had no test at all.
+ */
+export async function ensureDnsIngressIp(
+  moduleId: string,
+  manifest: ModuleManifest,
+  db: DbClient,
+): Promise<DnsIngressResult> {
+  const wantsDnsIngress = manifest.variables?.owns?.some(
+    (v) => v.name === 'dns_ingress_ip' && v.source === 'infrastructure',
+  );
+  if (!wantsDnsIngress) return { success: true };
+
+  const existing = getModuleConfigValue(moduleId, 'dns_ingress_ip', db)?.value;
+  if (typeof existing === 'string' && existing.length > 0) {
+    log.success(`Using existing DNS-ingress IP ${existing} for ${moduleId}`);
+    return { success: true };
+  }
+
+  const subnetRow = db.$client
+    .prepare('SELECT value FROM system_config WHERE key = ?')
+    .get('network.internal.subnet') as { value: string } | undefined;
+  if (!subnetRow?.value) {
+    return {
+      success: false,
+      error:
+        'network.internal.subnet is not configured — required to allocate the ' +
+        'dns_internal DNS-ingress IP (ISS-0156). Ensure the internal network is set up first.',
+    };
+  }
+
+  const { allocateIPFromSubnet, reserveIP } = await import('../ipam/allocator');
+  const { stripCIDR } = await import('../ipam/subnet-parser');
+  try {
+    const ip = stripCIDR(await allocateIPFromSubnet(subnetRow.value, 'internal', db));
+    await reserveIP(ip, 'internal', `dns-ingress:${moduleId}`, null, db);
+    upsertModuleConfig(db, moduleId, 'dns_ingress_ip', ip);
+    log.success(`Allocated DNS-ingress IP ${ip} (internal subnet) for ${moduleId}`);
+    return { success: true };
+  } catch (error) {
+    return {
+      success: false,
+      error: `DNS-ingress IP allocation failed: ${error instanceof Error ? error.message : String(error)}`,
+    };
+  }
+}
+
 export async function generateTemplates(options: GenerateOptions): Promise<GenerateResult> {
   const { moduleId, modulePath, outputPath, db = getDb() } = options;
 
@@ -815,49 +879,8 @@ export async function generateTemplates(options: GenerateOptions): Promise<Gener
     }
   }
 
-  // Dedicated DNS-ingress IP (ISS-0156). A dns_internal provider now deploys into
-  // a PROTECTED zone (dmz) so it can see protected-zone query sources for
-  // split-horizon views (openspec/specs/internal-dns-zone-views/spec.md). `internal` devices have
-  // no route into the 10-net, so they reach the resolver through a firewall DNAT
-  // on a dedicated `internal`-subnet address. A module opts in by declaring a
-  // `dns_ingress_ip` infrastructure variable; we allocate a free IP from the
-  // `internal` subnet via IPAM and RESERVE it (so it's never re-handed-out),
-  // idempotently (reuse the stored value on re-generate). The resolver's
-  // on_install passes it to firewall.exposeService({ ingressIp }).
-  const wantsDnsIngress = manifest.variables?.owns?.some(
-    (v) => v.name === 'dns_ingress_ip' && v.source === 'infrastructure',
-  );
-  if (wantsDnsIngress) {
-    const existing = getModuleConfigValue(moduleId, 'dns_ingress_ip', db)?.value;
-    if (typeof existing === 'string' && existing.length > 0) {
-      log.success(`Using existing DNS-ingress IP ${existing} for ${moduleId}`);
-    } else {
-      const subnetRow = db.$client
-        .prepare('SELECT value FROM system_config WHERE key = ?')
-        .get('network.internal.subnet') as { value: string } | undefined;
-      if (!subnetRow?.value) {
-        return {
-          success: false,
-          error:
-            'network.internal.subnet is not configured — required to allocate the ' +
-            'dns_internal DNS-ingress IP (ISS-0156). Ensure the internal network is set up first.',
-        };
-      }
-      const { allocateIPFromSubnet, reserveIP } = await import('../ipam/allocator');
-      const { stripCIDR } = await import('../ipam/subnet-parser');
-      try {
-        const ip = stripCIDR(await allocateIPFromSubnet(subnetRow.value, 'internal', db));
-        await reserveIP(ip, 'internal', `dns-ingress:${moduleId}`, null, db);
-        upsertModuleConfig(db, moduleId, 'dns_ingress_ip', ip);
-        log.success(`Allocated DNS-ingress IP ${ip} (internal subnet) for ${moduleId}`);
-      } catch (error) {
-        return {
-          success: false,
-          error: `DNS-ingress IP allocation failed: ${error instanceof Error ? error.message : String(error)}`,
-        };
-      }
-    }
-  }
+  const dnsIngress = await ensureDnsIngressIp(moduleId, manifest, db);
+  if (!dnsIngress.success) return dnsIngress;
 
   // Infrastructure Properties Resolution (Proxmox provider config)
   // For Proxmox services, extract provider config and store as temporary values

package/src/test-utils/bus-responder.ts

@@ -42,6 +42,7 @@ import { type DbClient, createDbClient } from '../db/client';
 import type {
   ConfigRequiredPayload,
   EnsureRequiredPayload,
+  InterviewRequiredPayload,
   SecretRequiredPayload,
 } from '../services/bus-interview';
 import {
@@ -79,6 +80,8 @@ export interface BusResponderFixture {
   seenSecretPayloads(): SecretRequiredPayload[];
   /** Snapshot of every ensure.required payload the responder saw. */
   seenEnsurePayloads(): EnsureRequiredPayload[];
+  /** Snapshot of every generic interview.required payload the responder saw. */
+  seenInterviewPayloads(): InterviewRequiredPayload[];
   /** Stop watching and close the bus + db connections. */
   close(): void;
 }
@@ -102,7 +105,16 @@ export function startBusResponderFixture(opts: BusResponderFixtureOptions): BusR
   const handle: ProgrammaticResponderHandle = startProgrammaticResponder({
     busDbPath: opts.busDbPath,
     db,
-    values: { config: opts.config, secrets: opts.secrets, ensures: opts.ensures },
+    // Every family the fixture's options type accepts must be forwarded, or a
+    // test supplies an answer that silently never arrives and the deploy hangs
+    // on a question nobody is listening for.
+    values: {
+      config: opts.config,
+      secrets: opts.secrets,
+      ensures: opts.ensures,
+      interview: opts.interview,
+      aspects: opts.aspects,
+    },
     onMissing: 'throw',
     emittedBy: 'test-bus-responder',
   });
@@ -114,6 +126,7 @@ export function startBusResponderFixture(opts: BusResponderFixtureOptions): BusR
     seenConfigPayloads: () => handle.seenConfigPayloads(),
     seenSecretPayloads: () => handle.seenSecretPayloads(),
     seenEnsurePayloads: () => handle.seenEnsurePayloads(),
+    seenInterviewPayloads: () => handle.seenInterviewPayloads(),
     close: () => {
       handle.close();
       db.$client.close();