loki-mode 11.17.86 → 11.17.88

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.86
+# Loki Mode v11.17.88
 
 **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.86 | [Autonomi](https://www.autonomi.dev/) flagship product | core skill**
+**v11.17.88 | [Autonomi](https://www.autonomi.dev/) flagship product | core skill**

package/VERSION

@@ -1 +1 @@
-11.17.86
+11.17.88

package/dashboard/__init__.py

@@ -7,6 +7,6 @@ Modules:
     control: Session control helpers (status, atomic writes, origin check)
 """
 
-__version__ = "11.17.86"
+__version__ = "11.17.88"
 
 __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.86. Do not edit by hand.
+Generated from `loki-ts/src/cli/registry.ts` by `scripts/generate-stale-zero.sh` for v11.17.88. 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.86
+**Version:** v11.17.88
 
 **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

@@ -1280,3 +1280,12 @@ L0 review rule (ENGINE-LAWS.md L0): a fix that adds an `if` or a regex about the
 - Siblings swept: the escape-only assumption lived in one place (the report condition in `ev`); outOfRepoTarget, seal's addedSymlinkNotes and the implement repro-test path make no such assumption.
 - Mechanism: `strayInTestDir` in phantomRepoPaths additionally reports a path that stays inside the test dir when its first segment is absent from the test dir but present at the package or repo root (the author meant a repo path). Same exemptions (plan with parent, created, ignored by the VCS, write/expect/tmp lines); fixtures the test dir lacks (fixtures/a.json) and __self__ stay unreported.
 - Fixture: fc23_wall_conventions.test.ts "in-testdir phantom" (incident lines report tests/plugins/ralph-loop; plan-named, fixtures, created and __self__ paths pass). Red before the fix, green after.
+- Siblings swept (review of 11.17.85): the package-root fallback trusts a known project model fully (its package cwd, else the repo root) and otherwise walks up to the nearest manifest-shaped JSON (string name plus another key); config files (tsconfig, linter, test-runner, xml, cfg, toml) are never roots, so they cannot hide a real phantom (fixture "fallback no false root"). Known limit: a nameless manifest or a non-JSON-manifest package resolves only through the model; without one the repo root is the cwd. The vendor-dir exemption is the ignore check alone, with no vendor-dir name or `*_modules` pattern, so src/my_modules/x and src/feature_modules/x are reported (fixture "modules dir phantom"). The release-gate pytest guard strips only the pip install segment before checking (tests/test-release-gate-dedup.sh M10).
+
+## FC-MEDIUM-REVIEWER-UNCREDITED The medium tier selects "one reviewer", nothing on the default path runs or credits it, so every medium run lists it NOT PROVEN and seals PARTIAL
+- User-visible vs raw: user-visible. A real run on anthropics/claude-code#81826 (v11.17.83, risk tier medium) listed "one reviewer" under NOT PROVEN.
+- Law broken: a check the tier selected is credited when, and only when, it really ran (evidence or it did not happen); a check that did not run stays NOT PROVEN and is never hidden or dropped from the plan.
+- Cause (measured): check_result.ts PLAN.medium selects "one reviewer"; deferredOf keeps it in checks_deferred unless markExecuted names it; markExecuted has one caller (verify.ts, naming only "full test command" and "full suite"); no code names "one reviewer". The only reviewers are seal's crossReview (xreview.ts, opt-in via loki.yaml review, LOKI_REVIEW_PROVIDER or LOKI_XVENDOR_DEFAULT) and deep's council session (a detached worker that runs after seal). deepGaps (11.17.82, FC-SEAL-NA-AS-UNPROVEN) began pushing every deferred non-deep item into notProven; before it the receipt listed only the four static deep items, so this is a visibility regression of an old unkept promise, not a new bug in the reviewer.
+- Siblings swept (every PLAN.selected item): "targeted tests" and "lint of changed files" run always (RAN_ALWAYS); "full test command" and "full suite" are credited by verify.ts markExecuted and deepGaps fullRan; "council" and "security scan" (high) are credited by deep checks via executed(); "one reviewer" had no credit path (fixed here). Low tier names are disclosed as not selected.
+- Mechanism: one `REVIEWER_ITEM` credit rule inside `deepGaps`: credited when seal's cross-review returned a verdict (level not "not_run") or a deep council check executed. No review configured or a not_run review keeps it NOT PROVEN. The default path still has no reviewer, so default medium runs stay PARTIAL by design until a reviewer is configured; running a default same-vendor reviewer on every medium run is a separate cost decision.
+- Fixture: loki-ts/tests/util/check_result.test.ts "medium reviewer" (tier alone, not_run review, verdict review, council pass and not_run, high council not credited by a cross-review, low unaffected). Red with the credit removed, green after.

package/docs/v10/PROGRESS.md

@@ -2632,3 +2632,9 @@ v11.17.21 published (Release success on 462fbc40a; npm latest 11.17.21, next 11.
 
 ## 2026-10-19T10:37Z (CoS) v11.17.86
 - 11.17.86: FC-WALL-PHANTOM-PATH in-testdir sibling (f2b930627 cherry-picked as 3f75ea650 onto 0a897c42c). HIGH opus APPROVE: revert red 32/1, gates 150 pass 0 fail, end-to-end runWall re-ask then discard verified on the #81826 shape, tsc 0 errors in engine10/project_model; route_matrix_mutation unverified (50 min suite). Non-blocking: helper-generated fixture with a root fixtures/ dir can cost one re-ask.
+
+## 2026-10-19T10:49Z (CoS) v11.17.87
+- 11.17.87: 11.17.85 review follow-ups (53549dba0, 29a44f936). HIGH opus BLOCK on 53549dba0 (extension/nameless-JSON fallback hid phantoms in 6 repros), fixed in 29a44f936, HIGH APPROVE: 6 repros + incident shapes report, revert red (fallback no false root, modules dir phantom), gate 186/0, dedup 13/0 incl M10, tsc clean for engine10/project_model. Follow-up: fixture for the model-known branch (stale multi-root M4).
+
+## 2026-10-19T10:52Z (CoS) v11.17.88
+- 11.17.88: FC-MEDIUM-REVIEWER-UNCREDITED b28cd44c6 (cherry-pick 8977befb8, HIGH APPROVE). deepGaps credits one reviewer only when the cross-review level is not not_run or a deep council check executed. Gate 158 pass 0 fail (check_result, seal, budget), tsc rc=0. Default same-vendor medium review 261db067d HIGH BLOCKED (seal 60s limit), in rework.