@spintax/core 0.1.4 → 0.1.6

package/CHANGELOG.md

@@ -3,6 +3,80 @@
 All notable changes to `@spintax/core` are documented here. This project adheres to
 [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## 0.1.6 — 2026-07-13
+
+Two post-process fixes. **Supersedes 0.1.5** — upgrade straight past it. No API change.
+
+### Fixed
+
+- **A run of sentence punctuation is no longer split from the inside.** This is not a Spanish issue
+  and it predates the 0.1.5 work: the "space after `.!?`" rule looked exactly one character ahead
+  and never at the rest of the run, so it fired *between* the marks.
+
+  ```
+  wait... what?   →  Wait. . . What?      (0.1.5 and earlier)
+  wow!!!          →  Wow! ! !
+  really?!        →  Really? !
+  ```
+
+  The ASCII ellipsis is the common casualty — and the Unicode `…` is *not* in the `[.!?]` class,
+  which is exactly why the corpus's existing ellipsis fixture never caught it. A run is now matched
+  whole and required to be complete: `([.!?]+)(?![.!?])`. The guard is load-bearing — a greedy `+`
+  alone gives ground back *into* the run to satisfy the lookaheads and yields `Wow!! !`.
+
+- **`¡¿Qué haces?!` keeps its capital.** The 0.1.5 opener rule allowed exactly *one* opener, so the
+  RAE form for a sentence that is both a question and an exclamation — the most Spanish sentence
+  there is — still lost its capital. An opener followed by markup (`¿<strong>cómo</strong> estás?`,
+  `<p>¿<a href="/ayuda">necesitas ayuda</a>?</p>`) failed for the same reason: the old lead only
+  allowed `tags → opener → letter`, never `opener → tags → letter`.
+
+  The lead is now any run of tags, sentence openers and whitespace, in any order. The opener set
+  stays deliberately **narrow** — quotes and brackets are still not openers, and the fixtures added
+  in 0.1.5 keep guarding that.
+
+### Notes
+
+- Mirrored into the PHP plugin engine (released there as 2.3.3). Verified against the shared golden
+  corpus in both engines: TS 243 tests; the conformance runner against the real plugin engine 107
+  tests / 120 assertions. No performance regression — the pathological-input cost is unchanged from
+  0.1.5 and comes from the URL/domain shields, not from these rules.
+
+## 0.1.5 — 2026-07-13
+
+Spanish post-process fix. No API change.
+
+### Fixed
+
+- **`postProcess` no longer strips the capital from every Spanish sentence.** Spanish is the only
+  European language whose punctuation *opens* a sentence, and the capitalization passes upper-cased
+  the first **character** after a sentence boundary — which, for `¿cómo estás?`, is `¿`. An inverted
+  mark has no uppercase form, so the pass was a no-op and the real first letter stayed lowercase.
+  The spacing pass had the mirror-image gap: it knew "no space *before* closing punctuation" but had
+  no rule for an opener, so `¿ qué tal ?` only half-collapsed.
+
+  ```
+  hola. ¿cómo estás? ¡genial!   →  Hola. ¿Cómo estás? ¡Genial!
+  Hola. ¿ qué tal ?             →  Hola. ¿Qué tal?
+  ```
+
+  A new `SENTENCE_OPENERS = '¿¡'` concept drives both: an opener binds to the word it opens (before
+  capitalization, deliberately), and the four capitalization sites — start of text, after `.!?…`,
+  after a block-level tag, and after a newline — allow an optional opener between the boundary and
+  the letter. HTML paragraphs and multi-line templates were broken exactly like the bare `. ¿` case.
+
+  The opener set is deliberately **narrow**: quotes and brackets both open *and* close, so
+  capitalizing after them would mangle list markers (`Elige una. (a) primero`). Golden-corpus
+  fixtures guard both the fix and its narrowness, in **both** engines.
+
+### Notes
+
+- Mirrored into the PHP plugin engine to hold the post-process parity contract. Verified against the
+  shared golden corpus in both engines: TS 230 tests; the conformance runner against the real plugin
+  engine 99 tests / 112 assertions; the plugin's own suite 578 tests, no regressions.
+- The plugin carries the same fix but ships it in a later release, so for a short window a published
+  plugin and this package can differ on Spanish output. The parity *contract* holds — the engines'
+  behavior agrees and the corpus proves it — only the release timing differs.
+
 ## 0.1.4 — 2026-07-13
 
 A post-process bug fix (hit in production) plus docs. No API change.

package/dist/index.cjs

@@ -913,13 +913,19 @@ var DECIMAL_RE = /\b\d+\.\d+\b/gu;
 var MULTI_ABBR_RE = new RegExp(`\\b(?:\\p{L}{1,2}\\.${S}*){2,}`, "gu");
 var SINGLE_ABBR_RE = new RegExp(`(?<![\\p{L}\\p{N}])(?:${SINGLE_ABBREVS.join("|")})\\.(?=${S}|$|<)`, "giu");
 var TRAILING_PUNCT_RE = /([.,;:!]+)$/u;
+var SENTENCE_OPENERS = "\xBF\xA1";
+var LEAD = `(?:<[^>]+>|[${SENTENCE_OPENERS}]|${S})*`;
 var SPACE_BEFORE_PUNCT_RE = new RegExp(`${S}+([,;:!?.])`, "gu");
 var SPACE_AFTER_COMMA_RE = new RegExp(`([,;:])(?!\\d)(?!${S}|$|<)`, "gu");
-var SPACE_AFTER_SENTENCE_RE = new RegExp(`([.!?])(?!\\d)(?!${S}|$|<)`, "gu");
-var CAP_FIRST_RE = new RegExp(`^(${S}*(?:<[^>]+>${S}*)*)(\\p{Ll})`, "u");
-var CAP_AFTER_SENTENCE_RE = new RegExp(`([.!?\u2026])(${S}*(?:<\\/?[^>]+>${S}*)*)(\\p{Ll})`, "gu");
-var CAP_AFTER_BLOCK_RE = new RegExp(`(<\\/?(?:p|h[1-6]|li|blockquote|div|td|th)[^>]*>${S}*)(\\p{Ll})`, "giu");
-var CAP_AFTER_BREAK_RE = new RegExp(`(\\n${S}*)(\\p{Ll})`, "gu");
+var SPACE_AFTER_SENTENCE_RE = new RegExp(`([.!?]+)(?![.!?])(?!\\d)(?!${S}|$|<)`, "gu");
+var SPACE_AFTER_OPENER_RE = new RegExp(`([${SENTENCE_OPENERS}])${S}+`, "gu");
+var CAP_FIRST_RE = new RegExp(`^(${LEAD})(\\p{Ll})`, "u");
+var CAP_AFTER_SENTENCE_RE = new RegExp(`([.!?\u2026])(${LEAD})(\\p{Ll})`, "gu");
+var CAP_AFTER_BLOCK_RE = new RegExp(
+  `(<\\/?(?:p|h[1-6]|li|blockquote|div|td|th)[^>]*>${LEAD})(\\p{Ll})`,
+  "giu"
+);
+var CAP_AFTER_BREAK_RE = new RegExp(`(\\n${LEAD})(\\p{Ll})`, "gu");
 var up = (ch) => ch.toUpperCase();
 function postProcess(input) {
   const placeholders = /* @__PURE__ */ new Map();
@@ -951,6 +957,7 @@ function postProcess(input) {
   text = text.replace(SPACE_BEFORE_PUNCT_RE, "$1");
   text = text.replace(SPACE_AFTER_COMMA_RE, "$1 ");
   text = text.replace(SPACE_AFTER_SENTENCE_RE, "$1 ");
+  text = text.replace(SPACE_AFTER_OPENER_RE, "$1");
   text = text.replace(CAP_FIRST_RE, (_m, lead, ch) => lead + up(ch));
   text = text.replace(CAP_AFTER_SENTENCE_RE, (_m, p, gap, ch) => p + gap + up(ch));
   text = text.replace(CAP_AFTER_BLOCK_RE, (_m, tag, ch) => tag + up(ch));