mirror of
https://github.com/EveryInc/compound-engineering-plugin.git
synced 2026-10-12 03:49:16 +02:00
Trevin ChowandClaude Opus 4.7
5841400ce2
Findings whose titles or descriptions contained a literal `|` (e.g. cache key delimiter examples like `userName + " |" + groups`, regex alternations, logical-OR operators) corrupted the markdown table -- unescaped pipes were parsed as column separators, splitting content across the `Reviewer`, `Confidence`, and `Route`/`Tier` columns. Add an escape rule to both review-output templates so the synthesis LLM writes literal pipes as `\|` inside table cells. The rule lives prominently next to the existing pipe-table directive at the top of each template, plus as a parallel Formatting Rules bullet in ce-code-review where the issue reporter expected to find it. The synthesis path is purely prose-driven (`@`-include from SKILL.md), so a missing rule = missing behavior; no code or test surface to change. Fixes #761 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>