"""ADR-0175 Phase 3b / ADR-0179 — lexeme-level quantity extraction.

Pulls ``(value, unit, source_token)`` triples from a problem using conservative
orthographic patterns. Per ADR-0165 these are *lexeme* patterns ("what this
piece looks like: a number, a unit word") — never grammar templates ("how words
combine to mean X"). The *combining* is the search's job (search.py / compose.py)
gated by self-verification, which is refuse-preferring; over-extraction here can
only cost *refusals*, never a wrong answer.

ADR-0179 enrichments integrated here (sealed lane only — ``chat/`` does not import
this module, so none of this can move the serving ``3/47/0``):

* **EX-1 — word-numbers.** ``"three apples"`` → ``3.0``, including tens-one
  hyphen compounds (``"twenty-four"`` → ``24.0``). Reuses the canonical
  ``WORD_NUMBERS`` table from :mod:`generate.math_roundtrip` (single number
  vocabulary). Factor-bearing forms (``half``/``third``/``quarter``) are excluded
  — they read as divisors, not counts.
* **EX-4 — list-unit inheritance.** In a bare numeric list with the unit stated
  once at the end (``"20, 36, 40 and 50 push-ups"``) the trailing unit attaches
  to every number in the list. Still orthographic: a run of number tokens joined
  by comma/``and`` delimiters, then one unit token. Whether the resulting
  quantities may compose is the gate's decision, not the extractor's.
* **EX-5 — sentence-final numbers.** A number with no following unit word (end of
  sentence/text or before terminal punctuation) extracts with an empty unit so it
  stays available to the completeness check without inventing a unit lexeme.
* **Unit hygiene (function-word filter).** When the token after a number is a
  function word (``$0.75 each`` → ``each``, ``$40 to go`` → ``to``, ``3/4 of`` →
  ``of``), the single-word unit pattern would tag it as the unit — a spurious unit
  that corrupts same-unit detection (GB-2/GB-3) and CP-1's ``unit_shape``. Such
  units are blanked (empty, like a sentence-final number): the value stays
  grounded, the unit is honestly unknown. Closed lexeme set (``_NON_UNIT_WORDS``),
  not a grammar template (ADR-0165).
* **EX-6 — hyphen-bonded number-units** (ADR-0163-F2). A number bonded to its unit
  by a hyphen (``25-foot``, ``20-inch``, ``2.5-mile``) was invisible to the base
  ``number + space + word`` pattern, so the completeness check never saw the
  divisor — the blind spot behind the pseudo-accumulation confusers (0005/0007).
  Tight lexeme (digit run, hyphen, alphabetic unit word); the alphabetic-only unit
  group keeps numeric ranges (``3-5``) out and only the first hyphen segment is
  taken, so it stays clear of the deferred EX-3 multi-word-unit traps below.

Workstream A (first increment, per ratified scope): additional conservative lexeme
passes for fractional ("half of", "X/Y of") and comparative ("X more than Y unit",
"X less than Y unit") surface forms. These passes surface only the component lexemes
that appear in the input text (source_token is always a literal substring of the
problem statement). For fractional surface factors, the visible factor is normalized
to a numeric value (0.5 for "half", num/den for "X/Y") while preserving the exact
surface source_token; comparative composition (more/less as relation on two grounded
counts) is fully deferred. This is required by the module contract (lexeme extraction
only for surface; combining is the search/compose job,
gated by self-verification).

EX-3 (multi-word units) is deliberately **not** integrated. Two distinct traps
defeat the tightest lookahead-anchored rule the brief admits:

1. **Connective-crossing** (in
   ``docs/handoff/AUDIT-ADR-0179-EX-RECONCILE.md``). The greedy lowercase unit
   span regresses GB-2's same-unit detection (``"6 apples and 4 apples"`` → unit
   ``"apples and"``) and does not cleanly recover real multi-word units from
   0024-class text (``"20 jumping jacks on Monday"`` → ``"jumping jacks on"``).
2. **Postmodifier-adjective tails** (discovered during the Track C redo of
   ``docs/handoff/PARALLEL-WORK-PLAN-2026-05-29.md``). Even a *tight*
   ``digit + lc word + lc word + (?=clause-terminator)`` rule fires on
   ``"25 years old?"`` and produces unit ``"years old"`` instead of
   ``"years"`` — regressing
   ``tests/test_adr_0176_ms1_question_target.py::TestQuestionQuantities::test_extracts_quantity_stated_in_question``.
   The pattern is endemic: GSM8K cases 0006/0033 and several MS2 chain tests use
   ``"X years old"``. Closing it would need a second closed lexeme set (a stop
   list of measurement postmodifiers — ``old``, ``tall``, ``long``, ``wide``,
   ``deep``, ``high``, ``away``, ``apart``, ``ago``, …) which the audit did not
   anticipate and which the Track C brief judged too open-ended to enumerate
   responsibly. ``TestEX3StillDeferred`` in
   ``tests/test_adr_0179_extract.py`` pins this second trap so no future redo
   silently re-introduces it.
"""

from __future__ import annotations

import re
from typing import Final

from generate.derivation.model import Quantity
from generate.math_roundtrip import WORD_NUMBERS

# Number (int or decimal) immediately followed by a single unit word. Lexeme-level.
_QTY_RE: Final[re.Pattern[str]] = re.compile(
    r"(?<![\w.])(\d+(?:\.\d+)?)\s+([a-zA-Z]+)"
)

# EX-4: a same-unit numeric list with the unit stated once at the end, e.g.
# ``20, 36, 40 and 50 push-ups``. A run of number tokens separated by comma/and
# delimiters, followed by one (optionally hyphenated) unit token.
_LIST_WITH_TRAILING_UNIT_RE: Final[re.Pattern[str]] = re.compile(
    r"(?<![\w.])"
    r"((?:\d+(?:\.\d+)?\s*(?:,\s*|\s+and\s+)){1,}\d+(?:\.\d+)?)"
    r"\s+([a-zA-Z]+(?:-[a-zA-Z]+)*)"
)
_NUMBER_RE: Final[re.Pattern[str]] = re.compile(r"\d+(?:\.\d+)?")

# EX-1: word-number (optionally a tens-one hyphen compound) followed by a unit
# word. Built from the round-trip table; factor-bearing forms excluded.
_WORD_NUMBER_ALT: Final[str] = "|".join(
    re.escape(word)
    for word in sorted(WORD_NUMBERS, key=len, reverse=True)
    if word not in {"half", "third", "quarter"}
)
_WORD_QTY_RE: Final[re.Pattern[str]] = re.compile(
    rf"(?i)\b({_WORD_NUMBER_ALT})(?:-({_WORD_NUMBER_ALT}))?\s+([a-zA-Z]+)\b"
)

# EX-5: a number with no following unit, at end of sentence/text.
_FINAL_NUMBER_RE: Final[re.Pattern[str]] = re.compile(
    r"(?<![\w.])(\d+(?:\.\d+)?)(?=\s*(?:[.?!]|$))"
)

# EX-6: a number bonded to its unit by a hyphen (``25-foot``, ``20-inch``,
# ``2.5-mile``). The base ``_QTY_RE`` requires whitespace before the unit word,
# so a hyphen-bonded unit was invisible — the blind spot behind the
# pseudo-accumulation confusers (``25-foot`` / ``20-inch`` divisors the
# completeness check never saw). Tight lexeme: a digit run, a single hyphen, an
# alphabetic unit word. The trailing ``[a-zA-Z]+`` (not ``\d``) keeps numeric
# ranges (``3-5``) out, and taking only the first hyphen segment keeps the
# postmodifier tail (``25-year-old`` -> unit ``year``) from inflating the unit —
# so this stays clear of the deferred EX-3 multi-word-unit traps.
_HYPHEN_QTY_RE: Final[re.Pattern[str]] = re.compile(
    r"(?<![\w.])(\d+(?:\.\d+)?)-([a-zA-Z]+)"
)

# New for Workstream A increment: fractional "half of" or "X/Y of".
# These are still lexeme-level (the surface words "half", "3/4" etc. are recognized), but we
# normalize the visible factor to a numeric value for convenience while always preserving
# the exact surface source_token from the input text. This limited normalization for factors
# is explicitly documented; full relation composition remains in the graph/compose/search layer.
_HALF_OF_RE: Final[re.Pattern[str]] = re.compile(r"(?i)\b(half|one half)\s+of\s+(?:the\s+|a\s+)?([a-zA-Z]+)")
_FRACTION_OF_RE: Final[re.Pattern[str]] = re.compile(
    r"(?i)\b(\d+)/(\d+)\s+of\s+([a-zA-Z]+)"
)

# Comparative "X more than Y unit" and "X less than Y unit" surface forms.
# The regex matches the surface lexemes; the code emits the two component numbers
# (with unit) as separate lexeme quantities. No arithmetic (sum/diff) is performed
# here. Helps "2 more than 5 miles", "3 less than 17 stop signs".
_MORE_THAN_RE: Final[re.Pattern[str]] = re.compile(
    r"(?<![\w.])(\d+(?:\.\d+)?)\s+more\s+than\s+(\d+(?:\.\d+)?)\s+([a-zA-Z]+)"
)
_LESS_THAN_RE: Final[re.Pattern[str]] = re.compile(
    r"(?<![\w.])(\d+(?:\.\d+)?)\s+less\s+than\s+(\d+(?:\.\d+)?)\s+([a-zA-Z]+)"
)


# Function words that are never units. When the token immediately after a number
# is one of these (``$0.75 each``, ``$40 to go``, ``3/4 of``), the single-word unit
# pattern would otherwise tag the function word as the unit — a spurious unit that
# corrupts same-unit detection (GB-2/GB-3) and CP-1's unit_shape. Emitting an empty
# unit instead (like a sentence-final number) is honest: the value is grounded, the
# unit is simply unknown. Closed lexeme set (cf. ``WORD_NUMBERS``); ADR-0165-safe —
# it names tokens that are not unit nouns, it does not parse sentence structure.
_NON_UNIT_WORDS: Final[frozenset[str]] = frozenset(
    {
        "a", "an", "the", "of", "to", "for", "in", "on", "at", "as", "than",
        "per", "each", "every", "and", "or", "with", "by", "from", "more",
        "less", "about", "that", "old", "young", "tall", "short", "long",
        "wide", "deep", "high", "away", "apart", "ago", "early", "late",
    }
)


def _clean_unit(unit: str) -> str:
    """Lowercase a unit token; blank it if it is a non-unit function word."""
    lowered = unit.lower()
    return "" if lowered in _NON_UNIT_WORDS else lowered


def _quantity(value_token: str, unit: str) -> Quantity | None:
    """Build a quantity from an already-matched numeric token."""
    try:
        value = float(value_token)
    except ValueError:  # pragma: no cover - regex guarantees numeric
        return None
    return Quantity(value=value, unit=_clean_unit(unit), source_token=value_token)


def _resolve_word_number(first: str, second: str | None) -> float | None:
    """Resolve a conservative word-number token from ``WORD_NUMBERS``.

    A bare word resolves directly. A hyphen compound resolves only as a tens-one
    form (``twenty-four``, ``ninety-nine``); anything else returns ``None`` so the
    extractor stays conservative rather than guessing a composition rule.
    """
    first_value = WORD_NUMBERS.get(first.lower())
    if first_value is None:
        return None
    if second is None:
        return float(first_value)
    second_value = WORD_NUMBERS.get(second.lower())
    if second_value is None:
        return None
    if first_value < 20 or first_value >= 100 or not 0 < second_value < 10:
        return None
    return float(first_value + second_value)


def _claimed(pos: int, spans: list[tuple[int, int]]) -> bool:
    """Whether a numeric token at ``pos`` was already claimed by an earlier pass."""
    return any(start <= pos < end for start, end in spans)


def extract_quantities(problem_text: str) -> tuple[Quantity, ...]:
    """Extract ``(value, unit, source_token)`` quantities in left-to-right order.

    Deterministic. ``source_token`` is the surface number string (used by the
    self-verification gate to prove the value is grounded in the text). Units are
    lowercased; the value's surface token is preserved verbatim.

    Passes run most-specific first and claim the digit spans they consume so later
    passes never double-count a number:

    1. EX-4 same-unit list (claims every number in the list);
    2. EX-6 hyphen-bonded number-unit (``25-foot``; claims the digit span);
    3. digit + single unit word (skips numbers a list/hyphen pass already claimed);
    4. EX-1 word-number + unit word (alphabetic, disjoint from digit spans);
    5. EX-5 sentence-final bare number (skips any already-claimed digit).
    6. New for Workstream A: _HALF_OF_RE / _FRACTION_OF_RE (fractional "half of" / "3/4 of");
       _MORE_THAN_RE / _LESS_THAN_RE (comparative "X more/less than Y unit").
    """
    found: list[tuple[int, Quantity]] = []
    claimed: list[tuple[int, int]] = []

    # 1. EX-4 — list with one trailing unit; the unit inherits to every number.
    for match in _LIST_WITH_TRAILING_UNIT_RE.finditer(problem_text):
        unit = match.group(2).lower()
        for num in _NUMBER_RE.finditer(match.group(1)):
            pos = match.start(1) + num.start()
            quantity = _quantity(num.group(0), unit)
            if quantity is not None:
                found.append((pos, quantity))
                claimed.append((pos, pos + len(num.group(0))))

    # 1b. EX-6 — hyphen-bonded number-unit (``25-foot``). Claims the digit span so
    #     the bare/final passes never re-surface the number with a blank unit.
    for match in _HYPHEN_QTY_RE.finditer(problem_text):
        if _claimed(match.start(1), claimed):
            continue
        quantity = _quantity(match.group(1), match.group(2))
        if quantity is not None:
            found.append((match.start(1), quantity))
            claimed.append(match.span(1))

    # 1c. New EX for Workstream A increment: fractional "half of" / "X/Y of".
    #     Lexeme-level only: surface the factor word or fraction string as it appears
    #     in the input (per the module contract: extraction is lexeme-level; combining
    #     and relation resolution belong to search/compose, gated by verify).
    #     No synthesized decimal source_tokens; source_token is always surface text.
    for match in _HALF_OF_RE.finditer(problem_text):
        unit = match.group(2)
        # "half" (or "one half") is the surface lexeme factor; value is interpretive
        # convenience for downstream, but source is the word that appears in text.
        quantity = Quantity(value=0.5, unit=_clean_unit(unit), source_token=match.group(1))
        if quantity is not None:
            pos = match.start(1)
            if not _claimed(pos, claimed):
                found.append((pos, quantity))
                claimed.append((pos, pos + len(match.group(1))))

    for match in _FRACTION_OF_RE.finditer(problem_text):
        num, den, unit = match.group(1), match.group(2), match.group(3)
        try:
            val = float(num) / float(den)
        except (ValueError, ZeroDivisionError):
            continue
        # "3/4" is the surface lexeme form in the text; keep it as source_token.
        quantity = Quantity(value=val, unit=_clean_unit(unit), source_token=f"{num}/{den}")
        pos = match.start(1)
        if not _claimed(pos, claimed):
            found.append((pos, quantity))
            claimed.append(match.span(1))

    # 1d. New EX for Workstream A: comparative "X more than Y unit", "X less than Y unit".
    #     Lexeme-level only: surface the two component numbers that appear in the text
    #     (with the unit). Do *not* synthesize a result value or non-surface source_token
    #     here (e.g. never emit "7.0" for "2 more than 5 miles"). The "more/less" relation
    #     and any composition are expressed via the recognizer graph (from exemplars) and
    #     resolved in compose/search/verify (the module contract). This avoids creating
    #     grounding hazards and keeps extraction strictly lexeme.
    for match in _MORE_THAN_RE.finditer(problem_text):
        x, y, unit = match.group(1), match.group(2), match.group(3)
        qx = _quantity(x, unit)
        if qx is not None:
            pos = match.start(1)
            if not _claimed(pos, claimed):
                found.append((pos, qx))
                claimed.append((pos, pos + len(x)))
        qy = _quantity(y, unit)
        if qy is not None:
            pos = match.start(2)
            if not _claimed(pos, claimed):
                found.append((pos, qy))
                claimed.append((pos, pos + len(y)))

    for match in _LESS_THAN_RE.finditer(problem_text):
        x, y, unit = match.group(1), match.group(2), match.group(3)
        qx = _quantity(x, unit)
        if qx is not None:
            pos = match.start(1)
            if not _claimed(pos, claimed):
                found.append((pos, qx))
                claimed.append((pos, pos + len(x)))
        qy = _quantity(y, unit)
        if qy is not None:
            pos = match.start(2)
            if not _claimed(pos, claimed):
                found.append((pos, qy))
                claimed.append((pos, pos + len(y)))

    # 2. digit + single unit word — the original base pattern.
    for match in _QTY_RE.finditer(problem_text):
        if _claimed(match.start(1), claimed):
            continue
        quantity = _quantity(match.group(1), match.group(2))
        if quantity is not None:
            found.append((match.start(1), quantity))
            claimed.append(match.span(1))

    # 3. EX-1 — word-numbers (and tens-one hyphen compounds) with a unit word.
    for match in _WORD_QTY_RE.finditer(problem_text):
        value = _resolve_word_number(match.group(1), match.group(2))
        if value is None:
            continue
        source_token = (
            match.group(1)
            if match.group(2) is None
            else match.group(0).rsplit(maxsplit=1)[0]
        )
        found.append(
            (
                match.start(1),
                Quantity(value=value, unit=_clean_unit(match.group(3)), source_token=source_token),
            )
        )

    # 4. EX-5 — sentence-final bare numbers (empty unit).
    for match in _FINAL_NUMBER_RE.finditer(problem_text):
        if _claimed(match.start(1), claimed):
            continue
        quantity = _quantity(match.group(1), "")
        if quantity is not None:
            found.append((match.start(1), quantity))

    found.sort(key=lambda item: item[0])

    # Post-process for age postmodifier hygiene (e.g. "6 years old" in "when she was 6 years old").
    # Prevents spurious "years" quantity in incidental age contexts (the motivating "8 pages when she
    # was 6 years old" proxy refusal case) while *preserving* legitimate age-as-target quantities
    # (pinned by TestEX3StillDeferred: "25 years old?" and "Rachel is 12 years old." must keep unit="years").
    # Rule (lexeme + local, no grammar): if a year-unit has "old"/"young" nearby, treat as incidental
    # (blank) *only if* there exists at least one *earlier* quantity in the list that carries a non-empty
    # unit (i.e., this age phrase is trailing background to a primary claim that has its own grounded unit).
    # Pure age statements or question targets remain "years" (satisfies the pinned tests and GSM8K age cases
    # where age *is* the measured quantity).
    if found:
        has_prior_grounded = False
        for i, (pos, q) in enumerate(found):
            if q.unit and q.unit not in ("year", "years"):
                has_prior_grounded = True
            if q.unit in ("year", "years"):
                snippet = problem_text[pos : pos + 30].lower()
                if ("old" in snippet or "young" in snippet) and has_prior_grounded:
                    found[i] = (pos, Quantity(value=q.value, unit="", source_token=q.source_token))
                # else: keep "years" (sole/primary age target or no competing grounded unit yet)

    return tuple(quantity for _, quantity in found)