feat: WSL2 Strix Halo performance optimization suite

.claude/commands/create-issue.md

@@ -0,0 +1,110 @@
+# Create GitHub Issue
+
+Create a GitHub issue for tracking a feature or bug fix (required before submitting PR to Microsoft repos).
+
+## Process
+
+### 1. Determine Issue Type
+
+Ask the user:
+- **Feature Request**: New functionality
+- **Bug Fix**: Fixing broken behavior
+- **Performance**: Optimization work
+- **Documentation**: Doc improvements
+
+### 2. Search for Duplicates
+
+```bash
+# Search existing issues
+gh issue list --repo microsoft/WSL --state all --search "<keywords>" --limit 20
+```
+
+If duplicates found, ask user whether to:
+- Comment on existing issue instead
+- Proceed with new issue (explain differences)
+
+### 3. Generate Issue Content
+
+#### For Feature Requests:
+```markdown
+## Feature Description
+[Clear description of the proposed feature]
+
+## Motivation
+[Why this feature is needed - what problem does it solve?]
+
+## Proposed Solution
+[High-level approach to implementation]
+
+## Alternatives Considered
+[Other approaches that were considered]
+
+## Additional Context
+[Any other relevant information, benchmarks, etc.]
+```
+
+#### For Bug Fixes:
+```markdown
+## Bug Description
+[Clear description of the bug]
+
+## Steps to Reproduce
+1. [Step 1]
+2. [Step 2]
+3. [Observe issue]
+
+## Expected Behavior
+[What should happen]
+
+## Actual Behavior
+[What actually happens]
+
+## Environment
+- Windows Version:
+- WSL Version:
+- Distribution:
+
+## Additional Context
+[Logs, screenshots, etc.]
+```
+
+#### For Performance Issues:
+```markdown
+## Performance Issue
+[Description of the performance problem]
+
+## Current Behavior
+[Current performance metrics]
+
+## Expected/Desired Performance
+[Target performance goals]
+
+## Proposed Optimization
+[Approach to improve performance]
+
+## Benchmarks
+[Before/after measurements if available]
+
+## Environment
+- Hardware:
+- Windows Version:
+- WSL Version:
+```
+
+### 4. Create the Issue
+
+```bash
+gh issue create --repo microsoft/WSL \
+  --title "<concise title>" \
+  --body "<generated content>"
+```
+
+### 5. Return Issue Number
+
+Save the issue number for use in PR creation:
+```
+Created issue #XXX: <title>
+Use this issue number when creating your PR.
+```
+
+$ARGUMENTS

.claude/commands/pr-workflow.md

@@ -0,0 +1,112 @@
+# PR Workflow
+
+Create a pull request following Microsoft's contribution guidelines.
+
+## Required Steps
+
+Before creating the PR, you MUST complete these steps in order:
+
+### Step 1: Search for Related PRs and Issues
+
+Search GitHub for existing PRs and issues related to the changes:
+
+```bash
+# Search for related open PRs
+gh pr list --repo microsoft/WSL --state open --search "<keywords from changes>"
+
+# Search for related closed PRs (to avoid duplicates)
+gh pr list --repo microsoft/WSL --state closed --search "<keywords from changes>" --limit 10
+
+# Search for related issues
+gh issue list --repo microsoft/WSL --state all --search "<keywords from changes>" --limit 10
+```
+
+Report findings to the user:
+- List any related open PRs (potential conflicts or duplicates)
+- List any related closed PRs (prior art, rejected approaches)
+- List any related issues (link these in the PR)
+
+If duplicates or conflicts are found, STOP and ask the user how to proceed.
+
+### Step 2: Verify CLA Status
+
+Inform the user:
+- Microsoft requires a Contributor License Agreement (CLA)
+- A bot will automatically prompt when the PR is created
+- One-time signing process at https://cla.microsoft.com
+
+### Step 3: Check for Required Issue
+
+Ask the user:
+- "Do you have a GitHub issue filed for this change?"
+- If not, offer to help create one first (required by Microsoft guidelines)
+
+### Step 4: Validate Changes
+
+Run pre-PR validation:
+
+```bash
+# Check for uncommitted changes
+git status
+
+# Verify branch is up to date with upstream
+git fetch origin
+git log HEAD..origin/main --oneline
+
+# Run code formatting check
+clang-format --dry-run --style=file $(git diff --name-only HEAD~1 | grep -E '\.(cpp|c|h)$') 2>/dev/null || echo "No C/C++ files to check"
+
+# Validate copyright headers
+python3 tools/devops/validate-copyright-headers.py 2>/dev/null || echo "Copyright validation skipped"
+```
+
+### Step 5: Generate PR Description
+
+Create a PR description following this template:
+
+```markdown
+## Summary
+[One paragraph describing what this PR does and why]
+
+## Related Issue
+Fixes #XXX (or "Related to #XXX")
+
+## Changes
+- [Bullet point list of key changes]
+
+## Testing
+- [How the changes were tested]
+- [Benchmark results if performance-related]
+
+## Checklist
+- [ ] Code follows project style guidelines
+- [ ] Changes have been tested locally
+- [ ] Documentation updated (if applicable)
+- [ ] No breaking changes (or documented if unavoidable)
+
+## Screenshots/Benchmarks
+[If applicable]
+```
+
+### Step 6: Create the PR
+
+```bash
+gh pr create --repo microsoft/WSL \
+  --title "<concise title>" \
+  --body "<generated description>" \
+  --base main
+```
+
+### Step 7: Post-Creation Checklist
+
+After PR is created:
+1. Verify CLA bot has commented
+2. Check automated validation status
+3. Respond to any bot feedback
+4. Share PR URL with user
+
+## Usage
+
+When the user asks to create a PR, run through ALL steps above. Do not skip the search for related PRs - this is critical to avoid duplicate work and conflicts.
+
+$ARGUMENTS

.claude/commands/search-related-prs.md

@@ -0,0 +1,76 @@
+# Search Related PRs
+
+Search for existing PRs and issues related to current changes before submitting new work.
+
+## Process
+
+### 1. Analyze Current Changes
+
+First, understand what's being changed:
+
+```bash
+# Get list of changed files
+git diff --name-only HEAD~1
+
+# Get commit messages on current branch
+git log origin/main..HEAD --oneline
+
+# Summarize the changes
+git diff --stat HEAD~1
+```
+
+Extract keywords from:
+- File paths (e.g., "plan9", "networking", "init")
+- Commit messages
+- Function/class names modified
+
+### 2. Search Open PRs
+
+```bash
+# Search by keywords
+gh pr list --repo microsoft/WSL --state open --search "<keyword1> <keyword2>"
+
+# Search by file paths
+gh pr list --repo microsoft/WSL --state open --search "path:<directory>"
+```
+
+### 3. Search Closed PRs
+
+```bash
+# Recent closed PRs with similar keywords
+gh pr list --repo microsoft/WSL --state closed --search "<keywords>" --limit 20
+
+# Check if similar changes were rejected
+gh pr list --repo microsoft/WSL --state closed --label "won't fix" --search "<keywords>"
+```
+
+### 4. Search Issues
+
+```bash
+# Open issues that might be addressed by these changes
+gh issue list --repo microsoft/WSL --state open --search "<keywords>"
+
+# Closed issues for context
+gh issue list --repo microsoft/WSL --state closed --search "<keywords>" --limit 10
+```
+
+### 5. Report Findings
+
+Provide a summary table:
+
+| Type | # Found | Action Needed |
+|------|---------|---------------|
+| Open PRs (related) | X | Review for conflicts |
+| Closed PRs (similar) | X | Check rejection reasons |
+| Open Issues | X | Link in new PR |
+| Closed Issues | X | Reference if relevant |
+
+### 6. Recommendations
+
+Based on findings, recommend:
+- **Proceed**: No conflicts found
+- **Coordinate**: Related open PR exists, consider collaborating
+- **Reconsider**: Similar PR was rejected, review reasons
+- **Link Issues**: Found issues that should be referenced
+
+$ARGUMENTS

.gitignore

@@ -65,4 +65,26 @@ package/x64
 /appx-logs.txt
 tools/clang-format.exe
 /linux-crashes
-doc/site/
+doc/site/
+
+# Strix-turbo build artifacts and temp files
+tools/strix-turbo/test_bug
+tools/strix-turbo/parasitic_batch/bench_parasitic
+tools/strix-turbo/parasitic_batch/test_parasitic
+tools/strix-turbo/dxgkrnl-dkms-temp/
+tools/strix-turbo/kernel-build-ubuntu-hwe/
+tools/strix-turbo/wsl2-kernel-staging/
+tools/strix-turbo/wsl2-kernel-temp/
+tools/strix-turbo/logs/
+kernel-build.log
+
+# IDE and editor files
+WSL.code-workspace
+.claude/
+
+# Blog/social media drafts (not source)
+doc/docs/blog-medium-wsl2-performance.md
+doc/docs/linkedin-post-wsl2.md
+
+# Misc
+nul