mcp-work-discipline

Behavior-preserving refactoring requires strict discipline and self-audit checks before reporting changes. You must enforce mandatory gate verification rules to ensure no behavior changes are overlooked, preventing unintended side effects and maintaining project integrity.

A self-audit check for refactoring verifies that pure moves and case extraction maintain original behavior. It enforces specific discipline rules and gate verification, requiring honest reporting of changes and their impact before finalizing the process.

To apply gate verification for CLI and MCP server refactorings, run discipline checks before reporting. This enforces adherence to specific rules, ensuring robust code quality and verifying that the refactorings preserve existing behavior without side effects.

Yes, the idu-pi refactoring discipline process is designed for use by implementer models including Claude, Qwen, MiniMax, and KM5. It enforces self-audit rules on refactorings generated by these models to maintain project integrity.

You need to run discipline checks before reporting any refactor in the idu-pi project to ensure it adheres to strict self-audit rules. This applies to pure moves, case extraction, and other behavior-preserving changes to prevent unintended side effects.

The limitation is that self-audit requires strict adherence to hard-won gate lessons and specific discipline rules. If implementer models bypass these mandatory checks before reporting, unintended side effects may occur, compromising the intended behavior-preserving nature of the refactoring.