[pull] main from imazen:main

.cargo/codelldb.sh

@@ -0,0 +1,2 @@
+#!/bin/bash
+code --open-url "vscode://vadimcn.vscode-lldb/launch/command?LD_LIBRARY_PATH=$LD_LIBRARY_PATH&$*"

.cargo/config.toml

@@ -0,0 +1,13 @@
+
+# ring isn't even supposed to be compiled - it's not in cargo tree -
+# but we can't build unless ring can find llvm/cland and it's terrible at finding it
+# ring is the one project with a worse build system than openssl...
+# Might replace reqwest with shelling out to wget for unit test fixtures instead.
+[env]
+PATH = { value = "C:\\Program Files\\Microsoft Visual Studio\\2022\\Community\\VC\\Tools\\Llvm\\ARM64\\bin;${PATH}", relative = false }
+
+#[target.x86_64-unknown-linux-gnu]
+#runner = ".cargo/codelldb.sh"
+
+#finds the current target triple
+#rustc -vV | sed -n 's|host: ||p' 

.cursor/rules/bash.mdc

@@ -0,0 +1,58 @@
+---
+description: Rules for working on bash scripts and their tests
+globs: *.sh, *.yml
+---
+# Goal: Enforce cross-platform bash script guidelines
+# Reasoning:
+#   1. We want all .sh scripts to work with Bash 3.2 on macOS, Git Bash on Windows, WSL2, Ubuntu 22–24. cygpath is never available.
+#   2. We need to ensure each .sh script has a corresponding test_ script. test_scripts should create a unique directory to contain all their filesystem work, remove it on pass/fail, and restore the current directory and env vars to what they were before it ran.
+#   3. For Windows, we assume a fresh install with only Git available; use powershell.exe if needed (no pwsh).
+#   4. Powershell automatically handles slash conversions, but /c/ must become C:/. Create tests for powershell files
+#   5. Use set -e and set -o pipefail for bash. Avoid silent failure. 
+#   6. For both powerhshell files and bash files, use functions and DRY things as much as possible. 
+#   7. Add verification checks for all inputs, whether files, dirs, or variables, and make contractual boundaries and division of responsibility clear.
+
+<rule>
+name: cross_platform_bash_scripts
+description: Ensures that all bash scripts are cross-platform compatible and have matching test scripts
+filters:
+  # Match any .sh file outside of test_ prefixed scripts
+  - type: file_extension
+    pattern: "\\.sh$"
+  - type: filename
+    pattern: "^(?!test_).+\\.sh$"
+
+actions:
+  - type: reject
+    conditions:
+      # Reject any .sh file without a matching test_ script of the same name
+      - pattern: "^(?!test_)(.+)\\.sh$"
+        message: |
+          Found a bash script without a corresponding test script. 
+          Please add a test_ script to ensure thorough testing across platforms.
+
+  - type: suggest
+    message: |
+      Ensure compatibility with:
+      • Bash 3.2 on macOS
+      • Git Bash on Windows (use powershell.exe where appropriate)
+      • WSL2
+      • Ubuntu 22–24
+      • x64 and arm64 architectures
+      Please provide a test_ script that verifies the script on each platform.
+      Use set -e and set -o pipefail for bash
+      For both powerhshell files and bash files, use functions and DRY things as much as possible. 
+      Add verification checks for all inputs, whether files, dirs, or variables, and make contractual boundaries and division of responsibility clear. 
+examples:
+  - input: |
+      # Good scenario:
+      build.sh and test_build.sh
+      deploy.sh and test_deploy.sh
+
+      # Bad scenario:
+      build.sh (no test script)
+    output: "All .sh files have matching test_ scripts for cross-platform testing"
+metadata:
+  priority: high
+  version: 1.0
+</rule>

.cursor/rules/creating-rules.mdc

@@ -0,0 +1,75 @@
+---
+description: Cursor Rules Location
+globs: *.mdc
+---
+# Cursor Rules Location
+
+Rules for placing and organizing Cursor rule files in the repository.
+
+<rule>
+name: cursor_rules_location
+description: Standards for placing Cursor rule files in the correct directory
+filters:
+  # Match any .mdc files
+  - type: file_extension
+    pattern: "\\.mdc$"
+  # Match files that look like Cursor rules
+  - type: content
+    pattern: "(?s)<rule>.*?</rule>"
+  # Match file creation events
+  - type: event
+    pattern: "file_create"
+
+actions:
+  - type: reject
+    conditions:
+      - pattern: "^(?!\\.\\/\\.cursor\\/rules\\/.*\\.mdc$)"
+        message: "Cursor rule files (.mdc) must be placed in the .cursor/rules directory"
+
+  - type: suggest
+    message: |
+      When creating Cursor rules:
+
+      1. Always place rule files in PROJECT_ROOT/.cursor/rules/:
+         ```
+         .cursor/rules/
+         ├── your-rule-name.mdc
+         ├── another-rule.mdc
+         └── ...
+         ```
+
+      2. Follow the naming convention:
+         - Use kebab-case for filenames
+         - Always use .mdc extension
+         - Make names descriptive of the rule's purpose
+
+      3. Directory structure:
+         ```
+         PROJECT_ROOT/
+         ├── .cursor/
+         │   └── rules/
+         │       ├── your-rule-name.mdc
+         │       └── ...
+         └── ...
+         ```
+
+      4. Never place rule files:
+         - In the project root
+         - In subdirectories outside .cursor/rules
+         - In any other location
+
+examples:
+  - input: |
+      # Bad: Rule file in wrong location
+      rules/my-rule.mdc
+      my-rule.mdc
+      .rules/my-rule.mdc
+
+      # Good: Rule file in correct location
+      .cursor/rules/my-rule.mdc
+    output: "Correctly placed Cursor rule file"
+
+metadata:
+  priority: high
+  version: 1.0
+</rule>

.cursor/rules/git-commits.mdc

@@ -0,0 +1,75 @@
+---
+description: Git Conventional Commits
+globs: 
+---
+Rule for automatically committing changes made by CursorAI using conventional commits format.
+
+<rule>
+name: conventional_commits
+description: Automatically commit changes made by CursorAI using conventional commits format
+filters:
+  - type: event
+    pattern: "build_success"
+  - type: file_change
+    pattern: "*"
+
+actions:
+  - type: execute
+    command: |
+      # Extract the change type and scope from the changes
+      CHANGE_TYPE=""
+      case "$CHANGE_DESCRIPTION" in
+        *"add"*|*"create"*|*"implement"*) CHANGE_TYPE="feat";;
+        *"fix"*|*"correct"*|*"resolve"*) CHANGE_TYPE="fix";;
+        *"refactor"*|*"restructure"*) CHANGE_TYPE="refactor";;
+        *"test"*) CHANGE_TYPE="test";;
+        *"doc"*|*"comment"*) CHANGE_TYPE="docs";;
+        *"style"*|*"format"*) CHANGE_TYPE="style";;
+        *"perf"*|*"optimize"*) CHANGE_TYPE="perf";;
+        *) CHANGE_TYPE="chore";;
+      esac
+
+      # Extract scope from file path
+      SCOPE=$(dirname "$FILE" | tr '/' '-')W
+
+      # Commit the changes
+      git add "$FILE"
+      git commit -m "$CHANGE_TYPE($SCOPE): $CHANGE_DESCRIPTION"
+
+  - type: suggest
+    message: |
+      Changes should be committed using conventional commits format:
+
+      Format: <type>(<scope>): <description>
+
+      Types:
+      - feat: A new feature
+      - fix: A bug fix
+      - docs: Documentation only changes
+      - style: Changes that do not affect the meaning of the code
+      - refactor: A code change that neither fixes a bug nor adds a feature
+      - perf: A code change that improves performance
+      - test: Adding missing tests or correcting existing tests
+      - chore: Changes to the build process or auxiliary tools
+
+      The scope should be derived from the file path or affected component.
+      The description should be clear and concise, written in imperative mood.
+      For anything in .github or ci folders, (ci) is the correct scope.
+
+examples:
+  - input: |
+      # After adding a new function
+      CHANGE_DESCRIPTION="add user authentication function"
+      FILE="src/auth/login.ts"
+    output: "feat(src-auth): add user authentication function"
+
+  - input: |
+      # After fixing a bug
+      CHANGE_DESCRIPTION="fix incorrect date parsing"
+      FILE="lib/utils/date.js"
+    output: "fix(lib-utils): fix incorrect date parsing"
+
+metadata:
+  priority: high
+  version: 1.0
+</rule>

.cursor/rules/rust.mdc

@@ -0,0 +1,4 @@
+---
+description: Run cargo fmt after making changes 
+globs: *.rs
+---

.github/actions/install-nasm/action.yml

@@ -0,0 +1,33 @@
+name: 'Install NASM'
+description: 'Install NASM (Netwide Assembler) on various platforms'
+runs:
+  using: "composite"
+  steps:
+    - name: Install NASM on macOS
+      if: runner.os == 'macOS'
+      shell: bash
+      run: brew install nasm
+
+    - name: Install NASM on Ubuntu
+      if: runner.os == 'Linux'
+      shell: bash
+      run: sudo apt-get install -y nasm || sudo apt-get update && sudo apt-get install -y nasm
+
+    - name: Install NASM on Windows
+      if: runner.os == 'Windows'
+      shell: powershell
+      run: |
+        try {
+          winget install NASM.NASM --accept-source-agreements --accept-package-agreements
+        } catch {
+          Write-Host "Winget installation failed, falling back to manual installation"
+          $url = "https://www.nasm.us/pub/nasm/releasebuilds/2.16.03/win64/nasm-2.16.03-installer-x64.exe"
+          Invoke-WebRequest -Uri $url -OutFile nasminst.exe
+          Start-Process -FilePath .\nasminst.exe -ArgumentList "/S" -Wait
+        }
+        echo "C:\Program Files\NASM" | Out-File -FilePath $env:GITHUB_PATH -Encoding utf8 -Append
+        echo "C:\Program Files (x86)\NASM" | Out-File -FilePath $env:GITHUB_PATH -Encoding utf8 -Append
+
+    - name: Print installed NASM version
+      shell: bash
+      run: nasm -v

.github/actions/setup-git-win-arm64/action.yml

@@ -0,0 +1,53 @@
+name: 'Setup Git for Windows ARM64'
+description: 'Set up Git for Windows ARM64 environment with necessary tools'
+# maybe switch to winget someday?
+# Add-AppxPackage -RegisterByFamilyName -MainPackage Microsoft.DesktopAppInstaller_8wekyb3d8bbwe
+runs:
+  using: "composite"
+  steps:
+
+    - name: Check if Git is installed, returning step variable
+      shell: powershell
+      id: git-installed
+      run: |
+        if (Test-Path "C:\Program Files\Git\bin\git.exe") {
+          Write-Host "Git is already installed. Skipping installation."
+          echo "git-installed=true" | Out-File -FilePath $env:GITHUB_OUTPUT -Encoding utf8 -Append
+        } else {
+          Write-Host "Git is not installed"
+          echo "git-installed=false" | Out-File -FilePath $env:GITHUB_OUTPUT -Encoding utf8 -Append
+        }
+
+
+    - name: Install Git
+      shell: powershell
+      run: |
+        echo "Installing Git"
+        $url = "https://github.com/git-for-windows/git/releases/download/v2.47.1.windows.2/Git-2.47.1.2-arm64.exe"
+        Invoke-WebRequest -Uri $url -OutFile git-installer.exe
+        Start-Process -FilePath .\git-installer.exe -ArgumentList "/VERYSILENT", "/NORESTART" -Wait
+      if: steps.git-installed.outputs.git-installed == 'false'
+
+
+    - name: Add Git and GNU tools (required for actions/cache to work (tar is needed)) to PATH
+      shell: powershell
+      run: |
+        echo "C:\Program Files\Git\usr\bin" | Out-File -FilePath $env:GITHUB_PATH -Encoding utf8 -Append
+        echo "C:\Program Files\Git\bin" | Out-File -FilePath $env:GITHUB_PATH -Encoding utf8 -Append
+        ls "C:\Program Files\Git\bin\"
+
+
+    - name: Verify Git and Bash are in PATH
+      shell: powershell
+      run: |
+        echo "PATH: $env:PATH"
+        echo "git --version"
+        git --version
+        echo "bash --version"
+        bash --version
+
+    - name: Verify bash steps now work
+      shell: bash
+      run: |
+        echo "shell: bash works"
+

.github/actions/setup-win-arm64/action.yml

@@ -0,0 +1,67 @@
+name: 'Setup Windows ARM64'
+description: 'Set up Windows ARM64 environment with necessary tools'
+# maybe switch to winget someday?
+# Add-AppxPackage -RegisterByFamilyName -MainPackage Microsoft.DesktopAppInstaller_8wekyb3d8bbwe
+runs:
+  using: "composite"
+  steps:
+    # - name: Cache tools
+    #   uses: actions/cache@v4
+    #   id: cache-tools
+    #   with:
+    #     path: |
+    #       C:\Users\runneradmin\.rustup
+    #       C:\Users\runneradmin\.cargo
+    #     key: ${{ runner.os }}-arm64-tools-v3
+
+    - name: Setup Git
+      uses: ./.github/actions/setup-git-win-arm64
+
+    - name: Install Visual Studio Build Tools (Preview)
+      shell: powershell
+      run: |
+        $url = "https://aka.ms/vs/17/release/vs_buildtools.exe"
+        Invoke-WebRequest -Uri $url -OutFile vs_buildtools.exe
+        Start-Process -FilePath .\vs_buildtools.exe -ArgumentList "--quiet", "--wait", "--norestart", "--nocache", `
+          "--installPath", "C:\BuildTools", `
+          "--channelUri", "https://aka.ms/vs/17/pre/channel", ` #https://aka.ms/vs/17/release/channel
+          "--add", "Microsoft.VisualStudio.Component.VC.Tools.ARM64", `
+          "--add", "Microsoft.VisualStudio.Component.Windows11SDK.22621" `
+          -NoNewWindow -Wait
+
+    - name: Install Rust
+      shell: powershell
+      run: |
+        $url = "https://static.rust-lang.org/rustup/dist/aarch64-pc-windows-msvc/rustup-init.exe"
+        Invoke-WebRequest -Uri $url -OutFile rustup-init.exe
+        .\rustup-init.exe -y --default-host aarch64-pc-windows-msvc --profile minimal
+
+
+    - name: Install NASM
+      uses: ./.github/actions/install-nasm
+
+    - name: List tool directories
+      shell: powershell
+      run: |
+        echo listing tool directories
+        ls "C:\BuildTools\Common7\Tools\"
+        ls "C:\Program Files\Git\bin\"
+        ls "C:\BuildTools\VC\Tools\MSVC\"
+        ls "C:\Program Files (x86)\Windows Kits\10\include\"
+        ls "C:\Program Files (x86)\Windows Kits\10\include\10.0.22621.0\ucrt"
+    - name: Adding tools to PATH/INCLUDE/LIB/LIBPATH
+      shell: powershell
+      env:
+        msvc_ver: "14.43.34618"
+        sdk_ver: "10.0.22621.0"
+
+      run: |
+        echo "Adding tools to PATH"
+        echo "C:\BuildTools\Common7\Tools"  | Out-File -FilePath $env:GITHUB_PATH -Encoding utf8 -Append
+        echo "C:\BuildTools\VC\Tools\MSVC\$msvc_ver\bin\Hostx64\arm64" | Out-File -FilePath $env:GITHUB_PATH -Encoding utf8 -Append
+        echo "C:\BuildTools\VC\Tools\MSVC\$msvc_ver\bin\Hostx64\x64" | Out-File -FilePath $env:GITHUB_PATH -Encoding utf8 -Append
+        echo "$env:USERPROFILE\.cargo\bin" | Out-File -FilePath $env:GITHUB_PATH -Encoding utf8 -Append
+        echo "Setting up INCLUDE, LIB, LIBPATH environment variables"
+        echo "INCLUDE=C:\BuildTools\VC\Tools\MSVC\$msvc_ver\include;C:\Program Files (x86)\Windows Kits\10\include\$sdk_ver\ucrt" | Out-File -FilePath $env:GITHUB_ENV -Encoding utf8 -Append
+        echo "LIB=C:\BuildTools\VC\Tools\MSVC\$msvc_ver\lib\arm64;C:\Program Files (x86)\Windows Kits\10\lib\$sdk_ver\ucrt\arm64" | Out-File -FilePath $env:GITHUB_ENV -Encoding utf8 -Append
+        echo "LIBPATH=C:\BuildTools\VC\Tools\MSVC\$msvc_ver\lib\arm64" | Out-File -FilePath $env:GITHUB_ENV -Encoding utf8 -Append