mirror of
https://github.com/EveryInc/compound-engineering-plugin.git
synced 2026-06-19 15:41:46 +02:00
Trevin Chow
33e00c4047
The interactive routing option B was labeled "LFG" in user-facing prose and "the LFG path" in skill internals. That name collides with the /lfg macro skill in this repo, creating confusion when an agent reads the ce-code-review skill while also having /lfg in scope. Rename: - User-facing menu (option B): "LFG. Apply the agent's best-judgment action per finding" -> "Auto-resolve with best judgment -- apply per-finding fixes the agent can defend, surface the rest" - User-facing per-finding option D: "LFG the rest" -> "Auto-resolve with best judgment on the rest" - Internal naming: "LFG path" / "LFG routing (option B)" -> "best-judgment path" / "best-judgment routing (option B)" - Routing tables, Step 3 fixer queue prose, completion-report bucket list, and other internal references updated to match - Test assertions updated against the new labels The user-facing label leads with "Auto-resolve" so the action is clear on scan; "with best judgment" qualifies how decisions are made. The internal name uses "best-judgment" (not "auto-resolve") to avoid lexical collision with the existing mode:autofix flag, since the two do different things and live at different structural levels -- autofix is a top-level mode while best-judgment is a routing option within interactive mode. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>