loki-mode 11.17.66 → 11.17.68

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 v11.17.66
+# Loki Mode v11.17.68
 
 **Current entry points (Loki 10 engine):** `loki "<task>"`, `loki owner/repo#N` and `loki quick "<task>"` run the Loki 10 engine and end with a signed receipt (`loki verify`). `loki backlog owner/repo --all` runs many issues in parallel. Guide: `docs/v10/GUIDE.md`. The skill instructions below, and `loki start`, describe the previous bash loop. PRD-file starts (`loki start ./prd.md`) and the opencode provider still run on it until FC38-SWEEP ports them; the legacy-engine command and the LOKI_ENGINE switch remain removed. Prefer `loki owner/repo#N` for issues.
 
@@ -483,4 +483,4 @@ See `CHANGELOG.md` entries [7.5.7], [7.5.8], [7.5.13] for the per-fix list and r
 
 ---
 
-**v11.17.66 | [Autonomi](https://www.autonomi.dev/) flagship product | core skill**
+**v11.17.68 | [Autonomi](https://www.autonomi.dev/) flagship product | core skill**

package/VERSION

@@ -1 +1 @@
-11.17.66
+11.17.68

package/dashboard/__init__.py

@@ -7,6 +7,6 @@ Modules:
     control: Session control helpers (status, atomic writes, origin check)
 """
 
-__version__ = "11.17.66"
+__version__ = "11.17.68"
 
 __all__ = ["__version__"]

package/docs/CLI-REFERENCE.md

@@ -1,6 +1,6 @@
 # CLI reference
 
-Generated from `loki-ts/src/cli/registry.ts` by `scripts/generate-stale-zero.sh` for v11.17.66. Do not edit by hand.
+Generated from `loki-ts/src/cli/registry.ts` by `scripts/generate-stale-zero.sh` for v11.17.68. Do not edit by hand.
 Hidden and legacy-only commands are omitted; see `docs/v10/CLI-MODERN.md` for the full inventory.
 
 | Command | Description |

package/docs/INSTALLATION.md

@@ -2,7 +2,7 @@
 
 Loki Mode, by [Autonomi](https://www.autonomi.dev/), turns a spec or an issue into a verified pull request with a receipt you can check. This page covers installing it, a first run, and the options around it.
 
-**Version:** v11.17.66
+**Version:** v11.17.68
 
 **Engine note:** `loki start` is the primary command. `loki start`, `loki "<task>"`, `loki owner/repo#N` and `loki quick` all run the Loki 10 engine, whatever the flag order or input form (PRD file, issue ref, task or one-word brief). The previous loop runs only on `--engine legacy`, `LOKI_ENGINE=legacy`, or for one call when a flag Loki 10 cannot honor is present. See the [user guide](v10/GUIDE.md) and the [5-minute quickstart](QUICKSTART.md).
 

package/docs/v10/FAILURE-CLASSES.md

@@ -1169,3 +1169,27 @@ L0 review rule (ENGINE-LAWS.md L0): a fix that adds an `if` or a regex about the
 - Siblings swept (known follow-up: group runs, where the group baseRef stays HEAD while its units skip; the predicate never fires off a loki/e10-* run branch, so not on main after a fast-forward accept, not on loki/epic-*, loki/group-*, loki/unit-* branches, and not when LOKI_PR_BASE is set by a stacked slice of `loki issues run`): unmergedEvidence/lokiOwn (still reports the mixed Loki plus operator range); the supervisor start line (baseLine now calls the same predicate, so it agrees with intake); ctx.baseSha (set before intake from HEAD; intake now updates it, which the Wall base run, verify, seal and the PR stage read); base_sha, the tree cache key and the contract snapshot (all taken after the checkout).
 - Mechanism: one predicate `stackedOnLokiRun` in loki-ts/src/util/base_guard.ts, used by intake.ts and baseLine. No new knob.
 - Fixture: loki-ts/tests/engine10/intake.test.ts describe "FC-STACKED-ON-LOKI-RUN" (all-Loki range branches from origin/main with the old branch intact and the note recorded; an operator commit in the range keeps HEAD; an unresolved target keeps HEAD) plus the FC-15 case D updated to the skip.
+
+## FC-LAZY-CONTROL-ENV Lazy-fetch control silenced by ambient git env or a racily clean index (GIT-ENV-LEAK, sibling of FC-25c-ci)
+- User-visible vs raw: Tests run 39174561642 (main 8cc81a1b8) failed shard 6/8 on tests/test-untracked-status-fsmonitor.sh with "control: plain git status did not run the lazy-fetch hook MARKER=no"; the same file passed an hour earlier and 5 of 5 locally.
+- Law broken: a test must be hermetic; a control that depends on inherited process env is not a control.
+- Cause (reproduced 2026-10-18, git 2.55.0): GIT_SSH_COMMAND (autonomy/run.sh:5868 exports GIT_SSH_COMMAND=false) or GIT_NO_LAZY_FETCH in the inherited env makes the plain `git status` skip core.sshCommand, so the hook marker is never written. `env GIT_SSH_COMMAND=false bash tests/test-untracked-status-fsmonitor.sh` and `env GIT_NO_LAZY_FETCH=1 ...` each fail the control exactly as in CI. A second cause remained in a clean env: 1 of 20 runs failed the control because `git status` re-hashes f.txt (and so lazy-fetches the attributes blob) only when the index entry is racily clean; otherwise stat matches and no fetch happens.
+- Siblings: both lazy-fetch fixtures in the file (run_lazy_case and the filter-case repo); any test asserting a repo-local ssh, fsmonitor or filter command runs.
+- Mechanism: both fixtures unset GIT_SSH, GIT_SSH_COMMAND, GIT_NO_LAZY_FETCH, GIT_CONFIG_COUNT, GIT_CONFIG_PARAMETERS, GIT_DIR, GIT_WORK_TREE and set GIT_CONFIG_NOSYSTEM=1 GIT_CONFIG_GLOBAL=/dev/null, and run_lazy_case sets f.txt mtime to 2030 (as run_eq_case already does) so status always re-hashes. The control runs first; a dead control is a FAIL that marks the real leg NOT PROVEN, never a skip or pass. The real assertion is unchanged.
+- Fixture: the same file passes 21/0 on 40 consecutive clean runs (was 19/1 once in 20) and with GIT_SSH_COMMAND=false GIT_NO_LAZY_FETCH=1 set.
+
+## FC-BASELINE-PER-PACKAGE A full suite already red on base was blocked as a regression because the baseline ran a different command (BASELINE-PER-PACKAGE)
+- User-visible vs raw: user-visible. `loki start asklokesh/FireLater#20` (run e10-20261018T205157Z-678e) ended FAILED with "full suite: frontend failed" after $2.60: verify ran one full suite per Project Model package, `(cd frontend && npm test)`, while the intake baseline had run only the repo's first test command at the root, so attributeFullSuite found no baseline for that command and excused nothing; vitest's per-test cross line also carried its duration ("5ms"), so even a matching command would give different ids on base and head.
+- Law broken: a failure the change did not cause is never charged to the change; base and head are measured with the same command and the same id parser.
+- Siblings: the legacy per-runner full suite (FULL_SUITE_CMD, `npm test --silent` vs the profile's `npm test`), the multi-root package suites (runPackageSuites), every runner whose failure line carries a timing suffix (failIds), and the REPOMEM reuse path (a new HEAD drops the per-command entries, so they are re-recorded).
+- Mechanism: package_suite.ts fullSuiteSpecs is the one list of full-suite commands; verify runs it and intake's baselineSuites records a baseline per command in its own cwd (shared budget, a suite past it is recorded not run); attributeFullSuite matches each failing check to its own command's baseline and stays fail-closed (no baseline for a command, an unattributable one, or no known ids: nothing excused); failIds strips a trailing duration ("5ms", "1.2s") from FAIL and cross lines.
+- Fixture: loki-ts/tests/runner/harness_intelligence.test.ts "baselineSuites records one entry per full-suite command" and "attributeFullSuite matches each package check to its own suite baseline"; loki-ts/tests/engine10/verify_prered.test.ts FC-BASELINE-PER-PACKAGE vitest duration case.
+
+## FC-DEPS-NOT-INSTALLED A fresh clone ran its tests with no dependencies installed, and the runner's "missing packages" error read as the code's failure (DEPS-NOT-INSTALLED)
+- User-visible vs raw: raw. In the same FireLater#20 run every package declared an install command (`npm ci`, citing its package-lock.json) but nothing was installed, so the Wall base run and the baseline ran against an empty dependency tree and npx printed "npm error npx canceled due to missing packages and no YES option"; that line matched no load pattern, so it was a test failure owned by the code and spent fix rounds.
+- Law broken: the harness prepares the environment the repo declares before it measures anything; an environment failure is the harness's, never a fix round.
+- Siblings: the FC-22b install library (prepareDeps) existed but was never wired; the runner load classifier (npm and npx missing packages, POSIX sh "N: tool: not found" next to the bash "command not found" already covered); every ecosystem whose install command the Project Model cites (decided by git, not by a list of dependency directory names).
+- Mechanism: install.ts absentDepRoots names a model package whose install command cites an existing manifest or lockfile in its root while git shows no untracked or ignored directory there (Loki's own .loki/ excluded); intakeDeps runs prepareDeps for those roots once per run, after the profile's first main baseline (measured on the bare clone) but before the Wall base run; after any successful install the main baseline and every per-command suite baseline are re-run, so none is left measured without dependencies; whatever the install created untracked (node_modules without a gitignore, lockfiles, .venv) is recorded in intake as install_created (a content hash per file, created directories) and never written to git config or exclude files, so an untouched install artifact stays out of verify changedFiles and the commit while an agent-edited lockfile still counts as a change; it emits deps.install per package, and a failed install becomes deps_not_proven, which verify carries into not_proven while the run goes on; the intake stage limit grows by the install and suite-baseline caps; runner_errors.ts LOAD_PATTERNS classify both missing-package forms as a harness-owned load error, anchored at the start of a line so test output quoting them stays a test failure.
+- Residual risk: source shipped inside an install-created directory (for example a new build/ or vendor/) is not committed, and a symlink to a directory is not recorded.
+- Fixture: loki-ts/tests/engine10/fc22_install.test.ts "absentDepRoots and intakeDeps (FC-DEPS-NOT-INSTALLED)"; loki-ts/tests/engine10/runner_errors.test.ts FC-DEPS-NOT-INSTALLED case.
+- Budget change: the intake stage limit is now STAGE_BUDGETS.intake.limitS + INSTALL_CAP_MS/1000 + SUITE_BASELINE_BUDGET_S (120s), so a repo that needs an install or a per-command baseline gets that extra time at intake; a repo with nothing absent and no suites spends none of it.

package/docs/v10/PROGRESS.md

@@ -2572,3 +2572,9 @@ v11.17.21 published (Release success on 462fbc40a; npm latest 11.17.21, next 11.
 
 ## 2026-10-18T22:58Z (CoS) v11.17.66
 - FC-STACKED-ON-LOKI-RUN: #21527 rerun on 11.17.64 based its run on loki/e10-20261018T205304Z-fdfc. Fix 304566e37 (base_guard.stackedOnLokiRun + intake checkout from target tip). HIGH review BLOCK on e869305 (B1/B2), APPROVE on f810c19; merged content equals approved (diff only 3c09faeb5 released files). intake.test.ts 54 pass; engine10 subset 138 pass 0 fail rc=0. help-drift was red (no backticked loki invocation in newest 5 sections); this section restores it.
+
+## 2026-10-19T00:10Z (CoS) v11.17.67
+- FC-LAZY-CONTROL-ENV: Tests 39174561642 shard 6 red on 8cc81a1b8. Causes reproduced: env GIT_SSH_COMMAND=false or GIT_NO_LAZY_FETCH=1 fails the control; clean env failed 1/20 (racy index). Fix 4735b5c14: env isolation + f.txt mtime 2030 + control-first fail. 40/40 clean runs 21/0; hostile env 21/0. TL APPROVE with mutation (drop GIT_NO_LAZY_FETCH in run.sh:10826 -> real leg FAIL 20/1, restored 21/0); select-tests 119/0.
+
+## 2026-10-19T00:19Z (CoS) v11.17.68
+- FireLater#20 (FC-BASELINE-PER-PACKAGE, FC-DEPS-NOT-INSTALLED): 4 HIGH rounds. R1 BLOCK c3ea3ec1e (B1 untyped not-found keys, B2 install leak, B3 FAIL-line duration strip). R2 BLOCK f1db1bb88 (info/exclude dropped agent lockfile, persisted, shared across worktrees). R3 BLOCK 37bff6049 (load_owner changedSince unfiltered: Cannot find package zod -> code failure). R4 APPROVE b8418f695: real runCheck repro fail -> not_run/harness; positive control stays fail; 650 pass 0 fail across 19 files; tsc clean outside control-plane. Rebased onto 0d153a7e9 as 52bb0fb78, loki-ts src/tests diff vs reviewed = empty. drift 4/0, sigpipe rc 0, select-tests 119/0.