\s expands to the source's whitespace class in both runtimes
The dialect contract claimed \d \w \s \b were pinned ASCII on both sides; measured, \s was the exception - JS \s is Unicode-ish in every mode (NBSP yes, FEFF yes, \x1c no) while Python re.ASCII \s is ASCII-only, so tables diverged between runtimes on NBSP-bearing legal text and no vector caught it. Both loaders now expand \s/\S at compile time to the exact whitespace set Python's Unicode \s gave the source grammars when they were battle-tested. cite.neutral gains the NBSP-separated CanLII-render vector; the engine differential dropped from 62 unicode findings to zero across 49 entries and 2,114 inputs. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012AgUm5EcRKbT3duVFMbrQD
| Repository | eliziff/Beaver |
|---|---|
| Author | Eli Ziff <eliasziff@gmail.com> |
| Authored | |
| Parents | e7343070 |
| Stats | 3 files changed , +109 , -13 |
| Part of | Legal agent-surface and context-compaction experiments |
Capture this commit into my fork
Download a Markdown prompt that tells Claude how to port this
exact commit into your working tree. Run it via
claude -p < capture-commit-6c42c881.md
from inside the repo you want the change in.