From df6fc8a432f73cc4e91940a8a878cb2164a4240e Mon Sep 17 00:00:00 2001
From: KernelDeimos <7225168+KernelDeimos@users.noreply.github.com>
Date: Mon, 29 Sep 2025 14:25:13 -0400
Subject: [PATCH] test: fix test kernel after adding runtimle modules

RuntimeModules (a feature for extensions) can be accessed by core
modules through a registry exposed in Context by Kernel. However,
TestKernel was not exposing this same registry which caused an error
when module installation occurred during tests.
---
 src/backend/tools/test.js | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/src/backend/tools/test.js b/src/backend/tools/test.js
index 82a298382..c017d7f51 100644
--- a/src/backend/tools/test.js
+++ b/src/backend/tools/test.js
@@ -24,6 +24,7 @@ const CoreModule = require("../src/CoreModule");
 const { Context } = require("../src/util/context");
 const { Kernel } = require("../src/Kernel");
 const { HTTPThumbnailService } = require("../src/services/thumbnails/HTTPThumbnailService");
+const { RuntimeModuleRegistry } = require("../src/extension/RuntimeModuleRegistry");
 
 
 /**
@@ -78,6 +79,8 @@ class TestKernel extends AdvancedBase {
         });
 
         this.logfn_ = (...a) => a;
+        
+        this.runtimeModuleRegistry = new RuntimeModuleRegistry();
     }
 
     add_module (module) {
@@ -109,6 +112,7 @@ class TestKernel extends AdvancedBase {
         const root_context = Context.create({
             services,
             useapi: this.useapi,
+            ['runtime-modules']: this.runtimeModuleRegistry,
         }, 'app');
         globalThis.root_context = root_context;