loki-mode 11.141.3 → 11.141.4

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.
Files changed (68) hide show
  1. package/SKILL.md +2 -2
  2. package/VERSION +1 -1
  3. package/dashboard/__init__.py +1 -1
  4. package/docs/CLI-REFERENCE.md +1 -1
  5. package/docs/INSTALLATION.md +1 -1
  6. package/docs/dev/architecture-reference.md +6 -1
  7. package/loki-ts/dist/loki.js +1688 -1680
  8. package/mcp/__init__.py +1 -1
  9. package/package.json +2 -2
  10. package/packages/control-plane/dist/server.js +644 -254
  11. package/plugins/loki-mode/.claude-plugin/plugin.json +1 -1
  12. package/web-app/dist/assets/{AdminPage-CXYutD4P.js → AdminPage-Dkj5FgZn.js} +1 -1
  13. package/web-app/dist/assets/{Avatar-DtQv32ei.js → Avatar-D6ZOMRQj.js} +1 -1
  14. package/web-app/dist/assets/{Badge-B0OEiGWj.js → Badge-przKIrx7.js} +1 -1
  15. package/web-app/dist/assets/{Button-DAxRHI93.js → Button-X5VdLM9H.js} +1 -1
  16. package/web-app/dist/assets/{CockpitPage-B9Hi4roF.js → CockpitPage-CWUPO4jE.js} +1 -1
  17. package/web-app/dist/assets/{ComparePage-BFCQ2npD.js → ComparePage-jinxUAH3.js} +1 -1
  18. package/web-app/dist/assets/{ErrorBoundary-iD00UcjA.js → ErrorBoundary-B3o_toch.js} +1 -1
  19. package/web-app/dist/assets/{EvidenceReceiptPanel-B76dpKnO.js → EvidenceReceiptPanel-ClySg933.js} +1 -1
  20. package/web-app/dist/assets/{GitHubIssuesPanel-B5-pxBUX.js → GitHubIssuesPanel-Dm_UsFAy.js} +1 -1
  21. package/web-app/dist/assets/{GitHubPRsPanel-Cz8MDVpH.js → GitHubPRsPanel-FAkViqVu.js} +1 -1
  22. package/web-app/dist/assets/{HomePage-RN8tGnly.js → HomePage-VeVb73XG.js} +2 -2
  23. package/web-app/dist/assets/{LoginPage-3bgx6JO5.js → LoginPage-BpEKt-6l.js} +1 -1
  24. package/web-app/dist/assets/{MagicPage-Csph1itx.js → MagicPage-CNC180dU.js} +1 -1
  25. package/web-app/dist/assets/{MetricsPage-C-gpg5dg.js → MetricsPage-BIfpdlcf.js} +1 -1
  26. package/web-app/dist/assets/{NotFoundPage-D_2iaSIZ.js → NotFoundPage-D54hg346.js} +1 -1
  27. package/web-app/dist/assets/{ProjectPage-sOWNmoyz.js → ProjectPage-Dl3rZ5bV.js} +3 -3
  28. package/web-app/dist/assets/{ProjectsPage-Bcj1zeOK.js → ProjectsPage-DzQrB1jU.js} +1 -1
  29. package/web-app/dist/assets/{SettingsPage-V3PvBKXt.js → SettingsPage-DYB5XNpM.js} +1 -1
  30. package/web-app/dist/assets/{ShowcasePage-Dgnx6rqF.js → ShowcasePage-CjhoM3rN.js} +1 -1
  31. package/web-app/dist/assets/{SystemSettingsPage-CYwtNhot.js → SystemSettingsPage-BVNnfllD.js} +1 -1
  32. package/web-app/dist/assets/{TeamsPage-zE5VGlot.js → TeamsPage-1KkrFd0Y.js} +1 -1
  33. package/web-app/dist/assets/{TemplatesPage-ByMfvWWy.js → TemplatesPage-DGDnu_RB.js} +1 -1
  34. package/web-app/dist/assets/{TerminalOutput-DWlKNNgH.js → TerminalOutput-DSomtLgf.js} +1 -1
  35. package/web-app/dist/assets/{activity-E89Nv0Gn.js → activity-CW1VLglI.js} +1 -1
  36. package/web-app/dist/assets/{bell-F5OLNHAS.js → bell-tJAz56Yb.js} +1 -1
  37. package/web-app/dist/assets/{bot-BgMvMeIE.js → bot-B6I5yrNn.js} +1 -1
  38. package/web-app/dist/assets/{check-DDjMmGIx.js → check-IVM56fVX.js} +1 -1
  39. package/web-app/dist/assets/{chevron-left-DOuYhQj3.js → chevron-left-SsA1da21.js} +1 -1
  40. package/web-app/dist/assets/{circle-alert-4RB4dTkg.js → circle-alert-Dsq3DqO-.js} +1 -1
  41. package/web-app/dist/assets/{clock-CuPAeSjR.js → clock-Cj9sLcEq.js} +1 -1
  42. package/web-app/dist/assets/{cloud-BMbPHSHB.js → cloud-CSbZsshu.js} +1 -1
  43. package/web-app/dist/assets/{code-xml-DM3_SytH.js → code-xml-qCQWXElP.js} +1 -1
  44. package/web-app/dist/assets/{database-Dg6mN6Ow.js → database-BnviiGuk.js} +1 -1
  45. package/web-app/dist/assets/{dollar-sign-B614dJTB.js → dollar-sign-DaU9xa0A.js} +1 -1
  46. package/web-app/dist/assets/{file-code-corner-Dl4JdVpI.js → file-code-corner-a393d0YD.js} +1 -1
  47. package/web-app/dist/assets/{file-plus-BInei2Fp.js → file-plus-C3J3IYsn.js} +1 -1
  48. package/web-app/dist/assets/{globe-D9dhwBk0.js → globe-DKRN-OfP.js} +1 -1
  49. package/web-app/dist/assets/{hammer-DkHCWudw.js → hammer-AJ4xEMEQ.js} +1 -1
  50. package/web-app/dist/assets/{index-CGg-uQi6.js → index-BmuNF2mZ.js} +3 -3
  51. package/web-app/dist/assets/{layers-D7FRJ2Cg.js → layers-ZxK3Lg-E.js} +1 -1
  52. package/web-app/dist/assets/{loader-circle-DWu2xFyT.js → loader-circle-BQGio77U.js} +1 -1
  53. package/web-app/dist/assets/{lock-DtQ7UEiT.js → lock-BSMOsGRv.js} +1 -1
  54. package/web-app/dist/assets/{package-D-uGJ1YH.js → package-Dc3iyh_u.js} +1 -1
  55. package/web-app/dist/assets/{plus-BfTkHz42.js → plus-BE-oSyaC.js} +1 -1
  56. package/web-app/dist/assets/{refresh-cw-BXeJY2sm.js → refresh-cw-B24IKBF1.js} +1 -1
  57. package/web-app/dist/assets/{rotate-ccw-CSugG-Ae.js → rotate-ccw-Cm9OyY5g.js} +1 -1
  58. package/web-app/dist/assets/{scroll-text-DRwM3FIU.js → scroll-text-gdM4zNkj.js} +1 -1
  59. package/web-app/dist/assets/{server-CClk8rzC.js → server-B8YzsGPg.js} +1 -1
  60. package/web-app/dist/assets/{shield-alert-xtO3fBXY.js → shield-alert-COu4qEAn.js} +1 -1
  61. package/web-app/dist/assets/{thumbs-up-DbWHOFPx.js → thumbs-up-Bs3ZSrCN.js} +1 -1
  62. package/web-app/dist/assets/{trash-2-CYZZlWrP.js → trash-2-vdl0RPBK.js} +1 -1
  63. package/web-app/dist/assets/{trending-down-DUl7D2qn.js → trending-down-DhxJxyuC.js} +1 -1
  64. package/web-app/dist/assets/{trending-up-CgDQ9rvV.js → trending-up-sBLyeLVo.js} +1 -1
  65. package/web-app/dist/assets/{upload-DuB3Cd-6.js → upload-B_SYHnav.js} +1 -1
  66. package/web-app/dist/assets/{usePolling-u10dSbx_.js → usePolling-CLtoYkMM.js} +1 -1
  67. package/web-app/dist/assets/{user-CUl0PWOM.js → user-CIt72Y0w.js} +1 -1
  68. package/web-app/dist/index.html +1 -1
package/SKILL.md CHANGED
@@ -3,7 +3,7 @@ name: loki-mode
3
3
  description: Runs an autonomous software factory that knows what it is supposed to deliver and proves it did, with a signed receipt. Use when the user says Loki Mode or asks to build, fix or verify software autonomously.
4
4
  ---
5
5
 
6
- # Loki Mode v11.141.3
6
+ # Loki Mode v11.141.4
7
7
 
8
8
  **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.
9
9
 
@@ -461,4 +461,4 @@ Implemented, planned and deprecated items, with the version each landed in: `CHA
461
461
 
462
462
  ---
463
463
 
464
- **v11.141.3 | [Autonomi](https://www.autonomi.dev/) flagship product | core skill**
464
+ **v11.141.4 | [Autonomi](https://www.autonomi.dev/) flagship product | core skill**
package/VERSION CHANGED
@@ -1 +1 @@
1
- 11.141.3
1
+ 11.141.4
@@ -7,6 +7,6 @@ Modules:
7
7
  control: Session control helpers (status, atomic writes, origin check)
8
8
  """
9
9
 
10
- __version__ = "11.141.3"
10
+ __version__ = "11.141.4"
11
11
 
12
12
  __all__ = ["__version__"]
@@ -1,6 +1,6 @@
1
1
  # CLI reference
2
2
 
3
- Generated from `loki-ts/src/cli/registry.ts` by `scripts/generate-stale-zero.sh` for v11.141.3. Do not edit by hand.
3
+ Generated from `loki-ts/src/cli/registry.ts` by `scripts/generate-stale-zero.sh` for v11.141.4. Do not edit by hand.
4
4
  Hidden and legacy-only commands are omitted; see `docs/CLI-INVENTORY.md` for the full inventory.
5
5
 
6
6
  | Command | Description |
@@ -2,7 +2,7 @@
2
2
 
3
3
  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.
4
4
 
5
- **Version:** v11.141.3
5
+ **Version:** v11.141.4
6
6
 
7
7
  **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).
8
8
 
@@ -171,6 +171,11 @@ These knobs together implement the RARV-C (closure) loop: findings -> override c
171
171
  - `LOKI_E10_INTAKE_CAP_S` -- off by default since acc-148 (unset, `0` or a non-number keeps the per-command caps alone); a positive number of seconds turns the shared budget on. When on and it cuts a baseline, intake prints one line starting `loki: intake budget spent after N s` (`repo_profile.ts` intakeBudgetNote). Turned off because it had no measured accuracy benefit and cut 6 of 65 past baselines (a complete 196 s gitea suite among them), and a cut baseline is unattributable base red. (R3; `loki-ts/src/runner/repo_profile.ts` intakeCapS / baselineSuites `deadlineMs`, wired in `stages/intake.ts` and `project_model/install.ts` intakeDeps). One budget in seconds for all of intake's baseline test runs together: the root baseline, its rerun after an install, and the per-suite baselines. A run the budget cuts is recorded as cut off, and a suite with no budget left reads "baseline budget used up", as before. The dependency install keeps its own cap (INSTALL_CAP_MS) and is not counted. The failure: a suite past the 300 s per-command cap was measured twice under two names, so intake spent 600 s on two cut-off runs that excuse nothing. Of 65 recorded bench baselines, 6 took over 180 s in all; 1 of them (195.8 s root, 219.2 s suite) completed and would now be cut.
172
172
  - `LOKI_E10_MOCHA_TARGETED` -- on by default, `0` opts out (R5; `loki-ts/src/engine10/testmap.ts` mochaTargets, used by `stages/verify.ts`). When verify selects no test at all, a changed JS/TS file whose nearest package.json declares mocha (a dependency, a script, a `mocha` key, or a .mocharc file beside it) maps to its own test file: itself under the package's test/, tests/ or spec/ directory (fixtures excluded), else the file at the same path under one of them (with or without the source's first directory). At most 8, each run as `npx --no-install mocha <file>` (runner `mocha`, which runner detection never lists) through the normal test path, so base subtraction and the flaky rerun apply and a passing one covers its source. Mocha test files carry no .test or .spec suffix, so such a repo verified with no test at all.
173
173
  - `LOKI_E10_BASE_RED_SHAPE` -- on by default, `0` opts out (acc-147; `loki-ts/src/runner/repo_profile.ts` sameUnattributableRed inside attributeFullSuite, `loki-ts/src/util/check_result.ts` failureShape). The intake baseline records the output shape of a base suite that is red with no parseable failing ids (`failing_shape`). A head full suite of the same command is pre-existing only when it fails in the identical kind: the same exit code, no parseable ids, and the same shape (whole output, only durations, clock times, timestamps and hex addresses normalized). A newly broken test, a different message or count, or another exit code stays introduced. The excuse is disclosed on NOT PROVEN. Dev corpus 2026-11-13: 4 of 24 runs ended FAILED with fix rounds chasing such a suite ("the base run is not attributable").
174
+ - `LOKI_E10_DEEP_POST` -- on by default, `0` opts out (fl24; `loki-ts/src/engine10/stages/deep.ts` deepPost, spawned by `loki-ts/src/engine10/supervisor.ts` beside the deep worker). The deep worker holds withheld GitHub credentials, so it no longer posts; the poster (push env, runs no repo code) waits for its pid, reads `receipt-addendum-1.json` and posts the comment and the `loki/deep-verify` status, `error` when no addendum was written. Its pid is the last `deep.started` event, so the run stays live until the status is posted.
175
+ - `LOKI_E10_WEAK_EXCUSE` -- on by default, `0` opts out (fl24; `loki-ts/src/util/test_guard.ts` testFileWeakened / excusedEdit). Fewer assertions only inside test cases the task names by exact title and asks to update are not a weakened test; seal lists each as `edited test kept uncapped (...)`.
176
+ - `LOKI_E10_WEAK_MOCK_NEW` -- off by default, `1` turns it on (fl24; same file). Also excuses a setup hook inside a describe block the change added, an added mock of a module new in the change, or a bare vi.fn() logger or metrics stub. Off because a mock of a new module can still reach existing tests when the change moved logic into it.
177
+ - `LOKI_E10_BASE_MEMO` -- on by default, `0` opts out (fl24; `loki-ts/src/engine10/stages/verify.ts` baseMemo in subtractBase). Base reruns are kept in `.loki/runs/<id>/base-runs.json`, bound to the base sha and to whether dependency dirs were linked, and reused by later verifies of the same run.
178
+ - `LOKI_E10_ONE_BASE_RUN` -- on by default, `0` opts out (acc-171; `loki-ts/src/runner/repo_profile.ts` repoRelCmd, used by baselineSuites rootSpeaks, baseFor and suiteEmptyOnBase). A command whose first word is the repo dir's absolute path is compared with the repo prefix dropped, so the root baseline speaks for the root package suite and intake runs it once.
174
179
  - `LOKI_E10_EVIDENCE_PER_PACKAGE` -- on by default, `0` opts out (acc-147; `loki-ts/src/engine10/testmap.ts` buildTestMap marks, `loki-ts/src/util/test_file_text.ts` scopeRunnersByPackage). Package scoping grants a runner to every package that owns a file proving it (go.mod, Cargo.toml, a test file), not only to the package of the first such file listed. Without it a multi-module repo whose nested module sorts first (go-chi/chi `_examples/rest/go.mod`) left the root module with no runner and 0 tests once the Project Model loaded. The 5 tuning repos' test maps are unchanged.
175
180
  - `LOKI_E10_ENCLOSING_DECL` -- on by default, `0` opts out (acc-147; `loki-ts/src/util/check_result.ts` changedSymbols / enclosingDecl, read by `stages/seal.ts` and `stages/verify.ts`). When a hunk declares nothing and git's `@@` context names nothing (an edit inside an indented method: git's default funcname reads only unindented lines, and JS/TS has no built-in driver), the enclosing declaration is read from the head file. Hunks whose context already names a declaration are unchanged. Without it the lean gate and the fail-then-pass proof read "(no declared symbol)" and a run with a real fail-then-pass test stayed PARTIAL (commander.js).
176
181
  - `LOKI_E10_ASSERT_JS` -- on by default, `0` opts out (acc-148; `loki-ts/src/util/check_result.ts` assertionFailure / jsAssertionFailure, read by the fail-then-pass proof in `stages/seal.ts`). node:test, jest and mocha failures on the base count as red by assertion when the output carries an assertion (ERR_ASSERTION, AssertionError, `expect(received).<matcher>`) and no missing-API or load failure (not a function or constructor, ReferenceError, SyntaxError, a missing module or export, a suite that failed to run). Before it, only pytest, vitest and go were read, so a real fail-then-pass on these runners never counted (commander.js).
@@ -203,7 +208,7 @@ These knobs together implement the RARV-C (closure) loop: findings -> override c
203
208
  - `LOKI_E10_PROOF_PROJECT_API` -- on by default, `0` opts out (acc-154; `loki-ts/src/engine10/stages/seal.ts` baseProofRunner and the Wall mutation proof). The fail-then-pass proof runs each test with the real repo's Project Model. RealBaseTestRunner otherwise read the model from the temporary base worktree, which has no `.loki/`, so in a multi-package repo a frontend vitest file ran from the repo root (no vitest there) and the proof read "inconclusive (the Wall command did not execute to a result)".
204
209
  - `LOKI_E10_PRECEDENCE_CHECK` -- on by default, `0` opts out (F3; `loki-ts/src/util/edit_shape.ts` precedenceSites / precedenceBrief, `util/conflict_resume.ts` resumeForPrecedence). The edit-shape precedence rule detects a widened check from the diff alone: a Go `x.(T)` replaced by `errors.As` or `errors.Is`, an `isinstance` or `instanceof` moved to another type, or an exact `==` / `===` comparison replaced by a membership test (`includes`, `in`, `strings.Contains`). For each such site it lists the other type or value checks in the same function, the inputs that took their own branch before. After a clean LOKI_DONE with a non-empty diff, a site that has such inputs gets one follow-up resume (`-pr`) naming each input and asking that it still take its branch, with a test case per input; only a clean LOKI_DONE replaces the first result. Nothing fires, and nothing is spent, without such a site. The implement stage records `precedence_check: {sites, resumed}`. The tuning case was a widened error check placed ahead of an existing assertion branch; the test fixtures are synthetic.
205
210
  - `LOKI_E10_BUILD_ARTIFACT_DROP` -- on by default, `0` opts out (GB; `buildArtifacts` in `loki-ts/src/e10ext/commit_filter.ts`, part of `dropSet`, so the commit stage, the supervisor backstop and the WIP commit all apply it; seal names each one with "generated or build file left out of the commit: <path>"). A file the run ADDED is left out when the repo's ignore rules match it (`git check-ignore --no-index`, so a force-added file counts), when it is byte-compiled or incremental build state anywhere (`*.pyc`, `*.pyo`, `*.tsbuildinfo`, `__pycache__/`, `<name>.egg-info/`), or when it sits under `dist/`, `build/`, `coverage/`, `.nyc_output/` or `target/` at the repo root or beside a package manifest. Kept: the task names the file, or that output or cache directory (`dist/`, `__pycache__/`, `<name>.egg-info/` ...) already holds a file tracked at the run base (a repo that commits it). Modified tracked files are never touched. The ignore rules are the tree's at commit time, which equal the base's unless the run edited a `.gitignore`.
206
- - `LOKI_E10_REGEN_DROP` -- on by default since 11.141.3 (measured on dev2, 2 seeds, GOALS A3.2), `0` opts out (RD; `noteRegenerated`, `regenDrops` in `loki-ts/src/e10ext/commit_filter.ts`; the machine snapshots the tree around every verify run in `engine10/machine.ts`, and the commit stage in `stages/seal.ts` applies it). A path a verify run changed joins `<runDir>/regenerated.json`; a path a model stage (wall, implement, fix) later writes leaves it. At commit, a staged path still in that set is left out unless the task names it or one of its changed lines carries a task keyword (a backticked span, or an identifier of 5 or more characters with a digit, underscore or camelCase, or 8 or more letters), so a doc a test run regenerated in step with the change stays. Each drop is named on the receipt: "rewritten only by Loki's own check run, not by the change, and left out of the commit: <path>". The failure: a test run regenerated an unrelated doc page with a machine-specific path, the commit shipped it, and review failed a VERIFIED run as an unrelated edit.
211
+ - `LOKI_E10_REGEN_DROP` -- on by default since 11.141.3 (measured on dev2, 2 seeds, GOALS A3.2), `0` opts out (RD; `noteRegenerated`, `regenDrops` in `loki-ts/src/e10ext/commit_filter.ts`; the machine snapshots the tree around every verify run in `engine10/machine.ts`, and the commit stage in `stages/seal.ts` applies it). A path a verify run changed joins `<runDir>/regenerated.json`; a path a model stage (wall, implement, fix) later writes leaves it. At commit, a staged path still in that set is left out unless the task names it or one of its changed lines carries a task keyword (a backticked span, or an identifier of 5 or more characters with a digit, underscore or camelCase, or 8 or more letters), so a doc a test run regenerated in step with the change stays. Each drop is named on the receipt: "rewritten only by Loki's own check run, not by the change, and left out of the commit: <path>". The failure: a test run regenerated an unrelated doc page with a machine-specific path, the commit shipped it, and review failed a VERIFIED run as an unrelated edit. acc-170 adds three rules. A NEW file only a check run wrote is left out unless the task names its exact path or file name; the task-keyword exemption keeps only modified files. The commit stage's picks go through `guardRegenDrops`: each goes back to base on disk (a modified file checked out, a new one removed), then `targetedBreak` (seal.ts) reruns the targeted tests verify passed (at most 6, about 20 s; never a full suite or lint). If one fails, or none could run, every pick is restored byte for byte, kept, and named on the receipt ("rewritten by Loki's own check run and kept: a targeted test fails without it"). And `commitUnsealedWork`, the run-end WIP commit of a run with no PR, applies the same RD drop, so a path the commit stage left out cannot come back.
207
212
  - `LOKI_E10_DIFF_NEED` -- on by default since 11.141.3 (measured on dev2, 2 seeds, GOALS A3.2), `0` opts out (DN; `needDrops`, `formattingOnly`, `suppressionOnly` in `loki-ts/src/e10ext/commit_filter.ts`, applied by the commit stage in `stages/seal.ts` after RD). Deliver only what the fix needs, with no model call: a staged modified file the task does not name is left out when its change is formatting only (base and head equal once whitespace, quote style, semicolons and trailing commas are normalized; Python, YAML and other whitespace-significant files keep their indentation, so only trailing space, blank lines and quotes are normalized), unless the task asks for formatting; or when its change only adds or removes lint-suppression comments (noqa, type: ignore, eslint-disable, @ts-ignore, @ts-expect-error, nolint, pylint: disable, rubocop:disable, #[allow(..)], @SuppressWarnings) in a file outside the stated scope (or with no scope signal), unless the task is about lint or warnings. Each drop is named on the receipt ("formatting-only change left out of the delivered diff: <path>"). The failures: a 177 KB delivered diff of reformatted generated route trees and schema files where the raw run delivered 4.5 KB, and a drive-by suppression removal in an unrelated file.
208
213
  - `LOKI_E10_TEST_REACH` -- on by default, `0` opts out (TK; `exercisesChange` in `loki-ts/src/e10ext/scope.ts`, applied inside J3 `crossPackageTestEdits`). J3 never drops a test that imports the changed code: a JS/TS import or require whose relative specifier resolves to a changed source file (extension and `/index` optional) or names the changed file's package (its package.json name or a subpath), or a Go import of a changed file's package path (go.mod module plus directory; import blocks and single imports). A test that imports nothing changed is still dropped as before. Measured on synthetic layouts: a JS tests workspace importing the changed package, a relative import from a sibling package, and a Go package importing the changed subpackage were all dropped before (the run's only regression test, so the diff carried none) and are kept now; Python src-layout and Rust `tests/` are never J3 candidates.
209
214
  - `LOKI_E10_SCOPE_TEST_DROP` -- on by default, `0` opts out (J3; `loki-ts/src/e10ext/scope.ts` crossPackageTestEdits, applied by the commit stage in `stages/seal.ts`). The one non-advisory scope rule: a test file the run added or modified in an owner package (a Go directory, or a JS/TS package with its own package.json) where the change has no non-test change, the package has source files, and the task names neither the file nor the package, is reset to base (index and tree) before commit, with a NOT PROVEN line naming it. Source files, Python layouts, Go tests-only directories and test-only changes are never touched. On the tuning bench it fires on the 3 cross-package test scope fails and on 0 of 160 lean runs.