+ lHjs^.Rt^RIHt^RIHt^RIHtHtRtRt RRlt RR lt R R lt ] !R R R] !R]4/.4t ] !RRR] !RR4RRRR.]P!4O]NRR/R] !RR4R] !RR4R] !RR 4/.4t] !R!R"R] !R]4R#] !RR$4R%] !R&R'4R(] !RR)4R*RR+R,RR/RR-/R.RR+R,RR/RR///.4t] !R0R1R] !R]4R2] !RR34R4RRR.RORR5//R2.4t] !R6R7R] !R]4R2] !RR84/.4t] !R9R:R] !R]4R#] !RR;4R<] !RR=4R%RR&RR>R?R@/R.RR+R,RR/RRA//R#.4t] !RBRCR] !R]4R2] !RRD4/R2.4t] !RERFR] !R]4RG] !RRH4/.4t] !RIRJR] !RRK4RL] !RRM4/RRL.4t] !RNROR] !R]4RP] !RRQ4RRRRRRS/RT] !RRU4/RPRR.4t] !RVRWR] !R]4RX] !RRY4RP] !RRZ4RT] !RR[4/RX.4t] !R\R]R] !R]4/.4t] !R^R_/R`] !RRa4bR] !RRb4bRL] !RRc4bRdRR+R,RR/RRe/bR] !RRf4bRg] !RRh4bRiRRR.RORRj/bRk] !RRl4bRm] !RRn4bRo] !RRp4bRq] !RRr4bRs] !RRt4bRuRRRRvRw.RRx/bRyRR+R,RR/RRz/bR{] !RR|4bR}] !RR~4bR] !RR4bR] !RR4R] !RR4/CR`R.4t] !RRR] !RR4/R.4t] !RRRRRRR/RRRRR//RR.4tR#)zLTool schemas for tools.kanban_tools (model-facing; strings are byte-frozen).) annotations)Any)ARCHIVEDDEFAULT_WORKFLOWuTask id. If omitted, defaults to HERMES_KANBAN_TASK from the env — the task the dispatcher spawned you to work on. That default only exists for a dispatcher-spawned worker; any other caller has no default and must pass an explicit task_id (use kanban_list to discover ids).uXKanban board slug to target. When omitted, the call resolves the active board the usual way: HERMES_KANBAN_DB env → HERMES_KANBAN_BOARD env → the 'current' symlink under the kanban home → 'default'. Pass an explicit slug only when the caller (e.g. a Telegram routing layer) needs to override the env-pinned active board for this one call.c$V^8dQhRRRRRR/#)type_str descriptionreturndict[str, str])formats"?/home/ubuntu/.hermes/hermes-agent/tools/kanban_tools_schemas.py __annotate__rs!77737>7cRVRV/#)typer r )rr s&&r_proprs E=+ 66rcV^8dQhRR/#)rr r r )rs"rrrs((N(rc"\R\4#)zJSchema fragment for the optional ``board`` parameter (one place to tweak).string)r _DESC_BOARDr rr_board_schema_proprs ; ''rc ,V^8dQhRRRRRRRRRR/#) rnamer r propertieszdict[str, Any]requiredz list[str]r r )rs"rrr"s0  # C ^ y ]k rc :RVRVRRRR/VCR\4/CRV//#) zLBuild a tool schema; every kanban tool takes an optional trailing ``board``.rr parametersrobjectrboardr)r)rr rrs&&&&r_schemar""s@ { H GZG2D2FG   r kanban_showuRead 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. Outside a dispatcher-spawned worker there is no default task: a bare call returns a pointer to ``kanban_list`` instead of task state.task_idr kanban_listuList 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.assigneez!Optional assignee/profile filter.statusrenumr zOptional task status filter.tenantz)Optional tenant/project namespace filter.include_archivedbooleanz*Include archived tasks. Defaults to false.limitintegerz6Optional maximum rows to return (default 50, max 200).kanban_completeuhMark 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. If you produced deliverable files (charts, PDFs, spreadsheets, generated images), list their absolute paths in ``artifacts`` — the gateway notifier will upload them as native attachments to the human who subscribed to the task, so the deliverable lands in their chat alongside the summary instead of being a path they have to fetch by hand.summaryzrHuman-readable handoff, 1-3 sentences. Appears in Run History on the dashboard and in downstream workers' context.metadatar uFree-form dict of structured facts about this attempt — {"changed_files": [...], "tests_run": 12, "findings": [...]}. Surfaced to downstream workers alongside ``summary``.resultzShort 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. created_cardsarrayitemsuOptional 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. artifactsuOptional list of absolute paths to deliverable files you produced during this run — generated charts, PDFs, spreadsheets, images, archives. Examples: ["~/.hermes/cache/scratch/q3-revenue.png", "~/.hermes/cache/scratch/report.pdf"]. The gateway notifier uploads each path as a native attachment to the subscribed chat (images embed inline, everything else uploads as a file) so the deliverable lands with the completion notification. Skip intermediate scratch files and references that are not the deliverable. The path must exist on disk at completion. Files inside a managed scratch workspace are copied to durable task attachments before cleanup; a missing declared scratch artifact keeps the task in-flight so you can fix the path and retry. kanban_blockuqStop work on this task and route it according to WHY you're stuck. Set ``kind`` to say which: 'dependency' (waiting on another task — goes to todo and auto-resumes when that task finishes, no human needed), 'needs_input' (you need a human decision/answer), 'capability' (a hard wall: no access, missing credentials, an action no agent can do), or 'transient' (a flaky failure that may clear). ``reason`` is shown to the human on the board. If a task keeps getting unblocked and re-blocked for the same reason, it is auto-escalated to triage. Use for genuine blockers only — don't block on things you can resolve yourself.reasonzWhat you need answered or what stopped you, in one or two sentences. Don't paste the whole conversation; the human has the board and can ask follow-ups via comments.kindzWhy you're blocked. 'dependency' waits in todo and resumes automatically when an incomplete parent finishes; if no parent is open it is recorded as needs_input instead. The others surface to a human. Omit only if none apply.kanban_schedulea&Park your current task in the 'scheduled' state while it waits for time or an external event. This ends the current run and makes the task non-dispatchable until an orchestrator unblocks it; it does not create a timer. Put any wake-up marker such as ``SCHEDULED_UNTIL=`` in ``reason``.zeOptional reason or machine-readable wake-up marker recorded on the completed run and scheduled event.kanban_request_reviewuHand the task off for review: implementation, self-review, and verification are complete and you want a human (or reviewer) to look before it is marked done. Moves the task to the 'review' column and notifies the subscriber. Unlike ``kanban_block`` this is NOT a blocker — it never counts toward unblock-loop detection, so a task can cycle through review across follow-ups without ever being falsely escalated to triage. Use this instead of blocking with a free-form 'review-required:' reason.uWhat was implemented and how it was verified, in one or two sentences — shown to the reviewer. Don't paste the whole diff; the reviewer has the board and the PR.reviewerzhOptional reviewer profile. When provided, the task is reassigned to that profile before review dispatch.zkOptional structured handoff facts for the reviewer, such as changed_files, tests_run, commit, or decisions.additionalPropertiesTuHOptional list of absolute paths to deliverable files this handoff names — generated charts, PDFs, spreadsheets, images, archives. Examples: ['~/.hermes/cache/scratch/q3-revenue.png', '~/.hermes/cache/scratch/report.pdf']. A review handoff is the last implementer transition, so the kernel copies these into the task's durable attachments before the reviewer's completion cleans the scratch workspace up, and the gateway notifier uploads them as native attachments to the subscribed chat. A missing declared scratch artifact keeps the task in place so you can fix the path and retry.kanban_request_changesaQReviewer verdict: return the current review run to the original implementer with concrete required changes. This closes the review run, reapplies parent dependency gating, and requeues the task without using block-loop accounting. Only use from a task claimed from the review column; use kanban_block only for a genuine external blocker.zXSpecific, actionable changes the implementer must make before requesting another review.kanban_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.notezHOptional short note describing current progress. Shown in the event log.kanban_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.uTask id. Required (may be your own task or another's — comment threads are per-task). Outside a dispatcher-spawned worker there is no default; use kanban_list to discover ids.bodyz Markdown-supported comment body. kanban_attachu]Attach a file to a task by passing its bytes inline (base64). Use for genuine file artifacts the next worker or a human should be able to download — generated reports, images, exports. The file is stored as a real attachment (not a comment link) under the task's attachments dir, capped at 25 MB. Prefer kanban_attach_url when you only have a URL.filenamezjFile name to store it under (e.g. 'report.pdf'). Directory components are stripped; only the leaf is kept.content_base64z5The file contents, base64-encoded. Max 25 MB decoded. content_typez,Optional MIME type (e.g. 'application/pdf').kanban_attach_urluAttach a file to a task by URL — Hermes downloads it server-side and stores it as a real attachment (capped at 25 MB). Use when you have a link rather than the bytes. Only http/https URLs are accepted.urlzhttp(s) URL to fetch and store.zKOptional name to store it under. Defaults to the URL path's leaf component.zMOptional MIME type override. Defaults to the Content-Type the server returns.kanban_attachmentszList the files attached to a task: id, filename, content_type, size, who uploaded it, and the absolute on-disk path you can read. 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.titlezShort 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.parentszParent 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.priorityzZDispatcher tiebreaker. Higher = picked sooner when multiple ready tasks share an assignee.workspace_kindzWorkspace flavor: 'scratch' (fresh tmp dir, default), 'dir' (shared directory, requires absolute workspace_path), 'worktree' (git worktree).workspace_pathzYAbsolute path for 'dir' or 'worktree' workspace. Relative paths are rejected at dispatch.projectzOptional project id or slug to link the task to. When set, the task becomes a git worktree under the project's primary repo with a deterministic branch (project slug + task id), instead of a random branch.triageuIf true, task lands in 'triage' instead of 'todo' — a specifier profile is expected to flesh out the body before work starts.idempotency_keyzIf a non-archived task with this key already exists, return that task's id instead of creating a duplicate. Useful for retry-safe automation.max_runtime_secondszxPer-task runtime cap. When exceeded, the dispatcher SIGTERMs the worker and re-queues the task with outcome='timed_out'.initial_statusrunningblockedzInitial card status. Use 'blocked' for tasks that require immediate human ops (R3 gate) to skip the brief running-to-blocked transition. Defaults to 'running', which preserves the usual dispatch path.skillsu:Skill names to force-load into the dispatched worker. The kanban lifecycle is already injected automatically; 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. goal_modeaRun the dispatched worker in a goal loop. When true, after each turn an auxiliary judge checks the worker's response against this card's title/body; if the work isn't done and budget remains, the worker keeps going in the same session until the judge agrees it's complete (or the goal-turn budget is exhausted, which blocks the task for human review). Use this for open-ended cards where one shot rarely finishes the work. Defaults to false (classic single-shot worker).completion_contractzDeclare at creation: local-only (default), OWNER/REPO for PR publication, or an exact GitHub PR URL. PR tasks cannot complete until repository-required exact-head CI passes. On publication pass metadata.published_pr.goal_max_turnszTurn budget for goal_mode workers. Caps how many continuation turns the worker may take before the task is blocked for review. Ignored unless goal_mode is true. Defaults to the goal-engine default (20).modelzPin the dispatched worker to this model instead of the assignee profile's configured model. Use the exact model name the target provider expects. Omit to use the profile default.provideru Provider the 'model' belongs to (e.g. 'openrouter', 'anthropic', 'nous'). Set this whenever the model is not from the assignee profile's configured provider — a model name alone is resolved against the profile's provider and will fail if it belongs to a different one. Requires 'model'.kanban_unblockuUnblock a Kanban task. It moves to ready when all parents are done, or todo while any parent remains open. Orchestrator-only — only profiles with the kanban toolset can unblock routed work; dispatcher-spawned task workers never see this tool.z6Blocked task id to move to ready or parent-gated todo. 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. A running child is rejected unless the active owning worker is linking its own card for a dependency handoff. parent_idzParent task id.child_idzChild task id.N) dependency needs_input capability transient)scratchdirworktree)__doc__ __future__rtypingrhermes_cli.kanban_workflowrr_DESC_TASK_ID_DEFAULTrrrr"KANBAN_SHOW_SCHEMAkeysKANBAN_LIST_SCHEMAKANBAN_COMPLETE_SCHEMAKANBAN_BLOCK_SCHEMAKANBAN_SCHEDULE_SCHEMAKANBAN_REQUEST_REVIEW_SCHEMAKANBAN_REQUEST_CHANGES_SCHEMAKANBAN_HEARTBEAT_SCHEMAKANBAN_COMMENT_SCHEMAKANBAN_ATTACH_SCHEMAKANBAN_ATTACH_URL_SCHEMAKANBAN_ATTACHMENTS_SCHEMAKANBAN_CREATE_SCHEMAKANBAN_UNBLOCK_SCHEMAKANBAN_LINK_SCHEMAr rrr|sLR"AB 7(  1 5#89$  E($GH H 8&++-8x8 9 %"MNE)-YZy"Z[ /4! >" 5#895$ E(1 %>  G fh'  ,   G fh' D  G8rYM^ 4 5#89%K  H L J  $JA!F! 7 5#89% 5 !( ' / 5#895I E(E   H E #D    G fh'  5  '%LKe3 j!( O 5#89%4 J!!&" & 5#89h* $  < 5/ h BC#( 6 5#89E(L   H R  h(VW !"-2#  5#89 uX@AE()  h3   G).$ M 5#89  C|x!?@|E( | h |  G fh' $  |0 %8 1|8 E)? 9|@  H 2 G  A|R %; S|Z 58 [|f % / g|p 5A q|z uY1 {|D  H Y * F  E|X  G fh' &  Y|r U9H  s|H uX B I|P % B Q|\ x. E(8 i|z jOHT  ? 5#[\K  ) fh 7HIfh 7GH*r