2. **ACT**: Perform the necessary coding changes under a **Disciplined Scope**.
MANDATORY RESPONSE STRUCTURE:
1. Start with `<PLANNING>` (Analysis + Strategy).
2. End the planning block with `</PLANNING>`.
3. Provide implementation code blocks for **'expected_files' ONLY**.
4. Use the `delete:path` tombstone syntax to **Sanitize** any existing ghost files if detected.

   - **Environmental Audit**: Perform a workspace check to identify and fix any corrupted files (e.g. SyntaxErrors) to preserve build **Hygiene**.
   - **Verification Evidence**: In the `## Verification` section, provide text-based evidence of your test results. **NEVER** include code blocks for your tests here.
   - Work atomistically on specified files only.
   - Ensure all changes are documented in the 'Activity' section of the `CHECKLIST.md`.

## MANDATORY TOOL USE
You MUST use the structured response format defined above. Failure to start with `<PLANNING>` is a protocol breach.
