loki-mode 9.35.0 → 9.36.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/SKILL.md +2 -2
- package/VERSION +1 -1
- package/autonomy/run.sh +19 -0
- package/dashboard/__init__.py +1 -1
- package/docs/INSTALLATION.md +1 -1
- package/loki-ts/dist/loki.js +321 -318
- package/mcp/__init__.py +1 -1
- package/package.json +1 -1
- package/plugins/loki-mode/.claude-plugin/plugin.json +1 -1
package/SKILL.md
CHANGED
|
@@ -3,7 +3,7 @@ name: loki-mode
|
|
|
3
3
|
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.
|
|
4
4
|
---
|
|
5
5
|
|
|
6
|
-
# Loki Mode v9.
|
|
6
|
+
# Loki Mode v9.36.0
|
|
7
7
|
|
|
8
8
|
**You are an autonomous agent. You make decisions. You do not ask questions. You do not stop.**
|
|
9
9
|
|
|
@@ -470,4 +470,4 @@ See `CHANGELOG.md` entries [7.5.7], [7.5.8], [7.5.13] for the per-fix list and r
|
|
|
470
470
|
|
|
471
471
|
---
|
|
472
472
|
|
|
473
|
-
**v9.
|
|
473
|
+
**v9.36.0 | [Autonomi](https://www.autonomi.dev/) flagship product | ~410 lines core**
|
package/VERSION
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
9.
|
|
1
|
+
9.36.0
|
package/autonomy/run.sh
CHANGED
|
@@ -24514,12 +24514,31 @@ EOF
|
|
|
24514
24514
|
_loki_check_claim_grounding || true
|
|
24515
24515
|
fi
|
|
24516
24516
|
local _loki_completion_ready=1
|
|
24517
|
+
# TIME THE COUNCIL. Measured on a one-function build: the agent did
|
|
24518
|
+
# the work in 71s and the council window was 142s -- the largest
|
|
24519
|
+
# single cost in the run -- yet it was the one major step with no
|
|
24520
|
+
# stage_complete record, so its cost could only be INFERRED from
|
|
24521
|
+
# artifact mtimes. Inferring duration from mtimes is invalid (an
|
|
24522
|
+
# mtime says when a file was written, not how long a step took), and
|
|
24523
|
+
# doing so produced a wrong attribution that had to be retracted.
|
|
24524
|
+
# Emitting the real number makes the profile measured rather than
|
|
24525
|
+
# guessed. Purely additive: emit_stage_complete never changes a
|
|
24526
|
+
# verdict, an exit code, or control flow.
|
|
24527
|
+
local _council_t0
|
|
24528
|
+
_council_t0=$(date +%s 2>/dev/null || echo "")
|
|
24517
24529
|
if loki_is_supervised_simple_web; then
|
|
24518
24530
|
_loki_supervised_completion_gates_pass "${gate_failures:-}" && _loki_completion_ready=0
|
|
24519
24531
|
elif type council_should_stop &>/dev/null \
|
|
24520
24532
|
&& LOKI_COMPLETION_CLAIMED="$_loki_completion_claimed" council_should_stop; then
|
|
24521
24533
|
_loki_completion_ready=0
|
|
24522
24534
|
fi
|
|
24535
|
+
# Status reports what the council DECIDED, not whether it errored:
|
|
24536
|
+
# "pass" = it approved a stop, "not_run" = it ran and declined to
|
|
24537
|
+
# stop (the build continues). Both are normal outcomes; neither is a
|
|
24538
|
+
# failure, so neither is reported as one.
|
|
24539
|
+
emit_stage_complete "completion_council" \
|
|
24540
|
+
"$([ "$_loki_completion_ready" -eq 0 ] 2>/dev/null && echo pass || echo not_run)" \
|
|
24541
|
+
"$_council_t0" 2>/dev/null || true
|
|
24523
24542
|
if [ "$_loki_completion_ready" -eq 0 ]; then
|
|
24524
24543
|
# bash-F1: council_should_stop returns 0 from a genuine approval
|
|
24525
24544
|
# AND from two force-stop safety valves (stagnation flood /
|
package/dashboard/__init__.py
CHANGED
package/docs/INSTALLATION.md
CHANGED
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
|
|
3
3
|
The flagship product of [Autonomi](https://www.autonomi.dev/). Loki Mode is a spec-driven autonomous builder with a built-in trust layer that takes any spec to a deployed product and verifies completion with evidence (quality gates plus a completion council), not just a "done" claim. Complete installation instructions for all platforms and use cases.
|
|
4
4
|
|
|
5
|
-
**Version:** v9.
|
|
5
|
+
**Version:** v9.36.0
|
|
6
6
|
|
|
7
7
|
---
|
|
8
8
|
|