StoneCypher / jssm / ddbf62424064f6720a6a92ac953524fb068d541b

100%

master: 100%

push

github

fix(tests): full ci_build green - 9 test repairs, coverage to 100%, two June bugs

The 9 vitest failures triaged to three causes, all fixed:
- render plugin exclusivity misfire (real June bug): --width/--height/--scale
  conflict check read the resolved config, which always carries the scale:3
  default, instead of the user's flags; any explicit --width collided.
- four binary-entry specs asserted the old process.exit contract; ported to
  the binaries.spec.ts waitForExitCode idiom for the #614 exitCode pattern.
- conformance harness conflated omitted data with explicit undefined (real
  June bug): apply_stimulus always made 2-arity calls, but the runtime
  distinguishes by arguments.length; data-free stimuli now call 1-arity.

Coverage restored to 100%: key_compare / code_unit_compare / feature_compare
exported and direct-tested on all three arms (scalar_compare precedent),
stringify_for_error bigint/symbol arms covered, mermaid undefined-label
branch pinned by regression tests, run plugin's unreachable non-string arm
carries the fsl_fence_render v8-ignore idiom with its audit comment.

Also: prefer-https disables on the draft-07 meta-schema id (it is http by
spec, a literal identifier), and a prefer-bigint-literals disable where the
test tsconfig's pre-ES2020 target makes 7n a TS2737 error.

Verified: npm run ci_build exit 0 (vet, make, typecheck_tests, stoch 1016,
spec incl. 100% coverage gates, docs).

3869 of 3869 branches covered (100.0%)

Branch coverage included in aggregate %.

2 of 2 new or added lines in 2 files covered. (100.0%)

6361 of 6361 relevant lines covered (100.0%)

33378.41 hits per line