[christso]

Summary

PR comments and short technical discussion now default to plain language, even when the request only asks for a concise comment. Necessary technical detail and the agreed review status remain required.

Validation

• Catalogue validation and all 21 Bun tests passed.
• Completed code review found no actionable issues.
• The full private suite passed 24/27 cases with no provider errors. Three older cases dropped required details; all six new cases passed again. No full-suite stock comparison was run.

Private comparison	Passed	Failed	Errors
Stock skill	6	0	0
Updated skill	6	0	0

The comparison used the same cases, models, judges and CLI settings. No quality gain was measured; this change makes the intended default explicit. Real examples and result artifacts remain in the private eval repository.

Post-Deploy Monitoring & Validation

The skill maintainer should check the first PR comment after merging and installing the update: ask without an explicit plain-English instruction, then check that the comment explains the behavior and retains the review decision. Revert the guidance change if it drops necessary technical detail or changes approval/blocker status. No service logs or dashboards apply.

---