v1.4.0

[minirang]

Description

• Added an automated regression test suite (tests/, bash tests/run.sh): tests/cases/
  (exact output diff), tests/errors/ (must fail with a specific error code), plus the
  existing examples//examples/error_cases/ are now checked the same way instead of only
  by hand. Wired into CI (.github/workflows/build-and-test.yaml).
• Fixed a real crash (SIGSEGV) in the regex matcher: a pattern with deep linear recursion
  (e.g. [any]+ against a ~20k+ character string) overflowed the real C++ stack before the
  matcher's own recursion-depth guard could throw its safety exception — the guard's limit
  (20,000) was measured, empirically, to be higher than where the actual crash occurs on an
  8MB stack (~19,500). Lowered the default depth limit to 3,000 (a large margin below the
  observed crash point) and verified no crash from 100 to 1,000,000 characters. Found by the
  new test suite.
• Found and documented (not yet fixed) that names using certain keywords — add, count,
  find, split, replace, match, in, by, not, global, etc. — can't be used as
  variable or function names anywhere (set number add to 5 fails to parse). Same root cause
  as the DLC:list import-parsing bug fixed earlier, but spread across every place an
  identifier is declared. See docs/IMPLEMENTATION_NOTES.md section 16.
• Fixed examples/06_error_recovery.cuff, which incorrectly demonstrated or_else "catching"
  a find that simply returns empty on no match (not an exception) — added the correct
  is empty check alongside a genuine or_else-recoverable example (out-of-range index).

---

This discussion was created from the release v1.4.0.