docs: Update specifications to reflect configuration management implementation

Updated all spec-kit documents to document the implemented configuration
management features (User Story 12):

Changes:
- spec.md: Added User Story 12 with implementation status and functional
  requirements (FR-039 through FR-045)
- plan.md: Added Phase 2 (Configuration Management) as completed, updated
  phase status and last updated date
- data-model.md: Added GCoreServer entity with schema, validation rules,
  CRUD status, and critical implementation details
- tasks.md: Added Phase 13 for User Story 12 with implementation summary,
  updated task counts and dependencies
- tasks-revised-mvp.md: Added configuration management completion notice

Implementation Highlights:
- G-Core Server CRUD (CREATE, READ, DELETE working; UPDATE has known bug)
- Action Mapping CRUD (all operations working)
- SetupClient integration for .set file operations
- Critical cascade deletion bug fix (delete in reverse order)
- Comprehensive test scripts and verification tools

Documentation: SERVER_CRUD_IMPLEMENTATION.md, CRITICAL_BUG_FIX_DELETE.md

🤖 Generated with Claude Code (https://claude.com/claude-code)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

specs/001-surveillance-api/tasks.md

@@ -459,7 +459,60 @@ This project uses **web application structure**:
 
 ---
 
-## Phase 13: Polish & Cross-Cutting Concerns
+## Phase 13: User Story 12 - GeViSoft Configuration Management (Priority: P1) ✅ IMPLEMENTED (2025-12-16)
+
+**Goal**: Manage GeViSoft configuration (G-Core servers, action mappings) via REST API
+
+**Implementation Status**: CRUD operations working with critical bug fixes applied
+
+### Implementation Summary (Completed)
+
+**REST API Endpoints**:
+- ✅ `GET /api/v1/configuration/servers` - List all G-Core servers
+- ✅ `GET /api/v1/configuration/servers/{server_id}` - Get single server
+- ✅ `POST /api/v1/configuration/servers` - Create new server
+- ⚠️ `PUT /api/v1/configuration/servers/{server_id}` - Update server (known bug)
+- ✅ `DELETE /api/v1/configuration/servers/{server_id}` - Delete server
+- ✅ `GET /api/v1/configuration/action-mappings` - List all action mappings
+- ✅ `GET /api/v1/configuration/action-mappings/{mapping_id}` - Get single mapping
+- ✅ `POST /api/v1/configuration/action-mappings` - Create mapping
+- ✅ `PUT /api/v1/configuration/action-mappings/{mapping_id}` - Update mapping
+- ✅ `DELETE /api/v1/configuration/action-mappings/{mapping_id}` - Delete mapping
+
+**gRPC SDK Bridge**:
+- ✅ ConfigurationService implementation
+- ✅ SetupClient integration for .set file operations
+- ✅ FolderTreeParser for binary configuration parsing
+- ✅ FolderTreeWriter for configuration updates
+- ✅ CreateServer, UpdateServer, DeleteServer methods
+- ✅ CreateActionMapping, UpdateActionMapping, DeleteActionMapping methods
+- ✅ ReadConfigurationTree for querying configuration
+
+**Critical Fixes**:
+- ✅ **Cascade Deletion Bug**: Fixed deletion order issue (delete in reverse order)
+- ✅ **Bool Type Handling**: Proper bool type usage for GeViSet compatibility
+- ✅ **Auto-increment Server IDs**: Find highest numeric ID and increment
+
+**Test Scripts**:
+- ✅ `comprehensive_crud_test.py` - Full CRUD verification
+- ✅ `safe_delete_test.py` - Cascade deletion fix verification
+- ✅ `server_manager.py` - Production server management
+- ✅ `cleanup_to_base.py` - Configuration reset utility
+- ✅ `verify_config_via_grpc.py` - Configuration verification
+
+**Documentation**:
+- ✅ `SERVER_CRUD_IMPLEMENTATION.md` - Complete implementation guide
+- ✅ `CRITICAL_BUG_FIX_DELETE.md` - Bug analysis and fix documentation
+- ✅ Updated spec.md with User Story 12 and functional requirements
+
+**Known Issues**:
+- ⚠️ Server UPDATE method has "Server ID is required" bug (workaround: delete and recreate)
+
+**Checkpoint**: Configuration management complete - can manage G-Core servers and action mappings via API
+
+---
+
+## Phase 14: Polish & Cross-Cutting Concerns
 
 **Purpose**: Improvements that affect multiple user stories
 
@@ -535,6 +588,7 @@ Phase 13: Polish
 - **US8 (NPR Integration)**: Depends on US4, US6 completion
 - **US9 (Video Export)**: Depends on US5 completion
 - **US10 (Health Monitoring)**: Can start after Foundational
+- **US12 (Configuration Management)**: ✅ COMPLETED - Depends on Foundational only
 
 ### Parallel Opportunities
 
@@ -552,13 +606,13 @@ Phase 13: Polish
 - [Similar pattern for all user stories]
 
 **Across User Stories** (if team capacity allows):
-- After Foundational completes: US1 can start
+- After Foundational completes: US1, US10, US12 can start in parallel
 - After US1 completes: US2, US5 can start in parallel
 - After US2 completes: US3, US4, US7 can start in parallel
 - After US4 completes: US6 can start
 - After US5 completes: US9 can start
 - After US6 completes: US8 can start
-- US10 can start any time after Foundational
+- US12 ✅ COMPLETED (Configuration Management)
 
 **Polish Phase**: T198-T212, T214-T215 all marked [P] can run in parallel
 
@@ -683,9 +737,11 @@ With 3 developers after Foundational phase completes:
 - Phase 10 (US8 - NPR Integration): 12 tasks
 - Phase 11 (US9 - Video Export): 14 tasks
 - Phase 12 (US10 - Health Monitoring): 14 tasks
-- Phase 13 (Polish): 18 tasks
+- Phase 13 (US12 - Configuration Management): ✅ COMPLETED (2025-12-16)
+- Phase 14 (Polish): 18 tasks
 
 **MVP Tasks** (Phases 1-6): 112 tasks
+**Configuration Management**: ✅ Implemented separately (not part of original task breakdown)
 
 **Tests**: 80+ test tasks (all marked TDD - write first, ensure FAIL)
 
@@ -711,4 +767,5 @@ With 3 developers after Foundational phase completes:
 ---
 
 **Generated**: 2025-12-08
-**Based on**: spec.md (10 user stories), plan.md (tech stack), data-model.md (7 entities), contracts/openapi.yaml (17 endpoints)
+**Updated**: 2025-12-16 (Configuration Management implemented)
+**Based on**: spec.md (12 user stories), plan.md (tech stack), data-model.md (8 entities), contracts/openapi.yaml (27+ endpoints)