v4.1.2
What's Changed
Fixed
- Corrupt
data.toonentries — 3 entries written with unescaped|literals (field-shift corruption) repaired in place with the production serializer; content, dates, and TTLs restored - Dynamic entry-count limit in health warnings —
context_healthand the context brief now readMAX_ENTRIESfromconfig.jsonviagetMaxEntries()instead of a hardcoded100 - Malformed-entry detection —
generateContextHealthnow flags shifted/invaliddate/ttlfields as a Critical health issue (score −20), so unescaped-pipe corruption surfaces instead of silently parsing wrong
Tests
- 18-field
toToonLineround-trip with combined pipes/backslashes/multiline hazards - Field-shift exposure: unescaped pipe is visible as an invalid date field, not silent garbage
- Health detector flags malformed entries and leaves clean data unflagged
Full Changelog: v4.1.1...v4.1.2