`gj!LdZddlmZddlZddlZddlZddlZddlmZddl m Z ddl m Z ddlmZeded d Zej$eZd Zd ZeGd dZddZej2dej4ZddZddZddd ddZddddZy)uKanban triage specifier — flesh out a one-liner into a real spec. Used by ``hermes kanban specify [task_id | --all]``. Takes a task that lives in the Triage column (a rough idea, typically only a title), calls the auxiliary LLM to produce: * A tightened title (optional — only replaces if the model proposes a materially different one) * A concrete body: goal, proposed approach, acceptance criteria and then flips the task ``triage -> todo`` via ``kanban_db.specify_triage_task``. The dispatcher promotes it to ``ready`` on its next tick (or immediately if there are no open parents). Design notes ------------ * This module intentionally mirrors ``hermes_cli/goals.py`` — same aux client pattern, same "empty config => skip, don't crash" tolerance. Keeps the surface area tiny and the failure modes predictable. * The prompt is a short system + user pair. We ask for JSON with ``{title, body}``; if parsing fails, we fall back to treating the whole response as the body and leave the title untouched. No retry loop — one shot, keep cost bounded. * Structured output / JSON mode is not requested explicitly so the specifier works on providers that don't implement it. The parse is lenient (tolerates markdown code fences around the JSON). ) annotationsN) dataclass)Optional) kanban_db)env_inti HERMES_KANBAN_SPECIFY_MAX_TOKENSipuYou are the Kanban triage specifier for the Hermes Agent board. A user dropped a rough idea into the Triage column. Your job is to turn it into a concrete, actionable task spec that an autonomous worker can pick up and execute without further clarification. Output a single JSON object with exactly two keys: { "title": "", "body": "" } The body MUST include these sections, each prefixed with a bold markdown heading, in this order: **Goal** — one sentence, user-facing outcome. **Approach** — 2-5 bullets on how a worker should tackle it. **Acceptance criteria** — checklist of concrete, verifiable conditions. **Out of scope** — short list of things NOT to touch (omit if nothing obvious; never invent scope creep). Rules: - Keep the tightened title close in meaning to the original idea — do NOT invent a different project. - If the original idea is already detailed, preserve its substance and just reformat into the sections above. - Never add invented requirements the user didn't hint at. - No preamble, no closing remarks, no code fences around the JSON. - Output only the JSON object and nothing else. z?Task id: {task_id} Current title: {title} Current body: {body} cBeZdZUdZded<ded<dZded<dZd ed <y) SpecifyOutcomez*Result of specifying a single triage task.strtask_idboolokreasonN Optional[str] new_title)__name__ __module__ __qualname____doc____annotations__rrL/root/.hermes/venv/lib/python3.12/site-packages/hermes_cli/kanban_specify.pyr r \s#4 L HFC#I}#rr c8t||kr|S|d|dz dzS)Nu…)len)textlimits r _truncater fs) 4yE  %!) u $$rz^\s*```(?:json)?\s*|\s*```\s*$cT|sytjd|j}|jd}|j d}|dk(s |dk(s||kry|||dz} t j |}t|tsy|S#tt jf$rYywxYw)u}Lenient JSON extraction — tolerates fenced code blocks and leading/trailing whitespace. Returns None if nothing parses.Nr{}r) _FENCE_REsubstripfindrfindjsonloads ValueErrorJSONDecodeError isinstancedict)rawstrippedfirstlast candidatevals r_extract_json_blobr6os }}R-H MM# E >># D {dbjDEM*Ijj# c4  J ,, -s#B B'&B'ctjjdxs#tjjdxsdS)z~Mirror of ``hermes_cli.kanban._profile_author``. Kept local to avoid a circular import when kanban.py imports this module.HERMES_PROFILEUSER specifier)osenvirongetrrr_profile_authorr>s7 '(  ::>>& !  r)authortimeoutc tj5}tj||}ddd t|ddS|jdk7rt|dd|jdS ddlm}tj|jt|jxsd d t|jxsd d} |ddt dd|dgdt"|xsd} |j*dj,j.xsd j1} t3| } | $| j1} | s t|ddSd} | } n| j5d}| j5d}t7|t8r |j1r|j1nd} t7|t8r|j1r|nd} | | t|ddStj5}tj:||| | |xs t=}ddds t|ddSt|dd | !S#1swYxYw#t$r-}tjd |t|dd cYd}~Sd}~wwxYw#t$rD}tj%d||t|ddt'|j(cYd}~Sd}~wwxYw#t$rd } YwxYw#1swYxYw)"uRSpecify a single triage task and promote it to ``todo``. Returns an outcome describing what happened. Never raises for expected failure modes (task not in triage, no aux client configured, API error, malformed response) — those surface via ``ok=False`` so the ``--all`` sweep can continue past individual failures. NFzunknown task idtriageztask is not in triage (status=)r)call_llmz+specify: auxiliary client import failed: %szauxiliary client unavailableriz (no body)i)r titlebodytriage_specifiersystem)rolecontentuserg333333?x)taskmessages temperature max_tokensr@u1specify: API call failed for %s (%s) — skippingz LLM error: zLLM returned an empty responserErFz#LLM response missing title and body)rErFr?z)task moved out of triage before promotionT specified)r)kbconnect_closingget_taskr statusagent.auxiliary_clientrD Exceptionloggerdebug_USER_TEMPLATEformatidr rErF_SYSTEM_PROMPTrinfotyperchoicesmessagerJr'r6r=r.r specify_triage_taskr>)r r?r@connrMrDexcuser_msgrespr0parsed stripped_rawrnew_body title_valbody_valrs r specify_taskrls   *{{4)* |gu.?@@ {{h U    D  seH9.I!I?)5K,'K!9I I<"I71I<7I<? K 9KK K  KK!K*)tenantctj5}tj|d|d}dddDcgc]}|jc}S#1swY#xYwcc}w)z{Return task ids currently in the triage column. ``tenant`` narrows the sweep; ``None`` returns every triage task. rBF)rUrminclude_archivedN)rRrS list_tasksr\)rmrctasksts rlist_triage_idsrss\     "    QADD     !sAAA)rr rintreturnr )r0r ruzOptional[dict])rur )r r r?rr@z Optional[int]rur )rmrruz list[str]) r __future__rr*loggingr;re dataclassesrtypingr hermes_clirrRutilsrmaxr getLoggerrrXr]rZr r compile IGNORECASEr%r6r>rlrsrrrrs>#  !&#& .5$   8 $@ $$ $% BJJ8"-- H *!! kK kK kK kK  kK\04 !r