Add .gitattributes and normalize line endings to LF

.gitattributes

@@ -0,0 +1,49 @@
+# Auto-detect text files and normalize line endings to LF in the repo.
+# Working-tree EOLs are decided per-pattern below.
+* text=auto
+
+# Source and config — normalize to LF in repo, check out as-is on each platform
+*.cs            text eol=lf
+*.csproj        text eol=lf
+*.sln           text eol=lf -crlf
+*.props         text eol=lf
+*.targets       text eol=lf
+*.json          text eol=lf
+*.xml           text eol=lf
+*.config        text eol=lf
+*.md            text eol=lf
+*.yml           text eol=lf
+*.yaml          text eol=lf
+*.editorconfig  text eol=lf
+*.gitattributes text eol=lf
+*.gitignore     text eol=lf
+
+# Shell scripts must stay LF
+*.sh            text eol=lf
+
+# Windows-only scripts must stay CRLF
+*.ps1           text eol=crlf
+*.psm1          text eol=crlf
+*.psd1          text eol=crlf
+*.cmd           text eol=crlf
+*.bat           text eol=crlf
+
+# Web assets
+*.js            text eol=lf
+*.ts            text eol=lf
+*.css           text eol=lf
+*.html          text eol=lf
+*.razor         text eol=lf
+*.cshtml        text eol=lf
+
+# Binary assets — never touch
+*.png  binary
+*.jpg  binary
+*.jpeg binary
+*.gif  binary
+*.ico  binary
+*.pdf  binary
+*.zip  binary
+*.dll  binary
+*.exe  binary
+*.snk  binary

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -1,89 +1,89 @@
-name: Bug Report
-description: Report a problem with SQL Performance Studio
-title: "[BUG] "
-labels: ["bug"]
-
-body:
-  - type: dropdown
-    id: component
-    attributes:
-      label: Component
-      description: Which part of SQL Performance Studio is affected?
-      options:
-        - Desktop App (Windows)
-        - Desktop App (macOS)
-        - Desktop App (Linux)
-        - CLI Tool
-        - SSMS Extension
-    validations:
-      required: true
-
-  - type: input
-    id: version
-    attributes:
-      label: SQL Performance Studio Version
-      description: Check the About dialog or the release you downloaded.
-      placeholder: "e.g., 0.7.0"
-    validations:
-      required: true
-
-  - type: input
-    id: os-version
-    attributes:
-      label: Operating System
-      description: The OS where you're running the app.
-      placeholder: "e.g., Windows 11 23H2, macOS 15.3, Ubuntu 24.04"
-    validations:
-      required: true
-
-  - type: textarea
-    id: description
-    attributes:
-      label: Describe the Bug
-      description: A clear description of what the bug is.
-    validations:
-      required: true
-
-  - type: textarea
-    id: steps
-    attributes:
-      label: Steps to Reproduce
-      description: How can we reproduce this?
-      placeholder: |
-        1. Open a .sqlplan file
-        2. Click on...
-        3. See error
-    validations:
-      required: true
-
-  - type: textarea
-    id: expected
-    attributes:
-      label: Expected Behavior
-      description: What you expected to happen.
-    validations:
-      required: true
-
-  - type: textarea
-    id: actual
-    attributes:
-      label: Actual Behavior
-      description: What actually happened.
-    validations:
-      required: true
-
-  - type: textarea
-    id: plan-file
-    attributes:
-      label: Plan File
-      description: If applicable, attach or paste the .sqlplan file that triggers the issue. You can redact sensitive table/column names.
-    validations:
-      required: false
-
-  - type: textarea
-    id: screenshots
-    attributes:
-      label: Screenshots
-      description: If applicable, add screenshots to help explain the problem.
-    validations:
-      required: false
+name: Bug Report
+description: Report a problem with SQL Performance Studio
+title: "[BUG] "
+labels: ["bug"]
+
+body:
+  - type: dropdown
+    id: component
+    attributes:
+      label: Component
+      description: Which part of SQL Performance Studio is affected?
+      options:
+        - Desktop App (Windows)
+        - Desktop App (macOS)
+        - Desktop App (Linux)
+        - CLI Tool
+        - SSMS Extension
+    validations:
+      required: true
+
+  - type: input
+    id: version
+    attributes:
+      label: SQL Performance Studio Version
+      description: Check the About dialog or the release you downloaded.
+      placeholder: "e.g., 0.7.0"
+    validations:
+      required: true
+
+  - type: input
+    id: os-version
+    attributes:
+      label: Operating System
+      description: The OS where you're running the app.
+      placeholder: "e.g., Windows 11 23H2, macOS 15.3, Ubuntu 24.04"
+    validations:
+      required: true
+
+  - type: textarea
+    id: description
+    attributes:
+      label: Describe the Bug
+      description: A clear description of what the bug is.
+    validations:
+      required: true
+
+  - type: textarea
+    id: steps
+    attributes:
+      label: Steps to Reproduce
+      description: How can we reproduce this?
+      placeholder: |
+        1. Open a .sqlplan file
+        2. Click on...
+        3. See error
+    validations:
+      required: true
+
+  - type: textarea
+    id: expected
+    attributes:
+      label: Expected Behavior
+      description: What you expected to happen.
+    validations:
+      required: true
+
+  - type: textarea
+    id: actual
+    attributes:
+      label: Actual Behavior
+      description: What actually happened.
+    validations:
+      required: true
+
+  - type: textarea
+    id: plan-file
+    attributes:
+      label: Plan File
+      description: If applicable, attach or paste the .sqlplan file that triggers the issue. You can redact sensitive table/column names.
+    validations:
+      required: false
+
+  - type: textarea
+    id: screenshots
+    attributes:
+      label: Screenshots
+      description: If applicable, add screenshots to help explain the problem.
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/config.yml

@@ -1,5 +1,5 @@
-blank_issues_enabled: false
-contact_links:
-  - name: Questions & Discussion
-    url: https://github.com/erikdarlingdata/PerformanceStudio/discussions
-    about: Ask questions and discuss SQL Performance Studio with the community
+blank_issues_enabled: false
+contact_links:
+  - name: Questions & Discussion
+    url: https://github.com/erikdarlingdata/PerformanceStudio/discussions
+    about: Ask questions and discuss SQL Performance Studio with the community

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -1,50 +1,50 @@
-name: Feature Request
-description: Suggest a new feature or enhancement
-title: "[FEATURE] "
-labels: ["enhancement"]
-
-body:
-  - type: checkboxes
-    id: component
-    attributes:
-      label: Which component(s) does this affect?
-      options:
-        - label: Desktop App
-        - label: CLI Tool
-        - label: SSMS Extension
-        - label: Plan Analysis Rules
-        - label: Documentation
-    validations:
-      required: true
-
-  - type: textarea
-    id: problem
-    attributes:
-      label: Problem Statement
-      description: Describe the problem you're trying to solve or the limitation you're facing.
-    validations:
-      required: true
-
-  - type: textarea
-    id: solution
-    attributes:
-      label: Proposed Solution
-      description: Describe your proposed feature or enhancement.
-    validations:
-      required: true
-
-  - type: textarea
-    id: use-case
-    attributes:
-      label: Use Case
-      description: How would you use this feature? Provide a specific example.
-    validations:
-      required: true
-
-  - type: textarea
-    id: alternatives
-    attributes:
-      label: Alternatives Considered
-      description: Have you considered any alternative solutions or workarounds?
-    validations:
-      required: false
+name: Feature Request
+description: Suggest a new feature or enhancement
+title: "[FEATURE] "
+labels: ["enhancement"]
+
+body:
+  - type: checkboxes
+    id: component
+    attributes:
+      label: Which component(s) does this affect?
+      options:
+        - label: Desktop App
+        - label: CLI Tool
+        - label: SSMS Extension
+        - label: Plan Analysis Rules
+        - label: Documentation
+    validations:
+      required: true
+
+  - type: textarea
+    id: problem
+    attributes:
+      label: Problem Statement
+      description: Describe the problem you're trying to solve or the limitation you're facing.
+    validations:
+      required: true
+
+  - type: textarea
+    id: solution
+    attributes:
+      label: Proposed Solution
+      description: Describe your proposed feature or enhancement.
+    validations:
+      required: true
+
+  - type: textarea
+    id: use-case
+    attributes:
+      label: Use Case
+      description: How would you use this feature? Provide a specific example.
+    validations:
+      required: true
+
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternatives Considered
+      description: Have you considered any alternative solutions or workarounds?
+    validations:
+      required: false

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,25 +1,25 @@
-## What does this PR do?
-
-A clear description of the change and why it's being made.
-
-## Which component(s) does this affect?
-
-- [ ] Desktop App (PlanViewer.App)
-- [ ] Core Library (PlanViewer.Core)
-- [ ] CLI Tool (PlanViewer.Cli)
-- [ ] SSMS Extension (PlanViewer.Ssms)
-- [ ] Tests
-- [ ] Documentation
-
-## How was this tested?
-
-Describe the testing you've done. Include:
-- Plan files tested (estimated, actual, Query Store, etc.)
-- Platforms tested (Windows, macOS, Linux)
-
-## Checklist
-
-- [ ] I have read the [contributing guide](https://github.com/erikdarlingdata/PerformanceStudio/blob/main/CONTRIBUTING.md)
-- [ ] My code builds with zero warnings (`dotnet build -c Debug`)
-- [ ] All tests pass (`dotnet test`)
-- [ ] I have not introduced any hardcoded credentials or server names
+## What does this PR do?
+
+A clear description of the change and why it's being made.
+
+## Which component(s) does this affect?
+
+- [ ] Desktop App (PlanViewer.App)
+- [ ] Core Library (PlanViewer.Core)
+- [ ] CLI Tool (PlanViewer.Cli)
+- [ ] SSMS Extension (PlanViewer.Ssms)
+- [ ] Tests
+- [ ] Documentation
+
+## How was this tested?
+
+Describe the testing you've done. Include:
+- Plan files tested (estimated, actual, Query Store, etc.)
+- Platforms tested (Windows, macOS, Linux)
+
+## Checklist
+
+- [ ] I have read the [contributing guide](https://github.com/erikdarlingdata/PerformanceStudio/blob/main/CONTRIBUTING.md)
+- [ ] My code builds with zero warnings (`dotnet build -c Debug`)
+- [ ] All tests pass (`dotnet test`)
+- [ ] I have not introduced any hardcoded credentials or server names