Files
meshcore-analyzer/.github/workflows
n30nex 4ea80da234 ci: run JavaScript unit tests before backend validation (#2322)
Fixes #2317. Partial follow-up to #1995.

JavaScript assertion failures currently reach their unit gate only after
the Go validation work. Move the existing `Run JS unit tests` step
directly after Go setup, before gofmt/vet and backend builds/tests.
Failed unit checks then stop later work under the existing default
failure behavior.

This is an exact three-line block relocation within the same job. Its
command remains `sh test-all.sh`. All ten jobs, twenty step
bodies/options/conditions, other step ordering, dependencies, security
checks, coverage outputs and publication gates are unchanged. No new
job, package, timeout, cache or application setting.

Validation: dependency audit found no need for prior Go outputs. All 218
standalone suites passed with no checkout build artifacts or external
Node packages, after earlier shared Go tests had finished and cleaned
up. The parent reran the suite, parsed-workflow equivalence checks and
browser smoke. The unchanged backend tree passed both full backend
suites.

TDD exemption: configuration-only; no test files modified, and CI is
green without test edits. Three independent reviews passed. [Final-head
CI](https://github.com/Kpa-clawbot/CoreScope/actions/runs/40238885639)
confirms the unit step precedes Go validation; backend checks, all
browser shards and architecture builds passed. No numerical speedup or
successful-pipeline duration claim is made.
2026-10-26 15:40:11 +01:00
..