ci(release): upload artifacts before alias sync

[cursor]

Summary

• Move GitHub release artifact upload before auxiliary alias-package synchronization.
• Keep alias sync strict after primary binaries are already attached to the GitHub Release.

Linked Artifacts

• Issue: n/a
• ADR: n/a
• OpenSpec: openspec/changes/fix-release-artifacts-before-alias-sync
• Discussion: n/a

Validation

• bun run memory:check
• bun run lint
• bun run format:check
• bun run typecheck
• bun run test (if behavior changed)
• Not run, explained below

bun run test was not run because this PR only changes GitHub Actions release step ordering and OpenSpec release-workflow documentation; it does not change CLI runtime behavior or a unit-testable TypeScript path.

Additional validation:

• bun run openspec:validate

Release Intent

• Release: not applicable - process-only release workflow ordering fix

Docs Updated

• Not needed
• docs/...
• openspec/...
• Follow-up issue or OpenSpec change created instead

Scope Check

• I did not add a new ad hoc root-level Markdown file.
• I updated the relevant issue, ADR, spec, runbook, or captured the missing doc work as follow-up.
• I did not silently expand project scope without recording it explicitly.

Closure Check

• Working tree was clean after commit.
• Branch was pushed and this PR is the active delivery artifact.
• OpenSpec change is not needed, still active by design until merge, already archived, or queued for agent-driven archive closure.
• Release is not applicable, delegated to release automation, or verified.

Notes

Verification on current origin/main showed Sync quantex alias package runs before Upload release artifacts. A failing alias sync could therefore stop the job after npm publish but before GitHub release binaries are uploaded.