+ jHjBRt^RIHt^RIt^RIt^RIt^RIHt^RIH t ^RIH t ^RIH t ^RIH t ^RIH t ] 'd^R IHtR;t]]]]3tR tR R ltR RltRRltRRRRRRRRRRRRRR/RRlltRRltR`` keeps working. ) annotationsN)Path)Any)Iterable)Mapping)Optional) TYPE_CHECKING)EventzDWHERE task_id = ? AND platform = ? AND chat_id = ? AND thread_id = ?c ,V^8dQhRRRRRRRRRR/#) task_idstrplatformchat_id thread_id Optional[str]returntuple)formats"@/home/ubuntu/.hermes/hermes-agent/hermes_cli/kanban_db_notify.py __annotate__r#s099c9S939=9UZ9cYY#;'gR3#)r)r rrrs&&&&r_sub_keyr#s wR 88rc V^8dQhRRRR/#)r metadataOptional[Mapping[str, Any]]rrr)rs"rrr's D D/J D} Drc\V\4'gR#VP4UUu/uF/wrVfK \V\4'gK#\ V4VbK1 pppV'gR#\ P !VRRR7#uuppi)zFSerialize platform send metadata stored on notification subscriptions.NT) sort_keys separators),:) isinstanceritems _SCALAR_TYPESr jsondumps)rkeyvaluecleans& r _encode_notify_delivery_metadatar,'sy h ( (#..* *JC  !+E=!A C%*    ::et CC sBBBc V^8dQhRRRR/#)r rawrrzdict[str, Any]r)rs"rrr5s ` `# `. `rc\V\4'd \V4#V'g/#\P!\ V44p\T\4'g/#TP4UUu/uF)wr#\T\4'gK\ T4TbK+ upp# \ d/u#i;iuuppiN) r$rdictr'loadsr Exceptionr%r&)r.datar)r*s& r _decode_notify_delivery_metadatar55s#wCy  zz#c(# dD ! ! .2jjl _l jP]>^OCHeOl __   `sB*7B=B=* B:9B:ruser_id user_id_alt chat_typenotifier_profile delivery_modedelivery_metadatacHV^8dQhRRRRRRRRRRR RR RR RR RR RRRRR/ #)r connsqlite3.Connectionr r rrrrr6r7r8r9r:r;rrNoner)rs"rrrCsJJ JJ J  J  JJJJ$J!J3J Jrc NV \9dT MRp T ;'g VR8XdRMRp \WW44p \P!V4;_uu_4VP R\ ,V 4P 4pV'd\VR,4M/p\V4pV 'dVPV 4V'd \V4MRpTP R.V OVNVNT;'gRNVNV NVN\\P!44NVN54R VR 3R VR 3R VR 3RVR 3RV R 3RVR 33FPwpppV'gKV'd RV RV R2MRpVP RV R2\ ,V,V.V O54KR RRR4R# +'giR#;i)aRegister a gateway source wanting terminal-state notifications for ``task_id``; idempotent on (task, platform, chat, thread). ``user_id_alt`` (Signal UUID, Feishu union_id, ...) and ``chat_type`` are replayed on active wake: ``build_session_key`` prefers the alt id, so omitting it would key the wake into a different session. ``None`` keeps an existing row's value. ``delivery_mode``: ``None`` leaves an existing row untouched, an explicit valid value is last-write-wins, unknown falls back to ``"notify"``. ``delivery_metadata`` merges supplied routing anchors into an existing row so re-subscribing never discards them. New subs start caught up (``last_event_id`` = ``MAX(task_events.id)``) so the notifier never replays history at boot. N api_server notify+wakenotifyz1SELECT delivery_metadata FROM kanban_notify_subs r;a INSERT OR IGNORE INTO kanban_notify_subs (task_id, platform, chat_id, thread_id, user_id, user_id_alt, chat_type, notifier_profile, delivery_mode, delivery_metadata, created_at, last_event_id) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, COALESCE((SELECT MAX(id) FROM task_events WHERE task_id = ?), 0)) dmr8Fr6Tr7r9r:z AND (z IS NULL OR z = '')rzUPDATE kanban_notify_subs SET z = ? ) _NOTIFY_DELIVERY_MODESr_kb write_txnexecute_SUB_KEY_WHEREfetchoner5r1updater,inttime)r=r rrrr6r7r8r9r:r; valid_mode insert_moder)existingexisting_metadatamerged_metadata metadata_jsoncolumnr* fill_onlyguards&$$$$$$$$$$ radd_notify_subrWCs6#03I"ItJYY(l2JPXK 7g 9C t  << ?. P   (* `hE  $)U +  & K . !14 8 j% 0 - 7 ) $FE9CLfVHL?RTE LL0>ORWW   ) 7    s A3F(F,A!F;F F$ c$V^8dQhRRRRRR/#)r notifier_profilesOptional[Iterable[str]]include_unownedboolrztuple[str, list[str]]r)rs"rrrs(66.66 6rcVfR.3#\VUu0uF=p\V4P4'gK$\V4P4kK? up4p.p.pV'dGVPRRP RV44,R,4VP V4V'dVPR4V'gR.3#RR P V4,R,V3#uupi) zCBuild an optional SQL predicate for notification profile ownership.rznotifier_profile IN (r"c3&"TFpRxK R#5i)?Nr).0_s& r )_notify_profile_filter..s9Px!#xs)z1notifier_profile IS NULL OR notifier_profile = ''0(z) OR ()sortedr stripappendjoinextend)rYr[pprofilesclausesparamss&$ r_notify_profile_filterrps  2v /@S/@!CFLLN~s1v||~/@STHGF.9Px9P1PPSVVW hJK Bw w' '# -v 55Ts !C4C4rYr[Fc ,V^8dQhRRRRRRRRR R /#) r r=r>r rrYrZr[r\rz list[dict]r)rs"rrrs:!! ! !/ !  !  !rc\W#R7wrE.p.pVe#VPR4VPV4V'd#VPV4VPV4RpV'd'VRRPRV44,, p.p VP W4P 4FCp \ V 4p RV 9d\V PR44V R&V PV 4KE V #)aList subscriptions, optionally restricted to notifier profile owners. No ``notifier_profiles`` -> all subscriptions. Gateway notifiers pass the profiles they own so they cannot claim another gateway's events; ``include_unowned`` (dispatch owner) covers legacy rows without a stamp. r[z task_id = ?z SELECT * FROM kanban_notify_subs WHERE  AND c3."TF pRV R2xK R#5i)rfrdNr)r`clauses& rrb#list_notify_subs..s'JE&!F81 Esr;) rprirkrjrHfetchallr1r5get) r=r rYr[ owner_where owner_paramswhererosqloutrowitems &&$$ rlist_notify_subsrs!7!KEF ]# g [! l# ,C  y7<<'JE'JJJJC||C(113Cy $ &(HReIf(gD$ % 4 4 Jrboardrrc8V^8dQhRRRRRRRRR RR RR RR R /#)r db_pathzOptional[Path]rrrYrZr[r\rrrrrLr)rs"rrrsZ22 2 2/ 2  2  222 2rcVeTM\P!VR7pVP4'g^#\W#R7wr.p .p V'd'V P RV R24V P V 4RV3RV3RV33F-wrV fK V P V 4V P V 4K/ R pV 'd VR R P V 4,, p\P!VP4P4R ,R R7pVPW4P4pT'd\#T^,4M^TP!4# \Pd;pR\T4P49dRp?TP!4^#hRp?ii;i TP!4i;i)uCount ``kanban_notify_subs`` rows via a read-only connection — the notifier's cheap zero-subscription early exit. Unlike :func:`connect` it never creates the file, runs init/migration or opens writable; WAL rows are still visible so a fresh sub is never missed. Missing DB / missing table counts as zero; platform matches case-insensitively (as notifier routing), chat/thread exactly. Raises :class:`sqlite3.Error` if the DB exists but is unreadable — callers pick their own fallback. N)rrsrfrdzLOWER(platform) = LOWER(?)z chat_id = ?z thread_id = ?z'SELECT COUNT(*) FROM kanban_notify_subsrtruz?mode=roT)uriz no such table)rFkanban_db_pathexistsrprirkrjsqlite3connectresolveas_urirHrJOperationalErrorr lowercloserL)rrrYr[rrrpathr{r|rnrorwr*queryr=rexcs&$$$$$$ rcount_notify_subsrs}$)7s/A/A/ND ;;== 6!KGF;-q)* l# %x0  )$    NN6 " MM%  6E W\\'222 ??4<<>002Z?T JD  ,,u-668C "s3q6{q( '' #c(.."22    s<E$7F6?F6$F39F.F6-F..F33F66Gc 0V^8dQhRRRRRRRRRRR R /#) r r=r>r r rrrrrr\r)rs"rrrsF            rc \P!V4;_uu_4VPR\,\ WW444pRRR4XP ^8# +'giL;i)zDELETE FROM kanban_notify_subs N)rFrGrHrIrrowcount)r=r rrrcurs&$$$$ rremove_notify_subrsR t  ll - > W ;   <rrLrr)rs"rrrs#%"%"'9%"C%"Y\%"rc\V4pV^8:d^#\\P!44VR,, p\P !V4;_uu_4VP RV34pRRR4\XP;'g^4# \\3d^pLi;i +'giLH;i)uDelete notify subs whose task sat in ``done``/``blocked`` untouched for longer than ``max_age_days`` (``<= 0`` disables); returns rows deleted. Subs survive ``done`` because a reopened task must still notify its origin, which accumulates forever on never-archiving boards. ``blocked`` is abandoned (unlike ``backlog``/``ready``) so it reaps on the same clock. Age = latest event, else ``completed_at``, else ``created_at`` — any activity, including a reopen, exempts the sub. The notifier keeps subscriptions alive through ``done`` because a completed task can be reopened (review corrections, continuation) and the reopened cycle must still notify its origin session. On boards that never archive, that retention would otherwise accumulate subscription rows forever — each one scanned every notifier tick. This GC bounds that: a task that has been ``done`` with no new events for the retention window is treated as settled and its subscriptions are purged. ``blocked`` tasks (circuit-breaker trips, dead workers) are reaped on the same clock — they are abandoned, not idle, unlike a ``backlog``/``ready`` card that is merely waiting for pickup (#100955). iQzDELETE FROM kanban_notify_subs WHERE task_id IN ( SELECT t.id FROM tasks t WHERE t.status IN ('done', 'blocked') AND COALESCE( (SELECT MAX(e.created_at) FROM task_events e WHERE e.task_id = t.id), t.completed_at, t.created_at, 0 ) < ?)N)rL TypeError ValueErrorrMrFrGrHr)r=rdayscutoffrs&$ rpurge_stale_done_notify_subsrs$<  qy  u ,F t  ll I    s||  q !!# z "  s B B4B10B14 C c 0V^8dQhRRRRRRRRRRR R /#) r r=r>r r rrrrrz Optional[int]r)rs"rrr7s<>> >'*>69>DG>Ta>>rc VPR\,\WW444P4pVfR#\ VR,4#)zI``last_event_id`` of one subscription row, or ``None`` when unsubscribed.z-SELECT last_event_id FROM kanban_notify_subs N last_event_id)rHrIrrJrL)r=r rrrrs&&&&& r_notify_cursorr7sK ,,7.HG7 hj;4=CO(<$==rkindsc4V^8dQhRRRRRRRRRRR R R R /#) r r=r>r r rrrrrrZrztuple[int, list[Event]]r)rs"rrrBsP       #rc\WW#V4pVf^.3#V'd \V4MRpRV'd0RRPR\V4,4,R,MR,R,pW.p V'dV P V4VP W4P 4p V U u.uF"p \PPV 4NK$ p p \V.R V 4O4p W3#uup i) zReturn ``(new_cursor, events)`` with ``id > last_event_id``. The cursor is NOT advanced here; call :func:`advance_notify_cursor` after delivery. Nz7SELECT * FROM task_events WHERE task_id = ? AND id > ? z AND kind IN (r"r_z) rzORDER BY id ASCc3F"TFp\VR,4xK R#5i)idN)rL)r`rs& rrb(unseen_events_for_sub..\s7$QC$LL$s!) rlistrjlenrkrHryrFr from_rowmax)r=r rrrrcursor kind_listqrorowsrrmax_ids&$$$$$ runseen_events_for_subrBsD8i HF ~"u $U $IAFO?SXXcC N&:; ;d BUW Y   !)F i << " + + -D*. /$Q399  a $C / &87$78 9F ; 0s1(C3c4V^8dQhRRRRRRRRRRR R R R /#) r r=r>r r rrrrrrZrztuple[int, int, list[Event]]r)rs"rrr`sP.. .. .  .  . #.".rc >\P!V4;_uu_4\WW#V4pVf^^.3uuRRR4#\WW#WER7wrxV'gWf.3uuRRR4#\ V\ WW44Wv4WgV3uuRRR4# +'giR#;i)aAtomically claim unseen events for one subscription. Returns ``(old_cursor, new_cursor, events)``; when events are returned the row's ``last_event_id`` has already been advanced inside ``BEGIN IMMEDIATE``, so concurrent gateway watchers on the same board DB serialize on SQLite's writer lock and only the first claims a given event range. Callers send the events, then leave the cursor or call :func:`rewind_notify_cursor` on delivery failure. N)r rrrr)rFrGrr _cas_cursorr) r=r rrrr old_cursor new_cursoreventss &$$$$$ rclaim_unseen_events_for_subr`s$ t  #D8iP  a8  3 H  2-   D(7gI:bv-    sB B &B  B c ,V^8dQhRRRRRRRRRR /#) r r=r>r)rrrLexpectedrzsqlite3.Cursorr)rs"rrrs2(u#QTYgrczVPR\,R,\V4.VO\V4N54#)zr r rrrrrrLrr?r)rs"rrrsP                  rc \P!V4;_uu_4VPR\,\ V4.\ WW44O54RRR4R# +'giR#;i)rNrFrGrHrIrLr)r=r rrrrs&$$$$$radvance_notify_cursorrsL t   > O _ Ox7N O      5A A/ c4V^8dQhRRRRRRRRRRR R R R /#) r r=r>r r rrrrevent_idrLrr?r)rs"rrrsF     *-  9<  GJ    /2     rc \P!V4;_uu_4VPR\,\ V4.\ WW44O54RRR4R# +'giR#;i)zBCheckpoint a sent ping independently of the retryable wake cursor.zNUPDATE kanban_notify_subs SET last_ping_event_id = MAX(last_ping_event_id, ?) Nr)r=r rrrrs&$$$$$rrecord_notify_pingrsO t   \  ] MXgL M     rc8V^8dQhRRRRRRRRRRR R R R R R /#)r r=r>r r rrrrclaimed_cursorrLrrr\r)rs"rrrsZ       rc \P!V4;_uu_4\V\WW44We4pRRR4XP^8# +'giL;i)zUndo a claim when delivery fails. The CAS guard only rewinds if no later notifier advanced the row, so retries never clobber newer progress. N)rFrGrrr)r=r rrrrrrs&$$$$$$ rrewind_notify_cursorrsF t  $G OQ[l  <rs#   * ;c5$' X9 D `J $ J"J"&J $J'+J$(J6:JZ6,!26 ! " !!H2 226 2 " 2 # 2"2 $22j  $  %"RT%"P> $ &*<. $ .&*.@  $   #   $ ((r