loki-mode 10.5.20 → 10.5.23

package/README.md

@@ -48,6 +48,7 @@ Upgrade with `loki self-update`. Long form: [Installation Guide](docs/INSTALLATI
 ```bash
 export ANTHROPIC_API_KEY=sk-...
 loki doctor
+loki quick "fix the login bug"   # one small task on the Loki 10 engine
 ```
 
 <details>
@@ -71,9 +72,9 @@ loki-seal is a Claude Code Stop hook that runs your repo's real test suite when
 
 ## Loki 10 engine
 
-Opt-in: set LOKI_ENGINE=v10 <!-- loki10-default -->
+Default: Loki 10 engine for `loki "<task>"`, `loki owner/repo#N` and `loki quick "<task>"`. Set LOKI_ENGINE=legacy or run `loki legacy <args>` for the previous engine. <!-- loki10-default -->
 
-Loki 10 is the rewritten engine. It is not the default yet: with `LOKI_ENGINE` unset, `loki` runs the [legacy engine](#legacy-engine-reference) exactly as before. A default flip is in flight; this section describes what `main` does today (`bin/loki` routes to the v10 engine only when `LOKI_ENGINE=v10` is set). Guide, provider table and summary format: [docs/v10/GUIDE.md](docs/v10/GUIDE.md).
+Loki 10 is the rewritten engine and the default for tasks, issue mode and `quick`; `status`, `verify` and `dashboard` use it when `LOKI_ENGINE=v10` is set. Guide, provider table and summary format: [docs/v10/GUIDE.md](docs/v10/GUIDE.md).
 
 ```
 LOKI_ENGINE=v10 loki "fix the login redirect loop" --no-pr

package/SKILL.md

@@ -3,7 +3,7 @@ name: loki-mode
 description: An autonomous software factory that knows what it is supposed to deliver, and proves it did. Use when the user says Loki Mode or asks to build, fix or verify software autonomously.
 ---
 
-# Loki Mode v10.5.20
+# Loki Mode v10.5.23
 
 **You are an autonomous agent. You make decisions. You do not ask questions. You do not stop.**
 
@@ -470,4 +470,4 @@ See `CHANGELOG.md` entries [7.5.7], [7.5.8], [7.5.13] for the per-fix list and r
 
 ---
 
-**v10.5.20 | [Autonomi](https://www.autonomi.dev/) flagship product | ~410 lines core**
+**v10.5.23 | [Autonomi](https://www.autonomi.dev/) flagship product | ~410 lines core**

package/VERSION

@@ -1 +1 @@
-10.5.20
+10.5.23

package/autonomy/loki

@@ -1606,7 +1606,9 @@ show_help() {
     echo "  loki doctor               Check your setup is ready (a few seconds)"
     echo "  loki quickstart           Guided first build from your idea (no PRD needed)"
     echo "  loki start ./prd.md       Build from a spec (PRD file, GitHub/GitLab/Jira/Azure issue, or no arg)"
-    echo "  quickstart = guided first build; quick = one small task (3 iters max)."
+    echo "  quickstart = guided first build; quick = one small task (Loki 10 engine, no PR)."
+    echo "  loki \"<task>\", loki owner/repo#N and loki quick run on the Loki 10 engine by default."
+    echo "  Previous engine: set LOKI_ENGINE=legacy or run 'loki legacy <args>'."
     echo "  Docs: https://github.com/asklokesh/loki-mode  |  Report a problem: loki crash"
     echo ""
     # CLI consolidation (Phase A): the front page presents ~17 canonical
@@ -1640,6 +1642,7 @@ show_help() {
     echo ""
     echo "Verify / trust:"
     echo "  verify [base]    Deterministic PR verification (CI-gate exit codes)"
+    echo "  keys export      Print the public receipt-signing key (JWK) for third-party verify --pubkey"
     echo "  review [opts]    Standalone code review with quality gates"
     echo "  ultracode \"task\" Run a task as a native Claude Code Dynamic Workflow (opt-in, Claude-only)"
     echo "  trust [cmd]      Visible trust trajectory; 'trust detail' for metrics"
@@ -1705,7 +1708,7 @@ show_help() {
     echo "  loki start PROJ-456           # Jira issue"
     echo "  loki start --bg ./prd.md      # Start in background"
     echo "  loki start --parallel ./prd.md   # Parallel mode (git worktrees)"
-    echo "  loki quick \"add dark mode\"  # Single-task mode (3 iters max)"
+    echo "  loki quick \"add dark mode\"  # Single-task mode (Loki 10 engine; LOKI_ENGINE=legacy for 3 iters max)"
     echo "  loki tour                     # See a real sample result (no provider, no key, no spend)"
     echo "  loki demo                     # Build a sample todo app end to end"
     echo "  loki init -t saas-starter     # Scaffold from template"
@@ -1916,7 +1919,7 @@ show_landing() {
     echo -e "  ${CYAN}loki doctor${NC}           Check your setup is ready (a few seconds)"
     echo -e "  ${CYAN}loki quickstart${NC}       Guided first build from your idea (no PRD needed)"
     echo -e "  ${CYAN}loki start ./prd.md${NC}   Build from a spec (PRD file, GitHub/GitLab/Jira/Azure issue, or no arg)"
-    echo "  quickstart = guided first build; quick = one small task (3 iters max)."
+    echo "  quickstart = guided first build; quick = one small task (Loki 10 engine, no PR)."
     echo ""
     echo -e "Need help? ${CYAN}loki help${NC} lists every command."
     echo "Tip: preview cost and scope before building: loki plan <your-prd.md>"
@@ -16408,8 +16411,10 @@ cmd_quick() {
             echo ""
             echo "Usage: loki quick \"description of what to do\""
             echo ""
-            echo "Runs Loki with a lightweight execution profile: 3 iterations max,"
-            echo "no quality council, no completion gate. Best for tiny tasks."
+            echo "Runs the Loki 10 engine on one small task (no PR is opened). Set"
+            echo "LOKI_ENGINE=legacy or run 'loki legacy quick ...' for the previous engine:"
+            echo "a lightweight profile, 3 iterations max, no quality council, no completion"
+            echo "gate. Best for tiny tasks. The options below apply to the previous engine."
             echo ""
             echo "Examples:"
             echo "  loki quick \"add dark mode to this React app\""
@@ -18647,6 +18652,11 @@ with open(manifest_path, 'w') as f:
 # usable.
 # ---------------------------------------------------------------------------
 cmd_verify() {
+    # D48: --pubkey verifies a receipt against a given public key (v10 engine, no ~/.loki needed).
+    local _pk_arg
+    for _pk_arg in "$@"; do
+        [ "$_pk_arg" = "--pubkey" ] && LOKI_ENGINE=v10 exec "$_LOKI_SCRIPT_DIR/../bin/loki" verify "$@"
+    done
     # --fast: deterministic checks only, in milliseconds. Measured on this repo
     # (1,932 tracked files): 298 ms cold, 87 ms warm, 19 ms diff-scoped, against
     # an 11,040 ms shell-based baseline.
@@ -21959,6 +21969,10 @@ main() {
         verify)
             cmd_verify "$@"
             ;;
+        keys)
+            # D48: public-key export lives in the Bun v10 engine; re-enter the shim on that route.
+            LOKI_ENGINE=v10 exec "$_LOKI_SCRIPT_DIR/../bin/loki" keys "$@"
+            ;;
         spec)
             cmd_spec "$@"
             ;;

package/bin/loki

@@ -271,26 +271,73 @@ if [ "${1:-}" = "modernize" ]; then
     unset _loki_mod_a
 fi
 
-# Loki 10 engine (D29): additive; skipped entirely unless LOKI_ENGINE=v10.
-if [ "${LOKI_ENGINE:-}" = "v10" ]; then
-    _e10=0
-    case "${1:-}" in
-        status|verify|dashboard) _e10=1 ;;
-        ""|-*) _e10=0 ;;
-        # http*://*/issues/* also covers GitLab's /-/issues/ URLs.
-        */*\#[0-9]*|http*://*/issues/*|http*://*/browse/*) _e10=1 ;;
-        *" "*) _e10=1 ;;
-        # ponytail: a one-word argument stays on the legacy CLI. The telemetry
-        # allowlist is not a command registry (estimate, intent, outcomes are
-        # missing from it), so it cannot decide routing. Multi-word tasks and
-        # issue refs reach v10.
-        *) _e10=0 ;;
-    esac
-    if [ "$_e10" = "1" ]; then
-        command -v bun >/dev/null 2>&1 || { echo "Error: LOKI_ENGINE=v10 needs bun. Unset LOKI_ENGINE to use the current engine." >&2; exit 1; }
-        exec bun "$BUN_CLI" engine10 "$@"
-    fi
-fi
+# `loki legacy <args>` (D29/D48): the previous engine, exactly as LOKI_ENGINE=legacy.
+# Re-runs this shim with the pin so every route below is the pre-flip route.
+case "${1:-}" in
+    legacy)
+        shift
+        [ -f "$REPO_ROOT/autonomy/lib/engine10-legacy-notice.txt" ] && cat "$REPO_ROOT/autonomy/lib/engine10-legacy-notice.txt" >&2
+        LOKI_ENGINE=legacy exec "$SCRIPT_PATH" "$@"
+        ;;
+esac
+
+# Loki 10 engine (D29, flipped to the default by D48 rows 7-9). LOKI_ENGINE unset
+# or v10 routes `loki "<task>"`, `loki owner/repo#N` and `loki quick "<task>"` to
+# engine10; LOKI_ENGINE=v10 (explicit) also routes status/verify/dashboard. Any
+# other value (legacy, v9, ...) skips this block: the previous engine, unchanged.
+_loki_engine_default="v10"
+case "${LOKI_ENGINE:-$_loki_engine_default}" in
+    v10)
+        _e10=0
+        _e10_args=("$@")
+        case "${1:-}" in
+            status|verify|dashboard|keys)
+                [ "${LOKI_ENGINE:-}" = "v10" ] && _e10=1
+                # Bare `loki verify` follows the newest run: a v10 run newer than the newest
+                # legacy proof is verified by v10, so a FAILED default run is never VERIFIED.
+                # Only a bare call or a v10 run id (e10-*) goes there; any flag (--fast, --pr, --json, unknown) stays on legacy verify.
+                if [ "$1" = "verify" ] && [ "$_e10" = "0" ] && [ -z "${LOKI_ENGINE:-}" ] && case "${2:-}" in ""|e10-*) true ;; *) false ;; esac; then
+                    _r10=""; _p10=""
+                    for _d in "${LOKI_DIR:-.loki}"/runs/e10-*/; do [ -d "$_d" ] && _r10="$_d"; done
+                    for _d in "${LOKI_DIR:-.loki}"/proofs/*/proof.json; do [ -f "$_d" ] && { [ -z "$_p10" ] || [ "$_d" -nt "$_p10" ]; } && _p10="$_d"; done
+                    if [ -n "$_r10" ] && { [ -z "$_p10" ] || [ "$_r10" -nt "$_p10" ]; }; then _e10=1; fi
+                    unset _r10 _p10 _d
+                fi
+                ;;
+            ""|-*) _e10=0 ;;
+            # quick: the lean small path, no PR (legacy quick never opened one). A flag-first
+            # call (--help, -v) stays on the legacy quick.
+            quick)
+                case "${2:-}" in
+                    ""|-*) _e10=0 ;;
+                    *) _e10=1; _e10_args=(--no-pr "${@:2}") ;;
+                esac
+                ;;
+            # http*://*/issues/* also covers GitLab's /-/issues/ URLs.
+            */*\#[0-9]*|http*://*/issues/*|http*://*/browse/*) _e10=1 ;;
+            *" "*) _e10=1 ;;
+            # ponytail: a one-word argument stays on the legacy CLI. The telemetry
+            # allowlist is not a command registry (estimate, intent, outcomes are
+            # missing from it), so it cannot decide routing. Multi-word tasks and
+            # issue refs reach v10.
+            *) _e10=0 ;;
+        esac
+        # Default (unset) mode never breaks a host: no bun, or a provider engine10 has no
+        # invoker for, falls through to the legacy engine. Explicit v10 keeps its hard error.
+        if [ "$_e10" = "1" ] && [ "${LOKI_ENGINE:-}" != "v10" ]; then
+            case "${LOKI_PROVIDER:-claude}" in claude|codex|cline|aider) ;; *) _e10=0 ;; esac
+            command -v bun >/dev/null 2>&1 || _e10=0
+            if [ "$_e10" = "0" ]; then
+                echo "loki: using the legacy engine (the Loki 10 engine needs bun and LOKI_PROVIDER of claude, codex, cline or aider)." >&2
+            fi
+        fi
+        if [ "$_e10" = "1" ]; then
+            command -v bun >/dev/null 2>&1 || { echo "Error: LOKI_ENGINE=v10 needs bun. Install bun, or set LOKI_ENGINE=legacy to use the previous engine." >&2; exit 1; }
+            exec bun "$BUN_CLI" engine10 "${_e10_args[@]}"
+        fi
+        unset _e10 _e10_args
+        ;;
+esac
 
 # Bun must be installed for the new path; if it isn't, fall through to bash
 # silently rather than fail. This keeps users on systems without Bun working.

package/completions/_loki

@@ -193,6 +193,7 @@ function _loki_commands {
         'spec:Living spec drift detection'
         'intent:Does the spec still say what was actually wanted'
         'verify:Deterministic PR verification'
+        'keys:Export the receipt-signing public key'
         'grill:Interrogate a spec before building'
         'trust:Visible trust trajectory'
         'trust-metrics:Trust metrics report'

package/completions/loki.bash

@@ -5,8 +5,8 @@ _loki_completion() {
     _init_completion || return
 
     # Main subcommands (must match autonomy/loki main case statement)
-    local main_commands="start backlog quick monitor demo tour welcome init stop pause resume steer status next ship dashboard web serve api sandbox notify import github issue config provider reset memory compound checkpoint council dogfood projects enterprise secrets cockpit secure own handoff doctor watchdog audit metrics syslog onboard share proof receipt outcomes explain plan report cost estimate kpis stats test ci watch telemetry agent context ctx code run export review optimize heal modernize migrate cluster worktree wt trigger failover remote deploy docker mcp magic assets analyze compliance crash open otel preview quickstart rc rollback self-update sentrux setup-skill spec state template trust trust-metrics ultracode update verify voice why wiki bench cleanup logs grill docs cp version completions help"
-    local main_commands="start backlog quick monitor demo tour welcome init stop pause resume steer status next ship dashboard web serve api sandbox notify import github issue intent config provider reset memory compound checkpoint council dogfood projects enterprise secrets cockpit secure own handoff doctor watchdog audit metrics syslog onboard share proof receipt explain plan report cost estimate kpis stats test ci watch telemetry agent context ctx code run export review optimize heal modernize migrate cluster worktree wt trigger failover remote deploy docker mcp magic assets analyze compliance crash open otel preview quickstart rc rollback self-update sentrux setup-skill spec state template trust trust-metrics ultracode update verify voice why wiki bench cleanup logs grill docs cp version completions help"
+    local main_commands="start backlog quick monitor demo tour welcome init stop pause resume steer status next ship dashboard web serve api sandbox notify import github issue config provider reset memory compound checkpoint council dogfood projects enterprise secrets cockpit secure own handoff doctor watchdog audit metrics syslog onboard share proof receipt outcomes explain plan report cost estimate kpis stats test ci watch telemetry agent context ctx code run export review optimize heal modernize migrate cluster worktree wt trigger failover remote deploy docker mcp magic assets analyze compliance crash open otel preview quickstart rc rollback self-update sentrux setup-skill spec state template trust trust-metrics ultracode update verify voice why wiki bench cleanup logs grill docs cp version completions help keys"
+    local main_commands="start backlog quick monitor demo tour welcome init stop pause resume steer status next ship dashboard web serve api sandbox notify import github issue intent config provider reset memory compound checkpoint council dogfood projects enterprise secrets cockpit secure own handoff doctor watchdog audit metrics syslog onboard share proof receipt explain plan report cost estimate kpis stats test ci watch telemetry agent context ctx code run export review optimize heal modernize migrate cluster worktree wt trigger failover remote deploy docker mcp magic assets analyze compliance crash open otel preview quickstart rc rollback self-update sentrux setup-skill spec state template trust trust-metrics ultracode update verify voice why wiki bench cleanup logs grill docs cp version completions help keys"
 
     # 1. If we are on the first argument (subcommand)
     if [[ $cword -eq 1 ]]; then

package/dashboard/__init__.py

@@ -7,7 +7,7 @@ Modules:
     control: Session control API (start/stop/pause/resume)
 """
 
-__version__ = "10.5.20"
+__version__ = "10.5.23"
 
 # Expose the control app for easy import
 try:

package/docs/INSTALLATION.md

@@ -2,7 +2,7 @@
 
 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.
 
-**Version:** v10.5.20
+**Version:** v10.5.23
 
 ---
 

package/docs/enterprise/integration-cookbook.md

@@ -173,16 +173,12 @@ curl -X POST "$LOKI_TEAMS_WEBHOOK_URL" \
 | Variable | Required | Description |
 |----------|----------|-------------|
 | `LOKI_JIRA_URL` | Yes | Jira Cloud base URL |
+| `LOKI_JIRA_EMAIL` | Yes | Email of the Jira user that owns the API token |
 | `LOKI_JIRA_TOKEN` | Yes | Jira API token |
 | `LOKI_JIRA_EPIC_KEY` | No | Epic that run events are synced to |
 
-These are read by `src/integrations/sync-subscriber.js`. The Jira user email is
-passed to `JiraApiClient` in code (see below); no environment variable carries it.
-
-Known issue on main: `src/integrations/sync-subscriber.js` constructs `JiraApiClient`
-without the `email` and `apiToken` it requires, so Jira auto-sync from these
-variables does not start. Construct `JiraApiClient({ baseUrl, email, apiToken })`
-in code until that is fixed.
+These are read by `src/integrations/sync-subscriber.js`. If only some of the
+three required variables are set, it logs one line naming the missing ones.
 
 ### Configuration
 
@@ -194,6 +190,7 @@ in code until that is fixed.
 
    ```bash
    export LOKI_JIRA_URL="https://company.atlassian.net"
+   export LOKI_JIRA_EMAIL="user@company.com"
    export LOKI_JIRA_TOKEN="your-api-token"
    ```
 

package/docs/enterprise/migration.md

@@ -98,6 +98,7 @@ These variables from v5.50.0 continue to work identically:
 | `LOKI_TLS_CERT` | (unset) | TLS certificate path |
 | `LOKI_TLS_KEY` | (unset) | TLS key path |
 | `LOKI_JIRA_URL` | (unset) | Jira Cloud base URL |
+| `LOKI_JIRA_EMAIL` | (unset) | Jira user email for the API token |
 | `LOKI_JIRA_TOKEN` | (unset) | Jira API token |
 | `LOKI_JIRA_EPIC_KEY` | (unset) | Jira epic that run events sync to |
 | `LOKI_LINEAR_TOKEN` | (unset) | Linear API key |

package/docs/exit-codes.md

@@ -89,9 +89,18 @@ not rank above UNCHECKED.
 | Legacy shell (`autonomy/verify.sh`) | BLOCKED (non-zero) | the receipt line passes with the same accepted line |
 
 Engine10 `loki verify [run-id]` exits: 0 verified, 1 tampered, 2 unchecked,
-3 unsigned (refused), 66 no runs. The flag never changes TAMPERED or UNCHECKED,
+3 unsigned (refused), 4 run outcome not verified (a sealed receipt of a FAILED or
+otherwise unverified run), 66 no runs. The outcome check runs before the UNSIGNED
+branch, so the flag never changes exit 4, TAMPERED or UNCHECKED,
 and verify never creates a signing key.
 
+`loki verify --pubkey FILE <receipt.json|run-id>` (v10 only) checks the signature
+against the supplied Ed25519 public key (JWK from `loki keys export`, or PEM) and
+never the local JWKS. Exits: 0 VERIFIED, 1 TAMPERED, 2 UNCHECKED (kid does not
+match the key, or the key file is unusable), 3 UNSIGNED (a receipt with no
+signature is refused even with `--allow-unsigned`, because the caller asked for a
+signature check), 4 run outcome not verified (checked before UNSIGNED).
+
 An early draft spec listed `1=BLOCKED, 2=CONCERNS`. That ordering was rejected:
 it is not used anywhere, it has no consumers, and it inverts the
 severity-rises-with-the-code rule that every other command follows.

package/docs/v10/BOARD.md

@@ -459,14 +459,14 @@ set is declared to avoid overlap with those and with each other.
 | E-129 | BACKLOG 117 remainder: WhatsNew.tsx hardcodes a stale CURRENT_VERSION (9.55.0) that drifts from the shipped release | web-app/src/components/WhatsNew.tsx, tests/test-whatsnew-version-sync.sh | LOW | bash tests/test-whatsnew-version-sync.sh | released@2026-09-30T18:50Z | Source: BACKLOG 117. Evidence: WhatsNew.tsx:5 against VERSION 10.5.3. Released in v10.5.7 (merge 0c9daffc is an ancestor of v10.5.7). |
 | E-130 | D41 item 4 (speed): cache dependency install by lockfile hash in the bash parallel-worktree bootstrap | autonomy/run.sh (create_worktree only), tests/test-worktree-install-cache.sh | MEDIUM | bash tests/test-worktree-install-cache.sh | released@2026-09-30T18:50Z | Source: D41 item 4. Evidence: run.sh:6298-6304 installs unconditionally on every worktree. Released in v10.5.7 (merge 17af0439 is an ancestor of v10.5.7). |
 | E-131 | BACKLOG 146: P7 sink regex misses a computed or bracket-indexed sink name, for example window[sinkName](rows) | tests/moat/p7-no-fabricated-data.sh | HIGH | bash tests/moat/p7-no-fabricated-data.sh | merged@2026-09-30T18:11Z | Source: BACKLOG 146. Evidence: SETTER regex at p7-no-fabricated-data.sh:771 matches only literal names. Same engineer as E-128. |
-| E-132 | Wall classifier: a missing test runner (python -m pytest exits 1 with No module named pytest) reads as red, not not_run; D42 red requires the runner to start and at least one test to fail, so require a pytest summary line with failed before red | loki-ts/src/engine10/stages/wall.ts, loki-ts/tests/engine10/wall.test.ts | HIGH | cd loki-ts and bun test tests/engine10/wall.test.ts with a pytest-less python first on PATH | ready@2026-09-28T22:47Z | Source: main red on 04d3ac9c and 708c2907 (CI Bun job had no pytest); reproduced locally with a pytest-less venv, tests (3b) and (4) read fail 1. Seal still refuses later (not_run), so no false VERIFIED, but the Wall mis-seals. Coordinate with E-125 (same classifier). Core budget binds. |
+| E-132 | Wall classifier: a missing test runner (python -m pytest exits 1 with No module named pytest) reads as red, not not_run; D42 red requires the runner to start and at least one test to fail, so require a pytest summary line with failed before red | loki-ts/src/engine10/stages/wall.ts, loki-ts/tests/engine10/wall.test.ts | HIGH | cd loki-ts and bun test tests/engine10/wall.test.ts with a pytest-less python first on PATH | merged@2026-10-01T06:47Z | Source: main red on 04d3ac9c and 708c2907 (CI Bun job had no pytest); reproduced locally with a pytest-less venv, tests (3b) and (4) read fail 1. Seal still refuses later (not_run), so no false VERIFIED, but the Wall mis-seals. Coordinate with E-125 (same classifier). Core budget binds. |
 | E-133 | release.sh guard: refuse to commit dist maps that contain an absolute path (a node_modules symlink in a release worktree wrote 133 /Users paths into loki.js.map and one into cockpit.js.map at v10.5.4) | scripts/release.sh, tests/test-release-dist-guard.sh | MEDIUM | bash tests/test-release-dist-guard.sh | released@2026-09-30T18:50Z | Source: v10.5.4 cut 2026-09-28, caught by hand before commit (paths rewritten to ../node_modules/). Guard: grep the dist maps for an absolute or home-directory path after the bump and exit nonzero. Released in v10.5.7 (merge 53918a30 is an ancestor of v10.5.7). |
 | E-134 | spawn_env_fsmonitor.test.ts positive control fails on Bun 1.4.2 (Nightly red 2026-09-29 and 09-30, both OSes): Bun no longer inherits the START env for a spawn with no env option, so the bare control call stops leaking the canary and the test proves nothing there. Keep the product assertions unconditional; add a control that passes the canary explicitly so the hook is proven to record env on any Bun; report which inheritance mode the running Bun has | loki-ts/tests/runner/spawn_env_fsmonitor.test.ts | HIGH | cd loki-ts and bun test tests/runner/spawn_env_fsmonitor.test.ts on Bun 1.3.13 and on latest | released@2026-09-30T18:50Z | Source: Nightly run 36719756873 job 109901555421 (bun-v1.4.2): control record held the withheld sentinel, not the canary. Product calls still did not leak. Security guard, opus review. Released in v10.5.7 (merge f0ba0d4d is an ancestor of v10.5.7). |
 | E-135 | Post-Release Smoke PyPI install gives up after about 10.5 min (6 attempts, 30s steps) while the published version is still propagating; v10.5.5 failed this way though PyPI now has it. Add --no-cache-dir and widen the window | .github/workflows/post-release-smoke.yml | LOW | bash -n on the step script; a rerun of the smoke on the next release | released@2026-09-30T18:50Z | Source: Post-Release Smoke run 36497082408 job 109179083720 (FATAL loki-mode-sdk==10.5.5 not installable after retries); PyPI shows 10.5.5 on 2026-09-30. Rerun of the failed jobs requested. Released in v10.5.7 (merge 1d4975a1 is an ancestor of v10.5.7). |
 | E-136 | measure-size.py counts any touched non-test .py file, so a docstring-only or typing-only second file makes a one-file fix read as medium (click-3449 utils.py, marshmallow-2170, pluggy-442); count only files whose change alters code, not comments or docstrings | eval/loki10/measure-size.py, its test | MEDIUM | the measure-size self test plus a fixture diff with a docstring-only second file reading small | released@2026-09-30T18:50Z | Source: S41-20a opus review 2026-09-30 (criterion 7 cannot stand in for criterion 1). Use the Python ast module to compare function bodies with docstrings stripped. Released in v10.5.7 (merge d116c91b is an ancestor of v10.5.7). |
 | E-137 | S41-18 interrupt test (legA in eval/loki10/test-scorecard-run.sh) leaks an orphaned run.sh plus harness.py (tasks rt1,rt2) when the run is torn down: two groups found reparented to PID 1 after 18 and 32 min on 2026-09-30, from a removed worktree and a reviewer probe dir | eval/loki10/test-scorecard-run.sh | MEDIUM | bash eval/loki10/test-scorecard-run.sh twice, then no run.sh or harness.py with --tasks rt1,rt2 remains | released@2026-09-30T19:22Z | Source: pulse Orphan worktree/run.sh processes 2 at 17:30Z; PIDs 56770/56781 and 96302/96310 stopped by literal PID after inspection (the python harness ignored SIGTERM). Fix: trap EXIT in the test that stops the recorded group, and assert no survivors. Released in v10.5.8 (merge 030cd521 is an ancestor of v10.5.8). |
 | E-138 | P7 scanner misses optional-call sinks and one-hop aliasing: setRows?.([...]), window[k]?.(rows), const s = setRows; s(rows), and a memo or local that forwards a fabricator result; accept an optional ?. before the call in the three sink heads and follow one alias hop | tests/moat/p7-no-fabricated-data.sh | HIGH | bash tests/moat/p7-no-fabricated-data.sh with red and green fixtures per form | parked@2026-09-30T20:04Z | Source: E-128/E-131 opus review 2026-09-30 (lines 776, 1067, 1172 use a (?=[(<]) or \s*\( lookahead); pre-existing at base, not opened by E-131. PARKED 20:05Z by the adoption directive (docs/v10/PROGRESS.md 20:05Z); resumes after Tier 0 is green. |
-| E-139 | spawn_env_fsmonitor.test.ts follow-ups from E-134 review: comments at lines 16-17 and 114 overstate Bun 1.4.2 (Bun.spawn and Bun.spawnSync with no env still inherit the START env; only node:child_process inherits current), name spawn_env_guard.test.ts as the guard for them; line 94 driver should run process.execPath, not the bun on PATH | loki-ts/tests/runner/spawn_env_fsmonitor.test.ts | LOW | cd loki-ts and bun test tests/runner/spawn_env_fsmonitor.test.ts | ready@2026-09-30T18:08Z | Source: E-134 opus review 2026-09-30 (probe: Bun.spawn on 1.4.2 printed START env). |
+| E-139 | spawn_env_fsmonitor.test.ts follow-ups from E-134 review: comments at lines 16-17 and 114 overstate Bun 1.4.2 (Bun.spawn and Bun.spawnSync with no env still inherit the START env; only node:child_process inherits current), name spawn_env_guard.test.ts as the guard for them; line 94 driver should run process.execPath, not the bun on PATH | loki-ts/tests/runner/spawn_env_fsmonitor.test.ts | LOW | cd loki-ts and bun test tests/runner/spawn_env_fsmonitor.test.ts | released@2026-09-30T23:00Z | Source: E-134 opus review 2026-09-30 (probe: Bun.spawn on 1.4.2 printed START env). |
 | E-140 | Something deletes run-owned loki-run.* directories under TMPDIR while another agent is using them (an opus reviewer's dir and its Bun 1.4.2 binary vanished mid-review on 2026-09-30; unfamiliar dirs with e10ext subdirs appeared inside). Find the sweeper (a test cleanup, a trap, or a script removing loki-run.* by pattern) and make it remove only its own validated dir | the offending script or test (to locate), plus a guard test | HIGH | a guard that plants two run-owned dirs and runs the suspected cleanup, asserting the foreign one survives | released@2026-09-30T19:22Z | Source: E-134 opus review cleanup note 2026-09-30. CLAUDE.md forbids sweeping TMPDIR by pattern. Released in v10.5.8 (merge 98eadf90 is an ancestor of v10.5.8). |
 | E-141 | treeswap passes an explicit env to its git spawns (spawn_env_guard, BACKLOG 149) | loki-ts/src/e10ext/treeswap.ts and its test | MEDIUM | bun test tests/e10ext | released@2026-09-30T18:50Z | Merged c2305c99 via 0bf98fd0. S41-13 binding note records the scrubbed-env requirement. Released in v10.5.7 (merge 0bf98fd0 is an ancestor of v10.5.7). |
 | E-142 | D44-C follow-ups: structural-checks changed_chars diffs against the merge-base (committed dashes/emoji caught), typecheck prints SKIP without node_modules, register test-v10-ops.sh and fix the IGNORE comment (slow, not hanging) | scripts/structural-checks.sh, tests/test-structural-checks.sh, tests/test-registration-coverage.sh, tests/run-all-tests.sh, tests/shard-durations.tsv | LOW | bash tests/test-structural-checks.sh; each check under 10s | merged@2026-09-30T18:49Z | Source: D44-C TL review (APPROVE with notes). |
@@ -478,7 +478,7 @@ set is declared to avoid overlap with those and with each other.
 | E-148 | Review follow-ups: test-stop-process-group.sh still kills by `pkill -f "loki-$PGTEST_TAG"` (pattern kill, forbidden by CLAUDE.md): replace with recorded PIDs or a process-group kill; test-audit-chain-cross-file.sh test 1 reads the real ~/.loki/dashboard/audit (fails on hosts with old tampered data): make it hermetic; E-147 timeout message says "after all cases passed" when there was zero output: say "no PASS output (possible hang before the first case)" | tests/test-stop-process-group.sh, tests/test-audit-chain-cross-file.sh, tests/test-trust-core-probe-isolation.sh | LOW | each suite passes on a host with a tampered ~/.loki audit file; no pkill -f remains | merged@2026-09-30T19:53Z | Source: E-143 and E-147 TL reviews (APPROVE with notes). |
 | E-149 | loki-ts/tests/engine10/modernize/java_capture.test.ts "unitClassesFromGraph (M-04 integration)" times out at bun's 5s default under CI load (5169ms, Coverage run 36764748814 on train/5 1cd5feac; also failed on train/2 and in a local full run): measure, make it cheaper or set an explicit measured timeout; sweep modernize tests over 2.5s | loki-ts/tests/engine10/modernize/*.test.ts | LOW | before/after durations under 3x load; bun test tests/engine10/modernize 0 fail | released@2026-09-30T20:08Z | Source: D44 train/5 red (Coverage). Rerun of the failed job in flight. Released in v10.5.10 (merge 2394dc4a is an ancestor of v10.5.10). |
 | E-151 | Release blocker guard: v10.5.10 (69ebc03e) shipped loki-ts/dist/loki.js.map stale because the bump changed it (version literal 10.5.9 to 10.5.10 changed length, shifting mappings) and the release commit staged a fixed file list. scripts/release.sh --bump-only should print every file it changed (including dist maps), and a check (in release.sh or a pre-push rule for "release: v*" commits) should refuse a release commit that leaves a stamped tracked file modified in the worktree | scripts/release.sh, tests/test-release-dist-guard.sh | LOW | fixture: a bump that changes the map, commit without it, check refuses; with it, passes | released@2026-09-30T21:23Z | Source: v10.5.10 release; interim procedure: assert `git status --porcelain` is empty after the release commit before pushing. Map corrected on the next train. Released in v10.5.11 (merge bd5834a9 is an ancestor of v10.5.11). |
-| E-152 | release.sh --bump-only "stage these files:" list must print a copy-paste command that works: loki-ts/dist is gitignored, so `git add loki-ts/dist/loki.js` refuses (seen 19:58Z on train/7); print `git add -f` for paths under an ignored directory (git check-ignore) and plain `git add` otherwise | scripts/release.sh, tests/test-release-dist-guard.sh | LOW | fixture with an ignored-but-tracked dist file: the printed command stages it | ready@2026-09-30T19:58Z | Source: first live use of E-151 --check-clean caught the unstaged dist (rc=1). |
+| E-152 | release.sh --bump-only "stage these files:" list must print a copy-paste command that works: loki-ts/dist is gitignored, so `git add loki-ts/dist/loki.js` refuses (seen 19:58Z on train/7); print `git add -f` for paths under an ignored directory (git check-ignore) and plain `git add` otherwise | scripts/release.sh, tests/test-release-dist-guard.sh | LOW | fixture with an ignored-but-tracked dist file: the printed command stages it | released@2026-10-01T06:40Z | Source: first live use of E-151 --check-clean caught the unstaged dist (rc=1). |
 | E-153 | Incident 20:16Z: a reviewer's fixture setup ran `git commit` with the MAIN CHECKOUT as cwd, committing author `t <t@t>` "init" that replaced the real package.json with a fixture and added sum.js/sum.test.js (local only, never pushed; undone with `git reset --keep 1c96ab16`). Guard: a pre-commit hook in .githooks refusing any commit in this repository whose author email is not the repo-local identity (git config user.email) unless LOKI_ALLOW_FOREIGN_AUTHOR=1, so fixture commits made in the wrong cwd fail loudly; fixture commits in real temp repos are unaffected | .githooks/pre-commit, tests/test-pre-commit-author-guard.sh | LOW | red first: in a scratch clone with the hook installed, `git -c user.email=t@t commit` is refused; the repo identity commits | ready@2026-09-30T20:17Z | Source: loki-seal r2 review fixture (agent stopped at 20:17Z). Reviewer prompts now require `git -C "$FIXTURE"` and a pwd check under LOKI_RUN_TMP. |
 | S41-10b | Static-first fixed-rules block for the implement and fix briefs (S41-10 card remainder): a byte-identical rules block in the cache-stable prefix, per-task context after it; drive-letter and ~ plan paths filtered like absolute ones | loki-ts/src/engine10/stages/implement.ts, fix.ts (prefix only), loki-ts/src/e10ext/context.ts and tests | MEDIUM | red first: two different tasks produce byte-identical prefix bytes; core net-zero lines | merged@2026-09-30T19:19Z | Source: S41-10 reviews (APPROVE r2, remainder). |
 | S41-20h | Medium-task MINING pass (no task building): shortlist 12 candidate merged PRs whose shape survives the one-file probe (a semantic or signature change in file A that an independently tested caller in file B must match; not helper extraction, parameter threading, moved classes or typing-only files), each with a written one-file-fix attempt run against the upstream tests and its result | eval/loki10/tasks/CANDIDATES.md (new) | MEDIUM | every shortlisted PR has a failing one-file attempt recorded with command and rc | merged@2026-09-30T19:19Z | Source: S41-20b/c/d/e/f: 11 of 16 candidates fell to a reviewer one-file fix; S41-20f built 0. |
@@ -628,10 +628,12 @@ Source: ~/git/autonomi-dev/research/2026-09-30-adoption/SWARM-PROMPT-ADOPTION.md
 | E-157 | D46: Security Audit verdict reuse. (a) security-audit.yml also runs on push to train/** so every train tip gets the full --all gitleaks scan before main is fast-forwarded; (b) required-ci reuses the parent Security Audit verdict for an eligible VERSION-only bump under the existing eligibility rule (diff is VERSION plus generated version stamps only, parent run success at that exact SHA). Moat test: a non-VERSION-only bump still re-runs Security Audit. Supersedes FOUNDER-QUEUE 14 | .github/workflows/security-audit.yml, release.yml (required-ci), tests | HIGH | non-VERSION-only bump re-runs the scan | merged@2026-10-01T03:03Z | after slice-D46-ci; r3 opus APPROVE 57b511d2; DROPPED from train/21 (D46): STEP 1 re-indent broke S-132 normalizer parity (test-version-bump-only 28/1), reverted 7d1a0f15, r4 with CI-health |
 | E-159 | Pre-existing secret-scan gaps found by the E-157 r2 opus reviewer: (a) an evil merge, a merge commit whose OWN content adds a secret (merge -s ours --no-commit, token in the merge commit), is invisible to both the PARENT..SHA range scan and the --all scan (only `gitleaks dir` found it); (b) pinned gitleaks 8.30.0 exits 0 when its internal git log fails (invalid range), a latent fail-open. Fix: --diff-merges=first-parent (or -m) in --log-opts for both modes or a working-tree scan at the release SHA; guard `git rev-list RANGE` success or treat `[git] fatal` as failure | scripts/security-audit-gitleaks.sh, workflows, tests | HIGH | evil-merge and bad-range fixtures fail the scan | merged@2026-10-01T03:03Z | CI-health engineer after E-157 r3; r1 opus REJECT 5f33451d: stdin merge scan false-positives on real history (v10.5.13..14 rc 1), Wall checks skip in CI |
 | E-160 | D46 runner contention (peer steer 02:11Z): a green train SHA fast-forwarded to main re-runs Tests (8 shards), Bun Parity, Security Audit and First-run gate on the identical SHA, doubling runner load and queueing the next train. Proposal: on push to main, a first job checks for a successful run of the same workflow at the same SHA from a train/** push and, if found, exits success recording the reused run id (D28: same SHA = same tree); any SHA not train-tested runs in full. CTO call FIRST: OPERATING-MODEL says "Tier B full verification on every main commit (never cancelled on main)"; confirm reuse does not weaken Release required-ci, branch-conditional steps (train vs main), or the Security Audit range (base tag config). Sequence after E-157 r4 (same files) | .github/workflows/test.yml, bun-parity.yml, security-audit.yml, tests/test_release_required_ci.py | HIGH | main push of a train-green SHA records reuse and finishes in under 1 min; an untested SHA runs in full; a train-red SHA is not reused | ready@2026-10-01T02:10Z | CTO decision first; after E-157 |
-| E-161 | INCIDENT 02:46Z: an opus reviewer ran `git checkout --detach <tag>` x7 plus a `.gitleaksignore` overwrite in the SHARED main checkout (reflog 02:46:04Z to 02:46:38Z). Cause: its run-owned clone dir was deleted, the next `cd` into a new clone failed, and the shell cwd fell back to the main checkout; every later command ran there. Restored by the Chief of Staff (`git checkout main`, fafe50dd, clean). Guard: v10-guard.sh (PreToolUse) blocks `git checkout`/`git switch`/`git reset`/`git worktree remove` and writes to tracked files when cwd resolves to the main checkout and the caller is an agent (not the leader session); agent prompts use `cd DIR` followed by an exit-on-failure check. Test: a hook test with cwd=main checkout blocks a detached checkout and allows it in a worktree | scripts/v10-guard.sh, tests | HIGH | detached checkout in main checkout blocked; same in a worktree allowed | ready@2026-10-01T02:47Z | GUARDS.md entry |
+| E-161 | INCIDENT 02:46Z: an opus reviewer ran `git checkout --detach <tag>` x7 plus a `.gitleaksignore` overwrite in the SHARED main checkout (reflog 02:46:04Z to 02:46:38Z). Cause: its run-owned clone dir was deleted, the next `cd` into a new clone failed, and the shell cwd fell back to the main checkout; every later command ran there. Restored by the Chief of Staff (`git checkout main`, fafe50dd, clean). Guard: v10-guard.sh (PreToolUse) blocks `git checkout`/`git switch`/`git reset`/`git worktree remove` and writes to tracked files when cwd resolves to the main checkout and the caller is an agent (not the leader session); agent prompts use `cd DIR` followed by an exit-on-failure check. Test: a hook test with cwd=main checkout blocks a detached checkout and allows it in a worktree | scripts/v10-guard.sh, tests | HIGH | detached checkout in main checkout blocked; same in a worktree allowed | merged@2026-10-01T06:47Z | GUARDS.md entry |
 | E-162 | Founder "faster" (03:05Z): slice CI runs only Tier A plus diff-selected suites (the existing Tier A selection), Bun Parity and the structural guards; the full 8-shard Tests stays on train/** and main, and the train stays the release verdict. Frees runners and targets about 2 min slice CI | .github/workflows/test.yml (slice-* job matrix only), tests | HIGH | slice-* push runs no 8-shard matrix; train/** and main still run all 8 shards; a slice touching a suite runs that suite | merged@2026-10-01T05:22Z | after E-157 r4 (same file) |
-| E-165 | tests/test-mirofish-integration.sh line 413 runs `autonomy/loki start --no-mirofish` in the repo root: a live autonomous build that ran about 45 min, switched a worktree branch to loki/session-* and committed a docs change (found by DOC-02). Guard: the test must run against a run-owned fixture repo with a stub provider and LOKI_NO_BROWSER=1, never the repo root; add a structural guard that no test launches start/run against REPO_ROOT | tests/test-mirofish-integration.sh, a structural guard | HIGH | the test never runs loki start in the repo root; guard catches a planted case | ready@2026-10-01T04:07Z | P0 guard (D26) |
-| E-166 | Jira auto-sync never starts: src/integrations/sync-subscriber.js builds JiraApiClient without the required email and apiToken, so LOKI_JIRA_URL plus LOKI_JIRA_TOKEN do nothing (DOC-02 added a known-issue note to the setup docs). Fix the wiring or remove the advertised auto-sync | src/integrations/sync-subscriber.js, tests | MEDIUM | with env set, the subscriber constructs a working client (mocked API) | ready@2026-10-01T04:07Z | none |
+| E-165 | tests/test-mirofish-integration.sh line 413 runs `autonomy/loki start --no-mirofish` in the repo root: a live autonomous build that ran about 45 min, switched a worktree branch to loki/session-* and committed a docs change (found by DOC-02). Guard: the test must run against a run-owned fixture repo with a stub provider and LOKI_NO_BROWSER=1, never the repo root; add a structural guard that no test launches start/run against REPO_ROOT | tests/test-mirofish-integration.sh, a structural guard | HIGH | the test never runs loki start in the repo root; guard catches a planted case | merged@2026-10-01T06:52Z | P0 guard (D26) |
+| E-166 | Jira auto-sync never starts: src/integrations/sync-subscriber.js builds JiraApiClient without the required email and apiToken, so LOKI_JIRA_URL plus LOKI_JIRA_TOKEN do nothing (DOC-02 added a known-issue note to the setup docs). Fix the wiring or remove the advertised auto-sync | src/integrations/sync-subscriber.js, tests | MEDIUM | with env set, the subscriber constructs a working client (mocked API) | merged@2026-10-01T06:43Z | none |
+| P0-promote-bun | Auto-promote of 10.5.22 failed: promote.yml ran the first-run gate without bun, the installed CLI fell back to legacy, 7 v10 checks failed and the cost check crashed (IndexError). Install bun before the gate; cost check fails closed; explicit engine-fallback check | .github/workflows/promote.yml, scripts/first-run-gate.sh, tests/test-first-run-gate.sh | test-first-run-gate 56/0 incl. fallback fixture; gate --stub 0 failed | HIGH | merged@2026-10-01T07:09Z | opus CTO APPROVE 5bdfe2f8 |
+| E-167 | Gate the no-bun path end to end (CTO follow-up to P0-promote-bun): run the default entry with bun absent from PATH and assert the legacy receipt, NOT VERIFIED on a skipped target and the documented exit codes; the promote gate currently proves only the bun path | scripts/first-run-gate.sh, tests/test-first-run-gate.sh | no-bun stub run fails closed on a skipped test; clean no-bun run reads its legacy receipt | MEDIUM | ready@2026-10-01T07:09Z | none |
 | D49-auto | Auto-promote to latest on Post-Release Smoke success (founder D49) | .github/workflows/promote.yml, tests/test_release_next_tag.py | HIGH | smoke-success from Release promotes; manual smoke never promotes; not-lower guard | merged@2026-10-01T03:03Z | opus APPROVE 5510b8c8. Follow-ups (D49-auto-b): not-lower guard fails OPEN on an npm error (make it fail closed); loki-mode-sdk latest has no not-lower guard; a newer queued promote can replace a pending one in a release burst |
 | D51-A3 | Headless `loki backlog owner/repo --all/--label/--issues` plus loki.yaml (schema, validator, env overrides) | autonomy/lib/backlog.py, autonomy/lib/loki_yaml.py, autonomy/loki, schemas/loki-yaml.schema.json, tests/test-backlog.sh | HIGH | backlog 47/0 | merged@2026-10-01T03:11Z | sonnet APPROVE 14ff9ae2; follow-up D51-A3b: `loki_yaml.py show` echoes a token pasted into git.token_env (redact x-secret-ref fields); no-parser test case; re-run of a failed issue discards its kept worktree |
 | D51-A4 | Slack on the v10 path (PR opened, BLOCKED, finished), webhook from the env var named by LOKI_SLACK_WEBHOOK_ENV, URL redacted, 5s bounded post | loki-ts/src/e10ext/slack_events.ts, engine10/supervisor.ts, tests | MEDIUM | slack tests 40/0 | merged@2026-10-01T03:11Z | sonnet APPROVE adb838b2; one labelled test message after it ships |

package/docs/v10/GUARDS.md

@@ -797,3 +797,25 @@ previously mismarked two merged guards (S-16, S-74) as PENDING.
   no-op (`return dict(row)`) reproduces the incident directly: the planted
   secret and the log paths both survive.
   Run: `bash tests/test-prune-worktrees.sh && bash tests/test-eval-archive.sh`.
+
+## 21. A failed `cd` let an agent detach the shared main checkout (E-161)
+
+- **Incident:** an agent ran `cd <temp clone>` which failed, then fell back
+  to the shared main checkout and ran `git checkout --detach <tag>` there 7
+  times, leaving the founder's checkout detached each time.
+- **Guard:** RULE8 in `scripts/v10-guard.sh` (PreToolUse Bash hook). In the
+  primary worktree (git-dir equals git-common-dir) it blocks `git checkout
+  --detach`, `git checkout <tag|sha|remote-ref>` and `git switch --detach`
+  for every caller. When the hook input carries `agent_id` (set only for
+  subagents; the leader has none) it also blocks all `git checkout`/`switch`,
+  `reset --hard`, `stash`, `clean` and `worktree remove` of the main
+  checkout. A dangerous git command after a `cd` not followed by `&&`/`||`
+  is blocked when the hook cwd is the primary worktree. The leader keeps
+  `git checkout main`, merge, revert and commit.
+- **Limit:** `cd X || true; git ...` counts as handled. If a host stops
+  sending `agent_id`, only the always-on detach forms remain.
+- **The test that proves it fires:** `tests/test-v10-guard.sh` (Rule 8
+  section): detached checkout in the main checkout blocked, same in a linked
+  worktree allowed, leader `git checkout main` allowed, subagent forms and
+  the unchecked-`cd` case blocked.
+  Run: `bash tests/test-v10-guard.sh`.

package/docs/v10/GUIDE.md

@@ -1,10 +1,20 @@
 # Loki 10 engine guide
 
-Opt-in: set LOKI_ENGINE=v10 <!-- loki10-default -->
-
-Loki 10 is the rewritten engine (docs/v10/ENGINE.md). It is not the default
-yet. Every command below only runs when LOKI_ENGINE=v10 is set; leave it
-unset and `loki` keeps using the current (legacy) engine exactly as before.
+Default: Loki 10 engine for `loki "<task>"`, `loki owner/repo#N` and `loki quick "<task>"`. Set LOKI_ENGINE=legacy or run `loki legacy <args>` for the previous engine. <!-- loki10-default -->
+
+Loki 10 is the rewritten engine (docs/v10/ENGINE.md). Since the D48 flip it
+is the default for three entry points: `loki "<task>"`, `loki owner/repo#N`
+(issue mode) and `loki quick "<task>"`. Each prints one start line,
+`Loki 10 engine (set LOKI_ENGINE=legacy or run 'loki legacy' for the previous
+engine)`, then the summary below. Everything else (`loki start`, `loki
+status`, `loki dashboard` and the rest) is unchanged unless you set
+LOKI_ENGINE=v10 explicitly, which also routes status, verify and dashboard
+to the v10 commands. Bare `loki verify` (no LOKI_ENGINE) follows the newest
+run: when the newest entry in .loki/runs/ is a v10 run newer than the newest
+legacy proof it runs the v10 verify, otherwise the legacy verify. If bun is
+missing or LOKI_PROVIDER is unsupported, the default mode falls back to the
+legacy engine and prints one stderr line saying why. The previous engine stays one step away:
+`loki legacy <args>` and LOKI_ENGINE=legacy.
 
 Some pieces named in this guide are still being built. Each one below says
 so plainly instead of describing a finished feature.
@@ -12,19 +22,34 @@ so plainly instead of describing a finished feature.
 ## Quickstart
 
 Put the task first, as a quoted multi-word string, so bin/loki's router
-sends it to the v10 engine instead of the legacy one. A one-word argument
-that is not an issue ref, or any first argument starting with `-`, stays
-on the legacy engine.
+sends it to the v10 engine. A one-word argument that is not an issue ref,
+or any first argument starting with `-`, stays on the legacy engine.
+
+```
+loki "fix the login redirect loop" --no-pr
+```
+
+`loki quick "<task>"` is the small-task entry. It runs the same engine
+without opening a pull request (the legacy quick never opened one), and the
+engine's own sizing picks the lean path for a small task: Plan and Wall are
+skipped and implement starts on sonnet, escalating to the top model only
+on a real test failure (E-64; `LOKI_E10_CASCADE=0` turns the cascade off).
+`loki quick --help` and a flag-first `loki quick -v "<task>"` stay on the
+legacy quick.
 
 ```
-LOKI_ENGINE=v10 loki "fix the login redirect loop" --no-pr
+loki quick "fix the login redirect loop"
 ```
 
+If bun is not installed, or LOKI_PROVIDER names a provider the v10 engine
+has no invoker for (anything but claude, codex, cline, aider), these entry
+points fall back to the legacy engine instead of failing.
+
 Issue refs work the same way:
 
 ```
-LOKI_ENGINE=v10 loki owner/repo#123
-LOKI_ENGINE=v10 loki https://github.com/owner/repo/issues/123
+loki owner/repo#123
+loki https://github.com/owner/repo/issues/123
 ```
 
 bin/loki routes GitHub, GitLab (`.../-/issues/N`) and Jira
@@ -58,9 +83,13 @@ verify, seal) and then, in the supervisor, the pr stage, ending in the
 Slack is not part of the v10 engine surface (no command, no notification
 hook) and is in progress, tracked with the other wave 3 items.
 
-## The 5-line summary
+## The summary
 
-A finished run prints five lines, one label each:
+A finished run prints the start line, then one label per line (Outcome,
+PR, Receipt, NOT PROVEN, Cost, Time; a Reason line is added for any
+outcome other than VERIFIED or ALREADY_SATISFIED). The quiet default stays
+within 8 lines. The block below is the older 5-line form; the labels are the
+same:
 
 ```
 PR:         https://github.com/owner/repo/pull/1
@@ -81,7 +110,13 @@ Time:       4m12s (intake 11s, plan 20s, implement 3m10s, verify 31s)
   separate `; flaky ...` clause on the same line.
 - **Cost**: the provider-reported dollar figure and token count. When the
   provider does not report cost, this line reads `not measured` instead of
-  `$0.00`; a missing cost is never rendered as free.
+  `$0.00`; a missing cost is never rendered as free. The one exception is the
+  CLI invoker (LOKI_E10_INVOKER=cli, which the first-run gate's stub uses): it
+  has no dollar figure to report, so the run records 0 with the source marker
+  `cli-invoker-unmetered` in the cost event, the receipt (`cost.source`) and
+  the efficiency record, shows `$0.00 (...; CLI invoker records no cost)`, and
+  adds `cost unmetered (CLI invoker; recorded as 0)` to NOT PROVEN. The cost
+  fields are never null on such a run.
 - **Time**: total wall time, then each stage's own duration in parentheses.
 
 This formatter (`loki-ts/src/engine10/output.ts`, `formatSummary`) is
@@ -138,15 +173,12 @@ provider names (`claude`, `codex`, `cline`, `aider`); it is not supported.
 
 ## After the flip
 
-Once v10 becomes the default (docs/v10/DECISIONS.md, D29), `loki`, `loki
-status`, `loki verify` and `loki dashboard` with no `LOKI_ENGINE` set will
-mean the v10 commands described above. The previous engine stays
-reachable through `LOKI_ENGINE=legacy` (bin/loki sends every value other
-than `v10` to it), unchanged. Nothing is removed at the flip. A separate
-legacy alias command is planned (docs/v10/ENGINE.md, E-31) but is not on
-main.
-
-That flip has not happened on main as of this guide. The opt-in line near
-the top of this file and of README.md's section is the one place that
-records which state we are in; it changes in the same commit as the flip
-itself.
+D48 made v10 the default for `loki "<task>"`, `loki owner/repo#N` and
+`loki quick "<task>"`. The previous engine stays fully reachable and
+unchanged: `loki legacy <args>` (prints a short deprecation notice to
+stderr, then runs exactly the pre-flip route for `<args>`) and
+`LOKI_ENGINE=legacy` (the same, without the notice, for scripts). Any
+LOKI_ENGINE value other than v10 or unset also keeps the legacy engine.
+Nothing is removed at the flip. The one place that records which state we
+are in is the marked line near the top of this file and of README.md's
+Loki 10 section; it changed in the same commit as the flip.

package/docs/v10/PROGRESS.md

@@ -1747,3 +1747,27 @@ The swarm is stopped: .loki/V10-STOP exists, the loop has no wake-ups, and the c
 - Merged on local main: D48-flip r3 (opus APPROVE: FAILED receipt exits 4 with or without --allow-unsigned; dispatch 56/0; gate --stub 0 failed), A-134b r4 (sonnet APPROVE; registration rc=0, shard rc=0, own test 6/0), E-162 (opus APPROVE as CTO call).
 - train/33 63db8710 pushed. Guards: registration rc=0, shard-coverage rc=0 (E2e Features row 19 -> 20 to keep the five heaviest suites in distinct shards), v10-ops rc=0, run-shellcheck rc=0, docs-cli-drift rc=0, release-dist-guard rc=0, budget.test 24 pass.
 - REJECTED, fix rounds building: E-163 (live /usage timeout has no process-group kill), D48-r2 (unsigned receipt exits 0 under --pubkey; merge conflicts with the exit-4 change).
+
+## 2026-10-01T05:34Z v10.5.19 published and auto-promoted; train/33 red, flip dropped
+- v10.5.19: Release run 47050d65 completed success; npm view loki-mode@10.5.19 gitHead 47050d6533d7 matches; dist-tags latest=10.5.19 next=10.5.19 (D49 auto-promote). Unblocks the CodeQL P0 (10.5.18 never published).
+- train/33 63db8710 RED: Tests shard 7/8, suite "first-run gate assertion logic (A-02)" (tests/test-first-run-gate.sh): "FAIL clean: gate exit 1". Reproduced locally on 63db8710, not on aad61f9a. Cause: D48-flip r3 added gate checks (engine-start-line, cost-non-null, output-lines 8, bare verify rc 4) that the test's clean fixture does not emit.
+- D46 drop: reverted c2c43fd10 on main (5d25b205; reverted paths identical to aad61f9a; local test-first-run-gate rc=0, 0 FAIL). train/34 5d25b205 pushed with E-163 r3 (haiku fix; env parse probes abc/-5/nan/inf/0 -> 20, 46/0), A-134b r4, E-162.
+- D48-flip r4 (fixture fix) building; D48-r2b (pubkey, null-jwt exits 3 under --pubkey) built, in opus re-review; it needs the flip re-landed first.
+
+## 2026-10-01T06:07Z v10.5.20 promoted; v10.5.21 (D48 engine flip) cut, Release FAILED, NOT published (see 06:30Z); train/39
+- v10.5.20 240f3285: Release success; npm gitHead 240f3285f42b matches; dist-tags latest=10.5.20 next=10.5.20 (auto-promote, watcher bybzbhat6). Contents A-134b, E-162, E-163.
+- train/35 RED (Tests shard 1/8: "1 command(s) absent from 'loki help': keys"). D46 drop of D48-r2b (76e3d25c, revert clean vs flip-r4 merge). Fix r2c 2e7c68a3 (one help line), re-landed as 3eade3d4; train/37 green on Tests, Bun Parity, Coverage, Security Audit.
+- train/36 76e3d25c green (all four); main fast-forwarded; v10.5.21 189f347e pushed (--check-clean rc=0, parent == origin/main). CHANGELOG corrected: the flip's Unreleased notes said "loki verify unchanged"; r3 routes bare verify to v10 when the newest run is a v10 run (bin/loki:296-305), exit 4 for a non-VERIFIED outcome. Watcher bpighrue2.
+- Tier A red on every train since train/33: E-162 ran tests/test-shard-coverage.sh before the Python deps install; two pytest-gated suites (run-all-tests.sh:782-787) were not registered, 666 of 668. Fix 55d559ea moves the step after pip install (train/38).
+- train/39 c34511e5 = flip + keys (D48 rows 2, 7-9) + Tier A fix + 10.5.21 merge; local help, registration, shard-coverage, docs-drift, v10-ops all rc=0.
+
+## 2026-10-01T06:29Z CORRECTION: v10.5.21 not published (P0, fix forward)
+- v10.5.21 189f347e: Release run completed failure. Tests at that SHA failed in shard 6/8: "CHANGELOG Unreleased does not record the v10 default flip" (tests/test-engine10-legacy-notice.sh). The release CHANGELOG moved the flip note from Unreleased into the v10.5.21 section. Post-Release Smoke and Promote skipped; npm dist-tags latest=next=10.5.20. The 06:07Z entry's "released" was premature and is corrected above; rows say released only once npm has the version.
+- Moat suite passed at 189f347e, so the train/39 P2.checklist-verify-not-shadowed failure did not recur on the same code (local p2 run on c34511e5 also PASS); still treated as unconfirmed until train/40.
+- Fix baf5e2c8: the test now requires 'Loki 10.*now the default' anywhere in CHANGELOG. Intent kept: a copy of CHANGELOG with that line removed fails the pattern, the real file passes. train/40 baf5e2c8 in CI; on green, fast-forward and cut 10.5.22 (flip, keys, Tier A fix), CHANGELOG stating 10.5.21 was never published.
+
+## 2026-10-01T07:03Z v10.5.22 published to next; auto-promote FAILED (P0)
+- v10.5.22 9b22a347: Release success; npm view loki-mode@10.5.22 gitHead 9b22a3477072 matches; dist-tags next=10.5.22, latest=10.5.20 (UNCHANGED). Release body 11 lines. Contents: D48 flip (rows 7-9), keys export and verify --pubkey (row 2), Tier A fix, E-35 test fix. v10.5.21 was never published.
+- promote.yml run at 07:00Z: completed failure, correctly refused to move latest. first-run-gate.sh --installed loki-mode@10.5.22 ran on ubuntu-latest WITHOUT bun; the installed CLI fell back to the legacy engine ("the Loki 10 engine needs bun"), so 7 v10 checks failed (digest-matches, verify-ok, receipt-signed, output-lines 13>8, engine-start-line, cost-non-null, skip-bare-verify) and the cost check crashed with IndexError (no v10 run dir).
+- P0 fix slice-P0-promote-bun building: setup-bun in promote (and any other gate job on an installed package), cost check fails closed instead of crashing, explicit "engine fell back to legacy" check. CTO (opus) review before merge; release-gate change.
+- train/42 73dbe61b (E-166, E-161, E-132 test, E-165) in CI.