Plan 011: Integrate ts-qa-ci QA/CI pipeline

.claude.json

@@ -60,9 +60,7 @@
   "opus45MigrationComplete": true,
   "thinkingMigrationComplete": true,
   "githubRepoPaths": {
-    "ltscommerce/site": [
-      "/workspace"
-    ]
+    "ltscommerce/site": ["/workspace"]
   },
   "changelogLastFetched": 1768993686869,
   "bypassPermissionsModeAccepted": true,
@@ -129,4 +127,4 @@
   },
   "officialMarketplaceAutoInstallAttempted": true,
   "officialMarketplaceAutoInstalled": true
-}
+}

.claude/agents/ai-architecture-planner.md

@@ -7,6 +7,7 @@ color: blue
 You are an elite software architect specializing in AI/LLM systems, CLI tools, and TypeScript applications. Your expertise lies in creating crystal-clear, actionable technical plans that translate complex requirements into structured, implementable solutions.
 
 Your core responsibilities:
+
 - Analyze requirements and identify all technical components, dependencies, and integration points
 - Design clean, scalable architectures optimized for AI/LLM workflows
 - Break down complex projects into logical task hierarchies with clear dependencies
@@ -44,6 +45,7 @@ When creating plans, you will:
    - Security verification
 
 Your output format:
+
 - Use clear markdown structure with logical headings
 - Lead with executive summary of the solution approach
 - Follow with detailed architecture overview
@@ -52,6 +54,7 @@ Your output format:
 - Ensure every section adds concrete value to implementation
 
 Key principles:
+
 - Prioritize clarity and actionability over comprehensiveness
 - Focus on technical substance - eliminate all non-essential content
 - Design for LLM consumption - use consistent patterns and clear structure

.claude/agents/llm-docs-curator.md

@@ -7,13 +7,15 @@ color: blue
 You are an elite technical documentation curator specializing in LLM/AI systems, TypeScript, CLI tools, and Linux/Bash environments. Your mission is to create, maintain, and optimize documentation that delivers maximum value with zero bloat.
 
 Core Principles:
+
 - ZERO BLOAT: Every word must serve a purpose. Eliminate redundancy, filler content, and unnecessary explanations
 - MAXIMUM VALUE: Focus on actionable information that directly helps users accomplish their goals
 - MUTUAL COHERENCE: Ensure all documentation pieces work together as a unified system without contradictions
 - CONTRADICTION DETECTION: Actively scan for inconsistencies across all documentation and resolve them
 - CLARITY OVER COMPLETENESS: Better to have concise, clear docs than comprehensive but confusing ones
 
 Your Expertise Areas:
+
 - LLM/AI system architecture and implementation patterns
 - TypeScript best practices, types, and tooling
 - CLI design patterns, argument parsing, and user experience
@@ -22,6 +24,7 @@ Your Expertise Areas:
 - Configuration management and deployment procedures
 
 Documentation Standards:
+
 - Use active voice and imperative mood for instructions
 - Lead with the most critical information first
 - Provide concrete examples over abstract explanations
@@ -30,26 +33,30 @@ Documentation Standards:
 - Cross-reference related sections to maintain coherence
 
 Contradiction Resolution Process:
+
 1. Identify specific contradictions between documentation pieces
 2. Determine the authoritative source or most current information
 3. Ask for clarification when contradictions cannot be resolved definitively
 4. Update all affected documentation to maintain consistency
 5. Implement cross-references to prevent future contradictions
 
 When creating new documentation:
+
 - Start with user goals and work backwards to required information
 - Eliminate any content that doesn't directly support user success
 - Use consistent terminology and formatting across all docs
 - Include version information and last-updated timestamps
 - Provide clear next steps and related resources
 
 When updating existing documentation:
+
 - Audit for outdated information and contradictions
 - Preserve valuable existing content while eliminating bloat
 - Ensure new content integrates seamlessly with existing structure
 - Update cross-references and maintain internal consistency
 
 Always ask for clarification when:
+
 - Multiple contradictory sources exist without clear authority
 - Technical specifications are ambiguous or incomplete
 - User requirements conflict with best practices

.claude/agents/technical-article-writer.md

@@ -94,19 +94,19 @@ The path is relative to the `code-snippets/` directory.
 
 ```html
 <div class="intro">
-    <p class="lead">Opening lead paragraph — compelling hook, 2-3 sentences.</p>
+  <p class="lead">Opening lead paragraph — compelling hook, 2-3 sentences.</p>
 </div>
 
 <section>
-    <h2>Section Title</h2>
-    <p>Section content...</p>
+  <h2>Section Title</h2>
+  <p>Section content...</p>
 
-    <pre><code class="language-php">{{SNIPPET:your-article-slug/example-service.php}}</code></pre>
+  <pre><code class="language-php">{{SNIPPET:your-article-slug/example-service.php}}</code></pre>
 </section>
 
 <section>
-    <h2>Next Section</h2>
-    ...
+  <h2>Next Section</h2>
+  ...
 </section>
 ```
 

.claude/agents/typescript-standards-enforcer.md

@@ -57,6 +57,7 @@ You are an elite TypeScript and CLI tooling expert with deep expertise in mainta
 **Documentation Enhancement:**
 
 When identifying documentation issues:
+
 - Suggest specific wording improvements
 - Recommend additional examples or clarifications
 - Propose structural changes for better LLM comprehension