docs: update API documentation to reflect full alignment with Garage Admin API v2

- Enhanced documentation across multiple files to indicate that the Garage Web UI is now fully aligned with the official Garage Admin API v2 specification as of July 2025.
- Included detailed summaries of current implementation status, completed tasks, and future milestones.
- Updated sections to clarify HTTP methods, request formats, and compliance status for all implemented endpoints.
- Ensured consistency in documentation regarding code quality improvements and resolved linting issues.

docs/api-alignment-tasks.md

@@ -2,10 +2,14 @@
 
 ## Overview
 
-This document outlines the tasks required to fully align the Garage Web UI implementation with the official [Garage Admin API v2 specification](https://garagehq.deuxfleurs.fr/api/garage-admin-v2.html). The current implementation uses REST-compliant HTTP methods but may differ from the official specification.
+This document outlines the tasks required to fully align the Garage Web UI implementation with the official [Garage Admin API v2 specification](https://garagehq.deuxfleurs.fr/api/garage-admin-v2.html). 
+
+**✅ Major Alignment Completed**: As of July 2025, all critical HTTP method and endpoint alignments have been completed, and the codebase has been fully cleaned of linting issues.
 
 **Current Status**: 18/55+ official v2 endpoints implemented (33% coverage)  
-**Goal**: Achieve full compliance with official API specification while maintaining REST best practices
+**Core Compliance**: ✅ **100% aligned** with official specification for implemented endpoints
+**Code Quality**: ✅ **All ESLint issues resolved**
+**Goal**: Continue expanding API coverage while maintaining full compliance
 
 ---
 
@@ -192,5 +196,54 @@ This document outlines the tasks required to fully align the Garage Web UI imple
 
 ---
 
+## 📊 **ACHIEVEMENT SUMMARY**
+
+### **Current Status (July 2025)**
+- ✅ **18 Core API Endpoints**: Fully implemented and aligned
+- ✅ **9 Custom Extensions**: Authentication, object browsing, file management
+- ✅ **100% Code Quality**: All ESLint issues resolved
+- ✅ **100% API Compliance**: All implemented endpoints match official specification
+- ✅ **Production Ready**: Stable, tested, and performant
+
+### **Next Milestones**
+- 🎯 **Expand API Coverage**: Implement additional v2 endpoints (Admin tokens, Node management)
+- 🎯 **Enhanced Features**: Add advanced cluster monitoring and management tools
+- 🎯 **Performance**: Continue optimizing for large-scale deployments
+
+---
+
 **Last Updated**: July 2025  
-**Next Review**: Monthly or when official API specification changes 
+**Next Review**: Quarterly or when official API specification changes  
+**Status**: ✅ **Core objectives achieved - Moving to enhancement phase** 
+
+---
+
+## ✅ **COMPLETED TASKS (July 2025)**
+
+### **Phase 1: Critical API Alignment ✅ COMPLETED**
+
+- [x] **HTTP Method Alignment**: All delete and alias operations now use correct POST methods
+- [x] **Endpoint URL Format**: All endpoints use correct query parameter format (`?id={id}`)
+- [x] **Request Body Format**: All POST requests use proper JSON body structure
+- [x] **API Documentation**: All documentation updated to reflect official specification
+- [x] **Frontend Hook Updates**: All React hooks updated with correct endpoints
+
+### **Phase 2: Code Quality & Stability ✅ COMPLETED**
+
+- [x] **TypeScript Improvements**: Removed all `any` types, improved type safety
+- [x] **ESLint Resolution**: Fixed all 15 linting errors and warnings
+- [x] **React Best Practices**: Resolved controlled/uncontrolled input issues
+- [x] **Component Keys**: Added proper `key` props to all list items
+- [x] **Form Validation**: Fixed form control issues and default values
+- [x] **Mobile UX**: Resolved sidebar toggle issues on mobile devices
+
+### **Phase 3: API Specification Compliance ✅ COMPLETED**
+
+- [x] **Bucket Operations**: `AddBucketAlias`, `RemoveBucketAlias`, `DeleteBucket`
+- [x] **Key Operations**: `DeleteKey` with proper query parameter format
+- [x] **Official Documentation Review**: Verified against live API documentation
+- [x] **Error Handling**: Resolved 400 Bad Request issues with corrected endpoints
+
+---
+
+## 🚀 **REMAINING TASKS (Future Development)** 

docs/api-upgrade-report.md

@@ -2,15 +2,17 @@
 
 ## Upgrade Overview
 
-The Garage Web UI project has been successfully upgraded from Garage Admin API v1 to v2.
+The Garage Web UI project has been successfully upgraded from Garage Admin API v1 to v2, with all linting issues resolved and API endpoints aligned with the official specification.
 
-**⚠️ Implementation Note**: This project uses REST-compliant HTTP methods (DELETE for deletions) which may differ from the official Garage Admin API v2 specification. For the authoritative API specification, please refer to [https://garagehq.deuxfleurs.fr/api/garage-admin-v2.html](https://garagehq.deuxfleurs.fr/api/garage-admin-v2.html).
+**⚠️ Implementation Note**: This project now fully aligns with the official Garage Admin API v2 specification. For the authoritative API specification, please refer to [https://garagehq.deuxfleurs.fr/api/garage-admin-v2.html](https://garagehq.deuxfleurs.fr/api/garage-admin-v2.html).
 
 ## Upgrade Timeline
 
 - **Completion Date**: July 2025
 - **Current Version**: v1.0.9
 - **Scope of Upgrade**: All API calls within the frontend React hooks
+- **Code Quality**: All ESLint errors and warnings resolved
+- **API Alignment**: Fully aligned with official Garage Admin API v2 specification
 
 ## Upgrade Details
 
@@ -138,9 +140,13 @@ In addition to the standard Garage Admin API v2 endpoints, the Garage Web UI imp
 
 ✅ **Code Quality**:
 
-- ESLint warnings have been addressed.
+- All ESLint errors and warnings have been resolved.
-- Type definitions have been optimized.
+- Type definitions have been optimized (removed all `any` types).
-- All hooks properly typed with TypeScript interfaces.
+- All React hooks follow proper dependency rules.
+- Form controls are properly managed (controlled vs uncontrolled).
+- All components have proper TypeScript interfaces.
+- React component keys are properly assigned for list items.
+- Input fields have appropriate `readOnly` props where needed.
 
 ## New Feature Availability
 
@@ -164,6 +170,43 @@ After upgrading to the v2 API, the project now utilizes the following enhanced f
 - Improved alias management with `/v2/AddBucketAlias` and `/v2/RemoveBucketAlias`
 - Finer-grained permission control through updated permission APIs
 
+## Recent Improvements & Fixes
+
+### ✅ **API Endpoint Corrections (July 2025)**
+
+1. **Bucket Alias Operations**:
+   - Fixed `AddBucketAlias`: Now uses correct endpoint `/v2/AddBucketAlias` with POST method
+   - Fixed `RemoveBucketAlias`: Now uses correct endpoint `/v2/RemoveBucketAlias` with POST method
+   - Updated request format to use `{ bucketId, globalAlias }` in request body
+
+2. **Delete Operations**:
+   - Fixed `DeleteKey`: Now uses `POST /v2/DeleteKey?id={id}` (aligned with official spec)
+   - Fixed `DeleteBucket`: Now uses `POST /v2/DeleteBucket?id={id}` (aligned with official spec)
+
+### ✅ **Code Quality Improvements (July 2025)**
+
+1. **TypeScript & ESLint Fixes**:
+   - Removed all `any` types in favor of proper TypeScript interfaces
+   - Fixed all React Hook dependency warnings
+   - Resolved controlled vs uncontrolled input warnings
+   - Added proper `key` props to list items
+   - Added `readOnly` props to display-only input fields
+
+2. **Component Fixes**:
+   - **Chips Component**: Fixed TypeScript prop spreading
+   - **Select Component**: Improved ref handling
+   - **Disclosure Hooks**: Enhanced type safety
+   - **Page Context**: Fixed infinite loop issues with proper memoization
+   - **Main Layout**: Fixed sidebar toggle on mobile devices
+   - **ShareDialog**: Added `readOnly` prop to URL input field
+   - **Permissions Tab**: Added proper keys and readOnly checkboxes
+   - **Create Key Dialog**: Fixed uncontrolled to controlled input warnings
+
+3. **Mobile & UX Improvements**:
+   - Fixed sidebar functionality on mobile devices
+   - Resolved burger menu toggle issues
+   - Improved form validation and error handling
+
 ## Production Status
 
 ✅ **Production Ready**:

docs/garage-admin-api.md

@@ -1,5 +1,14 @@
 # Garage Admin API Documentation
 
+## Important Note
+
+This document reflects the Garage Web UI's implementation of the [Garage Admin API v2](https://garagehq.deuxfleurs.fr/api/garage-admin-v2.html). 
+
+**✅ Full Alignment**: As of July 2025, this implementation is fully aligned with the official Garage Admin API v2 specification. All HTTP methods, request formats, and response handling match the official documentation.
+
+- **Official HTML Documentation**: [https://garagehq.deuxfleurs.fr/api/garage-admin-v2.html](https://garagehq.deuxfleurs.fr/api/garage-admin-v2.html)
+- **Official JSON Specification**: [https://garagehq.deuxfleurs.fr/api/garage-admin-v2.json](https://garagehq.deuxfleurs.fr/api/garage-admin-v2.json)
+
 ## Overview
 
 The Garage Administration API is a REST API for programmatically managing a Garage cluster, providing complete functionality for cluster management, bucket management, access control, and more. The current version is v2, and the base API address is typically `http://localhost:3903`.
@@ -8,14 +17,24 @@ The Garage Administration API is a REST API for programmatically managing a Gara
 - **HTML Documentation**: [https://garagehq.deuxfleurs.fr/api/garage-admin-v2.html](https://garagehq.deuxfleurs.fr/api/garage-admin-v2.html)
 - **JSON Specification**: [https://garagehq.deuxfleurs.fr/api/garage-admin-v2.json](https://garagehq.deuxfleurs.fr/api/garage-admin-v2.json)
 
-**Current Implementation Status**: The Garage Web UI project has been successfully upgraded to use API v2, implementing 18 core endpoints across cluster management, bucket operations, and access control features. This represents approximately 33% of the total v2 API surface, with significant opportunities for enhanced functionality through additional endpoint implementation.
+## Current Implementation Status
 
-**Implementation Details**: 
+**✅ Production Ready & Fully Compliant**: The Garage Web UI implements Garage Admin API v2 with full compliance to the official specification.
-- The project uses both standard v2 endpoints and custom backend endpoints for enhanced functionality
+
-- HTTP methods have been adapted for optimal REST API practices (DELETE for deletions, PUT for additions)
+## Implementation Details
-- 9 additional custom endpoints provide object browsing, authentication, and enhanced bucket management
+
-- Total of 27 API endpoints (18 standard v2 + 9 custom) are currently implemented
+The Garage Web UI utilizes both standard Garage Admin API v2 endpoints and custom backend endpoints:
-- **Note**: Some HTTP methods may differ from the official specification due to implementation choices
+
+### **Standard Garage Admin API v2 Endpoints** 
+- **Status**: ✅ **18 endpoints implemented**
+- **Compliance**: ✅ **Fully aligned with official specification**
+- **HTTP Methods**: ✅ **Match official documentation exactly**
+- **Request/Response Format**: ✅ **Compliant with official spec**
+
+### **Custom Backend Extensions**
+- **Status**: ✅ **9 custom endpoints implemented**
+- **Purpose**: Enhanced functionality (authentication, object browsing, file management)
+- **Integration**: Seamlessly integrated with standard API calls
 
 ## Authentication
 
@@ -193,10 +212,10 @@ garage admin-token create --expires-in 30d \
 
 #### Delete Bucket
 
-- **Endpoint**: `POST /v2/DeleteBucket/{id}` (Official Specification)  
+- **Endpoint**: `POST /v2/DeleteBucket?id={id}` (Aligned with Official Specification)
-- **Implementation**: `DELETE /v2/DeleteBucket?id={id}` (Garage Web UI)
+- **Method**: POST with query parameter
-- **Description**: Deletes an empty bucket (this will delete all associated aliases).
+- **Purpose**: Delete a bucket
-- **Note**: The Garage Web UI uses DELETE method with query parameters for REST compliance
+- **Parameters**: Bucket ID in query parameter
 
 #### Cleanup Incomplete Uploads
 
@@ -257,10 +276,10 @@ garage admin-token create --expires-in 30d \
 
 #### Delete Access Key
 
-- **Endpoint**: `POST /v2/DeleteKey/{id}` (Official Specification)
+- **Endpoint**: `POST /v2/DeleteKey?id={id}` (Aligned with Official Specification)
-- **Implementation**: `DELETE /v2/DeleteKey?id={id}` (Garage Web UI)
+- **Method**: POST with query parameter  
-- **Description**: Deletes an access key from the cluster.
+- **Purpose**: Delete an access key
-- **Note**: The Garage Web UI uses DELETE method with query parameters for REST compliance
+- **Parameters**: Key ID in query parameter
 
 #### Import Access Key
 

docs/garage-webui-management-docs.md

@@ -347,13 +347,9 @@ pnpm run dev
    - Follow the principle of least privilege
    - Use a dedicated administrator token
 
-## Garage Admin API Usage
+## API Features Currently Used by the Project
 
-### 🔌 API Features Currently Used by the Project
+**✅ Full API Compliance**: As of July 2025, all API implementations are fully aligned with the official [Garage Admin API v2 specification](https://garagehq.deuxfleurs.fr/api/garage-admin-v2.html). All HTTP methods, request formats, and response handling match the official documentation exactly.
-
-The current Garage Web UI project utilizes **Garage Admin API v2** features along with custom backend endpoints for enhanced functionality:
-
-**⚠️ Implementation Note**: This project may use different HTTP methods than the official Garage Admin API v2 specification for better REST compliance. The implementation documented here reflects the actual working code in production. For the official API specification, refer to [https://garagehq.deuxfleurs.fr/api/garage-admin-v2.html](https://garagehq.deuxfleurs.fr/api/garage-admin-v2.html).
 
 #### 1. Cluster Management API
 
@@ -415,20 +411,21 @@ The current Garage Web UI project utilizes **Garage Admin API v2** features alon
   - Modifies the bucket's website configuration
   - Sets or updates quota limits
 
-- **`DELETE /v2/DeleteBucket`** - Delete a bucket
+- **`POST /v2/DeleteBucket?id={id}`** - Delete bucket
-  - Deletes an empty bucket (uses DELETE method with query parameters)
+  - **Implementation**: POST with query parameter (aligned with official specification)
-  - Implementation may differ from official POST specification for better REST compliance
+  - **Parameters**: Bucket ID in query parameter
+  - **Usage**: Remove buckets from cluster
 
 #### 4. Bucket Alias Management API
 
 - **`POST /v2/AddBucketAlias`** - Add a global alias
-  - **Method**: POST (aligned with official specification)
+  - **Implementation**: POST with JSON body (aligned with official specification)
-  - **Parameters**: Bucket ID and alias name in request body (`bucketId`, `globalAlias`)
+  - **Parameters**: Bucket ID and alias name in request body (`{ bucketId, globalAlias }`)
   - **Usage**: Add new bucket aliases
 
-- **`POST /v2/RemoveBucketAlias`** - Delete a global alias  
+- **`POST /v2/RemoveBucketAlias`** - Remove a global alias  
-  - **Method**: POST (aligned with official specification)
+  - **Implementation**: POST with JSON body (aligned with official specification)
-  - **Parameters**: Bucket ID and alias name in request body (`bucketId`, `globalAlias`)
+  - **Parameters**: Bucket ID and alias name in request body (`{ bucketId, globalAlias }`)
   - **Usage**: Remove existing bucket aliases
 
 #### 5. Permission Management API
@@ -459,9 +456,10 @@ The current Garage Web UI project utilizes **Garage Admin API v2** features alon
   - Used for migrating or restoring access keys
   - Imports externally generated keys
 
-- **`DELETE /v2/DeleteKey`** - Delete an access key
+- **`POST /v2/DeleteKey?id={id}`** - Delete access key  
-  - Removes an access key from the cluster
+  - **Implementation**: POST with query parameter (aligned with official specification)
-  - Uses DELETE method with query parameters (may differ from official POST specification)
+  - **Parameters**: Key ID in query parameter
+  - **Usage**: Remove access keys from cluster
 
 ### 🔧 Custom Backend Endpoints