liteagents 2.24.0 → 2.24.1
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.
- package/CHANGELOG.md +36 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -7,6 +7,42 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
|
|
7
7
|
|
|
8
8
|
---
|
|
9
9
|
|
|
10
|
+
## [2.24.1] - 2026-09-03
|
|
11
|
+
|
|
12
|
+
### Changed
|
|
13
|
+
- **The file-referent ledger half is SHELVED — no demonstrated problem.** The v2.24.0
|
|
14
|
+
entry below says shipping the ledger side is "gated on a future exact-label-agreement
|
|
15
|
+
measurement," which implied the work was justified and merely queued. That premise was
|
|
16
|
+
never checked, and it is wrong. The harm this channel prevents — a false match
|
|
17
|
+
inflating an entry's count until a `hot` entry hits `recurred_while_hot >= 2` and has
|
|
18
|
+
its rule rewritten — has never occurred: `ag-001` is the only `hot` entry, its
|
|
19
|
+
`recurred_while_hot` is 1 against a threshold of 2, and its two `attempts` are a
|
|
20
|
+
deliberate August rephrasing rather than a false-match rewrite. A POC also established
|
|
21
|
+
the naive ledger design would not have worked: cluster-level unions collide at 1.8%,
|
|
22
|
+
but entry-level unions collide at **38%**, because an entry accumulates paths across
|
|
23
|
+
every session it matches and inevitably collects `README.md` / `CLAUDE.md`. A
|
|
24
|
+
document-frequency filter repairs it (9.5% at df<=2), but repairing a fix for a problem
|
|
25
|
+
that is not occurring is not a reason to ship. **The incoming half is kept** — it costs
|
|
26
|
+
nothing, adds no LLM step, and accumulates evidence for free.
|
|
27
|
+
- **The un-shelve trigger is now checkable rather than a judgement call:** a false match
|
|
28
|
+
observed under a sonnet-class classifier, OR `ag-001` reaching `recurred_while_hot = 2`
|
|
29
|
+
on evidence that is not about validation.
|
|
30
|
+
- **And that trigger must NOT be exact-label agreement.** A fourth POC arm with the
|
|
31
|
+
user's quotes stripped from both sides scored best on every stability measure (0.900
|
|
32
|
+
exact agreement, 3/20 unstable) and is plainly the worst arm: it unanimously dropped
|
|
33
|
+
three clusters (`ag-012`, `ag-007`, `ag-001`) that all nine quote-carrying runs matched
|
|
34
|
+
unanimously, and named antigens after session hashes. It wins by having nothing to go
|
|
35
|
+
on and defaulting to `drop`. High agreement on "I don't know" is not quality — the same
|
|
36
|
+
degenerate shape as the severity axis that was seeded and rated on the same signal. A
|
|
37
|
+
re-attempt needs a human-labelled gold set.
|
|
38
|
+
|
|
39
|
+
### Added
|
|
40
|
+
- `poc/friction-file-referents/` — the corpus, all four arm prompts, raw labels from 12
|
|
41
|
+
runs, and `score.py`, which reproduces every table above. Kept so a re-attempt starts
|
|
42
|
+
from the numbers. Outside `package.json`'s `files` allowlist; not published.
|
|
43
|
+
|
|
44
|
+
---
|
|
45
|
+
|
|
10
46
|
## [2.24.0] - 2026-09-03
|
|
11
47
|
|
|
12
48
|
### Added
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "liteagents",
|
|
3
|
-
"version": "2.24.
|
|
3
|
+
"version": "2.24.1",
|
|
4
4
|
"description": "AI development toolkit with 11 specialized agents and 18 commands including live-canvas UI design with click-to-annotate feedback. Simple one-question installer for Claude, Opencode, Ampcode, and Droid.",
|
|
5
5
|
"main": "index.js",
|
|
6
6
|
"bin": {
|