v4.1.0

fix(monorepo-third-pkg): v4.1.0 hotfix #2 — workflow build order: typecheck → build → test

CI run https://github.com/StoaChain/stoa-js/actions/runs/25502329229 (the
hotfix #1 retry) cleared the ERESOLVE blocker but failed at the next step:
"Typecheck + Test + Build (all 3 packages)" hit ERR_MODULE_NOT_FOUND on
all stoa-core test files trying to resolve @stoachain/kadena-stoic- legacy/{client,cryptography-utils,hd-wallet,hd-wallet/chainweaver}. Root
cause: the workflow ran npm test BEFORE npm run build, but stoa-core's
vitest config has no resolve.alias for kadena-stoic-legacy (the
documented Phase 4 T4.4 architectural deviation — vendored CJS source
layout is incompatible with vitest's transform), so Node's standard
module resolution flows via the kadena-stoic-legacy package's exports
map → dist/*/index.js. On a fresh CI checkout the dist/ tree doesn't
exist until the build step creates it.

Locally this was masked because dist/ was always present from prior
build runs across Phase 3 T3.8 / Phase 4 T4.6 / Phase 5 T5.6 / Phase 7
T7.16 verifications.

Fix: reorder the workflow's verification step from typecheck → test → build to typecheck → build → test. Build must precede test on a fresh
checkout. Step renamed accordingly.

This is the second of two hotfixes layered on top of the v4.1.0 atomic-
triplet ship. The first hotfix (49d69a3) aligned stoa-core's @scure/bip39
peer to 1.2.1; this one fixes the workflow ordering. Both are
mechanical CI-config fixes that don't change source behavior — the
underlying 819-spec test suite is unchanged.

This commit re-targets v4.1.0 once more — same retag protocol as
hotfix #1 (delete + recreate at this commit). No npm artifacts have
been published yet; no GitHub Release created (workflow hasn't reached
either step in either of the two failed runs). The retag remains safe.

Co-Authored-By: Claude Opus 4.7 (1M context) noreply@anthropic.com