feat: Add API to delete coding-style.md

[sebyx07]

Summary

• Added delete_coding_style() method to FileOperationsMixin for deleting coding-style.md
• Added REST API endpoint DELETE /coding-style with DeleteCodingStyleResponse model
• Added MCP tool delete_coding_style with DeleteCodingStyleResult response model
• Added comprehensive unit tests for core functionality, MCP tools, and REST API endpoint
• Updated CLAUDE.md documentation with new endpoint and tool

Implementation Details

This feature allows users to delete the generated coding-style.md file via both REST API and MCP tools. The file is automatically regenerated on the next planning phase if needed.

Test Results

All tests passing:

• ✅ 4551 tests passed
• ✅ ruff check & format passed
• ✅ mypy type checking passed

Related Files

• src/claude_task_master/core/state_file_ops.py - Core delete method
• src/claude_task_master/mcp/tools.py - MCP tool implementation
• src/claude_task_master/mcp/server.py - MCP tool wrapper
• src/claude_task_master/api/models.py - REST API response model
• src/claude_task_master/api/routes.py - REST API endpoint
• tests/core/test_state_file_ops.py - Core tests
• tests/mcp/test_tools_coding_style.py - MCP tests
• tests/api/test_routes_status.py - API tests
• CLAUDE.md - Documentation

🤖 Generated with Claude Task Master

Greptile Overview

Greptile Summary

Added API to delete the coding-style.md file from the state directory, allowing users to force regeneration when project conventions change.

Key Changes:

• Core delete_coding_style() method in FileOperationsMixin returns boolean indicating if file existed
• REST API DELETE /coding-style endpoint with proper error handling (404 for no task, 500 for errors)
• MCP tool delete_coding_style with DeleteCodingStyleResult response model
• Comprehensive test coverage: 3 core tests, 5 MCP tests, 4 API tests
• Updated CLAUDE.md documentation with new endpoint and tool

Implementation:
The implementation follows existing patterns in the codebase with proper separation of concerns. The core method is simple and safe (just file deletion), the MCP tool wraps it with proper error handling, and the API endpoint follows REST conventions. The response models differ between API (file_existed) and MCP (deleted) but both convey the same information. All tests pass including ruff, mypy, and 4551 existing tests.

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• Score reflects simple, well-tested implementation with comprehensive test coverage (12 new tests), passing CI checks (4551 tests, ruff, mypy), proper error handling, and consistency with existing codebase patterns. The change is low-risk file deletion functionality with proper validation and documentation.
• No files require special attention

Important Files Changed

Filename	Overview
src/claude_task_master/core/state_file_ops.py	Added simple delete_coding_style() method that removes coding-style.md file and returns boolean status
src/claude_task_master/mcp/tools.py	Added DeleteCodingStyleResult model and delete_coding_style() MCP tool with proper error handling
src/claude_task_master/api/routes.py	Added DELETE /coding-style endpoint with proper 404/500 error handling and response models
tests/core/test_state_file_ops.py	Added 3 comprehensive tests covering file exists, not exists, and content clearing scenarios
tests/mcp/test_tools_coding_style.py	Added 5 MCP tool tests covering no task, file exists/not exists, state manager integration, and idempotency
tests/api/test_routes_status.py	Added 4 API endpoint tests covering success, file not exists, no task, and idempotent deletion

Sequence Diagram

sequenceDiagram
    participant User
    participant API as REST API/MCP
    participant StateManager
    participant FileSystem

    User->>API: DELETE /coding-style OR delete_coding_style()
    API->>StateManager: Check if state exists
    alt No active task
        StateManager-->>API: exists() = False
        API-->>User: 404 Error (REST) / Error Response (MCP)
    else Active task exists
        StateManager-->>API: exists() = True
        API->>StateManager: delete_coding_style()
        StateManager->>FileSystem: Check if coding-style.md exists
        alt File exists
            FileSystem-->>StateManager: File found
            StateManager->>FileSystem: unlink() - delete file
            FileSystem-->>StateManager: Deleted
            StateManager-->>API: Return True
            API-->>User: Success (file_existed/deleted=True)
        else File does not exist
            FileSystem-->>StateManager: File not found
            StateManager-->>API: Return False
            API-->>User: Success (file_existed/deleted=False)
        end
    end
    
    Note over User,FileSystem: File regenerated automatically on next planning phase

Loading

Context used:

• Context from dashboard - CLAUDE.md (source)