| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| loki-mode-claude-code-10.10.3.tar.gz | < 14 hours ago | 7.0 MB | |
| npm-sbom.cdx.json | < 14 hours ago | 250.2 kB | |
| loki-mode-10.10.3.skill | < 14 hours ago | 152.8 kB | |
| loki-mode-10.10.3.tar.gz | < 14 hours ago | 44.8 MB | |
| loki-mode-10.10.3.zip | < 14 hours ago | 152.8 kB | |
| loki-mode-api-10.10.3.zip | < 14 hours ago | 153.6 kB | |
| loki-mode-claude-code-10.10.3.zip | < 14 hours ago | 8.0 MB | |
| Loki Mode v10.10.3 source code.tar.gz | < 14 hours ago | 44.7 MB | |
| Loki Mode v10.10.3 source code.zip | < 14 hours ago | 48.1 MB | |
| README.md | < 14 hours ago | 1.2 kB | |
| Totals: 10 Items | 153.4 MB | 0 | |
Fixed
- Fix (FC-19 R1): if the single resume after a spec conflict fails, is killed, or ends without a marker, the run keeps the first session's question and ends BLOCKED instead of PARTIAL or FAILED; duration_s counts both sessions.
- Fix (D86, FC-19, L0, L1): the implement stage does the full job. The implement brief (FIXED_RULES) no longer limits the model to named files or impacted tests and allows the full suite; STAGE_PREFIX and LEAN_PREFIX are role-neutral so the plan and Wall briefs keep their roles; the implement limit comes from the run budget instead of a fixed 480s. A LOKI_SPEC_CONFLICT from implement now gets one resume with a correction (Loki imposes no limits) before it is believed; a persisting conflict is the normal BLOCKED with its question. Side effect: deep-mode implement now gets its 1800s session limit (session.ts used to kill it at 480s).
Changed
- Control Plane run page follow-ups: changed files are taken from the receipt shas, a "why" line, structured evidence rows, a summary grid and a default repo chip.
Docs
- CP parity matrix against the legacy dashboard: 101 rows (57 wired, 37 backend-missing, 7 drop).
