+jb9dZddlmZddlZddlZddlZddlZddlZddlm Z ddl Z e e e jjdZeej vrej j#deddlmZmZmZmZmZmZmZe j4dZe j4dZe j4d Zdd Zdd Z d dd Z ddd Z!dZ"dZ#dZ$dZ%dZ&dZ'dZ(dZ)dZ*dZ+y)utask-2534 회귀 테스트: data_loader 자동머지 시그널 병합 (traffic_light_fix_b) 회장 §결정(2026-05-10) 신호등 sync fix B — dashboard/data_loader.py가 task-timers.json만이 아니라 cron schedule_history + events/*.merge-queue.json 시그널을 병합해 활성/유휴 판정. 검증 포인트 (회귀 8건): 1. timers running → 작업중 (heartbeat fresh + PID alive) 2. cron 발사 후 timers stale → 작업중 (cron 시그널이 idle 덮어씀) 3. merge-queue HEAD 있음 → 작업중 4. 모든 시그널 부재 → 유휴 5. heartbeat 가장 최근 source 우선 (cron > mq > heartbeat priority 검증) 6. chat=6937032012 격리 (다른 chat schedule_history 무시) 7. token raw 0 (prompt/response/schedule_id 절대 결과 dict에 노출 X) 8. task-2528+1 / task-2530 / task-2531 fixture 회귀 (회장 발견 사례 3건 박제) ) annotationsN)Path)DASHBOARD_CHAT_IDHEARTBEAT_FRESH_SECONDSSIGNAL_FRESHNESS_SECONDS_PidLivenessProvider_collect_cron_schedule_signals_collect_merge_queue_signals_compute_member_statusc#xKtj5}t|dddy#1swYyxYwwNtempfileTemporaryDirectoryrtmps I/home/jay/workspace/tests/dashboard/test_data_loader_signal_merge_2534.pytmp_heartbeat_dirr.1  $ $ &#3i:. :7:c#xKtj5}t|dddy#1swYyxYwwrrrs rtmp_schedule_history_dirr4rrc#xKtj5}t|dddy#1swYyxYwwrrrs rtmp_events_dirr:rrc0||z }|j|Sr)touch)dir_namefs r _touch_freshr!@s t AGGI Hc||z }|jtj|z }tj|||f|Sr)rtimeosutime)rrage_secr pasts r_touch_with_ager)Fs; t AGGI 99; DHHQt  Hr"c ||dz }|||d|dddd}|jtj|dd zd |d kDr/tj|z }t j |||f|S) u-schedule_history JSONL 1라인 파일 생성.z.logz (redacted)z2026-05-10T03:00:00.000+09:00oki) schedule_idchat_idpromptresponseworkspace_pathtsstatus duration_msF ensure_ascii utf-8encodingr write_textjsondumpsr$r%r&) rr,r-r.r0r'r recr(s r_write_schedule_logr?Ns +d##A" (- CLLCe4t;gLN{yy{W$ T4L! Hr"c||dz }d|ddd}|jtj|dd |d kDr/tj|z }t j |||f|S) Nz.merge-queue.jsonWAITING_FOR_PREDECESSORcz2026-05-10T03:10:26Z)decisiontask_id pr_number timestampFr4r7r8rr:)rrDr'r payloadr(s r_write_merge_queuerHisr '+,,A-+ G LLG%87LK{yy{W$ T4L! Hr"ct|dt}|jdditdddd||ii}|dk(sJy ) uPtimers running + heartbeat fresh + PID alive → working (기존 경로 회귀).ztask-A.heartbeatzsched-ATztask-Arunningr2r, cron_signalsmerge_queue_signalsworkingN)r!r set_overrider rpresults r2test_signal_merge_1_timers_running_returns_workingrT{sX"$67ANNIt$% #Y7  F Y  r"ct}|jidtjdz i}tdddi|||i}|dk(sJy)utimers status=completed(또는 hb stale)이지만 cron 시그널 fresh → 작업중. 회장 발견 사례 핵심 — cron --session으로 봇이 실 작업 중이지만 timers는 'idle'. task-2528+1N@r2 completedrLrONr rPr$r )rrRrMrSs r/test_signal_merge_2_cron_overrides_stale_timersrZs^ ANN2!499;#56L # ; ! F Y  r"ct}|jidtjdz i}tdi||i|}|dk(sJy)u?merge-queue HEAD에 fresh 진입 → 작업중 (timers 무관). task-2530>@rLrONrY)rrR mq_signalsrSs r4test_signal_merge_3_merge_queue_head_returns_workingr_sWANN2tyy{T12J #  & F Y  r"cpt}|jitdddd||ii}|dk(sJy)uCcron 부재 + merge-queue 부재 + timers stale/completed → idle.ztask-XYZrXnonerKrLidleN)r rPr rQs r+test_signal_merge_4_no_signals_returns_idlercsGANN2 #v6  F V  r"c jt}|jddit|dtdddd||dt jt z dz idt jt z dz i}|d k(sJt |d tdztd dd d||d t jd z id t jt z dz i}|d k(sJt |dtdztdddd||dt jt z dz idt jdz i}|d k(sJt |dtdztdddd||dt jt z dz idt jt z dz i}|dk(sJy)u4priority: cron > merge-queue > timers heartbeat. 검증 1: cron stale + mq stale + hb fresh+alive → working (heartbeat path) 검증 2: cron fresh + 나머지 stale → working (cron path) 검증 3: cron stale + mq fresh + hb stale → working (mq path) 검증 4: 모두 stale → idle zsched-XTztask-X.heartbeatztask-XrJrK<rLrOztask-Y.heartbeatztask-Yzsched-Yr]ztask-Z.heartbeatztask-Zzsched-ZrWztask-W.heartbeatztask-Wzsched-WrbN)r rPr!r r$rr)r)rrRresult1result2result3result4s r8test_signal_merge_5_priority_cron_over_mq_over_heartbeatrjs ANNIt$%"$67$Y7  .F F KL%tyy{5M'MPR'RS G i  %'9;RUW;WX$Y7  d 23%tyy{5M'MPR'RS G i  %'9;RUW;WX$Y7  .F F KL%tyy{T'9: G i  %'9;RUW;WX$Y7  .F F KL%tyy{5M'MPR'RS G f  r"ct|dtdt|dddt|t}d|vsJd |vsJy ) u~다른 chat의 schedule_history 라인은 결과에 포함 X. 회장 §명시: chat=6937032012 외 라인은 무시. ABCD0001utask-100 진행r-r.ABCD0002lc( utask-200 진행r-ztask-100ztask-200N)r?rr )rsignalss r"test_signal_merge_6_chat_isolationrqs^  !   - !G   W $$ $r"ct|dtddt|t}td|j DsJt j |}d|vsJd|vsJd|vsJy ) uW반환 dict에는 task_id/mtime만 — prompt/response/schedule_id raw 절대 노출 X.FF00FF00u$task-300 비밀 토큰 ABC123 포함z&/home/jay/.cokacdir/workspace/FF00FF00r-r.r0roc3<K|]}t|tywr) isinstancefloat).0vs r z5test_signal_merge_7_token_raw_zero..6s>z!U#>sABC123u 비밀 토큰N)r?rr allvaluesr<r=)rrp serializeds r"test_signal_merge_7_token_raw_zeror's !5? - !G >W^^-=> >> >G$J : %% % Z '' ' * ,, ,r"ct|dtddt|dt|t}t |}d|vsJd|vsJt }|j itdi||||}|dk(sJy ) u회장 §발견 fixture: task-2528+1 dev1 — cron+merge-queue 모두 fresh, timers entry 0. audit fix B 본질 — task-timers는 entry 0이지만 cron schedule_history와 merge-queue.json이 모두 살아있음 → 'working' 판정 보장. B9792045z&[task-2528+1] worktree timer reconcilez-/home/jay/workspace/.worktrees/task-2528-dev1rtrVrorLrON)r?rrHr r r rPr rrrrMr^rRrSs r0test_signal_merge_8_chairman_fixture_2528_plus_1rAs !7F ~}51 !L.n=J L (( ( J && &ANN2 #  !& F Y  r"ct|dtddt|t}t|}d|vsJd|vsJt }|j it dddi|||| }|d k(sJy ) u회장 §발견 fixture: task-2530 dev7 — cron 발사 26m43s 진행, timers idle 표시. audit fix B 본질 — cron 시그널만으로도 working 판정. 5AFBFD82uA[task-2530] composite ③ cross-cutting agent 페르소나 합성z-/home/jay/workspace/.worktrees/task-2530-dev7rtror\r2rXrLrONr?rr r r rPr rs r)test_signal_merge_8_chairman_fixture_2530rhs !RF 2 !L.n=J , && & j (( (ANN2 # ; !& F Y  r"ct|dtdt|t}t|}d|vsJd|vsJt }|j it dddi||||}|d k(sJy ) u회장 §발견 fixture: task-2531 dev4 — 표시=유휴(cron 미발견). audit fix B 본질 — cron 미발견이면 적법하게 idle 판정 (over-trigger 금지). 이 경계 케이스를 fixture로 박제해 회귀 보호. 298A007Bu[task-2999] 다른 작업rmroz task-2531r2rXrLrbNrrs r)test_signal_merge_8_chairman_fixture_2531rs !* 2 !L.n=J l ** * j (( (ANN2 # ; !& F V  r")rrrstrreturnr)rrrrr'rwrr))rrr,rr-intr.rr0rr'rwrr)r)rrrDrr'rwrr),__doc__ __future__rr<r%sysrr$pathlibrpytestr__file__resolveparents _PROJECT_ROOTpathinsertdashboard.data_loaderrrrr r r r fixturerrrr!r)r?rHrTrZr_rcrjrqrrrrr"rrsP #   DN**,44Q78  HHOOA}%                   6  $ &, & $9~%>-4$N#L#r"