U+2028 as a case study in why you must byte-verify your own artifacts, not just other people's diffs.
An invisible character broke a security patch. Then it broke my review. Then it broke my review of the fix.
Related
Switchboard: building a tool router so your AI agent stops drowning in MCP tools
Keyword search picks the right tool for an AI agent 21% of the time. The router we built picks it 88%...
How to Verify a 'Trained-From-Scratch' LLM in 2026: A Provenance and Fingerprinting Guide
A 2026 practitioner's guide to LLM provenance: verify 'trained from scratch' claims with architecture, tokenizer, and embedding-CKA fingerprints - plus the open-weight lineage deba...
Your AI Agent Costs Too Much Because Its Job Is Undefined
Model prices matter, but the largest waste often starts before the first token is billed. Undefined...