loki-mode 7.76.0 → 7.78.0

package/SKILL.md

@@ -3,7 +3,7 @@ name: loki-mode
 description: Autonomous spec-driven build system with a built-in trust layer. It does not call work done until it is verified (RARV-C closure loop, 8 quality gates, completion council, verified-completion evidence gate). Triggers on "Loki Mode". Takes a spec (PRD, GitHub issue, OpenAPI doc, etc.) to deployed product with minimal human intervention. Provider-agnostic. Requires --dangerously-skip-permissions flag.
 ---
 
-# Loki Mode v7.76.0
+# Loki Mode v7.78.0
 
 **You are an autonomous agent. You make decisions. You do not ask questions. You do not stop.**
 
@@ -406,4 +406,4 @@ See `CHANGELOG.md` entries [7.5.7], [7.5.8], [7.5.13] for the per-fix list and r
 
 ---
 
-**v7.76.0 | [Autonomi](https://www.autonomi.dev/) flagship product | ~260 lines core**
+**v7.78.0 | [Autonomi](https://www.autonomi.dev/) flagship product | ~260 lines core**

package/VERSION

@@ -1 +1 @@
-7.76.0
+7.78.0

package/autonomy/NOTIFY_INTEGRATION.md

@@ -2,6 +2,15 @@
 
 This document describes how to integrate multi-channel notifications (Slack, Discord, Webhook) into run.sh.
 
+> Note (v7.78.0): the convenience wrappers `notify_task_started`,
+> `notify_task_completed`, `notify_task_failed`, `notify_phase_complete`, and
+> `notify_all_complete` were never wired into the runtime and were removed as dead
+> code. The live notification helpers are `notify_intervention_needed` and
+> `notify_rate_limit` (plus the `notify_channels` snippets shown below). Snippets
+> in this guide that reference the removed wrappers are illustrative of where a
+> notification COULD be emitted; use `notify_channels` (or the live helpers) when
+> actually wiring one.
+
 ## Quick Start
 
 ```bash

package/autonomy/lib/voter-agents.sh

@@ -256,7 +256,22 @@ loki_council_dispatch_agents() {
     # default-off export in claude-flags.sh (sourced above) already covers this;
     # the inline prefix is belt-and-suspenders, self-documenting, and a no-op when
     # caveman is absent.
-    response=$(CAVEMAN_DEFAULT_MODE=off claude --dangerously-skip-permissions \
+    #
+    # timeout-guard the dispatch (parity with the heuristic council path in
+    # completion-council.sh:2074 and :2200, same LOKI_COUNCIL_REVIEW_TIMEOUT:-600
+    # knob). The heuristic loop this dispatch replaced wrapped every claude
+    # subcall in `timeout`; this helper did not, so a hung `claude --agents`
+    # would stall the entire run indefinitely. `timeout` precedes the env-var
+    # assignment, so `env` is used to set CAVEMAN_DEFAULT_MODE for the child.
+    # On timeout, `timeout` exits 124; that exit is the command-substitution exit
+    # (no pipe here), captured into rc via `|| rc=$?`. The existing rc check below
+    # then routes any non-zero exit (timeout 124 or any other claude failure) to
+    # `return 1` -- the heuristic fallback the caller falls through to
+    # (completion-council.sh:2792). Fail-closed: a hung or timed-out council can
+    # never become a false COMPLETE; it always degrades to the heuristic path
+    # (which has its own timeout + conservative defaults).
+    response=$(timeout "${LOKI_COUNCIL_REVIEW_TIMEOUT:-600}" \
+                      env CAVEMAN_DEFAULT_MODE=off claude --dangerously-skip-permissions \
                       -p "$prompt" \
                       --agents "$agents_json" \
                       --json-schema "$schema_path" 2>"$stderr_log") || rc=$?