@trafficgroup/knex-rel 0.1.6 → 0.1.7

package/plan.md

@@ -1,871 +0,0 @@
-# Total Vehicle Class Implementation Plan
-
-## Executive Summary
-
-This plan details the implementation of a "Total" vehicle class that aggregates all custom vehicle classes for both TMC and ATR minute results. The "Total" class will be added during transformation in the knex-rel module and will always appear as the LAST class in the vehicles object.
-
-**Key Requirements**:
-
-- Add "Total" class AFTER all custom classes
-- For ATR: "Total" reuses existing `lane_counts` (all classes per lane)
-- For TMC: "Total" sums all vehicle classes across all directions and turns
-- NO database schema changes required
-- Transformation happens in `ReportConfigurationDAO.applyConfigurationToNestedStructure()`
-
----
-
-## Current Architecture Analysis
-
-### Data Flow
-
-```
-1. Python Processor → Database (JSONB results with detection labels)
-   ↓
-2. VideoMinuteResultDAO → Retrieve raw minute results
-   ↓
-3. API Controller → Apply report configuration
-   ↓
-4. ReportConfigurationService.transformVideoResults()
-   ↓
-5. ReportConfigurationDAO.applyConfigurationToNestedStructure()
-   ↓
-6. Frontend → Display custom classes + Total
-```
-
-### Current Structure Patterns
-
-**ATR Format (Lane-based)**:
-
-```json
-{
-  "vehicles": {
-    "car": { "0": 45, "1": 50 },
-    "truck": { "0": 10, "1": 8 }
-  },
-  "lane_counts": { "0": 55, "1": 58 }, // Already has totals per lane!
-  "total_count": 113,
-  "study_type": "ATR"
-}
-```
-
-**TMC Format (Direction/Turn-based)**:
-
-```json
-{
-  "vehicles": {
-    "car": {
-      "NORTH": { "straight": 10, "left": 5, "right": 3, "u-turn": 0 },
-      "SOUTH": { "straight": 8, "left": 2, "right": 4, "u-turn": 1 }
-    },
-    "truck": {
-      "NORTH": { "straight": 5, "left": 1, "right": 0, "u-turn": 0 }
-    }
-  },
-  "counts": {
-    "total_vehicles": 39,
-    "entry_vehicles": 39
-  },
-  "study_type": "TMC"
-}
-```
-
-**After Custom Class Transformation** (2 custom classes: "Light" and "Heavy"):
-
-```json
-{
-  "vehicles": {
-    "Light": { "NORTH": { "straight": 10, "left": 5 }, ... },
-    "Heavy": { "NORTH": { "straight": 5, "left": 1 }, ... }
-  }
-}
-```
-
-**After Total Addition** (desired output):
-
-```json
-{
-  "vehicles": {
-    "Light": { "NORTH": { "straight": 10, "left": 5 }, ... },
-    "Heavy": { "NORTH": { "straight": 5, "left": 1 }, ... },
-    "Total": { "NORTH": { "straight": 15, "left": 6 }, ... }  // Sum of all classes
-  }
-}
-```
-
----
-
-## Implementation Location
-
-### File: `knex-rel/src/dao/report-configuration/report-configuration.dao.ts`
-
-**Method to Modify**: `applyConfigurationToNestedStructure()` (Lines 273-315)
-
-**Current Implementation**:
-
-1. Builds reverse mapping: detection label → custom class name (Lines 278-290)
-2. Initializes empty structure for each custom class (Lines 293-296)
-3. Iterates through detection labels and merges into custom classes (Lines 299-312)
-4. Returns transformed structure (Line 314)
-
-**Where to Add "Total"**: AFTER line 312, BEFORE return statement (Line 314)
-
----
-
-## Detailed Implementation Plan
-
-### Step 1: Add "Total" Class After Custom Class Transformation
-
-**Location**: `ReportConfigurationDAO.applyConfigurationToNestedStructure()` (After line 312)
-
-**Logic**:
-
-```typescript
-// After line 312 (end of detection label iteration)
-// Add "Total" class that aggregates all custom classes
-
-result["Total"] = this._createTotalClass(result);
-
-return result;
-```
-
-### Step 2: Implement `_createTotalClass()` Helper Method
-
-**Location**: Add new private method in `ReportConfigurationDAO` class (After line 350)
-
-**Method Signature**:
-
-```typescript
-private _createTotalClass(customClassesData: Record<string, any>): any
-```
-
-**Implementation**:
-
-```typescript
-/**
- * Create "Total" class by aggregating all custom vehicle classes
- *
- * Handles both ATR and TMC formats:
- * - ATR: Aggregates counts per lane across all vehicle classes
- * - TMC: Aggregates counts per direction and turn across all vehicle classes
- *
- * @param customClassesData - Transformed custom classes structure
- * @returns Aggregated totals matching the same nested structure
- */
-private _createTotalClass(customClassesData: Record<string, any>): any {
-    const total: any = {};
-
-    // Iterate through all custom classes and merge their data
-    for (const [className, nestedData] of Object.entries(customClassesData)) {
-        // Use existing _deepMergeNumericData to sum all nested values
-        Object.assign(total, this._deepMergeNumericData(total, nestedData));
-    }
-
-    return total;
-}
-```
-
-**Explanation**:
-
-- Reuses existing `_deepMergeNumericData()` helper (Lines 328-350)
-- Works for both ATR (2-level: vehicle → lane → count) and TMC (3-level: vehicle → direction → turn → count)
-- No need to detect study type - structure-agnostic aggregation
-- Handles empty data (returns empty object `{}`)
-
----
-
-## Key Ordering Strategy
-
-### Ensuring "Total" Appears Last
-
-JavaScript object key ordering is preserved in modern engines (ES2015+) when:
-
-1. String keys are added in insertion order
-2. Keys are enumerated via `Object.entries()`, `Object.keys()`, `for...in`
-
-**Our Implementation**:
-
-```typescript
-// Lines 293-296: Initialize custom classes FIRST (insertion order)
-for (const customClass of config.configuration.customClasses) {
-  result[customClass.name] = {};
-}
-
-// Lines 299-312: Populate custom classes (preserves order)
-for (const [detectionLabel, nestedData] of Object.entries(vehiclesStructure)) {
-  // ... merge logic
-}
-
-// NEW: Add "Total" LAST (after all custom classes)
-result["Total"] = this._createTotalClass(result);
-
-// Line 314: Return result (Total is last key)
-return result;
-```
-
-**Why This Works**:
-
-- Custom classes initialized in config order (Lines 293-296)
-- "Total" added AFTER all custom classes (new code)
-- JavaScript guarantees insertion order preservation
-- Frontend will render "Total" as last tab
-
----
-
-## ATR vs TMC Behavior
-
-### ATR (Lane-Based Totals)
-
-**Input Structure**:
-
-```json
-{
-  "Light": { "0": 45, "1": 50 },
-  "Heavy": { "0": 10, "1": 8 }
-}
-```
-
-**Total Output**:
-
-```json
-{
-  "Total": { "0": 55, "1": 58 } // Sum per lane
-}
-```
-
-**Calculation**:
-
-- Lane "0": 45 (Light) + 10 (Heavy) = 55
-- Lane "1": 50 (Light) + 8 (Heavy) = 58
-
-**Alternative (Use existing `lane_counts`)**:
-
-The ATR structure ALREADY has `lane_counts` at the top level:
-
-```json
-{
-  "vehicles": { "Light": {...}, "Heavy": {...} },
-  "lane_counts": { "0": 55, "1": 58 }  // Already calculated!
-}
-```
-
-**Decision**: For ATR, we can EITHER:
-
-1. ✅ **Option A (Recommended)**: Calculate "Total" by summing custom classes (consistent with TMC)
-2. ⚠️ **Option B**: Copy `lane_counts` directly into `vehicles["Total"]` (reuses existing data)
-
-**Recommendation**: Use Option A (sum custom classes) for consistency with TMC, even though Option B is technically available.
-
-### TMC (Direction/Turn-Based Totals)
-
-**Input Structure**:
-
-```json
-{
-  "Light": {
-    "NORTH": { "straight": 10, "left": 5, "right": 3 },
-    "SOUTH": { "straight": 8, "left": 2, "right": 4 }
-  },
-  "Heavy": {
-    "NORTH": { "straight": 5, "left": 1, "right": 0 },
-    "SOUTH": { "straight": 2, "left": 0, "right": 1 }
-  }
-}
-```
-
-**Total Output**:
-
-```json
-{
-  "Total": {
-    "NORTH": { "straight": 15, "left": 6, "right": 3 },
-    "SOUTH": { "straight": 10, "left": 2, "right": 5 }
-  }
-}
-```
-
-**Calculation**:
-
-- NORTH/straight: 10 (Light) + 5 (Heavy) = 15
-- NORTH/left: 5 (Light) + 1 (Heavy) = 6
-- SOUTH/straight: 8 (Light) + 2 (Heavy) = 10
-- etc.
-
----
-
-## Edge Cases & Validation
-
-### Edge Case 1: Empty Data (No Vehicles)
-
-**Input**:
-
-```json
-{
-  "vehicles": {}
-}
-```
-
-**After Transformation**:
-
-```json
-{
-  "vehicles": {
-    "Light": {},
-    "Heavy": {},
-    "Total": {} // Empty object
-  }
-}
-```
-
-**Behavior**: `_createTotalClass()` returns empty object `{}`
-
-### Edge Case 2: Single Custom Class
-
-**Input**:
-
-```json
-{
-  "vehicles": {
-    "AllVehicles": { "0": 100, "1": 95 }
-  }
-}
-```
-
-**Output**:
-
-```json
-{
-  "vehicles": {
-    "AllVehicles": { "0": 100, "1": 95 },
-    "Total": { "0": 100, "1": 95 } // Same as single class
-  }
-}
-```
-
-**Behavior**: "Total" equals the single custom class (valid)
-
-### Edge Case 3: Missing Directions/Turns
-
-**Input** (TMC - Light has NORTH, Heavy only has SOUTH):
-
-```json
-{
-  "Light": { "NORTH": { "straight": 10 } },
-  "Heavy": { "SOUTH": { "straight": 5 } }
-}
-```
-
-**Output**:
-
-```json
-{
-  "Total": {
-    "NORTH": { "straight": 10 },
-    "SOUTH": { "straight": 5 }
-  }
-}
-```
-
-**Behavior**: `_deepMergeNumericData()` handles missing keys gracefully (Lines 339-347)
-
-### Edge Case 4: Null/Undefined Values
-
-**Input**:
-
-```json
-{
-  "Light": { "0": 10, "1": null },
-  "Heavy": { "0": 5 }
-}
-```
-
-**Output**:
-
-```json
-{
-  "Total": { "0": 15, "1": 0 } // null treated as 0
-}
-```
-
-**Behavior**: `_deepMergeNumericData()` checks `typeof source === 'number'` (Line 330)
-
----
-
-## Testing Strategy
-
-### Unit Tests (to be created)
-
-**File**: `knex-rel/src/dao/report-configuration/report-configuration.dao.test.ts`
-
-**Test Cases**:
-
-1. **ATR: Total Class Aggregation**
-   - Input: 2 custom classes with lane counts
-   - Verify: Total sums all lanes correctly
-   - Verify: Total appears as last key
-
-2. **TMC: Total Class Aggregation**
-   - Input: 2 custom classes with direction/turn structure
-   - Verify: Total sums all directions and turns
-   - Verify: Total appears as last key
-
-3. **Edge Case: Empty Vehicles**
-   - Input: No vehicle data
-   - Verify: Total is empty object `{}`
-
-4. **Edge Case: Single Custom Class**
-   - Input: 1 custom class
-   - Verify: Total equals the single class
-
-5. **Edge Case: Missing Directions**
-   - Input: Asymmetric direction/turn data
-   - Verify: Total includes all unique keys
-
-6. **Key Ordering Test**
-   - Input: 5 custom classes
-   - Verify: Total is the 6th key (last)
-   - Verify: `Object.keys(result)` ends with "Total"
-
-### Integration Tests
-
-**Test in api-rel controller**:
-
-1. Create video with ATR results
-2. Apply configuration with 3 custom classes
-3. Call `GET /videos/:uuid/results?configUuid=...`
-4. Verify response includes "Total" as last class
-5. Verify Total values equal sum of custom classes
-
-**Test in traffic-webapp**:
-
-1. Display video results with custom classes
-2. Verify "Total" tab appears last
-3. Verify Total chart shows aggregated data
-4. Test with both ATR and TMC videos
-
----
-
-## Performance Considerations
-
-### Computational Complexity
-
-**Current**: O(n × m) where:
-
-- n = number of detection labels
-- m = average nesting depth (2 for ATR, 3 for TMC)
-
-**After Adding Total**: O(n × m + c × m) where:
-
-- c = number of custom classes (2-7 per validation)
-
-**Impact**: Minimal - additional O(c × m) is negligible
-
-- c ≤ 7 (max custom classes)
-- m ≤ 3 (max nesting depth)
-- Total iteration: ~21 operations per minute result
-
-### Memory Impact
-
-**Additional Memory**: One new key per transformed result
-
-- ATR Total: ~100 bytes (lanes object)
-- TMC Total: ~500 bytes (directions/turns object)
-- Per minute result: negligible
-- For 60 minutes: ~6-30 KB additional
-
-**Conclusion**: No performance concerns
-
----
-
-## Backward Compatibility
-
-### Changes Are Additive Only
-
-✅ **No Breaking Changes**:
-
-- Existing custom classes remain unchanged
-- Existing API response structure preserved
-- "Total" is a NEW key (optional to consume)
-
-✅ **Frontend Compatibility**:
-
-- Old frontend: Ignores "Total" key (no errors)
-- New frontend: Displays "Total" as last tab
-
-✅ **Database Compatibility**:
-
-- No schema changes required
-- Raw results in database unchanged
-- Transformation happens at runtime
-
----
-
-## Implementation Checklist
-
-### Pre-Implementation
-
-- [x] Analyze current transformation logic
-- [x] Identify exact insertion point (line 312)
-- [x] Verify `_deepMergeNumericData()` handles both ATR/TMC
-- [x] Confirm JavaScript key ordering guarantees
-
-### Implementation Phase
-
-- [ ] Add `_createTotalClass()` helper method after line 350
-- [ ] Add "Total" class insertion after line 312 in `applyConfigurationToNestedStructure()`
-- [ ] Add JSDoc comments for new method
-- [ ] Verify TypeScript compilation: `npm run build`
-
-### Testing Phase
-
-- [ ] Write unit tests for `_createTotalClass()`
-- [ ] Test ATR format (lane-based totals)
-- [ ] Test TMC format (direction/turn totals)
-- [ ] Test edge cases (empty, single class, missing keys)
-- [ ] Test key ordering (Total is last)
-- [ ] Run all tests: `npm test`
-
-### Integration Phase
-
-- [ ] Build knex-rel: `npm run build`
-- [ ] Test in api-rel: `npm run start:dev`
-- [ ] Call `/videos/:uuid/results` endpoint with ATR video
-- [ ] Call `/videos/:uuid/results` endpoint with TMC video
-- [ ] Verify "Total" appears in response as last class
-- [ ] Verify Total values are correct sums
-
-### Frontend Integration (Separate Task)
-
-- [ ] Update traffic-webapp to display "Total" tab
-- [ ] Position "Total" tab as last tab
-- [ ] Render Total data in charts/tables
-- [ ] Test with both ATR and TMC videos
-
----
-
-## Code Changes Summary
-
-### File 1: `knex-rel/src/dao/report-configuration/report-configuration.dao.ts`
-
-**Location 1: After Line 312 (Inside `applyConfigurationToNestedStructure()`)**
-
-```typescript
-// Lines 299-312: Existing iteration through detection labels
-for (const [detectionLabel, nestedData] of Object.entries(vehiclesStructure)) {
-  const customClassName = detectionToCustomClass[detectionLabel];
-  if (!customClassName) {
-    continue;
-  }
-  result[customClassName] = this._deepMergeNumericData(
-    result[customClassName],
-    nestedData,
-  );
-}
-
-// NEW CODE: Add "Total" class that aggregates all custom classes
-result["Total"] = this._createTotalClass(result);
-
-return result;
-```
-
-**Location 2: After Line 350 (New Private Method)**
-
-```typescript
-/**
- * Create "Total" class by aggregating all custom vehicle classes
- *
- * Sums all custom class counts across their nested structures.
- * Works for both ATR (lane-based) and TMC (direction/turn-based) formats.
- *
- * @param customClassesData - Transformed custom classes structure
- *                            Example ATR: { "Light": { "0": 45, "1": 50 }, "Heavy": { "0": 10 } }
- *                            Example TMC: { "Light": { "NORTH": { "straight": 10 } }, ... }
- * @returns Aggregated totals matching the same nested structure
- *          Example ATR: { "0": 55, "1": 50 }
- *          Example TMC: { "NORTH": { "straight": 10 }, ... }
- */
-private _createTotalClass(customClassesData: Record<string, any>): any {
-    let total: any = {};
-
-    // Iterate through all custom classes and merge their data
-    for (const [className, nestedData] of Object.entries(customClassesData)) {
-        total = this._deepMergeNumericData(total, nestedData);
-    }
-
-    return total;
-}
-```
-
----
-
-## Validation Plan
-
-### Manual Testing Checklist
-
-**Test 1: ATR Video (2 Custom Classes)**
-
-- [ ] Create configuration: "Light" (FHWA 1-3), "Heavy" (FHWA 4-13)
-- [ ] Upload ATR video with mixed vehicle types
-- [ ] Process video and get results
-- [ ] Verify "Light" shows cars/motorcycles per lane
-- [ ] Verify "Heavy" shows trucks/buses per lane
-- [ ] Verify "Total" shows sum of Light + Heavy per lane
-- [ ] Verify "Total" is last key in vehicles object
-
-**Test 2: TMC Video (3 Custom Classes)**
-
-- [ ] Create configuration: "Cars", "Trucks", "Buses"
-- [ ] Upload TMC video with turning movements
-- [ ] Process video and get results
-- [ ] Verify each class shows direction/turn breakdown
-- [ ] Verify "Total" shows sum across all classes
-- [ ] Verify NORTH/straight in Total = sum of all classes' NORTH/straight
-- [ ] Verify "Total" is last key in vehicles object
-
-**Test 3: Edge Cases**
-
-- [ ] Video with no vehicles detected (empty Total)
-- [ ] Video with single custom class (Total equals that class)
-- [ ] Video with asymmetric turns (Light has left, Heavy doesn't)
-- [ ] Configuration with 7 custom classes (max allowed)
-
-**Test 4: Grouped Results (Multiple Minutes)**
-
-- [ ] Get grouped results with grouping=15
-- [ ] Verify each timeGroup has "Total" class
-- [ ] Verify "Total" sums correctly across aggregated minutes
-- [ ] Verify ordering preserved in all timeGroups
-
----
-
-## Risks & Mitigations
-
-### Risk 1: Key Ordering Not Guaranteed
-
-**Risk**: JavaScript object keys might not preserve insertion order
-
-**Likelihood**: Very Low (ES2015+ guarantees string key order)
-
-**Mitigation**:
-
-- Add unit test to verify `Object.keys(result)` ends with "Total"
-- If ordering fails, use explicit ordering array in frontend
-
-### Risk 2: Performance Degradation
-
-**Risk**: Additional aggregation adds processing time
-
-**Likelihood**: Very Low (O(c × m) is negligible)
-
-**Mitigation**:
-
-- Benchmark transformation time before/after
-- If impact > 10ms, consider caching Total class
-
-### Risk 3: Frontend Breaks on Unknown Class
-
-**Risk**: Old frontend version throws error on "Total" key
-
-**Likelihood**: Very Low (key is additive, not breaking)
-
-**Mitigation**:
-
-- "Total" is just another custom class name
-- Frontend already iterates dynamic class names
-- No special handling needed
-
-### Risk 4: Incorrect Aggregation Logic
-
-**Risk**: `_deepMergeNumericData()` doesn't handle all cases
-
-**Likelihood**: Low (method already tested for custom class merging)
-
-**Mitigation**:
-
-- Comprehensive unit tests for edge cases
-- Manual validation with real ATR/TMC videos
-- Use existing, battle-tested `_deepMergeNumericData()`
-
----
-
-## Alternative Approaches Considered
-
-### Alternative 1: Add "Total" in Frontend
-
-**Approach**: Calculate "Total" in traffic-webapp instead of backend
-
-**Pros**:
-
-- No backend changes required
-- Frontend controls display logic
-
-**Cons**:
-
-- Duplicates logic across frontend
-- Inconsistent if API consumed elsewhere
-- Cannot use "Total" in backend reports/exports
-
-**Decision**: ❌ Rejected - Backend is single source of truth
-
-### Alternative 2: Add "Total" as Separate Field
-
-**Approach**: Add `results.totalClass` instead of `results.vehicles["Total"]`
-
-**Pros**:
-
-- Clearer separation of concerns
-- No risk of key ordering issues
-
-**Cons**:
-
-- Inconsistent with custom class structure
-- Frontend needs special handling
-- Breaks uniform class iteration logic
-
-**Decision**: ❌ Rejected - Keep "Total" as vehicle class for uniformity
-
-### Alternative 3: Make "Total" Configurable
-
-**Approach**: Add `includeTotalClass: boolean` to report configuration
-
-**Pros**:
-
-- User control over Total display
-- Backward compatible (default false)
-
-**Cons**:
-
-- Adds complexity to configuration
-- Not needed (Total is always useful)
-- Extra validation logic
-
-**Decision**: ❌ Rejected - Always include "Total" (KISS principle)
-
----
-
-## Success Criteria
-
-### Implementation Success
-
-✅ TypeScript compiles without errors
-✅ `npm run build` succeeds in knex-rel
-✅ All existing unit tests pass
-✅ New unit tests pass (Total class logic)
-
-### Functional Success
-
-✅ ATR videos show "Total" with correct lane sums
-✅ TMC videos show "Total" with correct direction/turn sums
-✅ "Total" appears as LAST class in all responses
-✅ Edge cases handled (empty, single class, missing keys)
-
-### Integration Success
-
-✅ API endpoint returns "Total" in response
-✅ Grouped results include "Total" in each timeGroup
-✅ No breaking changes to existing API consumers
-✅ Frontend displays "Total" tab correctly (separate task)
-
----
-
-## Timeline Estimate
-
-### Backend Implementation (knex-rel)
-
-- Code changes: 30 minutes
-- Unit tests: 1 hour
-- Build & test: 15 minutes
-- **Total: ~2 hours**
-
-### Integration Testing (api-rel)
-
-- Manual testing with ATR video: 30 minutes
-- Manual testing with TMC video: 30 minutes
-- Edge case validation: 30 minutes
-- **Total: ~1.5 hours**
-
-### Frontend Integration (traffic-webapp - Separate)
-
-- Display "Total" tab: 1 hour
-- Chart/table rendering: 1 hour
-- Testing both video types: 1 hour
-- **Total: ~3 hours**
-
-**Overall Estimate: ~6.5 hours** (Backend: 3.5 hours, Frontend: 3 hours)
-
----
-
-## Summary
-
-### What Changes
-
-✅ **ADD**: `_createTotalClass()` private method in ReportConfigurationDAO
-✅ **ADD**: `result["Total"] = ...` line after custom class transformation
-✅ **ADD**: Unit tests for Total class aggregation
-
-### What Stays the Same
-
-✅ Database schema (no migrations)
-✅ Existing custom classes (no modifications)
-✅ API response structure (additive only)
-✅ `_deepMergeNumericData()` helper (reused, not changed)
-
-### Key Benefits
-
-✅ Unified "Total" view across all custom classes
-✅ Consistent with existing transformation architecture
-✅ No breaking changes (backward compatible)
-✅ Minimal performance impact (< 1ms per minute result)
-✅ Reuses existing, tested aggregation logic
-
-**Ready for Implementation** - Plan is complete with exact code locations, logic, edge cases, and validation strategy.
-
----
-
-## Files to Modify
-
-### knex-rel/src/dao/report-configuration/report-configuration.dao.ts
-
-- **Line 312**: Add `result["Total"] = this._createTotalClass(result);`
-- **After Line 350**: Add `_createTotalClass()` private method
-
-### knex-rel/src/dao/report-configuration/report-configuration.dao.test.ts (New File)
-
-- Create unit tests for Total class aggregation
-- Test ATR format, TMC format, edge cases, key ordering
-
----
-
-## Pattern Compliance Summary
-
-### Database Patterns ✅
-
-- No database changes required (transformation only)
-- Follows DAO pattern (logic in ReportConfigurationDAO)
-- No new migrations needed
-
-### Code Patterns ✅
-
-- Reuses existing `_deepMergeNumericData()` helper
-- Follows private method naming convention (`_methodName`)
-- Maintains nested structure consistency
-- Preserves key ordering via insertion order
-
-### Performance Patterns ✅
-
-- O(c × m) additional complexity (negligible)
-- No N+1 queries (transformation in memory)
-- No database roundtrips
-- Minimal memory overhead (~500 bytes per result)
-
----
-
-## Next Steps
-
-1. **Implement** `_createTotalClass()` method in ReportConfigurationDAO
-2. **Add** Total class insertion after line 312
-3. **Write** unit tests for all edge cases
-4. **Build** knex-rel package and verify compilation
-5. **Test** with real ATR and TMC videos in api-rel
-6. **Validate** key ordering and correct aggregation
-7. **Document** changes (if needed)
-8. **Coordinate** with frontend team for Total tab display