docs: prepare v0.8.5 release documentation

- Update release-notes.md with v0.8.5 features and fixes
- Move unreleased content to v0.8.5 section in CHANGELOG.md
- Update README status section to reflect v0.8.5 release
- Highlight advanced date parsing system and task assignment fixes

Preparing for v0.8.5 release with GitHub workflow automation.

Author: taazkareem

CHANGELOG.md

@@ -2,7 +2,13 @@
 
 ## Unreleased
 
-### 🚀 New Improvements
+### 🚀 New Features & Improvements
+
+### 🐛 Bug Fixes
+
+## v0.8.5 (2025-07-11)
+
+### 🚀 New Features & Improvements
 
 - **Major Enhancement: Advanced Date Parsing System (Option A Implementation)**:
   - **Smart Preprocessing Layer**: Automatically corrects typos and normalizes natural language expressions

README.md

@@ -6,7 +6,7 @@
 
 A Model Context Protocol (MCP) server for integrating ClickUp tasks with AI applications. This server allows AI agents to interact with ClickUp tasks, spaces, lists, and folders through a standardized protocol.
 
-> 🚀 **Status Update:** v0.8.4 is released with security features and compatibility improvements! Added comprehensive opt-in enhanced security features, fixed Gemini compatibility (Issue #79), and resolved priority handling and subtask retrieval issues. See [Release Notes](release-notes.md) for full details.
+> 🚀 **Status Update:** v0.8.5 is released with advanced date parsing and critical bug fixes! Added major date parsing enhancements with smart preprocessing, fixed task assignment functionality, and resolved time tracking tool response formatting. See [Release Notes](release-notes.md) for full details.
 
 ## Setup
 

release-notes.md

@@ -1,65 +1,47 @@
-# v0.8.4 Release Notes
-
-### � Security Features
-
-- **Comprehensive MCP Streamable HTTPS Transport Security Implementation**:
-  - **HTTPS/TLS Support**: Added optional HTTPS server alongside HTTP for encrypted communication
-    - Environment variables: `ENABLE_HTTPS`, `SSL_KEY_PATH`, `SSL_CERT_PATH`, `SSL_CA_PATH`, `HTTPS_PORT`
-    - Dual protocol support: HTTP (3231) and HTTPS (3443) run simultaneously for backwards compatibility
-    - Self-signed certificate generation script: `./scripts/generate-ssl-cert.sh`
-    - Production-ready with CA-issued certificates
-  - **Origin Header Validation**: Prevents cross-site attacks by validating Origin header against whitelist
-    - Environment variable: `ENABLE_ORIGIN_VALIDATION=true`
-    - Default allowed origins: `127.0.0.1:3231`, `localhost:3231`, plus HTTPS variants
-    - Smart handling: Allows non-browser clients (n8n, MCP Inspector) while blocking unauthorized origins
-  - **Rate Limiting Protection**: Protects against DoS attacks with configurable request limits
-    - Environment variable: `ENABLE_RATE_LIMIT=true`
-    - Default: 100 requests per minute per IP address
-    - Configurable via: `RATE_LIMIT_MAX`, `RATE_LIMIT_WINDOW_MS`
-  - **CORS Configuration**: Secure cross-origin resource sharing for web applications
-    - Environment variable: `ENABLE_CORS=true`
-    - Supports GET, POST, DELETE, OPTIONS methods
-    - Headers: Content-Type, mcp-session-id, Authorization
-  - **Security Headers**: Web security best practices when `ENABLE_SECURITY_FEATURES=true`
-    - X-Content-Type-Options, X-Frame-Options, X-XSS-Protection
-    - Referrer-Policy, Strict-Transport-Security (HTTPS only)
-  - **Request Size Limits**: Prevents memory exhaustion attacks
-    - Configurable limit: `MAX_REQUEST_SIZE=10mb` (default)
-    - Hard limit: 50MB maximum
-  - **Security Monitoring**: Comprehensive logging and health endpoint
-    - Health endpoint: `/health` shows security status
-    - Security event logging: origin validation, rate limits, violations
-    - Log levels: DEBUG, INFO, WARN, ERROR for security events
-  - **Zero Breaking Changes**: All security features are opt-in and disabled by default
-    - Existing clients (Claude Desktop, n8n, MCP Inspector) work unchanged
-    - No configuration changes required for current users
-    - Backwards compatibility thoroughly tested and verified
+# v0.8.5 Release Notes
+
+### 🚀 New Features & Improvements
+
+- **Major Enhancement: Advanced Date Parsing System**:
+  - **Smart Preprocessing Layer**: Automatically corrects typos and normalizes natural language expressions
+    - Typo correction: `"tommorow"` → `"tomorrow"`, `"yesterady"` → `"yesterday"`
+    - Natural language enhancement: `"tomorrow morning"` → `"tomorrow 9am"`, `"yesterday evening"` → `"yesterday 6pm"`
+    - Complex expression normalization: `"day after tomorrow"` → `"+2 days"`, `"day before yesterday"` → `"-2 days"`
+    - Time format normalization: Handles `"@"`, `"at"`, and various am/pm formats
+  - **Enhanced Pattern Matching**: Consolidated regex patterns with improved flexibility
+    - Relative days with time: `"+3 days 2pm"`, `"-2 days 9:30am"`
+    - Relative weeks with time: `"+2 weeks 1pm"`, `"-1 weeks 5pm"`
+    - Enhanced yesterday/tomorrow: `"tomorrow 8am"`, `"yesterday 7:30pm"`
+  - **Expanded Format Support**: Added support for multiple new date formats
+    - US dates with time: `"7/4/2025 5pm"`, `"11/11/2030 11:11pm"`
+    - Text month formats: `"march 10 2025 6:30pm"`
+    - Dates without year: `"10/10 6:00pm"` (assumes current year)
+    - Timestamp boundary fix: Now accepts Year 2000 boundary (`946684800000`)
+  - **Improved Date Clearing**: Fixed date clearing functionality to properly set `null` values
+  - **Code Optimization**: Reduced code duplication by 40% with helper functions and consolidated patterns
+  - **Performance**: Maintains sub-millisecond parsing speed (~0.188ms average)
+  - **Comprehensive Testing**: Achieves 100% success rate on 50-test comprehensive suite
+  - **Backward Compatibility**: All existing functionality preserved while adding significant new capabilities
 
 ### 🐛 Bug Fixes
 
-- **Fixed Gemini compatibility (Issue #79)**:
-  - **Root cause**: Priority enum values were defined as numbers `[1, 2, 3, 4, null]` but Gemini API expects strings
-  - **Solution**: Updated priority enum to use string values `["1", "2", "3", "4", null]` in `update_task` and `update_bulk_tasks` tools
-  - **Schema changes**: Changed type from `"number"` to `"string"` for priority field in affected tools
-  - **Backward compatibility**: Maintained via existing `toTaskPriority()` function that handles string-to-number conversion
-  - **Impact**: Resolves schema validation errors in Cursor IDE and other Gemini-based MCP clients
-  - **Affected tools**: `update_task_ClickUp__Local_` and `update_bulk_tasks_ClickUp__Local_`
-  - **Testing**: Verified priority setting and removal functionality works correctly
-
-- **Fixed priority null handling in task updates (Issue #23)**:
-  - Fixed `update_task` tool failing when setting priority to `null` to clear/remove priority
-  - Modified `buildUpdateData` function to use `toTaskPriority` helper for proper null value conversion
-  - Priority updates now work correctly for both setting valid values (1-4) and clearing priority (null)
-  - Bulk task updates (`update_bulk_tasks`) already worked correctly and continue to function properly
-
-- **Fixed subtasks not being retrieved (Issue #69)**:
-  - Fixed `getSubtasks` method in `task-core.ts` to include required query parameters
-  - Added `subtasks=true` and `include_subtasks=true` parameters to ClickUp API call
-  - Subtasks are now properly retrieved and displayed when using `get_task` tool with `subtasks=true`
-  - Resolves issue where subtasks arrays were always empty despite subtasks existing in ClickUp
-
-### 🔧 Compatibility Improvements
-
-- **Enhanced MCP Client Support**: Improved compatibility with Cursor IDE and Gemini-based MCP clients
-- **Schema Standardization**: Aligned tool schemas with MCP protocol best practices for broader client support
-- **Testing Coverage**: Verified functionality across multiple MCP client implementations
+- **Fixed Task Assignment Functionality**:
+  - **Root Cause**: ClickUp API uses different formats for assignees in task creation vs updates
+    - Creation: `"assignees": [user_id1, user_id2]` (simple array)
+    - Updates: `"assignees": { "add": [user_id1], "rem": [user_id2] }` (object with add/rem arrays)
+  - **Parameter Parsing**: Fixed MCP serialization issue where assignee arrays were received as strings
+  - **Smart Assignment Logic**: Implemented intelligent add/remove calculation by comparing current vs desired assignees
+  - **Complete Functionality**: Now supports adding, removing, and updating task assignees
+  - **Multiple Formats**: Supports user IDs, emails, and usernames for assignee resolution
+  - **TypeScript Types**: Updated interfaces to support both array and object assignee formats
+  - **Testing**: Verified full assignment cycle (add → remove → re-add) works correctly
+
+- **Fixed Track Time tool response formatting issue**:
+  - Fixed issue where Track Time tools (start/stop time tracking, get time entries, etc.) were executing successfully but returning no output to users
+  - **Root cause**: Time tracking handlers were returning raw JavaScript objects instead of using proper MCP server response formatting
+  - **Solution**: Updated all 6 time tracking handlers to use `sponsorService.createResponse()` method for consistent response formatting
+  - **Handlers fixed**: `handleStartTimeTracking`, `handleStopTimeTracking`, `handleGetTaskTimeEntries`, `handleAddTimeEntry`, `handleDeleteTimeEntry`, `handleGetCurrentTimeEntry`
+  - **Enhanced error handling**: All error responses now use `sponsorService.createErrorResponse()` for consistent error formatting
+  - **Added null safety**: Fixed potential undefined property access in time entries data with proper null checks
+  - **Improved user experience**: Added helpful success messages and proper data structure formatting
+  - **Impact**: Track Time tools now provide clear, formatted JSON responses instead of appearing to run silently