lithermes-ai 0.8.6 → 0.8.8

package/README.md

@@ -39,6 +39,15 @@ Install the plugin:
 npx lithermes-ai install --yes
 ```
 
+For a non-interactive first install through npx, pass both approvals:
+
+```sh
+npx --yes lithermes-ai@latest install --yes
+```
+
+The first `--yes` is for npx; the second `--yes` is for LitHermes. The npm
+package is `lithermes-ai`; `lithermes` is the installed CLI/plugin name.
+
 Restart any running Hermes CLI or Hermes gateway process. Then open Hermes and try:
 
 ```text
@@ -53,7 +62,9 @@ Restart any running Hermes CLI or Hermes gateway process. Then open Hermes and t
 - `/lit-plan`: create a durable implementation plan.
 - Natural routing: a standalone `lit` or `litwork` in normal prose activates Litwork;
   `lit plan`, `lit review`, `lit research`, and `lit goal` route to the matching
-  Lithermes mode contract. Tokens inside code spans, fenced code, substrings,
+  Lithermes mode contract; `lit workflow` / `lit kanban` route durable work to
+  Hermes Kanban setup/proposal guidance, and `lit team` maps team-like work to
+  Kanban profile lanes instead of claiming a literal native team mode. Tokens inside code spans, fenced code, substrings,
   compounds, paths, and real slash-command mentions are ignored.
 - `/litwork-loop` and `/litwork-plan`: longer aliases.
 - `/lit_loop` and `/lit_plan`: gateway-friendly aliases for Telegram dispatch.
@@ -61,6 +72,8 @@ Restart any running Hermes CLI or Hermes gateway process. Then open Hermes and t
 - Interactive install spinner keeps terminal installs lively while redirected or scripted installs stay plain; use `npx lithermes-ai install --yes --no-spinner` for quiet terminal installs.
 - `/start-work`: execution-only for an approved plan. Natural-language `lit start work`
   is `BLOCKED` because a hook cannot switch Hermes commands; invoke `/start-work <plan>` explicitly.
+- `/review-work` records a local redacted `delegate_batch_intent` summary for its
+  single five-lane `delegate_task` batch under `.hermes/lithermes/runs/<run>/delegate_batches/<batch>/`.
 - LitHermes workflow skill set: `ai-slop-remover`, `comment-checker`,
   `debugging`, `deep-interview`, `frontend-ui-ux`, `git-master`, `init-deep`,
   `lsp`, `programming`, `refactor`,
@@ -84,6 +97,11 @@ Restart any running Hermes CLI or Hermes gateway process. Then open Hermes and t
   and uncertainty; keep any journal under `.hermes/lithermes/litresearch/`.
 - `lit goal`: litgoal mode. Bind one objective plus checkable criteria through
   `goal_set` / `goal_*` tools; state lives in `.hermes/lithermes/litgoal/`.
+- `lit workflow` / `lit kanban`: durable-workflow mode. Probe `hermes version`,
+  `hermes kanban --help`, and `hermes profile list`; if setup is missing, print
+  `hermes kanban init` and `hermes gateway start` next steps. Create/propose a
+  Kanban root card only when setup and approval are present.
+- `lit team`: no literal native team mode is claimed; use Hermes Kanban profile lanes.
 - `lit start work`: `BLOCKED` unless the user invokes the native `/start-work`
   command. `/start-work` is execution-only for approved plans.
 
@@ -128,6 +146,16 @@ Install with npm:
 npx lithermes-ai install --yes
 ```
 
+Non-interactive npx install:
+
+```sh
+npx --yes lithermes-ai@latest install --yes
+```
+
+`npx --yes` only suppresses npm's prompt to download/run the package. LitHermes
+still requires `install --yes` before it mutates Hermes config. Running
+`npx --yes lithermes-ai@latest install` is therefore expected to stop safely.
+
 Install with Bun:
 
 ```sh
@@ -142,6 +170,10 @@ npx lithermes-ai install --yes --hermes-home /path/to/.hermes
 
 LitHermes refuses to mutate Hermes config unless you pass `--yes`. If `~/.hermes/plugins/lithermes` already exists but was not created by this installer, installation stops instead of overwriting user files.
 
+Do not install as `npx lithermes@latest ...`: `lithermes` is not the npm package
+name. Use `lithermes-ai` (or `npx --package lithermes-ai@latest lithermes ...`
+when you explicitly want the `lithermes` binary name).
+
 ## Verify
 
 Check the package and Hermes compatibility:
@@ -229,6 +261,28 @@ Uninstall intentionally preserves unrelated files in `~/.hermes/plugins`.
 
 ## Troubleshooting
 
+### `Refusing to mutate Hermes config without --yes`
+
+You passed `--yes` to npx but not to the LitHermes installer. Use:
+
+```sh
+npx --yes lithermes-ai@latest install --yes
+```
+
+### `No matching version found for lithermes@latest`
+
+The npm package is `lithermes-ai`, not `lithermes`:
+
+```sh
+npx --yes lithermes-ai@latest install --yes
+```
+
+If you need the `lithermes` binary explicitly, run:
+
+```sh
+npx --yes --package lithermes-ai@latest lithermes install --yes
+```
+
 ### `Hermes installation not found`
 
 Pass the Hermes home explicitly:

package/README_Ko-KR.md

@@ -39,6 +39,16 @@ bunx lithermes-ai doctor
 npx lithermes-ai install --yes
 ```
 
+npx를 통한 첫 설치에서 확인 질문을 모두 생략하려면 두 종류의 `--yes`를 모두
+전달합니다.
+
+```sh
+npx --yes lithermes-ai@latest install --yes
+```
+
+앞의 `--yes`는 npx용이고, 뒤의 `install --yes`는 LitHermes installer용입니다.
+npm 패키지명은 `lithermes-ai`이며, `lithermes`는 설치 후 CLI/plugin 이름입니다.
+
 실행 중인 Hermes CLI 또는 Hermes gateway를 재시작합니다. 그 다음 Hermes에서 이렇게 사용합니다.
 
 ```text
@@ -52,13 +62,16 @@ npx lithermes-ai install --yes
 - `/lit-loop`: 같은 실행 loop를 명시적으로 호출합니다.
 - `/lit-plan`: 구현 계획을 먼저 세웁니다.
 - natural routing: 일반 문장 속 standalone lit / litwork / lit plan / lit review /
-  lit research / lit goal을 Hermes-native mode로 라우팅합니다. code spans,
+  lit research / lit goal을 Hermes-native mode로 라우팅하고, lit workflow / lit kanban은
+  Hermes Kanban setup/proposal 안내로, lit team은 literal native team mode가 아니라
+  Kanban profile lane으로 매핑합니다. code spans,
   fenced code, substring, compound token, path 안의 lit, 실제 slash-command 언급은 무시합니다.
 - `/litwork-loop`, `/litwork-plan`: 긴 이름의 alias입니다.
 - `/lit_loop`, `/lit_plan`: Telegram dispatch에 맞춘 gateway alias입니다.
 - 네이티브 `/goal` 바인딩: Hermes에는 model-facing goal tool이 없으므로 `/lit`, `/lit-loop`, `/lit-plan`은 세션 goal manager를 통해 네이티브 standing `/goal`을 대신 설정합니다(턴을 넘어 유지되고 네이티브 evidence-judge가 완료를 판정). success criteria와 증거는 durable `goal_*` 도구로 추적합니다.
 - interactive install spinner가 terminal 설치는 더 생동감 있게 보여주고, redirect/script 설치는 기존처럼 plain output을 유지합니다. 조용한 terminal 설치가 필요하면 `npx lithermes-ai install --yes --no-spinner`를 사용합니다.
 - `/start-work`: 승인된 plan만 실행하는 execution-only 명령입니다. 자연어 `lit start work`는 hook이 Hermes command 전환을 할 수 없으므로 `BLOCKED`되고, 사용자가 `/start-work <plan>`을 직접 호출해야 합니다.
+- `/review-work`: 단일 5-lane `delegate_task` batch에 대해 redacted local `delegate_batch_intent` 요약을 `.hermes/lithermes/runs/<run>/delegate_batches/<batch>/`에 기록합니다.
 - LitHermes workflow skill set: `ai-slop-remover`, `comment-checker`,
   `debugging`, `deep-interview`, `frontend-ui-ux`, `git-master`, `init-deep`,
   `lsp`, `programming`, `refactor`,
@@ -75,6 +88,10 @@ npx lithermes-ai install --yes
 - `lit review`: review-work mode입니다. behavior, tests, docs/package readiness, security/safety, cleanup evidence를 5-lane으로 검증합니다.
 - `lit research`: verified facts, hypotheses, sources, uncertainty를 분리하고 journal은 `.hermes/lithermes/litresearch/`에 둡니다.
 - `lit goal`: one objective plus checkable criteria를 `.hermes/lithermes/litgoal/`에 `goal_*` 도구로 기록합니다.
+- `lit workflow` / `lit kanban`: durable-workflow mode입니다. `hermes version`,
+  `hermes kanban --help`, `hermes profile list`를 먼저 확인하고, setup이 없으면
+  `hermes kanban init`, `hermes gateway start` 안내만 출력합니다. setup과 승인이 있을 때만 Kanban root card를 만들거나 제안합니다.
+- `lit team`: literal native team mode를 주장하지 않고 Hermes Kanban profile lane을 사용합니다.
 - `lit start work`: `BLOCKED`; 승인된 plan에 대해 native `/start-work <approved-plan>`을 직접 호출해야 합니다.
 
 Natural routing은 `code spans`, fenced code, `/lit` 같은 실제 slash-command mention,
@@ -114,6 +131,16 @@ npm으로 설치합니다.
 npx lithermes-ai install --yes
 ```
 
+npx 확인 질문까지 생략하는 설치:
+
+```sh
+npx --yes lithermes-ai@latest install --yes
+```
+
+`npx --yes`는 npm의 패키지 다운로드/실행 확인만 생략합니다. LitHermes가 Hermes
+config를 수정하려면 여전히 `install --yes`가 필요합니다. 따라서 `npx --yes
+lithermes-ai@latest install`이 안전하게 멈추는 것은 정상 동작입니다.
+
 Bun으로 설치합니다.
 
 ```sh
@@ -128,6 +155,10 @@ npx lithermes-ai install --yes --hermes-home /path/to/.hermes
 
 LitHermes는 `--yes`가 없으면 Hermes config를 수정하지 않습니다. 또한 `~/.hermes/plugins/lithermes`가 이미 있는데 이 installer가 만든 파일이 아니면, 사용자 파일을 덮어쓰지 않고 멈춥니다.
 
+`npx lithermes@latest ...`로 설치하지 마세요. npm 패키지명은 `lithermes-ai`이고,
+`lithermes`는 binary/plugin 이름입니다. binary 이름을 명시하고 싶다면
+`npx --package lithermes-ai@latest lithermes install --yes`를 사용하세요.
+
 ## 확인
 
 패키지와 Hermes 호환성을 확인합니다.
@@ -215,6 +246,28 @@ npx lithermes-ai uninstall --yes
 
 ## 문제 해결
 
+### `Refusing to mutate Hermes config without --yes`
+
+`--yes`를 npx에는 넘겼지만 LitHermes installer에는 넘기지 않은 경우입니다.
+
+```sh
+npx --yes lithermes-ai@latest install --yes
+```
+
+### `No matching version found for lithermes@latest`
+
+npm 패키지는 `lithermes`가 아니라 `lithermes-ai`입니다.
+
+```sh
+npx --yes lithermes-ai@latest install --yes
+```
+
+`lithermes` binary 이름을 꼭 명시하려면 다음처럼 실행하세요.
+
+```sh
+npx --yes --package lithermes-ai@latest lithermes install --yes
+```
+
 ### `Hermes installation not found`
 
 Hermes home을 직접 지정하세요.

package/assets/lithermes-plugin/README.md

@@ -3,6 +3,16 @@
 Hermes-native workflow tools for plan-first execution, evidence ledgers, and
 first-class Hermes skills:
 
+Install from npm with the package name `lithermes-ai`:
+
+```sh
+npx --yes lithermes-ai@latest install --yes
+```
+
+`npx --yes` only approves npm package execution; `install --yes` is the LitHermes
+installer approval to mutate Hermes config. `lithermes` is the installed
+CLI/plugin name, not the npm package name.
+
 - `/lit-plan` and `/litwork-plan` create durable plans in `plans/`, then forward a
   goal bootstrap to the Hermes agent instead of stopping at plan creation.
 - `/lit-loop` and `/litwork-loop` create run state under
@@ -11,7 +21,10 @@ first-class Hermes skills:
   execution-only and never bootstraps a plan from a brief.
 - The `pre_llm_call` hook injects an Litwork directive when the user says
   a standalone `lit` or `litwork`. It also routes `lit plan`, `lit review`,
-  `lit research`, and `lit goal` to the matching `lithermes:*` skill contract.
+  `lit research`, `lit goal`, and durable `lit workflow` / `lit kanban` / `lit team`
+  intents to the matching Hermes-native contract. Kanban routes are setup/proposal
+  guidance for Hermes Kanban profile lanes; `lit team` does not claim a literal
+  native team mode.
   Hermes has no model-facing goal tools, so a direct `lit <task>` (and the /lit
   command) binds the native standing `/goal` via the session goal manager;
   criteria + evidence use the durable `goal_*` tools.
@@ -26,7 +39,8 @@ first-class Hermes skills:
   `lithermes:lit-plan`, `lithermes:litgoal`, and `lithermes:litwork`.
 - Delegation fans lanes out through the native `delegate_task` tool (children
   run in parallel, the parent blocks for all); there is no named-agent registry
-  and no per-child model selection.
+  and no per-child model selection. Broad review commands record a local redacted
+  `delegate_batch_intent` summary under `.hermes/lithermes/runs/<run>/delegate_batches/<batch>/`.
 
 ## Mode Contract
 
@@ -40,6 +54,11 @@ first-class Hermes skills:
   journals live under `.hermes/lithermes/litresearch/<slug>/`.
 - `lit goal`: bind one objective plus checkable criteria in
   `.hermes/lithermes/litgoal/`.
+- `lit workflow` / `lit kanban`: durable-workflow setup/proposal mode through
+  Hermes Kanban. Probe `hermes version`, `hermes kanban --help`, and
+  `hermes profile list`; initialize/start gateway if missing; create/propose a
+  Kanban root card only after setup and approval.
+- `lit team`: no literal native team mode is claimed; use Hermes Kanban profile lanes.
 - `lit start work`: `BLOCKED` in natural routing because `pre_llm_call` cannot
   switch Hermes commands. The user must invoke `/start-work <approved-plan>`.
 

package/assets/lithermes-plugin/core.py

@@ -198,6 +198,66 @@ def record_event(event: str, **fields: Any) -> None:
         pass
 
 
+_REMOTE_REF_RE = re.compile(r"https?://[^\s,;\"'<>]+", re.IGNORECASE)
+
+
+def _redact_local_only_preview(value: Any) -> str:
+    """Small local-only diagnostic preview for event metadata.
+
+    Delegate batch events must never become remote telemetry. Keep the preview
+    bounded, secret-redacted, and URL-redacted so audit logs prove intent without
+    preserving endpoints or pasted secret-bearing child context.
+    """
+    text = json.dumps(redact_obj(value), sort_keys=True) if not isinstance(value, str) else redact_text(value)
+    text = _REMOTE_REF_RE.sub("[REDACTED_URL]", text)
+    return text[:1000]
+
+
+def record_delegate_batch_intent(
+    *,
+    workspace: Path,
+    mode: str,
+    lanes: Iterable[str],
+    session_id: str = "",
+    context: Any = None,
+) -> dict[str, Any]:
+    """Record a local, redacted intent event for a Hermes delegate_task batch.
+
+    This is evidence only: it does not orchestrate workers, create persistent
+    teams, or send telemetry anywhere. Hermes still performs the actual short
+    parallel work through one synchronous delegate_task batch.
+    """
+    rid = run_id("lithermes")
+    batch_id = run_id("delegate-batch")
+    lane_list = [str(lane) for lane in lanes]
+    artifact_dir = lithermes_dir(workspace) / "runs" / rid / "delegate_batches" / batch_id
+    payload = {
+        "event": "delegate_batch_intent",
+        "timestamp": utc_now().isoformat(),
+        "session_id": session_id,
+        "run_id": rid,
+        "batch_id": batch_id,
+        "mode": mode,
+        "lanes": lane_list,
+        "artifact_dir": str(artifact_dir) + "/",
+    }
+    if context is not None:
+        payload["context_preview"] = _redact_local_only_preview(context)
+    try:
+        artifact_dir.mkdir(parents=True, exist_ok=True)
+        (artifact_dir / "summary.json").write_text(
+            json.dumps(redact_obj(payload), indent=2, sort_keys=True) + "\n",
+            encoding="utf-8",
+        )
+    except OSError:
+        pass
+    try:
+        append_jsonl(event_log_path(), payload)
+    except OSError:
+        pass
+    return redact_obj(payload)
+
+
 _RUN_CONTEXT_TASK_PATTERN = re.compile(r"^task:\s*(?P<task>.+?)\s*$", re.MULTILINE)
 
 
@@ -282,6 +342,17 @@ def detect_lit_mode(message: str) -> NaturalLitRoute | None:
         if token == "litwork":
             return NaturalLitRoute(mode="litwork", objective=_clamp_task(after), visible_message=visible)
 
+        for word in ("workflow", "kanban"):
+            rest = _after_mode_word(after, word)
+            if rest is not None:
+                return NaturalLitRoute(mode="durable-workflow", objective=_clamp_task(rest), visible_message=visible)
+
+        team_rest = _after_mode_word(after, "team")
+        if team_rest is not None:
+            mode_rest = _after_mode_word(team_rest, "mode")
+            objective = mode_rest if mode_rest is not None else team_rest
+            return NaturalLitRoute(mode="kanban-team", objective=_clamp_task(objective), visible_message=visible)
+
         start_rest = _after_start_work(after)
         if start_rest is not None:
             block = (
@@ -312,6 +383,33 @@ def detect_lit_mode(message: str) -> NaturalLitRoute | None:
 
 def build_natural_mode_context(route: NaturalLitRoute) -> str:
     objective = route.objective or "(no objective text supplied — ask for the missing objective if needed)"
+    if route.mode in {"durable-workflow", "kanban-team"}:
+        team_note = (
+            "Hermes has no literal native team mode; team-like work maps to Hermes Kanban profile lanes and worker lanes."
+            if route.mode == "kanban-team"
+            else "Hermes durable-workflow route: use Hermes Kanban for broad/background work."
+        )
+        return "\n".join(
+            [
+                f"<lithermes-natural-route mode=\"{route.mode}\">",
+                "Natural routing: durable-workflow intent -> Hermes Kanban.",
+                team_note,
+                f"Objective: {objective}",
+                "Mode Contract: setup/propose only unless Kanban is already available, initialized, and the user approved creation.",
+                "Capability probe before creating anything:",
+                "- hermes version",
+                "- hermes kanban --help",
+                "- hermes profile list",
+                "If setup is missing, do not fake a workflow start; print these next commands:",
+                "- hermes kanban init",
+                "- hermes gateway start",
+                "- hermes profile list",
+                "If setup and approval are present, create/propose a Kanban root card via kanban_create or `hermes kanban create`.",
+                "Root card fields: title/objective, acceptance criteria, assignee/profile, workspace, skills, dependencies, and goal_mode when open-ended.",
+                "External CLI worker lanes are not paved without a separate spawn_fn integration; do not promise them.",
+                "</lithermes-natural-route>",
+            ]
+        )
     if route.blocked:
         return "\n".join(
             [
@@ -986,6 +1084,16 @@ def command_review_work(raw_args: str) -> dict[str, str]:
         diff = diff[:60000] + "\n... [diff truncated at 60k chars — lanes should read full files as needed]"
     run_cmd = detect_run_command(workspace)
     files_block = changed or "(no changed files detected vs " + base + ")"
+    batch_event = record_delegate_batch_intent(
+        workspace=workspace,
+        mode="review-work",
+        lanes=[key for key, _ in REVIEW_LANES],
+        context={
+            "base": base,
+            "changed_file_count": len([f for f in changed.splitlines() if f.strip()]),
+            "run_command": run_cmd,
+        },
+    )
 
     lane_lines = []
     for key, brief in REVIEW_LANES:
@@ -998,6 +1106,7 @@ def command_review_work(raw_args: str) -> dict[str, str]:
         f"workspace: {workspace}",
         f"base: {base}",
         f"run command (for QA lane): {run_cmd}",
+        f"delegate batch evidence: {batch_event.get('artifact_dir', '')}",
         "",
         "Changed files:",
         files_block,

package/assets/lithermes-plugin/payload-version.json

@@ -1,7 +1,7 @@
 {
-  "syncedAt": "2026-06-19T02:30:00.000Z",
+  "syncedAt": "2026-06-21T06:34:00.000Z",
   "source": "source-reference",
-  "sourceHash": "0a2b29742e4410128d26429945f694c77d47dc5a0d3f80a6bda8b1cbbb21200f",
+  "sourceHash": "19037e85902a521d49548d34c1ceaefa0894d89343ed1829ed5cb85500eeedfb",
   "files": [
     {
       "path": "NOTICE.md",
@@ -9,7 +9,7 @@
     },
     {
       "path": "README.md",
-      "sha256": "29a32fca9db9fd12a2a9e307e93f44ba2a8274fde19946011944958c1a1ebc6d"
+      "sha256": "9eea08f516c7db2a6d1f8c622b6ea3f6b18a37e800013c38cfbb062a0594b28a"
     },
     {
       "path": "__init__.py",
@@ -17,7 +17,7 @@
     },
     {
       "path": "core.py",
-      "sha256": "d0689b196a2721c99c3c83a5e82482869da0d80e57a52c07f54d9268989c31b0"
+      "sha256": "2784fd77147e539e32aee44db81ecc6744ae084732eaf134e90313b3e2cacd48"
     },
     {
       "path": "litgoal/__init__.py",
@@ -49,7 +49,7 @@
     },
     {
       "path": "plugin.yaml",
-      "sha256": "9d49a09370193484755d21941af9f6d977dfef780c7a8d6657c115ff643b0bbd"
+      "sha256": "92bb4dabbc0de842b811471a407a426dd6165d96a433937ab9ab687c4291ad5e"
     },
     {
       "path": "redaction.py",
@@ -65,7 +65,7 @@
     },
     {
       "path": "skills/debugging/SKILL.md",
-      "sha256": "48bdb0df0f41633aca17d6193aa98aabac4c49cc25c36e50f26b020f89f77d43"
+      "sha256": "5b1b4f536579d0fb459eb9e5a79ee7d70bad26149799c0417b3c258b3f00bba5"
     },
     {
       "path": "skills/debugging/references/methodology/00-setup.md",
@@ -169,7 +169,7 @@
     },
     {
       "path": "skills/litresearch/SKILL.md",
-      "sha256": "363468a509f7743037b2f132171b7b1351d11c10680985a49cab1693855a0a20"
+      "sha256": "31ee558ac64f3cadd229adf5255255cd7bf3fa5a8dbc049920d7ed7692ea2c96"
     },
     {
       "path": "skills/litwork/SKILL.md",
@@ -281,7 +281,7 @@
     },
     {
       "path": "skills/programming/SKILL.md",
-      "sha256": "ffb201197e7386c848f8efb9b90d0a024d7b8000e8bea1b13b0ed7a83627a56b"
+      "sha256": "a373df296ce4ce7e0fed2118a11e6cc70eedcc6e81520035d097d079a6484f99"
     },
     {
       "path": "skills/programming/references/go/README.md",
@@ -569,7 +569,7 @@
     },
     {
       "path": "skills/refactor/SKILL.md",
-      "sha256": "d4e160e256b5a5e1fae4170edeee7a6bc8e2338bbebec797e24f07ea70687a10"
+      "sha256": "37913c1154e1110492f14cafe3836e344728b1fd85a7a324e837e52b9f03e3d6"
     },
     {
       "path": "skills/remove-ai-slops/SKILL.md",
@@ -577,7 +577,7 @@
     },
     {
       "path": "skills/review-work/SKILL.md",
-      "sha256": "4af425ec7924f1cd3d5fac633351f84d587cbaa68498d46daad9faf066c937ec"
+      "sha256": "a232c83f95b2109231c4b752267d5bc0a96a4c853c7e7b8b590c73445391d94a"
     },
     {
       "path": "skills/rules/SKILL.md",

package/assets/lithermes-plugin/plugin.yaml

@@ -1,5 +1,5 @@
 name: lithermes
-version: 0.8.6
+version: 0.8.8
 description: "Hermes-native workflow toolkit: litgoal durable runtime, 5-lane review orchestrator, Litwork commands, skills, and prompt steering."
 author: "Hermes Agent"
 kind: standalone

package/assets/lithermes-plugin/skills/debugging/SKILL.md

@@ -67,7 +67,7 @@ Each phase has exactly one reference. Read it as you enter the phase — not in
 | 0 | **Environment assessment** — know the runtime, ports, symbols, env vars, watchers before attaching | [references/methodology/00-setup.md](references/methodology/00-setup.md) |
 | 1 | **Journal setup** — single `.debug-journal.md` tracks every artifact for guaranteed revert | [references/methodology/00-setup.md](references/methodology/00-setup.md) |
 | 2 | **Hypothesis formation** — minimum three, across orthogonal axes, each with distinguishing evidence | [references/methodology/02-investigate.md](references/methodology/02-investigate.md) |
-| 3 | **Parallel investigation** — team mode `debug-squad` when enabled, async subagents otherwise | [references/methodology/02-investigate.md](references/methodology/02-investigate.md) |
+| 3 | **Parallel investigation** — one Hermes-native `delegate_task` batch for short investigations; use Kanban profile lanes for durable/background debugging programs | [references/methodology/02-investigate.md](references/methodology/02-investigate.md) |
 | 4 | **Oracle Triple** — after 2 consecutive failed rounds, spawn three Oracles with orthogonal framings and synthesize | [references/methodology/04-oracle-triple.md](references/methodology/04-oracle-triple.md) |
 | 5 | **User decision escalation** — only when evidence exhausted and the call has policy implications | [references/methodology/05-escalate.md](references/methodology/05-escalate.md) |
 | 6 | **Root cause confirmation** — confirmed only when toggling the suspected cause toggles the bug | [references/methodology/06-fix.md](references/methodology/06-fix.md) |

package/assets/lithermes-plugin/skills/litresearch/SKILL.md

@@ -28,6 +28,11 @@ If a single retrieval would answer it, do that directly and do not invoke litres
 
 Everything in this skill runs on one tool: the native `delegate_task`.
 
+Use this mode for short, in-turn research where the parent should wait for the
+parallel children and synthesize their returns. If the user asks for durable,
+background, dynamic-workflow-style collaboration, route to Hermes Kanban (`lit workflow`
+/ `lit kanban`) instead of stretching `delegate_task` into a queue.
+
 - **Parallel swarm fan-out** is a single `delegate_task` call carrying a `tasks` array — one entry per worker. The parent blocks until every child in the batch stops, then you merge their returns. This replaces any notion of a separate workflow tool, background spawning, or named-agent registry: there is no `subagent_type`, no per-child model selection, and no foreign agent name. You shape each child entirely through its `goal`, `context`, optional `toolsets`, and optional `role`.
 - **Worker roles** (codebase explorer, web/docs librarian, browsing, repo deep-dive, verifier) are not registered agents. Each is a read-only `delegate_task` child whose `goal`/`context` fully describe the role's mandate, scope, protocol, and required reply tail. Two children differ only by the text you give them.
 - **Recursion** comes from your expansion waves, not from a child spawning its own children. Children are leaves; depth is the parent's job.

package/assets/lithermes-plugin/skills/programming/SKILL.md

@@ -11,7 +11,40 @@ This skill is an index. The hard per-language rules live under `references/`. Lo
 
 ---
 
-## PHASE 0 — LANGUAGE GATE (RUN THIS FIRST, EVERY TIME)
+## PHASE -1 — BUILD-DECISION GATE (RUN BEFORE PHASE 0)
+
+Before writing or editing a single line of implementation code, work down these
+checks and stop at the first one that cleanly meets the need:
+
+1. Does this need to exist at all? If the outcome does not require it, do not build it.
+2. Does the standard library already do it well? If so, use it.
+3. Is there a native platform, runtime, or framework feature for it? If so, use it.
+4. Does an already-installed dependency cover it cleanly? If so, reuse it — do not add or hand-roll.
+5. Can the remaining gap be one clear line? If so, write the one line.
+6. Only after all of the above fail: write the minimum code that genuinely works — nothing speculative.
+
+Scope and floor (these keep the gate from under-building):
+
+- Judge "minimum that works" over the WHOLE task, not per call site. If the same
+  logic appears at more than one call site, the minimum that works IS one small
+  shared helper — extract it.
+- "Works" includes error handling for any failure the code can realistically hit
+  (network, parse, missing file, bad state) and the tests that prove the behavior
+  you just wrote. Only handling for states that genuinely cannot occur is the
+  speculative part to cut.
+- Reach for a stdlib / native / dependency option only when it fits the need
+  cleanly, not merely because it technically can.
+- Never shorten away, for the sake of fewer lines: input validation at trust
+  boundaries, handling that prevents data loss or corruption, security controls
+  (auth, secret handling, injection/escaping), or accessibility. The point is to
+  remove redundancy and speculation, never to lower the correctness floor.
+
+PHASE -1 decides WHETHER and FROM WHAT to build; PHASE 0 and the per-language iron
+list decide HOW.
+
+---
+
+## PHASE 0 — LANGUAGE GATE (RUN AFTER PHASE -1, EVERY TIME)
 
 **DO NOT WRITE OR EDIT A SINGLE LINE OF CODE BEFORE COMPLETING THIS GATE.**
 
@@ -355,6 +388,7 @@ After every code-writing session, answer these out loud (in your reply) before d
 5. **Defensive layer?** Any null check, try/except, or `isinstance` guarding a value the type system already proves? If yes, delete.
 6. **Helpers for one-off?** Any function, class, or trait introduced for a single caller that will never get a second caller? If yes, inline.
 7. **Tests?** Is the behavior I just introduced locked by a test that would fail if I revert this commit?
+8. **Necessity & reuse?** Did everything I wrote need to exist, and did I confirm the standard library, a native feature, or an already-installed dependency did not already cover it before I hand-rolled? If not, remove it.
 
 **If any answer fails, fix it before declaring done.** This loop is the difference between "the code compiles" and "the code is correct."
 

package/assets/lithermes-plugin/skills/refactor/SKILL.md

@@ -32,6 +32,11 @@ section wins — every foreign delegation call in the prose below is a LEGACY il
 copied from another harness; never call any of them literally, map each to a
 `delegate_task` child.
 
+For durable/background refactor programs that need profile assignees, dependencies,
+comments, and audit trails over time, use Hermes Kanban through the `lit workflow` /
+`lit kanban` route. Do not fake a persistent refactor team on top of short `delegate_task`
+batches.
+
 export const REFACTOR_TEMPLATE = `# Intelligent Refactor Command
 
 ## Usage

package/assets/lithermes-plugin/skills/review-work/SKILL.md

@@ -22,6 +22,11 @@ the five lane briefs plus the gate contract. Then:
 Lane → child mapping (dispatch all five in the single batch):
 `goal` · `qa` · `code-quality` · `security` (supplementary) · `context/docs/package`.
 
+The `/review-work` command records a local, redacted `delegate_batch_intent` event and
+summary directory before handing off to the model. Treat this as audit evidence only:
+it does not create a persistent team, does not make remote telemetry, and does not
+replace Hermes' fork/join `delegate_task` execution.
+
 Each child returns: `verdict` (PASS|FAIL), `confidence`, and findings with `file:line`.
 The review must cover behavior, tests, docs/package readiness, security/safety,
 and cleanup evidence; green tests without a real-surface probe are insufficient.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "lithermes-ai",
-  "version": "0.8.6",
+  "version": "0.8.8",
   "description": "npx/bunx installer for the LitHermes Hermes plugin",
   "license": "MIT",
   "repository": {