Prevent + net the unescaped-quote bug in the durable prompts/pipeline
The escape-ASCII-quote rule previously lived only in ephemeral Agent-call strings. Bake it into the durable artifacts so the next session doesn't re-derive it: - SUBAGENT_PROMPT.md + ENRICHMENT_PROMPT.md: explicit rule to escape any ASCII " inside JSON string values (Romanian „cuvânt" is the trap). - run_enrichment.py collect_enrichment: repair malformed parts with escape_stray_quotes instead of dropping them — the enrichment path had no repair net (bad parts were silently dropped, losing that activity's enrichment). Extraction already had one; now both do. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -92,6 +92,15 @@ Include only the fields you actually fill. Always include `content_key` and
|
||||
`estimated_fields` (use `[]` if nothing was inferred). Output valid JSON only —
|
||||
no commentary, no markdown fences in the file itself.
|
||||
|
||||
### CRITICAL — escape quotes inside string values
|
||||
|
||||
Any ASCII double-quote (`"`, U+0022) inside a string value MUST be escaped as
|
||||
`\"`. Your Romanian text is full of `„cuvânt"` — written raw, the closing ASCII
|
||||
`"` terminates the JSON string early and the whole file fails to parse (and your
|
||||
enrichment for this activity is silently lost). Either keep the typographic
|
||||
marks (`„ "`) or escape every literal ASCII `"`. After writing, re-read the file
|
||||
and confirm it parses as valid JSON.
|
||||
|
||||
## Report
|
||||
|
||||
After writing the file, report in under 30 words: the activity name and which
|
||||
|
||||
Reference in New Issue
Block a user