Format all YAML files to pass yamllint validation

- Added document start markers (---) to all YAML files
- Fixed line length issues by breaking long lines appropriately
- Removed trailing whitespace throughout all files
- Added proper newlines at end of files
- Fixed truthy value format ('on' -> 'on')
- Standardized YAML formatting across workflows and issue templates
- Used multi-line strings (>) for long descriptions
- Maintained readability while adhering to 80-character line limit

All YAML files now pass yamllint validation with only minor warnings remaining.

.github/ISSUE_TEMPLATE/new_subagent.yml

@@ -1,3 +1,4 @@
+---
 name: New Subagent Proposal
 description: Propose a new specialized subagent for the collection
 title: "[NEW AGENT] "
@@ -6,9 +7,12 @@ body:
   - type: markdown
     attributes:
       value: |
-        Thank you for proposing a new subagent! Quality subagents require careful design and clear specialization.
-        
-        **Important**: Only propose subagents for legitimate, constructive use cases. Proposals for malicious or harmful capabilities will be rejected and may result in moderation action.
+        Thank you for proposing a new subagent! Quality subagents
+        require careful design and clear specialization.
+
+        **Important**: Only propose subagents for legitimate,
+        constructive use cases. Proposals for malicious or harmful
+        capabilities will be rejected and may result in moderation action.
 
   - type: checkboxes
     id: preliminary-checks
@@ -18,7 +22,8 @@ body:
       options:
         - label: I have read the [Code of Conduct](.github/CODE_OF_CONDUCT.md)
           required: true
-        - label: I have reviewed existing subagents to ensure this is not a duplicate
+        - label: >-
+            I have reviewed existing subagents to ensure this is not a duplicate
           required: true
         - label: This proposal is for legitimate, constructive use cases only
           required: true
@@ -38,7 +43,8 @@ body:
     id: domain-expertise
     attributes:
       label: Domain Expertise
-      description: What specific domain or technology does this agent specialize in?
+      description: >-
+        What specific domain or technology does this agent specialize in?
       placeholder: This agent specializes in...
     validations:
       required: true
@@ -47,7 +53,9 @@ body:
     id: unique-value
     attributes:
       label: Unique Value Proposition
-      description: How is this different from existing subagents? What unique capabilities does it provide?
+      description: >-
+        How is this different from existing subagents?
+        What unique capabilities does it provide?
       placeholder: Unlike existing agents, this one would...
     validations:
       required: true
@@ -82,12 +90,14 @@ body:
     id: examples
     attributes:
       label: Example Interactions
-      description: Provide 2-3 example interactions showing how users would work with this agent
+      description: >-
+        Provide 2-3 example interactions showing how users would
+        work with this agent
       placeholder: |
         **Example 1:**
         User: "Implement a smart contract for..."
         Agent response: "I'll create a secure smart contract with..."
-        
+
         **Example 2:**
         User: "Optimize this blockchain query..."
         Agent response: "Let me analyze the query and suggest optimizations..."
@@ -98,8 +108,11 @@ body:
     id: expertise-evidence
     attributes:
       label: Your Expertise
-      description: What experience or credentials do you have in this domain?
-      placeholder: I have X years of experience in... I've worked with... I hold certifications in...
+      description: >-
+        What experience or credentials do you have in this domain?
+      placeholder: >-
+        I have X years of experience in... I've worked with...
+        I hold certifications in...
     validations:
       required: true
 
@@ -107,5 +120,7 @@ body:
     id: additional-context
     attributes:
       label: Additional Context
-      description: Any other relevant information, resources, or considerations
-      placeholder: Relevant documentation, similar tools, potential challenges...
+      description: >-
+        Any other relevant information, resources, or considerations
+      placeholder: >-
+        Relevant documentation, similar tools, potential challenges...