momentry_studio

Author	SHA1	Message	Date
Momentry Studio	cb7ebfb633	feat: add Face Group search mode back to SearchView - 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	2026-07-25 19:24:54 +08:00
Momentry Studio	e7f9740e72	refactor: change face trace display from 'F{id}' to 'Face{id}' 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)	2026-07-25 13:11:47 +08:00
Momentry Studio	70889b25d1	docs: update Core Team response - deployment complete Core Team has deployed all fixes: - src/worker/job_worker.rs: 6 running status updates - src/api/files.rs:866: Initialize stages at registration - src/api/files.rs:1762: sync-status TKG + chunks check - src/api/files.rs:16: New imports Status: ✅ Production (3002) running Build: 2026-07-24T18:43:52Z Studio team ready to test	2026-07-25 03:35:28 +08:00
Momentry Studio	cb7e1ba0ba	fix: resolve TypeScript compilation errors Fixes: - VideoPlayer.vue: restore allTags, filteredMarks, marksByTag (removed by mistake) - PeopleView.vue: fix frameTime scope in playFaceDetailVideo catch block - Both errors caused white screen on build failure Root cause: 1. visibleTags duplicate declaration (old + new logic) 2. frameTime undefined in catch block (scope issue) Solution: 1. Keep allTags/filteredMarks/marksByTag (needed in template) 2. Keep visibleTags (new logic for processor toggles) 3. Move frameTime calculation to correct scope in catch block	2026-07-24 23:33:40 +08:00

4 Commits