ci: avoid redundant dashboard builds

[ScriptedAlchemy]

Summary

• remove duplicate dashboard Node setup/build steps from Rust test, Clippy, and Hermes integration jobs
• keep dashboard asset build, dist verification, unit tests, integration tests, and smoke tests in the dedicated Dashboard job
• disable debug info for CI dev/test profiles to reduce compile/link work, especially on Windows

Validation

• python3 YAML parse for .github/workflows/ci.yml
• git diff --check

[changeset-bot]

⚠️ No Changeset found

Latest commit: dbc9df2

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[chatgpt-codex-connector]

💡 Codex Review

tracedecay/.github/workflows/ci.yml

Lines 55 to 56 in dbc9df2

	- name: Run tests
	run: cargo test --workspace

Restore pinned Node setup before Cargo builds

In these Rust jobs, a fresh checkout still reaches build.rs when cargo test/cargo clippy/cargo build starts; the dashboard JS/CSS dist files are gitignored, and build.rs detects them as missing then runs npm ci and npm run build (build.rs:263-273, build.rs:125-134). Because this change removed actions/setup-node from those jobs without sharing the Dashboard job’s generated dist artifacts across job workspaces, they now rebuild the dashboard using whatever npm happens to be on the runner PATH, losing the pinned Node 22 setup/cache and making the CI path slower and less deterministic rather than avoiding redundant builds.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".