[BUG] ARM64 platform binaries missing for latest @ruvector/attention and @ruvector/gnn releases

[proffesor-for-testing]

Problem

ARM64 platform binaries are not published in sync with main package releases for @ruvector/attention and @ruvector/gnn. This causes installation failures on ARM64 Linux systems (e.g., GitHub Codespaces, Docker DevContainers on M1/M2 Macs, AWS Graviton).

Error Message

When installing @agentic-qe/v3 which depends on @ruvector/attention@^0.1.4:

Error: Cannot find module '@ruvector/attention-linux-arm64-gnu'
Require stack:
- /workspaces/project/node_modules/@ruvector/attention/index.js

Version Analysis

@ruvector/attention

Version	Main Package	linux-arm64-gnu	darwin-arm64
0.1.4	✅ Published	❌ Missing	❌ Missing
0.1.3	✅ Published	✅ Published	✅ Published
0.1.2	✅ Published	❌ Missing	❌ Missing
0.1.1	✅ Published	✅ Published	✅ Published
0.1.0	✅ Published	✅ Published	✅ Published

@ruvector/gnn

Version	Main Package	linux-arm64-gnu	darwin-arm64
0.1.22	✅ Published	❌ Missing	❌ Missing
0.1.21	✅ Published	❌ Missing	❌ Missing
0.1.19	✅ Published	✅ Published	✅ Published
0.1.18	✅ Published	❌ Missing	❌ Missing
0.1.17	✅ Published	❌ Missing	❌ Missing
0.1.15	✅ Published	✅ Published	✅ Published

Root Cause

Looking at the CI/CD workflows (build-attention.yml, build-gnn.yml), ARM64 builds are configured in the matrix:

matrix:
  settings:
    - host: ubuntu-22.04
      target: aarch64-unknown-linux-gnu
      platform: linux-arm64-gnu

However, the publish steps may not be triggering correctly for all releases:

• build-attention.yml: Commits binaries only on workflow_dispatch or push to main (not tags)
• build-gnn.yml: Publishes only when inputs.publish == true or on version tags

This means ARM64 binaries may be built but not published to npm when version bumps happen.

Impact

• Agentic QE v3 fails to start MCP server on ARM64 Linux
• GitHub Codespaces users cannot use the package
• Docker DevContainers on Apple Silicon fail
• AWS Graviton and other ARM64 cloud instances affected

Requested Fix

Option 1: Publish missing ARM64 binaries (immediate)

Manually trigger the workflows to build and publish ARM64 binaries for:

• @ruvector/attention@0.1.4
• @ruvector/gnn@0.1.20, 0.1.21, 0.1.22

Option 2: Fix CI/CD for future releases (long-term)

Ensure ARM64 platform packages are published whenever the main package is published:

• Add ARM64 binaries to the same publish workflow as main package
• Or ensure workflow_dispatch is run after each release
• Consider atomic publishing of all platform packages together

Option 3: WASM fallback (alternative)

Provide guidance on using WASM packages as a fallback:

• @ruvector/attention-unified-wasm (0.1.29 available)
• @ruvector/gnn-wasm (0.1.0 available)

Environment

• Platform: ARM64 Linux (aarch64-unknown-linux-gnu)
• Node.js: 20.x
• OS: Ubuntu 22.04 in Docker/Codespaces
• Package versions needed:
  • @ruvector/attention@0.1.4
  • @ruvector/gnn@0.1.22
  • @ruvector/sona@0.1.5 (this one works - ARM64 binary published)

Workaround (temporary)

Until fixed, users can:

1. Pin to older versions with ARM64 support:

   "@ruvector/attention": "0.1.3",
   "@ruvector/gnn": "0.1.19"

2. Use WASM packages if feature-compatible
3. Use x86_64 emulation (slower)

[proffesor-for-testing]

Additional finding: The ARM64 binary packages exist on npm but are NOT listed in the main package's optionalDependencies:

@ruvector/attention@0.1.3 optionalDependencies:
- @ruvector/attention-darwin-x64
- @ruvector/attention-linux-x64-gnu  
- @ruvector/attention-win32-x64-msvc
(Missing: darwin-arm64, linux-arm64-gnu)

Compare to gnn which correctly includes ARM64:

@ruvector/gnn@0.1.19 optionalDependencies:
- @ruvector/gnn-darwin-x64
- @ruvector/gnn-darwin-arm64 ✓
- @ruvector/gnn-linux-x64-gnu
- @ruvector/gnn-linux-arm64-gnu ✓
- ...

The fix needed: Update npm/packages/attention/package.json to add:

"optionalDependencies": {
  "@ruvector/attention-darwin-arm64": "0.1.3",
  "@ruvector/attention-linux-arm64-gnu": "0.1.3",
  ...
}