Fix ESLint config syntax error and format codebase

Co-authored-by: lachieh <[email protected]>

Author: Copilot

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -1,7 +1,7 @@
 name: 🐛 Bug Report
 description: Report a bug or unexpected behavior in wasmCloud TypeScript
-title: "[Bug]: "
-labels: ["bug", "triage"]
+title: '[Bug]: '
+labels: ['bug', 'triage']
 assignees: []
 
 body:
@@ -32,7 +32,7 @@ body:
       value: |
         1. 
         2. 
-        3. 
+        3.
     validations:
       required: true
 
@@ -60,13 +60,13 @@ body:
       label: Affected Component
       description: Which part of the repository is affected?
       options:
-        - "@wasmcloud/lattice-client-core"
-        - "@wasmcloud/lattice-client-react"
-        - "Washboard UI"
-        - "TypeScript Examples"
-        - "Documentation"
-        - "Build/Development Tools"
-        - "Other"
+        - '@wasmcloud/lattice-client-core'
+        - '@wasmcloud/lattice-client-react'
+        - 'Washboard UI'
+        - 'TypeScript Examples'
+        - 'Documentation'
+        - 'Build/Development Tools'
+        - 'Other'
     validations:
       required: true
 
@@ -120,4 +120,4 @@ body:
       description: By submitting this issue, you agree to follow our Code of Conduct
       options:
         - label: I agree to follow this project's Code of Conduct
-          required: true
+          required: true

.github/ISSUE_TEMPLATE/config.yml

@@ -11,4 +11,4 @@ contact_links:
     about: Join the wasmCloud Slack community for real-time discussion
   - name: 🐛 wasmCloud Core Issues
     url: https://github.com/wasmCloud/wasmCloud/issues
-    about: Report issues with the core wasmCloud runtime
+    about: Report issues with the core wasmCloud runtime

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -1,7 +1,7 @@
 name: ✨ Feature Request
 description: Suggest a new feature or enhancement for wasmCloud TypeScript
-title: "[Feature]: "
-labels: ["enhancement", "triage"]
+title: '[Feature]: '
+labels: ['enhancement', 'triage']
 assignees: []
 
 body:
@@ -41,14 +41,14 @@ body:
       label: Target Component
       description: Which part of the repository would this feature affect?
       options:
-        - "@wasmcloud/lattice-client-core"
-        - "@wasmcloud/lattice-client-react"
-        - "Washboard UI"
-        - "TypeScript Examples"
-        - "Documentation"
-        - "Build/Development Tools"
-        - "New Package/Component"
-        - "Other"
+        - '@wasmcloud/lattice-client-core'
+        - '@wasmcloud/lattice-client-react'
+        - 'Washboard UI'
+        - 'TypeScript Examples'
+        - 'Documentation'
+        - 'Build/Development Tools'
+        - 'New Package/Component'
+        - 'Other'
     validations:
       required: true
 
@@ -58,14 +58,14 @@ body:
       label: Feature Type
       description: What type of feature is this?
       options:
-        - "New API/Function"
-        - "UI/UX Enhancement"
-        - "Developer Experience"
-        - "Performance Improvement"
-        - "Integration/Plugin"
-        - "Documentation"
-        - "Tooling/Build"
-        - "Other"
+        - 'New API/Function'
+        - 'UI/UX Enhancement'
+        - 'Developer Experience'
+        - 'Performance Improvement'
+        - 'Integration/Plugin'
+        - 'Documentation'
+        - 'Tooling/Build'
+        - 'Other'
     validations:
       required: true
 
@@ -96,10 +96,10 @@ body:
       label: Priority
       description: How important is this feature to you?
       options:
-        - "Low - Nice to have"
-        - "Medium - Would improve my workflow"
-        - "High - Blocking my use case"
-        - "Critical - Cannot proceed without this"
+        - 'Low - Nice to have'
+        - 'Medium - Would improve my workflow'
+        - 'High - Blocking my use case'
+        - 'Critical - Cannot proceed without this'
     validations:
       required: true
 
@@ -121,9 +121,9 @@ body:
       description: Are you willing to help implement this feature?
       options:
         - label: "I'm willing to submit a PR to implement this feature"
-        - label: "I can help with testing and feedback"
-        - label: "I can help with documentation"
-        - label: "I can provide use case validation"
+        - label: 'I can help with testing and feedback'
+        - label: 'I can help with documentation'
+        - label: 'I can provide use case validation'
 
   - type: textarea
     id: additional
@@ -140,4 +140,4 @@ body:
       description: By submitting this issue, you agree to follow our Code of Conduct
       options:
         - label: I agree to follow this project's Code of Conduct
-          required: true
+          required: true

.github/ISSUE_TEMPLATE/proposal.yml

@@ -1,7 +1,7 @@
 name: 💡 Proposal
 description: Propose significant changes, new packages, or architectural improvements
-title: "[Proposal]: "
-labels: ["proposal", "discussion", "triage"]
+title: '[Proposal]: '
+labels: ['proposal', 'discussion', 'triage']
 assignees: []
 
 body:
@@ -30,11 +30,11 @@ body:
       placeholder: |
         ## Motivation
         Currently...
-        
+
         ## Goals
         - Goal 1
         - Goal 2
-        
+
         ## Non-Goals
         - Non-goal 1
     validations:
@@ -46,14 +46,14 @@ body:
       label: Scope of Changes
       description: What is the scope of this proposal?
       options:
-        - "Single package changes"
-        - "Multiple package changes"
-        - "New package/library"
-        - "Architecture changes"
-        - "Breaking changes"
-        - "Documentation overhaul"
-        - "Tooling/infrastructure"
-        - "Repository structure"
+        - 'Single package changes'
+        - 'Multiple package changes'
+        - 'New package/library'
+        - 'Architecture changes'
+        - 'Breaking changes'
+        - 'Documentation overhaul'
+        - 'Tooling/infrastructure'
+        - 'Repository structure'
     validations:
       required: true
 
@@ -67,12 +67,12 @@ body:
       placeholder: |
         ## Overview
         The proposed solution...
-        
+
         ## API Design
         ```typescript
         // Example interfaces
         ```
-        
+
         ## Architecture
         Describe the architecture...
       render: markdown
@@ -89,10 +89,10 @@ body:
       placeholder: |
         ## Alternative 1
         We considered...
-        
+
         ## Alternative 2
         Another option was...
-        
+
         ## Decision Rationale
         We chose the proposed approach because...
 
@@ -107,7 +107,7 @@ body:
         ## Breaking Changes
         - Change 1: Description and migration path
         - Change 2: Description and migration path
-        
+
         ## Migration Strategy
         Users can migrate by...
 
@@ -121,11 +121,11 @@ body:
         ## Phase 1 (Week 1-2)
         - Task 1
         - Task 2
-        
+
         ## Phase 2 (Week 3-4)
         - Task 3
         - Task 4
-        
+
         ## Dependencies
         This implementation depends on...
 
@@ -139,10 +139,10 @@ body:
       placeholder: |
         ## Unit Tests
         - Test coverage for...
-        
+
         ## Integration Tests
         - Integration scenarios...
-        
+
         ## E2E Tests
         - End-to-end workflows...
 
@@ -155,7 +155,7 @@ body:
       placeholder: |
         ## Risk 1: Description
         **Mitigation**: Strategy to address this risk
-        
+
         ## Risk 2: Description
         **Mitigation**: Strategy to address this risk
 
@@ -165,10 +165,10 @@ body:
       label: Priority
       description: What is the priority level of this proposal?
       options:
-        - "Low - Future consideration"
-        - "Medium - Important but not urgent"
-        - "High - Should be prioritized"
-        - "Critical - Urgent need"
+        - 'Low - Future consideration'
+        - 'Medium - Important but not urgent'
+        - 'High - Should be prioritized'
+        - 'Critical - Urgent need'
     validations:
       required: true
 
@@ -183,7 +183,7 @@ body:
         ## Acceptance Criteria
         - Criteria 1
         - Criteria 2
-        
+
         ## Success Metrics
         - Metric 1: Target value
         - Metric 2: Target value
@@ -195,10 +195,10 @@ body:
       description: How do you plan to be involved in this proposal?
       options:
         - label: "I'm willing to lead the implementation"
-        - label: "I can contribute to the implementation"
-        - label: "I can help with design and review"
-        - label: "I can provide testing and feedback"
-        - label: "I can help with documentation"
+        - label: 'I can contribute to the implementation'
+        - label: 'I can help with design and review'
+        - label: 'I can provide testing and feedback'
+        - label: 'I can help with documentation'
 
   - type: textarea
     id: additional
@@ -215,4 +215,4 @@ body:
       description: By submitting this issue, you agree to follow our Code of Conduct
       options:
         - label: I agree to follow this project's Code of Conduct
-          required: true
+          required: true

.github/actions/crate-versions/action.yml

@@ -14,7 +14,7 @@ inputs:
   lookback:
     description: Number of versions to go back
     required: false
-    default: "3"
+    default: '3'
 
 runs:
   using: composite

.github/actions/wash-versions/action.yml

@@ -14,7 +14,7 @@ inputs:
 
 runs:
   using: composite
-  
+
   steps:
     - name: Fetch crate versions
       id: fetch_versions

.github/workflows/ci_.yml

@@ -37,10 +37,10 @@ jobs:
       BOT_APP_ID: ${{ secrets.BOT_APP_ID }}
       BOT_APP_PRIVATE_KEY: ${{ secrets.BOT_APP_PRIVATE_KEY }}
     permissions:
-      actions: write        # Needed to create releases
-      contents: write       # Needed to commit changesets
-      pull-requests: write  # Needed to create pull requests
-      id-token: write       # Needed for npm provenance
+      actions: write # Needed to create releases
+      contents: write # Needed to commit changesets
+      pull-requests: write # Needed to create pull requests
+      id-token: write # Needed for npm provenance
 
   ci-check:
     needs: [build, test]

.github/workflows/ci_build.yml

@@ -31,4 +31,4 @@ jobs:
           name: build-assets
           path: |
             ./**/dist/
-            !**/node_modules/
+            !**/node_modules/

.github/workflows/ci_release.yml

@@ -25,9 +25,9 @@ jobs:
       (github.event_name == 'push' && github.ref == 'refs/heads/main')
 
     permissions:
-      contents: write       # Needed to commit changesets
-      pull-requests: write  # Needed to create pull requests
-      id-token: write       # Needed for npm provenance
+      contents: write # Needed to commit changesets
+      pull-requests: write # Needed to create pull requests
+      id-token: write # Needed for npm provenance
 
     runs-on: ubuntu-latest
 
@@ -102,4 +102,3 @@ jobs:
     uses: ./.github/workflows/release_washboard-ui.yml
     with:
       version: ${{ fromJson(needs.changesets.outputs.packageVersions || '{}').washboard-ui }}
-      

.github/workflows/ci_test.yml

@@ -41,7 +41,7 @@ jobs:
         uses: ./.github/actions/crate-versions
         with:
           crate: wash-cli
-          lookback: "1"
+          lookback: '1'
 
     outputs:
       versions: ${{ steps.fetch.outputs.versions }}