- height:100vh (not min-height) so align-items:stretch actually works
- Footer shows when expanded, hides when collapsed (dynamic class)
- Remove align-self:stretch (unnecessary with flex stretch)
- Restore flex-shrink on divider
- Replace v-show with CSS .gs-nav-label + .collapsed display: none
- Use CSS class .gs-hidden instead of v-show for footer/divider
- Fix content not re-displaying after collapse/expand
- Add 'Face Group' mode to search modes
- Use search_identities API temporarily
- Update summary: 'Identity' → 'FS'
- Will replace with Core Team's search_tkg_node_face_trace_profile API
- Rename computed property to match current API semantics
- face_groups are definitive, not pending
- Add detailed console.log for debugging empty groups issue
- Explicitly define data source for Move Faces Modal
- Use clusterAsPending directly
- Add console.log for debugging
Purpose: Diagnose why only one group shows in Move Faces Modal
Problem:
- Some groups may not have name field
- Display would show blank or undefined
Solution:
- Add fallback: c.name || 'Unnamed Group'
- Add fallback: c.trace_count || 0
- Ensures always shows meaningful text
Impact:
- Move Faces Modal now always shows group names
- No blank entries even with incomplete data
Replace merge_trace implementation with merge_groups API
Changes:
1. src/api/index.ts:
- Add merge_groups API definition
- POST /api/v1/file/:file_uuid/groups/merge
- Parameters: file_uuid, source_groups[], target_group_name
2. src/views/PeopleView.vue:
- Rewrite executeMerge() function
- Use group names instead of trace IDs
- Single API call for all groups
- Remove trace-level loop
3. src/views/PeopleView.vue:
- Delete updateClusterAfterMerge() function
- No longer needed with new API
Benefits:
- ✅ Atomic operation (single API call)
- ✅ Correct merge behavior (groups, not traces)
- ✅ Better performance (1 call vs N calls)
- ✅ Data consistency guaranteed
API behavior:
- Merge N groups into 1 target group
- All traces from source groups merged to target
- Source groups deleted after merge
- Returns traces_merged count
Core API: Implemented by Core Team (2026-07-25)
Status: Ready for testing
Display format with # separator:
- Frame: F#{number} (e.g., F#333)
- Face Trace: FS#{number} (e.g., FS#233)
Changes:
- Line 105: Frame range display (F#2219–F#2225)
- Line 143: Face Detail Modal (file_uuid:FS#233)
- Line 262: Cluster strip fallback (FS#233)
- Line 264: Cluster strip label (FS#233)
Benefits:
- # separator makes ID clearer
- Consistent format across all displays
- Visual distinction between type and number
- Import BuildVersion component
- Add to template (top-right corner fixed)
- Visible on all views
Build version format: 20260725133504-gitHash
Shows in top-right corner with monospace font
Critical bug fix:
- updateClusterAfterMerge() was called after EACH trace merge
- This caused source group to be deleted after first trace
- Remaining traces had no group to merge into
Problem flow:
1. Merge trace #1 from Group B → Group A
2. updateClusterAfterMerge(B, A) deletes Group B
3. Try to merge trace #2 from Group B → Group B is gone!
4. Result: All source groups deleted after first trace
Solution:
- Remove updateClusterAfterMerge() from loop
- Let all traces merge successfully
- Reload cluster data at the end (Line 1813)
- Core API handles the merge, we just refresh UI
Impact:
- Merge now works correctly for all traces in a group
- No premature deletion of source groups
- UI refreshes after all operations complete
Problem:
- After merge, source groups become empty
- Empty groups stay in UI as garbage data
- User sees empty groups with 0 faces
Solution:
- updateClusterAfterMerge() now removes source groups after merge
- Added removal from clusterAsPending computed property
- Ensures clean UI after merge operation
Behavior:
- Source group is deleted after all members merged to target
- Target group receives all members
- No empty groups left in UI
Related: merge functionality debug logging added in previous commit
Add debug logs to diagnose merge not working issue:
1. batchMergeGroups():
- Log selected groupIds
- Log mergeCandidateGroups count
2. executeMerge():
- Log targetGroupId and targetGroup
- Log targetTraceId type and value
- Log targetTrace data
- Log sourceGroups count
- Log totalTraces and validTraces
- Log each merge_trace API call params
- Log success/fail counts
Purpose: Identify why merge fails when move works
Next: Check browser console for specific errors
Problem:
- 'F13' display text confused with Frame numbers
- Users cannot distinguish between Trace ID and Frame Number
Solution:
- Change display format from 'F{trace_id}' to 'Face{trace_id}'
- Example: F13 → Face13, F142 → Face142
Changes:
- src/views/PeopleView.vue:264 - Cluster Detail Modal label
Benefits:
- Clear semantic meaning (Face vs Frame)
- No ambiguity for users
- Display layer only, data layer unchanged (still trace_id)
Problem:
- rule1_ingestion weight was 0.10 (should be 0.05)
- face_tracing weight was 0.10 (should be 0.05)
- identity_agent was filtered out (should be included with 0.10)
- Progress percentage calculation was incorrect
Solution:
1. Correct weights based on Core team specifications
2. Remove identity_agent filter (now part of pipeline)
3. Use correct weights:
- processors: 0.30
- rule1_ingestion: 0.05
- face_tracing: 0.05
- identity_agent: 0.10
- tkg_nodes: 0.20
- tkg_edges: 0.15
- rule2_ingestion: 0.15
Impact:
- Progress percentage now accurately reflects pipeline completion
- All stages properly tracked and weighted
Thanks Core team for the correct weight configuration!
Problem:
- syncFileStatus() doesn't load pipeline progress data
- Files stuck in 'processing' without percentage display
- pollPipelineProgress() not started when pipeline data missing
Solution:
1. Add loadPipelineStats() call in syncFileStatus() for processing files
2. Start pollPipelineProgress() even when pipeline data is missing
3. Ensure progress bar always has data to display
Impact:
- Progress bar now shows percentage during deep scan
- Files no longer stuck in 'processing' state indefinitely
- Better handling of edge cases when API data is missing
Related: Core team needs to verify get_pipeline_stats API accuracy
Problem:
- Status badge showed 'Scanning'
- Progress bar showed 'Processing...'
- Two different texts displayed simultaneously
Solution:
- Change progress bar text to 'Scanning...'
- Now both badge and progress bar use consistent terminology
Responsive Design:
- Mobile (<768px): 98% width, 50vh video height
- Tablet (769-1024px): 900px max, 65vh video
- Desktop (1025-1440px): 1000px max, 70vh video
- Large (1441px+): 1200px max, 75vh video (advanced)
- Ultra-wide (21:9 aspect): 60vh video height
Features:
- min() for max-width to prevent overflow
- min() for max-height to respect viewport
- calc() for dynamic height calculation
- Aspect ratio media query for ultra-wide screens
- Flexible toggle wrap on mobile
Advanced Mode Enhancements:
- Processor visibility toggles (ASRX/OCR/Face/Pose)
- Toggle switches to show/hide each processor type
- Larger video size in advanced mode (1200px vs 720px)
- Video max-height increased to 75vh
Features:
- showAsrxInPlayer/showOcrInPlayer/showFaceInPlayer/showPoseInPlayer refs
- visibleTags computed respects toggle state
- ms-proc-toggles UI with colored labels
- ms-modal-video-advanced CSS class
