imcp 0.0.16 → 0.0.18

package/dist/services/RequirementService.js

@@ -0,0 +1,110 @@
+import { createInstallerFactory } from '../core/installers/index.js';
+import { exec } from 'child_process';
+import util from 'util';
+/**
+ * Service responsible for managing requirements installation and status
+ */
+export class RequirementService {
+    static instance;
+    installerFactory = createInstallerFactory(util.promisify(exec));
+    constructor() { }
+    /**
+     * Get the singleton instance of RequirementService
+     * @returns The RequirementService instance
+     */
+    static getInstance() {
+        if (!RequirementService.instance) {
+            RequirementService.instance = new RequirementService();
+        }
+        return RequirementService.instance;
+    }
+    /**
+     * Check the installation status of a requirement
+     * @param requirement The requirement to check
+     * @returns The installation status
+     */
+    async checkRequirementStatus(requirement, options) {
+        // Validate requirement
+        this.validateRequirement(requirement);
+        // Check the installation status
+        return await this.installerFactory.checkInstallation(requirement, options);
+    }
+    /**
+     * Check if updates are available for a requirement
+     * @param requirement The requirement to check for updates
+     * @returns Updated status with available updates information
+     */
+    async checkRequirementForUpdates(requirement, currentStatus) {
+        // Validate requirement
+        this.validateRequirement(requirement);
+        // Get current status
+        // Check for updates using the appropriate installer
+        const installer = this.installerFactory.getInstaller(requirement);
+        if (!installer || !installer.supportCheckUpdates()) {
+            return currentStatus;
+        }
+        // Pass pythonEnv from currentStatus if it exists for pip packages
+        const options = requirement.type === 'pip' && currentStatus.pythonEnv
+            ? { settings: { pythonEnv: currentStatus.pythonEnv } }
+            : undefined;
+        const status = await this.checkRequirementStatus(requirement, options);
+        return await installer.checkForUpdates(requirement, status);
+    }
+    /**
+     * Update a requirement to a new version
+     * @param requirement The requirement configuration
+     * @param updateVersion The version to update to
+     * @returns The updated requirement status
+     */
+    async updateRequirement(requirement, updateVersion, options) {
+        // Validate requirement
+        this.validateRequirement(requirement);
+        // Create an updated requirement with the new version
+        const updatedRequirement = {
+            ...requirement,
+            version: requirement.version.includes('latest') ? requirement.version : updateVersion,
+        };
+        // Install the updated version
+        return await this.installerFactory.install(updatedRequirement, options);
+    }
+    /**
+     * Validate a requirement configuration
+     * @param requirement The requirement to validate
+     * @throws Error if the requirement is invalid
+     */
+    validateRequirement(requirement) {
+        // Ensure requirement has required fields
+        if (!requirement.name) {
+            throw new Error('Requirement name is required');
+        }
+        if (!requirement.type) {
+            throw new Error('Requirement type is required');
+        }
+        // For type 'other', registry must be specified
+        if (requirement.type === 'other' && !requirement.registry) {
+            throw new Error('Registry must be specified for requirement type "other"');
+        }
+        // Validate registry configuration if provided
+        if (requirement.registry) {
+            const { githubRelease, artifacts } = requirement.registry;
+            // Validate GitHub release configuration
+            if (githubRelease) {
+                if (!githubRelease.repository) {
+                    throw new Error('Repository is required for GitHub release registry');
+                }
+                if (!githubRelease.assetName) {
+                    throw new Error('Asset name is required for GitHub release registry');
+                }
+            }
+            // Validate artifacts registry configuration
+            if (artifacts) {
+                if (!artifacts.registryUrl) {
+                    throw new Error('Registry URL is required for artifacts registry');
+                }
+            }
+        }
+    }
+}
+// Export a singleton instance
+export const requirementService = RequirementService.getInstance();
+//# sourceMappingURL=RequirementService.js.map

package/dist/services/ServerService.d.ts

@@ -1,5 +1,5 @@
-import { ServerSchema } from '../core/ServerSchemaProvider.js';
-import { MCPServerCategory, ServerInstallOptions, ServerCategoryListOptions, ServerOperationResult, ServerUninstallOptions, FeedConfiguration } from '../core/types.js';
+import { ServerSchema } from '../core/loaders/ServerSchemaProvider.js';
+import { MCPServerCategory, ServerInstallOptions, ServerCategoryListOptions, ServerOperationResult, ServerUninstallOptions, FeedConfiguration } from '../core/metadatas/types.js';
 import { OperationStatus } from '../core/onboard/OnboardStatus.js';
 /**
  * ServerService provides a unified interface for server management operations.

package/dist/services/ServerService.js

@@ -1,9 +1,9 @@
 import path from 'path';
 import { fileURLToPath } from 'url';
 import { Logger } from '../utils/logger.js';
-import { getServerSchemaProvider } from '../core/ServerSchemaProvider.js';
-import { mcpManager } from '../core/MCPManager.js';
-import { UPDATE_CHECK_INTERVAL_MS } from '../core/constants.js';
+import { ServerSchemaProvider } from '../core/loaders/ServerSchemaProvider.js';
+import { mcpManager } from './MCPManager.js';
+import { UPDATE_CHECK_INTERVAL_MS } from '../core/metadatas/constants.js';
 import { updateCheckTracker } from '../utils/UpdateCheckTracker.js';
 const __dirname = path.dirname(fileURLToPath(import.meta.url));
 /**
@@ -53,8 +53,8 @@ export class ServerService {
             return;
         }
         try {
-            const { requirementService } = await import('../core/RequirementService.js');
-            const { configProvider } = await import('../core/ConfigurationProvider.js');
+            const { requirementService } = await import('./RequirementService.js');
+            const { configProvider } = await import('../core/loaders/ConfigurationProvider.js');
             for (const requirement of serverCategory.feedConfiguration.requirements) {
                 if (requirement.version.includes('latest')) {
                     // Get current status if available
@@ -102,7 +102,7 @@ export class ServerService {
      */
     async getServerSchema(categoryName, serverName) {
         try {
-            const provider = await getServerSchemaProvider();
+            const provider = ServerSchemaProvider.getInstance();
             const serverMcpConfig = await mcpManager.getServerMcpConfig(categoryName, serverName);
             return await provider.getSchema(categoryName, serverMcpConfig?.schemas || `${serverName}.json`);
         }

package/dist/utils/adoUtils.d.ts

@@ -1,4 +1,4 @@
-import { RequirementConfig, RegistryConfig } from '../core/types.js';
+import { RequirementConfig, RegistryConfig } from '../core/metadatas/types.js';
 export interface AdoArtifactResult {
     type: 'npm' | 'pip';
     package: string;
@@ -25,5 +25,5 @@ targetDir?: string): Promise<AdoArtifactResult>;
  * @param options Optional server install options (e.g., for pythonCommand).
  * @returns The latest version string, or undefined if not found or an error occurs.
  */
-export declare function getArtifactLatestVersion(requirement: RequirementConfig, registry: RegistryConfig['artifacts'], options?: import('../core/types.js').ServerInstallOptions, // Added import for ServerInstallOptions
+export declare function getArtifactLatestVersion(requirement: RequirementConfig, registry: RegistryConfig['artifacts'], options?: import('../core/metadatas/types.js').ServerInstallOptions, // Added import for ServerInstallOptions
 targetDir?: string): Promise<string | undefined>;

package/dist/utils/adoUtils.js

@@ -1,4 +1,4 @@
-import { SETTINGS_DIR } from '../core/constants.js';
+import { SETTINGS_DIR } from '../core/metadatas/constants.js';
 import { Logger } from './logger.js';
 import { exec } from 'child_process';
 import util from 'util';

package/dist/utils/feedUtils.js

@@ -1,6 +1,6 @@
 import fs from 'fs/promises';
 import { Logger } from './logger.js';
-import { LOCAL_FEEDS_DIR } from '../core/constants.js';
+import { LOCAL_FEEDS_DIR } from '../core/metadatas/constants.js';
 /**
  * Checks if local feeds exist in the LOCAL_FEEDS_DIR
  * Returns true if the directory exists and contains at least one .json file

package/dist/utils/githubUtils.d.ts

@@ -1,4 +1,4 @@
-import { RegistryConfig, RequirementConfig } from '../core/types.js';
+import { RegistryConfig, RequirementConfig } from '../core/metadatas/types.js';
 /**
  * Get the latest version available for a GitHub repository
  * @param execPromise The promise-based exec function

package/dist/utils/githubUtils.js

@@ -3,7 +3,7 @@ import util from 'util';
 import fs from 'fs/promises';
 import path from 'path';
 import { extractZipFile } from './clientUtils.js';
-import { SETTINGS_DIR } from '../core/constants.js';
+import { SETTINGS_DIR } from '../core/metadatas/constants.js';
 const execAsync = util.promisify(exec);
 /**
  * Get the latest version available for a GitHub repository

package/dist/utils/logger.d.ts

@@ -9,6 +9,8 @@ export declare class Logger {
     private static getTimestamp;
     private static writeToLogFile;
     static log(message: string): Promise<void>;
+    static info(message: string): Promise<void>;
+    static warn(message: string): Promise<void>;
     static debug(message: string | object): Promise<void>;
     static error(message: string, error?: unknown): Promise<void>;
 }

package/dist/utils/logger.js

@@ -1,6 +1,6 @@
 import fs from 'fs';
 import path from 'path';
-import { SETTINGS_DIR } from '../core/constants.js';
+import { SETTINGS_DIR } from '../core/metadatas/constants.js';
 export class Logger {
     static verbose = false;
     static fileLoggingEnabled = true;
@@ -48,6 +48,16 @@ export class Logger {
         console.log(message);
         await this.writeToLogFile('INFO', message);
     }
+    static async info(message) {
+        console.info(message);
+        await this.writeToLogFile('INFO', message);
+    }
+    static async warn(message) {
+        const yellowColor = '\x1b[33m';
+        const resetColor = '\x1b[0m';
+        console.warn(`${yellowColor}${message}${resetColor}`);
+        await this.writeToLogFile('WARN', message);
+    }
     static async debug(message) {
         let formattedMessage;
         if (typeof message === 'object') {

package/dist/utils/macroExpressionUtils.d.ts

@@ -1,4 +1,4 @@
-import { ServerInstallOptions } from '../core/types.js';
+import { ServerInstallOptions } from '../core/metadatas/types.js';
 export declare const MACRO_EXPRESSIONS: {
     readonly PYTHON_PACKAGE: "${PYTHON_PACKAGE}";
     readonly NPMPATH: "${NPMPATH}";

package/dist/utils/osUtils.d.ts

@@ -1,4 +1,4 @@
-import { OSType } from '../core/types.js';
+import { OSType } from '../core/metadatas/types.js';
 export declare function getOSType(): OSType;
 export declare function installCLI(tool: 'gh' | 'git'): Promise<void>;
 /**

package/dist/utils/osUtils.js

@@ -1,4 +1,4 @@
-import { OSType } from '../core/types.js';
+import { OSType } from '../core/metadatas/types.js';
 import os from 'os';
 import { exec } from 'child_process';
 import util from 'util';

package/dist/web/contract/serverContract.d.ts

@@ -1,4 +1,4 @@
-import { DependencyConfig, RegistryConfig, ServerInstallOptions } from '../../core/types.js';
+import { DependencyConfig, RegistryConfig, ServerInstallOptions } from '../../core/metadatas/types.js';
 export interface OnboardServerConfig {
     name: string;
     description: string;

package/dist/web/public/index.html

@@ -167,7 +167,7 @@
 
     <!-- Module scripts -->
     <script type="module">
-        import { fetchServerCategories, handleInstallServer, installRequirement, upgradeRequirement, uninstallTool } from './js/api.js';
+        import { fetchServerCategories, handleInstallServer, uninstallTool } from './js/api.js';
         import { setupSearch } from './js/serverCategoryList.js';
         import { showServerDetails } from './js/serverCategoryDetails.js';
         import { showInstallModal, closeModal, setupModalOutsideClick } from './js/modal.js';
@@ -182,8 +182,6 @@
                                                     // If other parts of the app call window.showOnboardModal, they'll need updating too.
         window.closeModal = closeModal;
         window.handleInstallServer = handleInstallServer;
-        window.installRequirement = installRequirement;
-        window.upgradeRequirement = upgradeRequirement;
         window.uninstallTool = uninstallTool;
 
         // Initialize

package/dist/web/public/js/api.js

@@ -42,7 +42,7 @@ async function fetchServerCategories() {
 async function handleInstallServer(event, categoryName, serverName, callback, options = {}) {
     event.preventDefault(); // Prevent page reload
     console.log("Handling install for:", categoryName, serverName);
-    
+
     // Get selected targets from the form if not provided in options
     const selectedTargets = options.targets || [...document.querySelectorAll('input[name="targets"]:checked')]
         .map(cb => cb.value);
@@ -71,7 +71,7 @@ async function handleInstallServer(event, categoryName, serverName, callback, op
         const response = await fetch(`/api/categories/${categoryName}/install`, {
             method: 'POST',
             headers: { 'Content-Type': 'application/json' },
-            body: JSON.stringify({serverList: serverList})
+            body: JSON.stringify({ serverList: serverList })
         });
 
         if (!response.ok) {
@@ -90,82 +90,6 @@ async function handleInstallServer(event, categoryName, serverName, callback, op
     }
 }
 
-// Install requirement handler
-async function installRequirement(reqName) {
-    const detailsDiv = document.getElementById('serverCategoryDetails');
-    const serverTitle = detailsDiv.querySelector('h3');
-    if (!serverTitle) {
-        showToast('No server selected.', 'error');
-        return;
-    }
-    let serverName = serverTitle.textContent;
-    if (serverName.includes(' for ')) {
-        serverName = serverName.split(' for ')[0];
-    }
-    const confirmed = await showConfirm(`Do you want to install requirement '${reqName}' for ${serverName}?`);
-    if (!confirmed) {
-        return;
-    }
-    
-    const btn = Array.from(document.querySelectorAll('button')).find(b => b.textContent.trim() === 'Install' && b.onclick?.toString().includes(reqName));
-    if (btn) btn.disabled = true;
-    
-    try {
-        const response = await fetch(`/api/categories/${serverName}/install-requirement`, {
-            method: 'POST',
-            headers: { 'Content-Type': 'application/json' },
-            body: JSON.stringify({ requirementName: reqName })
-        });
-        if (!response.ok) {
-            const errorData = await response.text();
-            throw new Error(`Installation failed: ${errorData || response.statusText}`);
-        }
-        showToast(`Requirement '${reqName}' installation initiated successfully!`, 'success');
-        setTimeout(() => {
-            fetchServerCategories();
-            window.showServerDetails(serverName);
-        }, 1000);
-    } catch (error) {
-        console.error('Error installing requirement:', error);
-        showToast(`Error installing requirement: ${error.message}. Please check console.`, 'error');
-    } finally {
-        if (btn) btn.disabled = false;
-    }
-}
-
-// Handle upgrade/uninstall actions
-async function upgradeRequirement(name) {
-    const serverTitle = document.querySelector('#serverCategoryDetails h3')?.textContent;
-    if (!serverTitle) {
-        showToast('No server selected.', 'error');
-        return;
-    }
-
-    const upgradeConfirmed = await showConfirm(`Do you want to upgrade requirement '${name}' for ${serverTitle}?`);
-    if (!upgradeConfirmed) {
-        return;
-    }
-
-    try {
-        const response = await fetch(`/api/categories/${serverTitle}/upgrade-requirement`, {
-            method: 'POST',
-            headers: { 'Content-Type': 'application/json' },
-            body: JSON.stringify({ requirementName: name })
-        });
-
-        if (!response.ok) {
-            const errorData = await response.text();
-            throw new Error(`Upgrade failed: ${errorData || response.statusText}`);
-        }
-
-        showToast(`Requirement '${name}' upgrade initiated successfully!`, 'success');
-        fetchServerCategories();
-        window.showServerDetails(serverTitle);
-    } catch (error) {
-        console.error('Error upgrading requirement:', error);
-        showToast(`Error upgrading requirement: ${error.message}`, 'error');
-    }
-}
 
 async function uninstallTool(name) {
     const serverTitle = document.querySelector('#serverCategoryDetails h3')?.textContent;
@@ -204,7 +128,5 @@ export {
     allServerCategoriesData,
     fetchServerCategories,
     handleInstallServer,
-    installRequirement,
-    upgradeRequirement,
     uninstallTool
 };

package/dist/web/public/js/modal/installation.js

@@ -175,7 +175,7 @@ async function pollInstallStatus(categoryName, serverName, targets, interval = 2
                             delayedAppendInstallLoadingMessage(`${target}: ${msg}`);
                             lastMessages[target] = msg;
                         }
-                        if (status !== "completed") {
+                        if (status !== "completed" && status !== "failed") {
                             allTargetsCompleted = false;
                         }
                     }

package/dist/web/public/js/onboard/ONBOARDING_PAGE_DESIGN.md

@@ -168,9 +168,9 @@ A toggle switch allows users to switch between the standard form view and a raw
   - Calls `getFormData()` (from `formProcessor.js`) to get the current form data as `FeedConfiguration`.
   - Sends an initial POST request to `/api/categories/onboard` with the `FeedConfiguration` object and an `isUpdate` flag.
   - The "Publish" button shows a spinning loader icon and its text changes to "Publishing...". Both "Validate" and "Publish" buttons are disabled.
-  - **Polling for Status**: If the initial publish request is successful and the operation is not immediately completed or failed, `handlePublish` initiates polling using the shared `pollOperationStatus` function (from `validationHandlers.js`). This function periodically calls `GET /api/categories/:categoryName/onboard/status`.
-  - **Displaying Results**: The shared `updateOperationDisplay` function (from `validationHandlers.js`) formats and displays the results from both the initial publish call and subsequent status polls in the relevant status panel. It shows overall status, messages, PR info (if available), and detailed validation results if included in the publish response.
-  - **Completion/Failure**: Polling stops when the status is 'COMPLETED', 'FAILED', or 'succeeded'. Upon completion or failure, the "Publish" button reverts to its original state, and both "Validate" and "Publish" buttons are re-enabled. Success and error messages are displayed using `showToast()`.
+  - **Polling for Status**: If the initial publish request is successful and the operation is not immediately completed or failed, `handlePublish` initiates polling. The shared `pollOperationStatus` function (from `validationHandlers.js`) is called, which periodically queries `GET /api/categories/:categoryName/onboard/status?operationType=FULL_ONBOARDING`. `pollOperationStatus` now returns a boolean to manage polling continuation.
+  - **Displaying Results**: The shared `updateOperationDisplay` function (from `validationHandlers.js`) formats and displays detailed progress, including individual steps, from both the initial publish call and subsequent status polls.
+  - **Completion/Failure**: Polling stops based on the status returned by `pollOperationStatus`. Upon completion or failure, buttons are reset, and `showToast()` displays messages. For detailed information on recent changes to polling and status display, see Section 9: "Enhanced Operation Status Polling and Display".
 - **Validation (`handleValidation` in `validationHandlers.js`)**:
 - **Validation (`handleValidation` in `validationHandlers.js`)**:
   - The `validationStatusPanel` (unique per tab) is located under the "MCP Servers" section (or equivalent) and above the main action buttons ("Validate", "Publish"). It is a foldable panel.
@@ -179,14 +179,14 @@ A toggle switch allows users to switch between the standard form view and a raw
     - Sends an initial POST request to `/api/categories/onboard/validate`.
     - The "Validate" button shows a spinning loader icon and its text changes to "Validating...". Both "Validate" and "Publish" buttons are disabled.
   - **Polling for Status**:
-    - If the initial validation request is successful and the operation is not immediately completed or failed, `handleValidation` initiates polling using the shared `pollOperationStatus` function (from `validationHandlers.js`).
-    - This function uses the `onboardingId` (category name) from the validation response to periodically call `GET /api/categories/:categoryName/onboard/status`.
+    - If the initial validation request is successful and the operation is not immediately completed or failed, `handleValidation` initiates polling.
+    - The shared `pollOperationStatus` function (from `validationHandlers.js`) is called, which periodically queries `GET /api/categories/:categoryName/onboard/status?operationType=VALIDATION_ONLY` (using the category name from the form). `pollOperationStatus` now returns a boolean to manage polling continuation.
   - **Displaying Results**:
-    - The shared `updateOperationDisplay` function (from `validationHandlers.js`) formats and displays the results from both the initial validation call and subsequent status polls in the relevant status panel.
-    - It handles different structures of the `validationStatus` object in the response, including displaying overall status, messages, and detailed results for each server if `validationStatus.serverResults` is present.
+    - The shared `updateOperationDisplay` function (from `validationHandlers.js`) formats and displays detailed progress, including individual steps, from both the initial validation call and subsequent status polls.
+    - It handles different structures of the `validationStatus` object and overall operation status.
   - **Completion/Failure**:
-    - Polling stops when the status is 'COMPLETED', 'FAILED', or 'succeeded'.
-    - Upon completion or failure, the "Validate" button reverts to its original state ("Validate" text and icon), and both "Validate" and "Publish" buttons are re-enabled.
+    - Polling stops based on the status returned by `pollOperationStatus`.
+    - Upon completion or failure, buttons are reset. For detailed information on recent changes to polling and status display, see Section 9: "Enhanced Operation Status Polling and Display".
 - **Copy JSON (`copyJsonToClipboard` in `uiHandlers.js`)**: Copies the content of `jsonEditorTextarea` to the clipboard. Uses `showToast()` for feedback.
 - **Global Function Exposure**: Necessary UI handler functions (like `addServer`, `removeServer`, `toggleSectionContent`, etc.) are attached to the `window` object so they can be called from `onclick` attributes in the HTML templates.
 - **Custom Notifications**: Standard browser `alert()` calls have been replaced with a custom toast notification system (`showToast()` from `../notifications.js`). This system requires an `.alert-container` div in the host HTML (`onboard.html`) and uses CSS from `css/notifications.css` for styling. The `notifications.js` module handles the creation, display, and dismissal (manual and automatic) of these toasts without relying on Bootstrap's JavaScript.
@@ -290,6 +290,38 @@ This section documents significant fixes and behavior changes implemented recent
         - **Outcome:** The "Publish" and "Validate" buttons now reliably revert to their default active states when an operation (validation or publish) concludes with a failure, regardless of the casing of the status string from the backend or whether the failure occurs immediately or during polling.
   - **Overall Outcome:** These changes improve the reliability of data submission and provide more accurate UI feedback for asynchronous operations on the "Create Server in Existing Category" tab.
 
+- **Enhanced Operation Status Polling and Display (May 2025 - Current Session):**
+  - **Context:** Significant improvements were made to the handling of asynchronous operations (validation and publishing), including more detailed progress display, robust polling, and clearer API interactions.
+  - **Issues Addressed & Solutions:**
+    1.  **Server-Side API (`server.ts` - `/api/categories/:categoryName/onboard/status`):**
+        -   The endpoint now requires an `operationType` query parameter (e.g., `VALIDATION_ONLY`, `FULL_ONBOARDING`).
+        -   The response payload (`OperationStatus`) was enhanced to include:
+            -   `steps`: An array of objects detailing each step of the operation (name, serverName, timestamp, status, errorMessage).
+            -   `operationType`: Reflects the type of operation being tracked, taken from the status object.
+            -   `feedConfiguration`: Conditionally included for successful `VALIDATION_ONLY` operations if present in the result.
+            -   The `onboardingId` in the response is `categoryName_operationType`.
+            -   The `message` field in the response now prioritizes the last step's name or an overall error message.
+    2.  **Client-Side Polling Logic (`validationHandlers.js` - `pollOperationStatus`):**
+        -   The function now accepts an `operationType` parameter, which is passed to the API.
+        -   It returns a boolean promise (`Promise<boolean>`) indicating whether polling should continue, allowing the caller (`handleValidation` or `handlePublish`) to manage `clearInterval`.
+        -   Calls `ensureProgressToggleListener` to ensure the UI for displaying progress steps is interactive.
+        -   Status comparisons (`COMPLETED`, `FAILED`, `SUCCEEDED`) are now case-insensitive.
+    3.  **Operation Initiation (`publishHandler.js` - `handlePublish`, `validationHandlers.js` - `handleValidation`):**
+        -   When initiating polling, these functions now pass the correct `operationType` (`FULL_ONBOARDING` for publish, `VALIDATION_ONLY` for validate) and use the original `finalFeedConfiguration.name` as the `categoryName` for the polling request.
+        -   They now manage `clearInterval` based on the boolean returned by `pollOperationStatus`.
+        -   Both handlers call `ensureProgressToggleListener` at the beginning to prepare the UI for status updates.
+        -   `handlePublish` includes improved error handling for the initial publish request, ensuring UI elements are correctly updated even if the initial call fails or returns a terminal status.
+    4.  **UI Display (`validationHandlers.js` - `updateOperationDisplay`):**
+        -   A new collapsible "Progress" section is displayed, showing detailed `steps` from the API response. Each step includes:
+            -   A status icon (error, in-progress spinner, success).
+            -   The step name, server name (if applicable), and timestamp.
+            -   An error message for the step, if any.
+        -   The visibility of the "Progress" section is managed by `ensureProgressToggleListener` (which attaches a click handler to the section header) and the `toggleSectionContent` utility.
+        -   The `operationType` is now displayed.
+        -   The logic for displaying the overall status spinner has been updated to cover more in-progress states (e.g., `PENDING`, `VALIDATING`, `PRCREATING`, `PUBLISHING`) and uses case-insensitive comparisons.
+    5.  **Progress Section Toggling (`validationHandlers.js` - `ensureProgressToggleListener`):**
+        -   A new exported utility function, `ensureProgressToggleListener`, was added. It attaches a click event listener to the status content element. This listener delegates to `toggleSectionContent` (from `uiHandlers.js`) when the progress section header is clicked, allowing users to expand or collapse the detailed list of progress steps. The listener is attached only once per status content element.
+  - **Outcome:** These changes provide users with more granular and interactive feedback on long-running operations, improve the robustness and accuracy of status polling, and align client-server communication for tracking asynchronous onboarding tasks.
 ---
 
 ## 10. Server Validation System