fix: disable strict markdown linting rules for documentation

Author: alvagante

.kiro/specs/puppetdb-integration/design.md

@@ -2,7 +2,12 @@
 
 ## Overview
 
-This design document outlines the architecture for version 0.2.0 of Padawi, transforming it from a Bolt-specific web interface into a general-purpose remote execution platform. The core architectural shift introduces a plugin-based integration system where PuppetDB serves as the first additional integration beyond Puppet Bolt. This establishes patterns and abstractions that will support future integrations with Ansible, Terraform, AWS CLI, Azure CLI, Kubernetes, and other infrastructure management tools.
+This design document outlines the architecture for version 0.2.0 of Pabawi, transforming it from a
+Bolt-specific web interface into a general-purpose remote execution platform. The core architectural
+shift introduces a plugin-based integration system where PuppetDB serves as the first additional
+integration beyond Puppet Bolt. This establishes patterns and abstractions that will support future
+integrations with Ansible, Terraform, AWS CLI, Azure CLI, Kubernetes, and other infrastructure
+management tools.
 
 The design introduces two key concepts:
 
@@ -19,13 +24,17 @@ PuppetDB integration provides:
 
 Additionally, this version introduces action re-execution capabilities, allowing users to quickly repeat operations with preserved parameters, and comprehensive UI enhancements to support the multi-tool architecture.
 
-**Expert Mode Enhancement**: A critical priority for this version is enhancing the expert mode experience to provide complete transparency into command execution. When expert mode is enabled, users will see the full command line being executed and complete, untruncated output (stdout/stderr). This visibility is essential for debugging, auditing, and understanding exactly what operations are being performed on managed infrastructure.
+**Expert Mode Enhancement**: A critical priority for this version is enhancing the expert mode
+experience to provide complete transparency into command execution. When expert mode is enabled,
+users will see the full command line being executed and complete, untruncated output (stdout/stderr).
+This visibility is essential for debugging, auditing, and understanding exactly what operations are
+being performed on managed infrastructure.
 
 ## Architecture
 
 ### High-Level Architecture
 
-```
+```text
 ┌─────────────────────────────────────────────────────────────┐
 │                        Frontend (Svelte)                     │
 │  ┌──────────────┐  ┌──────────────┐  ┌──────────────┐     │
@@ -501,7 +510,7 @@ interface AggregatedNodeData {
 
 ### Prework Analysis
 
-1.1 WHEN the system is configured with PuppetDB connection details THEN Padawi SHALL retrieve the list of active nodes from PuppetDB
+1.1 WHEN the system is configured with PuppetDB connection details THEN Pabawi SHALL retrieve the list of active nodes from PuppetDB
 Thoughts: This is about the system's ability to connect to PuppetDB and retrieve data. We can test this by generating random PuppetDB configurations (valid and invalid), attempting connections, and verifying that valid configs return node lists while invalid ones fail appropriately.
 Testable: yes - property
 
@@ -601,7 +610,7 @@ Testable: yes - property
 Thoughts: This is about filter functionality. We can verify all filter types work correctly.
 Testable: yes - property
 
-6.1 WHEN the system starts THEN Padawi SHALL read PuppetDB connection configuration from environment variables or configuration files
+6.1 WHEN the system starts THEN Pabawi SHALL read PuppetDB connection configuration from environment variables or configuration files
 Thoughts: This is about configuration loading. We can verify the system reads config from expected sources.
 Testable: yes - example
 
@@ -1218,7 +1227,7 @@ UI tests will verify:
 
 ### New PuppetDB Endpoints
 
-```
+```http
 GET    /api/integrations/status
 GET    /api/integrations/puppetdb/nodes
 GET    /api/integrations/puppetdb/nodes/:certname
@@ -1232,7 +1241,7 @@ POST   /api/integrations/puppetdb/query
 
 ### Enhanced Execution Endpoints
 
-```
+```http
 GET    /api/executions/:id/original          # Get original execution for re-execution
 GET    /api/executions/:id/re-executions     # Get all re-executions of an execution
 POST   /api/executions/:id/re-execute        # Trigger re-execution
@@ -1244,7 +1253,7 @@ GET    /api/executions/:id/command           # Get full command line for executi
 
 ### Enhanced Inventory Endpoints
 
-```
+```http
 GET    /api/inventory?sources=bolt,puppetdb  # Get inventory from specific sources
 GET    /api/inventory/sources                # Get available inventory sources and status
 ```

.kiro/specs/puppetdb-integration/requirements.md

@@ -2,13 +2,13 @@
 
 ## Introduction
 
-This document specifies the requirements for version 0.2.0 of Padawi, a general-purpose remote execution interface that integrates multiple infrastructure management tools. This version adds PuppetDB as the first additional integration beyond Puppet Bolt, establishing patterns for future integrations with tools like Ansible, Terraform, AWS CLI, Azure CLI, and Kubernetes. PuppetDB will serve as both a dynamic inventory source for discovering nodes and as a rich data source for displaying node facts, Puppet run reports, catalogs, and events. This version also introduces task re-execution capabilities and UI enhancements to support the multi-tool architecture.
+This document specifies the requirements for version 0.2.0 of Pabawi, a general-purpose remote execution interface that integrates multiple infrastructure management tools. This version adds PuppetDB as the first additional integration beyond Puppet Bolt, establishing patterns for future integrations with tools like Ansible, Terraform, AWS CLI, Azure CLI, and Kubernetes. PuppetDB will serve as both a dynamic inventory source for discovering nodes and as a rich data source for displaying node facts, Puppet run reports, catalogs, and events. This version also introduces task re-execution capabilities and UI enhancements to support the multi-tool architecture.
 
 **Priority Focus:** A key priority for this version is enhancing the expert mode experience by ensuring full visibility of command execution details. When expert mode is enabled, users must be able to see the complete command line that was executed and the full, untruncated output (stdout/stderr). This transparency is critical for debugging, auditing, and understanding exactly what operations are being performed on managed infrastructure.
 
 ## Glossary
 
-- **Padawi**: A general-purpose remote execution interface that integrates multiple infrastructure management tools (Bolt, PuppetDB, Ansible, Terraform, etc.)
+- **Pabawi**: A general-purpose remote execution interface that integrates multiple infrastructure management tools (Bolt, PuppetDB, Ansible, Terraform, etc.)
 - **PuppetDB**: A centralized storage service that collects and serves data generated by Puppet, including node facts, catalogs, reports, and events
 - **Inventory Source**: A system or service that provides a list of nodes available for remote execution operations
 - **Node Facts**: System information collected about managed nodes (OS, hardware, network configuration, etc.)
@@ -28,7 +28,7 @@ This document specifies the requirements for version 0.2.0 of Padawi, a general-
 
 #### Acceptance Criteria
 
-1. WHEN the system is configured with PuppetDB connection details THEN Padawi SHALL retrieve the list of active nodes from PuppetDB
+1. WHEN the system is configured with PuppetDB connection details THEN Pabawi SHALL retrieve the list of active nodes from PuppetDB
 2. WHEN PuppetDB returns node data THEN the system SHALL transform it into a normalized inventory format compatible with multiple execution tools
 3. WHEN the inventory page loads THEN the system SHALL display nodes from PuppetDB alongside nodes from other inventory sources with clear source attribution
 4. WHERE PuppetDB is configured as an inventory source THEN the system SHALL support filtering nodes by PuppetDB query language (PQL)
@@ -84,11 +84,11 @@ This document specifies the requirements for version 0.2.0 of Padawi, a general-
 
 ### Requirement 6
 
-**User Story:** As an infrastructure administrator, I want to configure PuppetDB connection settings, so that I can connect Padawi to my PuppetDB instance securely.
+**User Story:** As an infrastructure administrator, I want to configure PuppetDB connection settings, so that I can connect Pabawi to my PuppetDB instance securely.
 
 #### Acceptance Criteria
 
-1. WHEN the system starts THEN Padawi SHALL read PuppetDB connection configuration from environment variables or configuration files
+1. WHEN the system starts THEN Pabawi SHALL read PuppetDB connection configuration from environment variables or configuration files
 2. WHERE PuppetDB uses HTTPS THEN the system SHALL support SSL certificate validation with options for custom CA certificates
 3. WHERE PuppetDB requires authentication THEN the system SHALL support token-based authentication
 4. WHEN PuppetDB configuration is invalid THEN the system SHALL log detailed error messages for troubleshooting

.markdownlint.json

@@ -1,10 +1,12 @@
 {
   "default": true,
-  "MD013": {
-    "line_length": 120,
-    "code_blocks": false,
-    "tables": false
+  "MD013": false,
+  "MD024": {
+    "siblings_only": true
   },
   "MD033": false,
-  "MD041": false
+  "MD036": false,
+  "MD040": false,
+  "MD041": false,
+  "MD060": false
 }

README.md

@@ -1,8 +1,8 @@
-# Padawi
+# Pabawi
 
 Version 0.2.0 - Unified Remote Execution Interface
 
-Padawi is a general-purpose remote execution platform that integrates multiple infrastructure management tools including Puppet Bolt and PuppetDB. It provides a unified web interface for managing infrastructure, executing commands, viewing system information, and tracking operations across your entire environment.
+Pabawi is a general-purpose remote execution platform that integrates multiple infrastructure management tools including Puppet Bolt and PuppetDB. It provides a unified web interface for managing infrastructure, executing commands, viewing system information, and tracking operations across your entire environment.
 
 ## Features
 
@@ -543,7 +543,7 @@ npm test --workspace=backend
 
 ## Acknowledgments
 
-Padawi builds on excellent open-source projects:
+Pabawi builds on excellent open-source projects:
 
 - **Puppet Bolt**: Remote task execution engine
 - **PuppetDB**: Centralized Puppet data storage

backend/src/integrations/index.ts

@@ -2,7 +2,7 @@
  * Integration Plugin System
  *
  * This module provides the plugin architecture for integrating multiple
- * backend systems into Padawi. It exports the core interfaces, base classes,
+ * backend systems into Pabawi. It exports the core interfaces, base classes,
  * and types needed to create and manage integration plugins.
  *
  * @module integrations

backend/src/integrations/types.ts

@@ -2,7 +2,7 @@
  * Integration Plugin Types and Interfaces
  *
  * This module defines the core plugin architecture for integrating multiple
- * backend systems (execution tools and information sources) into Padawi.
+ * backend systems (execution tools and information sources) into Pabawi.
  */
 
 import type { Node, Facts, ExecutionResult } from "../bolt/types";

docs/api.md

@@ -1048,19 +1048,19 @@ curl http://localhost:3000/api/executions/jkl012
 curl "http://localhost:3000/api/executions?page=1&pageSize=20"
 ```
 
-2. **Filter by status:**
+1. **Filter by status:**
 
 ```bash
 curl "http://localhost:3000/api/executions?status=failed&page=1"
 ```
 
-3. **Filter by node:**
+1. **Filter by node:**
 
 ```bash
 curl "http://localhost:3000/api/executions?targetNode=node1"
 ```
 
-4. **Filter by date range:**
+1. **Filter by date range:**
 
 ```bash
 curl "http://localhost:3000/api/executions?startDate=2024-01-01T00:00:00Z&endDate=2024-01-31T23:59:59Z"

docs/puppetdb-api.md

@@ -4,7 +4,7 @@ Version: 0.2.0
 
 ## Overview
 
-This document describes the API endpoints added in version 0.2.0 for PuppetDB integration, re-execution capabilities, and expert mode enhancements. These endpoints extend the base Padawi API to support multi-source infrastructure management.
+This document describes the API endpoints added in version 0.2.0 for PuppetDB integration, re-execution capabilities, and expert mode enhancements. These endpoints extend the base Pabawi API to support multi-source infrastructure management.
 
 ## Table of Contents
 
@@ -1004,7 +1004,7 @@ curl -H "X-Expert-Mode: true" \
 
 ## Error Handling
 
-All endpoints follow the standard Padawi error response format:
+All endpoints follow the standard Pabawi error response format:
 
 ```json
 {
@@ -1114,6 +1114,6 @@ List endpoints support pagination:
 ## Additional Resources
 
 - [PuppetDB Integration Setup Guide](./puppetdb-integration-setup.md)
-- [Padawi Configuration Guide](./configuration.md)
-- [Padawi User Guide](./user-guide.md)
+- [Pabawi Configuration Guide](./configuration.md)
+- [Pabawi User Guide](./user-guide.md)
 - [PuppetDB API Documentation](https://puppet.com/docs/puppetdb/latest/api/index.html)