3jE\dZddlmZddlmZmZddlmZddlm Z m Z m Z m Z ddl mZmZmZmZmZmZdZdZd Zd Zd ZeeehZd Zd ZdZdZ dZ!dZ"dZdZ#dZdZ$dZ%edGddZ& d*dZ'dddd d+d Z(edGd!d"Z)Gd#d$Z*dd% d,d&Z+d-d'Z,gd(Z-y)).u* anu_v3.callback_event_trigger — normal-callback durable-success registry write-back + read-only event-driven next_action resolver. task-2553+47 (NORMAL_CALLBACK_REGISTRY_WRITEBACK_AND_EVENT_TRIGGER, 회장 결정). Problem (회장 §2 / +45 실증): the +45 normal-callback collector finished at 14:24 but the durable 4-tuple ledger stayed ``role=dispatch / REGISTERED`` (``normal_collector_cron_id=null``), so ANU could not see the normal callback as completed and the next step / summary was only recovered manually at 14:44. There was no write-back of the verified normal durable-success into ``callback_4tuple_index`` and no read-only event-trigger that detects a COMPLETED record and computes the next action *without* a fixed-time gate or a dead-man fallback as the progress trigger. This module supplies the two missing seams (회장 §3): 1. ``write_back_completed`` — the정정 표준 (a) normal-callback collector session, *after* verification, calls this exactly once to append a correctly-bound ``state=COMPLETED`` ledger record carrying the ``normal_collector_cron_id / fallback_cron_id / task_id / dispatch_id / chat_id / role`` binding. It uses the +44 registry's existing append-only API (``registry.append``) — the +44 module stays byte-0 (additive-only carve-out unused; no escalation of the registry to a merge/dispatch executor, §6). 2. ``CallbackEventTrigger.scan`` — a *read-only* resolver that detects a registry COMPLETED event and, when the dependency is satisfied, computes the next_action. **It never uses a fixed-time gate or a dead-man fallback as the progress trigger** (Layer A, 9-R.1): the only accepted progress trigger is the registry COMPLETED event. A dead-man signal is a missed-callback safety net, not a primary trigger; a fixed-time gate offered as the dependency trigger is rejected with ``FORBIDDEN_TRIGGER_SOURCE`` (regression §8.5). Layer A / NO-CRON (9-R.1): this module performs ZERO cron register/remove, ZERO dispatch, ZERO merge, ZERO ``cokacdir`` / ``subprocess`` exec. The only write surface is the +44 append-only ledger (its designed Layer A role). A next_action for which this session has no write authority is emitted as a **proposal JSON only** — never auto-dispatched / merged / closed out (§6). ) annotations) dataclassfield)Path)DictListOptionalSequence)Callback4TupleRecordCallback4TupleRegistryNORMAL_CALLBACK_COMPLETEDNO_LEDGER_RECORDTRACK_MISMATCH make_recordz#anu_v3.callback_4tuple_writeback.v1z anu_v3.callback_event_trigger.v1registry_completed_eventfixed_time_gatedead_man_fallbackWRITEBACK_COMPLETEDWRITEBACK_IDEMPOTENT_SKIPCALLBACK_MANDATORY_VIOLATIONNEXT_ACTION_READYNEXT_ACTION_DEFERREDNEXT_ACTION_BLOCKEDrFORBIDDEN_TRIGGER_SOURCErnoneproposalT)frozencheZdZUdZded<ded<ded<ded<ded <ee Zd ed <dd Zy)WritebackResultz?Outcome of a single normal durable-success registry write-back.strschemastatustask_idboolappendedOptional[Dict[str, object]]recorddefault_factory List[str]reasonsc|j|j|j|j|jt |j dS)Nr!r"r#r%r'r+)r!r"r#r%r'listr+selfs 4/home/jay/workspace/anu_v3/callback_event_trigger.pyto_jsonzWritebackResult.to_jsonns;kkkk|| kkDLL)   NreturnDict[str, object] __name__ __module__ __qualname____doc____annotations__rr.r+r2r3r1rrcs3I K K LN ''t4GY4 r3rc|j|D]L}|jdk(s|j|k(s#|jt |k(s<|j |k(sLyy)uTrue iff an append-only COMPLETED line with the SAME normal-collector binding already exists (idempotency key — repeated write-back is a skip, never a duplicate append; regression §8.6). COMPLETEDTF) history_forr" dispatch_idchat_idr normal_collector_cron_id)registryr#rArBrCrs r1_completed_identity_presentrFys] ! !' * HH # , S\)**.FF r3executorF)role no_fallbackts_kstc `g} |s*| jdttt|dd| St |||||rttt |dddgSt ||||t||||d| |  } |j| ttt|d | jgS) uAppend a correctly-bound ``state=COMPLETED`` ledger record (회장 §3/§4.1). Called ONCE by the 정정 표준 (a) normal-callback collector session after it has verified the normal durable-success. Unlike a naive ``registry.mark_completed`` (which would copy a stale ``role=dispatch / normal_collector_cron_id=null`` line — the exact +45 14:24→14:44 defect), this binds the *verified* normal-collector identity: ``normal_collector_cron_id / fallback_cron_id / task_id / dispatch_id / chat_id / role``. Append-only & idempotent (§4.4 / §8.6): a repeated call with the same normal-collector binding is a ``WRITEBACK_IDEMPOTENT_SKIP`` — no duplicate line. ``normal_collector_cron_id`` missing -> ``CALLBACK_MANDATORY_ VIOLATION`` with NO append (callback mandatory rule preserved, §8.10). Uses only the +44 registry's existing append-only API — the +44 module stays byte-0; the registry is NOT escalated to a merge/dispatch executor (§6). unormal_collector_cron_id missing — MANDATORY executor normal completion callback lifecycle signal; write-back refused, callback mandatory rule NOT weakened (§8.10).FNr-)r#rArBrCueCOMPLETED record with identical normal-collector binding already present — idempotent skip (§8.6).r?) r#rAdispatch_cron_idrGrBrCfallback_callback_cron_idrIr"rJrKT) appendrWRITEBACK_SCHEMArrFrrr rr2) rDr#rArMrGrBrCrNrIrJrKr+recs r1write_back_completedrRsBG # = #/   #!9 #,LM   !,)G !9";  !C OOC "{{}  r3ceZdZUdZded<ded<ded<ded<ded <ded <ded <ded <ded <ded<ded<eeZded<ddZy)NextActionResultuRead-only event-trigger verdict for one task. ``trigger_source`` is ALWAYS the registry COMPLETED event when ``ready`` is True (9-R.1 Layer A). ``fixed_time_used`` / ``dead_man_used`` are explicit FALSE evidence (회장 §9-4 보고 항목). r r!r#verdictr$ready Optional[str]trigger_sourcefixed_time_used dead_man_usedfallback_pending_non_blockingsummary_candidater*summary_inputs_completedr& next_actionr(r+c4|j|j|j|j|j|j |j |j|jt|j|jt|jd S)N r!r#rUrVrXrYrZr[r\r]r^r+) r!r#rUrVrXrYrZr[r\r.r]r^r+r/s r1r2zNextActionResult.to_jsonsxkk||||ZZ"11#33!//22!%!7!7(,T-J-J(K++DLL)  r3Nr4r7r=r3r1rTrTs[ K L L K!!#'''',,t4GY4 r3rTc eZdZdZd dZ d dZd dZdddeddddd dd Z dd Z y)CallbackEventTriggerupRead-only event-driven next_action resolver over the +44 ledger. ZERO write (the only write surface is ``write_back_completed`` above, explicitly invoked once by the collector). ZERO cron / dispatch / merge / subprocess. ``scan`` is idempotent: repeated scans of the same ledger state yield an identical verdict and never append a record (§8.6). c||_y)N)rD)r0rDs r1__init__zCallbackEventTrigger.__init__s   r3c`|jj|}||jdk(r|Sy)Nr?)rD latest_forr"r0r#rQs r1_completed_recordz&CallbackEventTrigger._completed_records0mm&&w/ ?szz[8Jr3cr|jj|}|y|js |jsyy)uA fallback cron is bound and still pending (not yet cancelled). Layer A NO-CRON never cancels a fallback, so a bound fallback stays pending after normal durable-success until +45/+48 enacts the verified single cancel. This is surfaced ONLY to ASSERT non-blocking (§8.3): a pending fallback never blocks a completed task's progress. An ABSENT fallback (or an explicit no_fallback contract) returns False — it is never treated as a cancel target (§8.7).FT)rDrfrJrNrgs r1_fallback_pendingz&CallbackEventTrigger._fallback_pending's5mm&&w/ ; ??#"?"?r3Ndispatch_next_taskF)expected_dispatch_idexpected_chat_idexpected_dispatch_cron_iddependency_trigger_sourceconsolidated_inputsnext_action_kindnext_action_payloaddead_man_signalc g} |tvr4| jd|dtt|tddddddgd|  S|j j ||||} | tk(r0| jdtt|tddddddgd|  S|j|} | tk7s| f| tk(rt} | jdnt} | jd | r| jd tt|| ddddddgd|  S|j|}|r| jd g}d}|ro|D]7}|j j | tk(s'|j|9t|tt!|k(}|r| jd |j#|| ||||}| jdtt|t$dt&dd|||||  S)uDetect a registry COMPLETED event and compute the next_action. * ``dependency_trigger_source`` MUST be ``registry_completed_event``. A ``fixed_time_gate`` / ``dead_man_fallback`` offered as the dependency trigger -> ``FORBIDDEN_TRIGGER_SOURCE`` (FAIL, §8.5). * No COMPLETED record -> ``NEXT_ACTION_DEFERRED`` (fail-safe wait; a ``dead_man_signal`` alone does NOT promote this to ready — §8.4: dead-man is a safety net, not a primary trigger). * COMPLETED + identity match -> ``NEXT_ACTION_READY``. A pending fallback is recorded non-blocking (§8.3) and an absent fallback is never treated as a cancel target (§8.7). * ``consolidated_inputs`` all COMPLETED -> ``summary_candidate`` emitted immediately (§3 consolidated summary). * The emitted ``next_action`` is a proposal only (no write/dispatch authority — §6); idempotent across repeated scans (§8.6). zdependency_trigger_source=u~ is forbidden as a progress/dependency-stage trigger; only registry_completed_event is permitted (회장 §6 / 9-R.1 Layer A).FNr`)r#rlrmrnulregistry identity mismatch — an unrelated track's callback is never cited as this task's progress (§8.9).unno ledger record — fail-safe DEFER (defer to schedule_history + canonical artifact; not a progress trigger).unregistry record present but not COMPLETED — wait for the normal-callback durable-success write-back (§8.4).ua dead-man signal was observed but is EXPLICITLY NOT promoted to a progress trigger — safety net only (§8.4, 회장 §6 verbatim). ready stays False.ufallback binding pending — recorded NON-BLOCKING; the completed task proceeds (§8.3). A pending/absent fallback is never a cancel target here (§8.7, Layer A NO-CRON).)r#uYall consolidated inputs COMPLETED — summary candidate emitted immediately (회장 §3).)r# completedkindpayloadr\r]uregistry COMPLETED event detected — next_action computed via the registry_completed_event trigger ONLY (no fixed-time gate, no dead-man fallback; 9-R.1 Layer A).T)FORBIDDEN_PROGRESS_TRIGGERSrOrTEVENT_TRIGGER_SCHEMArrDclassifyREG_TRACK_MISMATCHrrhr REG_NO_LEDGER_RECORDrrrjlenr._build_proposalrTRIGGER_REGISTRY_COMPLETED)r0r#rlrmrnrorprqrrrsr+ verdict_regrurU fb_pendingr]r\depr^s r1scanzCallbackEventTrigger.scan7s:  %(C C NN,-F,IJ  $+0# %#.3"')+    mm,,!5-&? - , , NNB $+&# %#.3"')+   **73 3 3y7H22*) /NG $+# %$.3"')+  $++G4  NNJ /1 ! * 9MM**3*701-33C8  9 !$$< =()B! !8 **!'/%= +   4  '%5!*4/%=#  r3cdttd||t|j|j|j |j |j|j|jd|t|t|xsidd S)uBuild a write-authority-free next_action **proposal** (§6). This resolver never auto-dispatches / merges / closes out. The proposal is data only; an authorized session must enact it. z,anu_v3.callback_event_trigger.next_action.v1F)r#rArMrCrNrBrIuPROPOSAL ONLY — write 권한 없는 next_action 은 proposal JSON 으로만 산출(자동 dispatch/merge/closeout 0, 회장 §3/§6). An authorized session must enact this.) r! authority action_mode auto_executedrvsource_task_idrXbindingr\r]rwnote) AUTHORITY_NONEACTION_MODE_PROPOSALrr#rArMrCrNrBrIr.dict)r0r#rurvrwr\r]s r1r~z$CallbackEventTrigger._build_proposals E'/"%8$,,(44$-$>$>6677$,,! "3(,-E(FGMr*93  r3)rDr r5None)r#r r5zOptional[Callback4TupleRecord])r#r r5r$)r#r rlrWrmrWrnrWror rpzOptional[Sequence[str]]rqr rrr&rsr$r5rT)r#r rur rvr rwr&r\r$r]r*r5r6) r8r9r:r;rdrhrjrrr~r=r3r1rbrbs! '(/3*.37)C7; 4;? %q q , q ( q $1 q $'q 5q q 9q q  q f, , ( ,  , - ,  , #,,  , r3rb)generated_at_kstc@d|ttd|jdS)umSerialize a NextActionResult as the standalone next-action-proposal artifact (회장 §5 expected_files).z$task-2553+47.next-action-proposal.v1F)r!rrrrresult)rrr2)rrs r1proposal_envelopers' 9,#+.."  r3c*tt|S)zEConvenience: build a read-only registry over an explicit ledger path.)r r) ledger_paths r1 load_registryr(s !${"3 44r3)rPryrTRIGGER_FIXED_TIMETRIGGER_DEAD_MANrxrrrrrrrrrrrTrRrbrrN) rDr r#r rAr rBr rCr r5r$)rDr r#r rAr rMr rGr rBr rCrWrNrWrIr rJr$rKr r5r)rrTrr r5r6)r5r ).r; __future__r dataclassesrrpathlibrtypingrrr r anu_v3.callback_4tuple_registryr r r rr|rr{rrPryrrr frozensetrxrrrrrrrrrrrFrRrTrbrr__all__r=r3r1rs'P#(11998'&')* ,7 >(.+!5%! $   *$    "  @W$WW W  W  WW,W -W WW WWt $% % % PD D P:<   36  5  r3