fix: global plugin hook AdminForth/1955/implement-ability-for-agent-pl

validateConfigAfterDiscover was called only for plugins in
resource.plugins, so a global plugin never got it. The agent built its
system prompt there, so the model got "undefined" in its place, and its
startup checks (MCP plugin, audio and chat surface adapters) never ran.

Call it for config.globalPlugins after all resources are discovered;
resourceConfig is optional, a global plugin belongs to no resource.

Author: srelon

adminforth/index.ts

@@ -629,6 +629,10 @@ class AdminForth implements IAdminForth {
     for (const res of this.config.resources) {
       this.configValidator.postProcessAfterDiscover(res);
     } 
+    // resource plugins are validated by postProcessAfterDiscover, global ones belong to no resource
+    for (const plugin of this.config.globalPlugins ?? []) {
+      plugin.validateConfigAfterDiscover?.(this);
+    }
 
     this.operationalResources = {};
     this.config.resources.forEach((resource) => {

adminforth/types/Back.ts

@@ -799,8 +799,9 @@ export interface IAdminForthPlugin {
   /**
    * Optional method which will be called after AdminForth discovers all resources and their columns.
    * Can be used to validate types of columns, check if some columns are missing, etc.
+   * `resourceConfig` is the resource of a resource plugin; a global plugin gets no resource.
    */
-  validateConfigAfterDiscover?(adminforth: IAdminForth, resourceConfig: AdminForthResource): void;
+  validateConfigAfterDiscover?(adminforth: IAdminForth, resourceConfig?: AdminForthResource): void;
 
   /**
    * Here you can register custom endpoints for your plugin.