mirror of
https://github.com/EveryInc/compound-engineering-plugin.git
synced 2026-10-30 20:15:09 +01:00
Trevin Chow
aac566dce5
The previous wording framed "non-interactive mode" as the clearest example of when un-validated bets need a visible Assumptions section. That framing assumes synchronous = validated, which doesn't hold for skills like ce-compound where the interactive flow asks only meta-questions (Full vs Lightweight, session-history opt-in) and never validates the substantive inferences (track, category, filename, overlap). Reframe the test: compare per skill, not per mode. An Assumptions section is audit content when the corresponding interactive mode would have validated content that the headless run skips. When neither mode validates the inferences, labeling them only in headless is misleading — it implies interactive runs validated content they didn't. Prompted by Codex review feedback on the ce-compound mode:headless PR, where the literal reading of the old rule generated incorrect guidance for a skill whose interactive mode doesn't validate the relevant content.