Fix asset loading by deploying from Dioxus build output

The previous workflow was using 'mv dist/public/* dist' which didn't
properly preserve the directory structure, causing assets to fail loading.

Now deploying directly from target/dx/.../release/web/public which:
- Preserves the correct assets/ and wasm/ directory structure
- Eliminates file moving operations that could fail
- Uses Dioxus's standard build output location

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

Author: mxgordon

.github/workflows/gh-pages-deploy.yml

@@ -45,20 +45,19 @@ jobs:
 
       - name: Build with Dioxus CLI
         run: |
-          dx bundle --release --out-dir dist
-          mv dist/public/* dist
-          cp dist/index.html dist/404.html
+          dx bundle --release
+          cp target/dx/mxgordon-github-io/release/web/public/index.html target/dx/mxgordon-github-io/release/web/public/404.html
 
       - name: Copy CNAME for custom domain
-        run: cp CNAME dist/
+        run: cp CNAME target/dx/mxgordon-github-io/release/web/public/
 
       - name: Setup Pages
         uses: actions/configure-pages@v5
 
       - name: Upload artifact
         uses: actions/upload-pages-artifact@v3
         with:
-          path: './dist'
+          path: './target/dx/mxgordon-github-io/release/web/public'
 
       - name: Deploy to GitHub Pages 🚀
         id: deployment