everything-test

The everything-test skill is a diagnostic utility designed for the inventory_master framework to manage and verify the status of Everything search integrations. It facilitates robust connectivity testing across three primary communication channels: the ES Command Line Interface (CLI), the local HTTP server, and the Python SDK provider. This skill is intended for system administrators and developers who rely on Everything as a high-speed, read-only indexing engine for file system management, specifically within the Plan-Approve-Apply folder tidying workflow.

By leveraging this tool, users can systematically validate whether the underlying Everything process is active, ensure that the HTTP API is responding to queries, and confirm that the Python SDK can correctly interface with the indexing service. It is a critical component for troubleshooting configuration issues, identifying network or permission-related failures, and confirming that the system is ready for automated inventory tasks.

• Performs health checks on the Everything application process via PowerShell integration.

• Validates the ES CLI (es.exe) availability and conducts basic wildcard pattern searches to ensure command-line functionality.

• Tests HTTP server connectivity using curl-based requests to verify endpoint responsiveness and API authentication.

• Integrates with the inventory_master Python SDK to confirm data retrieval capabilities for production-grade file operations.

• Provides actionable feedback, including fallback recommendations when Everything is unavailable or when the HTTP server fails to respond.

• Always run these tests when initially setting up the inventory_master environment or after modifying system firewall and port settings.

• Use the provided PowerShell and curl examples to isolate issues between the CLI and the HTTP interface.

• If connection tests fail, the tool recommends falling back to the local scanner to prevent workflow disruptions.

• Ensure the Everything HTTP server port (default 8080) is not occupied by other services and that credentials are correctly configured for authenticated access.

• Inputs typically include target search patterns; outputs provide success statuses, error diagnostics, and connectivity reports.