PL j5dZddlmZddlZddlZddlZddlmZmZddl m Z m Z ej e ZdZdZdd Zdd Zdd ZddZddZddZdZddZddZdddd"Zdd$Zdd&Zdd'Zdd(Zdd)Zdd*Z dd+Z!dd,Z"dd-Z#dd.Z$dd/Z%d0Z&d1d2d3dd4e&d5igd6d7Z'd8d9d3d4d:d5d4gd;dd5d?d@d5dAdBd5dCgd6d7Z(dDdEd3d4e&d5d4dFd5d3dGd5d4dHd5dIdJd4idKdLdMgd6d7Z)dNdOd3d4e&d5d4dPd5dQdRgd6d7Z*dSdTd3d4e&d5d4dUd5dVgd6d7Z+dWdXd3d4dYd5d4dZd5d[dd\gd6d7Z,d]d^d3d4d_d5d4d`d5d4dad5dIdJd4idbdLd4dcd5dAddd5d4gdedfd=d4dgd5d?dhd5d4did5dAdjd5dIdJd4idkdLdl dmdngd6d7Z-dodpd3dd4dqd5idgd6d7Z.drdsd3d4dtd5d4dud5dvdwdxgd6d7Z/e j0d1dye'eedz{e j0d8dye(eedz{e j0dDdye)eed|{e j0dNdye*e ed}{e j0dSdye+e!ed~{e j0dWdye,e"ed{e j0d]dye-e#ed{e j0dodye.e$ed{e j0drdye/e%ed{dS)uKanban tools — structured tool-call surface for worker + orchestrator agents. These tools are only registered into the model's schema when the agent is running under the dispatcher (env var ``HERMES_KANBAN_TASK`` set). A normal ``hermes chat`` session sees **zero** kanban tools in its schema. Why tools instead of just shelling out to ``hermes kanban``? 1. **Backend portability.** A worker whose terminal tool points at Docker / Modal / Singularity / SSH would run ``hermes kanban complete …`` inside the container, where ``hermes`` isn't installed and the DB isn't mounted. Tools run in the agent's Python process, so they always reach ``~/.hermes/kanban.db`` regardless of terminal backend. 2. **No shell-quoting footguns.** Passing ``--metadata '{"x": [...]}'`` through shlex+argparse is fragile. Structured tool args skip it. 3. **Better errors.** Tool-call failures return structured JSON the model can reason about, not stderr strings it has to parse. Humans continue to use the CLI (``hermes kanban …``), the dashboard (``hermes dashboard``), and the slash command (``/kanban …``) — all three bypass the agent entirely. The tools are ONLY for the worker agent's handoff back to the kernel. ) annotationsN)AnyOptional)registry tool_error2returnboolcz ddlm}|}|dg}d|vS#t$rYdSwxYw)Nr) load_configtoolsetskanbanF)hermes_cli.configr get Exception)r cfgrs 6/home/kuhnn/.hermes/hermes-agent/tools/kanban_tools.py_profile_has_kanban_toolsetr.sd111111kmm77:r**8## uus ), ::c`tjdrdStS)aTask-lifecycle tools are available when: 1. ``HERMES_KANBAN_TASK`` is set (dispatcher-spawned worker), OR 2. The current profile has ``kanban`` in its toolsets config (orchestrator profiles like techlead that route work via Kanban). Humans running ``hermes chat`` without the kanban toolset see zero kanban tools. Workers spawned by the kanban dispatcher (gateway- embedded by default) and orchestrator profiles with the kanban toolset enabled see the Kanban lifecycle tool surface. HERMES_KANBAN_TASKTosenvironrrr_check_kanban_moder;s, z~~*++t & ( ((rc`tjdrdStS)aBoard-routing tools (kanban_list, kanban_unblock) are intentionally hidden from task workers. Dispatcher-spawned workers should close their own task via the lifecycle tools (complete/block/heartbeat), not enumerate or unblock board state. Profiles that explicitly opt into the kanban toolset and are NOT scoped to a single task are the orchestrator surface. rFrrrr_check_kanban_orchestrator_moderLs, z~~*++u & ( ((rarg Optional[str]cP|r|Stjd}|pdS)zGResolve ``task_id`` arg or fall back to the env var the dispatcher set.rN)rrr)r env_tids r_default_task_idr$^s-  jnn122G ?drtask_idstr Optional[int]ctjd|krdStjd}|sdS t|S#t$rYdSwxYw)zDReturn this worker's dispatcher run id when it is scoped to task_id.rNHERMES_KANBAN_RUN_ID)rrrint ValueError)r%raws r_worker_run_idr-fst z~~*++w66t *../ 0 0C t3xx tts A A'&A'tidctjd}|sdS||krtd|d|dSdS)u_Reject worker-driven destructive calls on foreign task IDs. A process spawned by the dispatcher has ``HERMES_KANBAN_TASK`` set to its own task id. Tools like ``kanban_complete`` / ``kanban_block`` / ``kanban_heartbeat`` mutate run-lifecycle state, so a buggy or prompt-injected worker that passed an explicit ``task_id`` for some other task could corrupt sibling or cross-tenant runs (see #19534). Orchestrator profiles (kanban toolset enabled but **no** ``HERMES_KANBAN_TASK`` in env) aren't subject to this check — their job is routing, and they sometimes legitimately close out child tasks or reopen blocked ones. Workers are narrowly scoped to their one task. Returns ``None`` when the call is allowed, or a tool-error string when it must be rejected. Callers should ``return`` the error verbatim. rNzworker is scoped to task z; refusing to mutate zf. Use kanban_comment to hand off information to other tasks, or kanban_create to spawn follow-up work.rrrr)r.r#s r_enforce_worker_task_ownershipr1ssp&jnn122G t g~~ @ @ @ @ @ @   4rc:ddlm}||fS)zImport + connect lazily so the module imports cleanly in non-kanban contexts (e.g. test rigs that import every tool module).r) kanban_db) hermes_clir3connect)kbs r_connectr7s)+***** rzz|| rfieldsrc 2tjddi|S)NokT)jsondumps)r8s r_okr=s :tT,V, - --rvaluec|dSt|}|r|dvrdS|S)zANormalize CLI-compatible assignee sentinels for the tool surface.N>-nonenull)r&striplower)r>texts r_normalize_profilerFsH }t u::    D 4::<<#888t KrF)defaultargsdictnamerGc||}||dfSt|tr|dfSt|}|dvrdS|dvrdS||dfS)N>1yestrue)TN>0nofalse)FNz$ must be a boolean or 'true'/'false')r isinstancer r&rCrD)rHrJrGr>rEs r_parse_bool_argrSs HHTNNE }}%d{ u::     # # % %D ###z ###{ tAAA AAr tool_namechtjdrt|dSdS)aBelt-and-suspenders runtime guard for orchestrator-only handlers. The check_fn (`_check_kanban_orchestrator_mode`) keeps these tools out of the worker schema entirely, but in case a stale registration or test harness routes a worker to one of them anyway, return a structured tool_error so the model gets a clear refusal instead of silently mutating board state from a worker context. rz is orchestrator-only; dispatcher-spawned workers must use kanban_complete, kanban_block, kanban_heartbeat, or kanban_comment for their assigned task.Nr0)rTs r_require_orchestrator_toolrVsF z~~*++  6 6 6   4rdict[str, Any]c|||j}|||j}id|jd|jd|jd|jd|jd|jd|jd|j d |j d |j d |j d |j d |jd|d|dt|dt|S)z+Compact task shape for board-listing tools.idtitleassigneestatusprioritytenantworkspace_kindworkspace_path created_by created_at started_at completed_atcurrent_run_idparentschildren parent_count child_count) parent_idsrY child_idsrZr[r\r]r^r_r`rarbrcrdrelen)r6conntaskrfrgs r_task_summary_dictros(mmD$'**G||D$'**H  dg   DM  $+   DM   $+   $-  $-  do  do  do  )  $-  7  H  G ! " s8}}# rc  t|d}|stdS t\}} |||}|'td|d|S|||}|||}|||}| ||} | ||} d} d tj | || | d|Dd |d dD fd |D| ||d |S#|wxYw#t$r6} td td| cYd} ~ Sd} ~ wwxYw)zsRead a task's full state: task row, parents, children, comments, runs (attempt history), and the last N events.r%:task_id is required (or set HERMES_KANBAN_TASK in the env)Nztask z not foundc|j|j|j|j|j|j|j|j|j|j |j |j |j |j |jdS)NrYrZbodyr[r\r^r]r_r`rarbrcrdresultrers)ts r _task_dictz _handle_show.._task_dictsZ$!& ! ahhAJ&'&6&'&6"#,al"#,$%Nh&'&6   rc t|j|j|j|j|j|j|j|j|jd S)N rYprofiler\outcomesummaryerrormetadatarcended_atry)rs r _run_dictz_handle_show.._run_dicts:$19h19 y17 ! "#,AJ rc8g|]}|j|j|jdS)authorrtrbr.0cs r z _handle_show..s? !x#$<11rcDg|]}|j|j|j|jdS)kindpayloadrbrun_idr)res rrz _handle_show..sEV #$<18EEric&g|] }|Srr)rrrs rrz _handle_show..s!444!1444r)rnrfrgcommentseventsrunsworker_contextzkanban_show failedz kanban_show: )r$rrr7get_taskclose list_comments list_events list_runsrjrkr;r<build_worker_contextrlogger exception)rHkwr.r6rmrnrrrrfrgrwrrs @r _handle_showrs2 488I.. / /C   H   </::D7 ;;tS))D|!"9#"9"9"9::h JJLLLLg''c22H^^D#..F<<c**DmmD#..G||D#..H      :" 4(("$& $CDD\ 5444t444 #%"9"9$"D"D', JJLLLLDJJLLLL ///-...-!--......../sBF *E02F CE0F 0FF G +G>G G c td}|r|S|d}|d}|d}t|d\}}|rt|S|d}|t} t |}n&#t tf$rtdcYSwxYw|d krtd S|tkrtd tS t\  }  |||||d z } t| |k} | d|} tjfd | Dt| || | r#|tkrt|dztnd| dS#wxYw#t$r} td| cYd} ~ Sd} ~ wt"$r6} t$dtd| cYd} ~ Sd} ~ wwxYw)z:List task summaries with the same core filters as the CLI. kanban_listr[r\r^include_archivedlimitNzlimit must be an integerzlimit must be >= 1zlimit must be <= r[r\r^rrc2g|]}t|Sr)ro)rrvrmr6s rrz _handle_list..Us&IIIa,Rq99IIIr)taskscountr truncated next_limitpromotedz kanban_list: zkanban_list failed)rVrrSrKANBAN_LIST_DEFAULT_LIMITr* TypeErrorr+KANBAN_LIST_MAX_LIMITr7recompute_ready list_tasksrlr;r<minrrrr)rHrguardr[r\r^r bool_errorrrrowsrrrrmr6s @@r _handle_listr,s &} 5 5E  xx ##H XXh  F XXh  F#249K#L#L j&*%%% HHW  E })6E  z "6664555556 qyy./// $$$E.CEEFFF#/::D ))$//H==!!1ai !DD E)I%LE:IIIII5IIIU&!M%*-B%B%B #8999HL$     JJLLLLDJJLLLL ///-!--........ ///-...-!--......../s[B(( C  C G/B)GG/G,,G// I9H I I+IIIc Xt|d}|stdSt|}|r|S|d}|d}|d}|d}|dt |t r|g}t |t tfs$tdt|j Sd |D}|s|std S|9t |ts$td t|j S t\}} | | |||||t| } nV#|j$rI} td d| jdcYd} ~ | Sd} ~ wwxYw| s'td|d| S|| |} t'|| r| jnd| S#| wxYw#t*$r6} t,dtd| cYd} ~ Sd} ~ wwxYw)z5Mark the current task done with a structured handoff.r%rqr|r~ru created_cardsNz.created_cards must be a list of task ids, got cg|]D}t|#t|ESr)r&rCrs rrz$_handle_complete..sI    SVV\\^^ FFLLNN   rz4provide at least one of: summary (preferred), resultz%metadata must be an object/dict, got )rur|r~rexpected_run_idzfkanban_complete blocked: the following created_cards do not exist or were not created by this worker: z, z. Your task is still in-flight (no state change). Retry kanban_complete with the same summary/metadata and either drop these ids from created_cards, or pass created_cards=[] to skip the card-claim check entirely.zcould not complete z! (unknown id or already terminal)r%rzkanban_complete failedzkanban_complete: )r$rrr1rRr&listtupletype__name__rIr7 complete_taskr-HallucinatedCardsErrorjoinphantomr latest_runr=rYrrr)rHrr. ownership_errr|r~rurr6rmr:hall_errrunrs r_handle_completerhs8 488I.. / /C   H   3377Mhhy!!Gxx ##H XXh  FHH_--M mS ) ) ,*OM-$77 2 &&/22    $1     v  B   Jx$>$> MDNN4K M M   (3::D#  %%#!7X"/$23$7$7 & ,   "Oyy!122OOO JJLLLL7 ( !P#PPP JJLLLL--c**CsS+B366dCCC JJLLLLDJJLLLL 33312221a11222222223srI)#)F I G *GG II)G  I7I) /I;I)I&&I)) J)3+J$J)$J)c  t|d}|stdSt|}|r|S|d}|r!t |stdS t \}} ||||t|}|s'td|d| S| ||}t||r|j nd | S#| wxYw#t$r6} td td | cYd} ~ Sd} ~ wwxYw) z?Transition the task to blocked with a reason a human will read.r%rqreasonu2reason is required — explain what input you need)rrzcould not block z% (unknown id or not in running/ready)Nrzkanban_block failedzkanban_block: )r$rrr1r&rCr7 block_taskr-rrr=rYrrr) rHrr.rrr6rmr:rrs r _handle_blockrs 488I.. / /C   H   3377M XXh  F PV**,,PNOOO0::D c .s 3 3B  !&s&&& JJLLLL--c**CsS+B366dCCC JJLLLLDJJLLLL 000.///.1..////////0sBE !:D4E 0/D4E 4E  E F +FF F c t|d}|stdSt|}|r|S|d} t \}} t jd}||||||||t|}|s'td|d| St| | S#| wxYw#t$r6} td td | cYd } ~ Sd } ~ wwxYw) uSignal that the worker is still alive during a long operation. Extends the claim TTL via ``heartbeat_claim`` AND records a heartbeat event via ``heartbeat_worker``. Without the ``heartbeat_claim`` half, a diligent worker that loops this tool while a single tool call blocks the agent for >DEFAULT_CLAIM_TTL_SECONDS still gets reclaimed by ``release_stale_claims`` — which is exactly the trap that ``heartbeat_claim``'s docstring warns against. r%rqnoteHERMES_KANBAN_CLAIM_LOCK)claimer)rrzcould not heartbeat z (unknown id or not running))r%zkanban_heartbeat failedzkanban_heartbeat: N)r$rrr1r7rrheartbeat_claimheartbeat_workerr-rr=rrr) rHrr.rrr6rm claim_lockr:rs r_handle_heartbeatrs 488I.. / /C   H   3377M 88F  D4::D  (BCCJ   tS*  = = =$$ .s 3 3 %B  !L3LLL JJLLLLs### JJLLLLDJJLLLL 44423332q22333333334sCD2/A1D D25DD2D//D22 E2<+E-'E2-E2c |d}|stdS|d}|r!t|stdStjdpd} t \}} ||||t|}t||| S#| wxYw#t$r6}t d td |cYd }~Sd }~wwxYw) z$Append a comment to a task's thread.r%uotask_id is required (use the current task id if that's what you mean — pulls from env but kept explicit here)rtzbody is requiredHERMES_PROFILEworker)rrt)r% comment_idzkanban_comment failedzkanban_comment: N) rrr&rCrrr7 add_commentr=rrrr) rHrr.rtrr6rmcidrs r_handle_commentr sP ((9  C   B    88F  D .s4yy((.,---Z^^, - - 9F 2::D ..s6D .JJCss333 JJLLLLDJJLLLL 22201110Q00111111112s6D"6C-D-DD E+E;EEc J|d}|r!t|stdS|d}|stdS|d}|dpg}|dptjd}|d }|d pd }|d } t |d \} } | rt| S|d} |d} |d}t|tr|g}|@t|ttfs$tdt|j St|tr|g}t|ttfs$tdt|j S t\}} | |t||t|t|||t|ndt|| | | | t| nd|tjdpd}|||}t!||r|jnd|S#|wxYw#t&$r}td|cYd}~Sd}~wt($r6}t*dtd|cYd}~Sd}~wwxYw)zCreate a child task. Orchestrator workers use this to fan out. ``parents`` can be a list of task ids; dependency-gated promotion works as usual. rZztitle is requiredr[uassignee is required — name the profile that should execute this task (the dispatcher will only spawn tasks with an assignee)rtrfr^ HERMES_TENANTr]r_scratchr`triageidempotency_keymax_runtime_secondsskillsNz*skills must be a list of skill names, got z(parents must be a list of task ids, got rrr) rZrtr[rfr^r]r_r`rrrrrar%r\zkanban_create: zkanban_create failed)rr&rCrrrrSrRrrrrr7 create_taskr*rr=r\rr+rrr)rHrrZr[rtrfr^r]r_r`rrrrrr6rmnew_tidnew_taskrs r_handle_creater*s HHW  E /E ((**/-...xx ##H   K    88F  Dhhy!!'RG XXh   B2:>>/#B#BFxx ##HXX.//<9NXX.//N(x88FJ&*%%%hh011O((#899 XXh  F&# *VdE]"C"C Pf9N P P   '3) ge} - -  OtG}}7M O O   !1::D nn%jj&&((Xg*2*>XA">22- /+6+,,,<@:>>*:;;Gx#%G&{{411H*27CL%L>%L;;L>> N"MN" N",+NN"N"c td}|r|S|d}|stdStt |}|r|S t \}} ||t |}|s'td|d|Stt |d|S#|wxYw#t$r6}t dtd |cYd }~Sd }~wwxYw) z(Transition a blocked task back to ready.kanban_unblockr%ztask_id is requiredzcould not unblock z (not blocked or unknown)readyrzkanban_unblock failedzkanban_unblock: N) rVrrr1r&r7 unblock_taskrr=rrr) rHrrr.rr6rmr:rs r_handle_unblockrvsZ &'7 8 8E  ((9  C 1/00023s88<>> JJLLLLDJJLLLL ///-!--........ ///-...-!--......../sGB'(B9B'B$$B'' D 1CD  D +DD D zrTask id. If omitted, defaults to HERMES_KANBAN_TASK from the env (the task the dispatcher spawned you to work on). kanban_showuORead a task's full state — title, body, assignee, parent task handoffs, your prior attempts on this task if any, comments, and recent events. Use this to (re)orient yourself before starting work, especially on retries. The response includes a pre-formatted ``worker_context`` string suitable for inclusion verbatim in your reasoning.objectstring)r description)r propertiesrequired)rJr parametersruList Kanban task summaries so an orchestrator profile can discover work to route. Supports the same core filters as the CLI: assignee, status, tenant, include_archived, and limit. Returns compact rows with ids, title, status, assignee, priority, parent/child ids, and counts. Bounded to 50 rows by default, 200 max, with truncation metadata. Also recomputes ready tasks before listing, matching the CLI. Orchestrator-only — dispatcher-spawned task workers never see this tool.z!Optional assignee/profile filter.)rtodorrunningblockeddonearchivedzOptional task status filter.)renumrz)Optional tenant/project namespace filter.booleanz*Include archived tasks. Defaults to false.integerz6Optional maximum rows to return (default 50, max 200).rkanban_completeuMark your current task done with a structured handoff for downstream workers and humans. Prefer ``summary`` for a human-readable 1-3 sentence description of what you did; put machine-readable facts in ``metadata`` (changed_files, tests_run, decisions, findings, etc). At least one of ``summary`` or ``result`` is required. If you created new tasks via ``kanban_create`` during this run, list their ids in ``created_cards`` — the kernel verifies them so phantom references are caught before they leak into downstream automation.zrHuman-readable handoff, 1-3 sentences. Appears in Run History on the dashboard and in downstream workers' context.uFree-form dict of structured facts about this attempt — {"changed_files": [...], "tests_run": 12, "findings": [...]}. Surfaced to downstream workers alongside ``summary``.zShort result log line (legacy field, maps to task.result). Use ``summary`` instead when possible; this exists for compatibility with callers that still set --result on the CLI.arrayruOptional structured manifest of task ids you created via ``kanban_create`` during this run. The kernel verifies each id exists and was created by this worker's profile; any phantom id blocks the completion with an error listing what went wrong (auditable in the task's events). Only list ids you got back from a successful ``kanban_create`` call — do not invent or remember ids from prose. Omit the field if you did not create any cards.)ritemsr)r%r|r~rur kanban_blockuTransition the task to blocked because you need human input to proceed. ``reason`` will be shown to the human on the board and included in context when someone unblocks you. Use for genuine blockers only — don't block on things you can resolve yourself.zWhat you need answered, in one or two sentences. Don't paste the whole conversation; the human has the board and can ask follow-ups via comments.)r%rrkanban_heartbeatuSignal that you're still alive during a long operation (training, encoding, large crawls). Call every few minutes so humans see liveness separately from PID checks. Pure side effect — no work changes.zHOptional short note describing current progress. Shown in the event log.)r%rkanban_commentuAppend a comment to a task's thread. Use for durable notes that should outlive this run (questions for the next worker, partial findings, rationale). Ephemeral reasoning doesn't belong here — use your normal response instead.uWTask id. Required (may be your own task or another's — comment threads are per-task).z Markdown-supported comment body.)r%rtrt kanban_createucCreate a new kanban task, optionally as a child of the current one (pass the current task id in ``parents``). Used by orchestrator workers to fan out — decompose work into child tasks with specific assignees, link them into a pipeline, then complete your own task. The dispatcher picks up the new tasks on its next tick and spawns the assigned profiles.zShort task title (required).uProfile name that should execute this task (e.g. 'researcher-a', 'reviewer', 'writer'). Required — tasks without an assignee are never dispatched.zkOpening post: full spec, acceptance criteria, links. The assigned worker reads this as part of its context.zParent task ids. The new task stays in 'todo' until every parent reaches 'done'; then it auto-promotes to 'ready'. Typical fan-in: list all the researcher task ids when creating a synthesizer task.zUOptional namespace for multi-project isolation. Defaults to HERMES_TENANT env if set.zZDispatcher tiebreaker. Higher = picked sooner when multiple ready tasks share an assignee.)rdirworktreezWorkspace flavor: 'scratch' (fresh tmp dir, default), 'dir' (shared directory, requires absolute workspace_path), 'worktree' (git worktree).zYAbsolute path for 'dir' or 'worktree' workspace. Relative paths are rejected at dispatch.uIf true, task lands in 'triage' instead of 'todo' — a specifier profile is expected to flesh out the body before work starts.zIf a non-archived task with this key already exists, return that task's id instead of creating a duplicate. Useful for retry-safe automation.zxPer-task runtime cap. When exceeded, the dispatcher SIGTERMs the worker and re-queues the task with outcome='timed_out'.u4Skill names to force-load into the dispatched worker (in addition to the built-in kanban-worker skill). Use this to pin a task to a specialist context — e.g. ['translation'] for a translation task, ['github-code-review'] for a reviewer task. The names must match skills installed on the assignee's profile.) rZr[rtrfr^r]r_r`rrrrrZr[ruMove a blocked Kanban task back to ready. Orchestrator-only — only profiles with the kanban toolset can unblock routed work; dispatcher-spawned task workers never see this tool.z#Blocked task id to return to ready. kanban_linkuAdd a parent→child dependency edge after both tasks already exist. The child won't promote to 'ready' until all parents are 'done'. Cycles and self-links are rejected.zParent task id.zChild task id.rrrru📋)rJtoolsetschemahandlercheck_fnemojiu✔u⏸u💓u💬u➕u▶u🔗)r r )r r!r r!)r%r&r r')r.r&r r!)r8rr r&)r>rr r!)rHrIrJr&rGr )rTr&r r!)r rW)rHrIr r&)1__doc__ __future__rr;loggingrtypingrrtools.registryrr getLoggerrrrrrrrr$r-r1r7r=rFrSrVrorrrrrrrrr_DESC_TASK_ID_DEFAULTKANBAN_SHOW_SCHEMAKANBAN_LIST_SCHEMAKANBAN_COMPLETE_SCHEMAKANBAN_BLOCK_SCHEMAKANBAN_HEARTBEAT_SCHEMAKANBAN_COMMENT_SCHEMAKANBAN_CREATE_SCHEMAKANBAN_UNBLOCK_SCHEMAKANBAN_LINK_SCHEMAregisterrrrr s2#"""""  ////////  8 $ $    ))))" ) ) ) )$    @....?D B B B B B B$:D/D/D/D/N9/9/9/9/xK3K3K3K3\ 0 0 0 0F-4-4-4-4`2222BI1I1I1I1X22222////48  &  4   .  !B ! > !J "K!! "W+  49**Z  !4 !(!5!B  (+ 0 ?/ / `e33BBJ  !4 !E   J!<  & !4 !.   8  < !C!A   '8  C!= !"!#  (+(  !<"C!666K !?"3!E  "5$$  (+*  od d Jj)Ohhssl  ?   D K  (  : "*;LMM"*;KLL  !*- ,            ,     !              "                     ,         r