@furongjun1999/dsh-memory 0.10.1 → 0.10.3

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.en.md CHANGED
@@ -8,6 +8,71 @@ The format follows [Keep a Changelog](https://keepachangelog.com/zh-CN/1.1.0/);
8
8
 
9
9
  ## [Unreleased]
10
10
 
11
+ ## [0.10.2] - 2026-11-12
12
+
13
+ ### Added: `recall` now returns a timeline — the state sequence becomes first-class (#868 / #869)
14
+
15
+ **Headline of this release, and the single largest gain in a dozen versions.**
16
+
17
+ - **Root cause**: given 20–30 fragments ordered by retrieval score, the model has **no deterministic
18
+ temporal basis** for picking "the earliest occurrence". The same question produced different
19
+ anchors across two runs (`P20-037`: 6-22 right / 5-22 wrong); more directly, `P01-ADD-004`
20
+ (gold 2026-06-10) still answered 2026-06-19 and `P17-025` (gold 2026-04-01) still answered
21
+ 2026-07-20 — **those dates were printed in the material**. Prompting it to "sort by date and
22
+ take the earliest" makes it sort its own recollection, not the material. Hence: **temporal
23
+ induction is not the model's job.**
24
+ - `recall` returns `timeline: [{date, id, head}]`, sorted ascending by `created_at`.
25
+ All inputs are existing fields (`frontmatter.created_at` + first body sentence) — zero extra
26
+ extraction cost; each row carries `id` for traceability, skips CCG headers, ≤80 chars.
27
+ - `recall` returns `timeline_groups`: sequences merged along a **topic axis**
28
+ (`frontmatter.bucket` condition bucket → first `tag` → "ungrouped"; ascending within a group,
29
+ groups ordered by size). A **heuristic merge layer** requiring no extractor; when coverage is
30
+ partial, the flat `timeline` still backstops.
31
+ - **Readings (time subset, 75 questions, 2 arms × 2 repeats)**:
32
+
33
+ | Stage | Stable set | Delta |
34
+ |---|---:|---:|
35
+ | Five algorithm patches (#851→#858) | 52 | — |
36
+ | + three answer-side fixes | 55 | +3 |
37
+ | **+ `timeline` + `timeline_groups`** | **66** | **+11** |
38
+
39
+ Time subset: **62.7% (baseline 47/75) → 88.0% (66/75)**.
40
+ - **Two decisive pieces of evidence**:
41
+ 1. **Timeline only, no source text** still scores 14/19 on the B-class subset ⇒ the information
42
+ lives mainly in the sequence; the extractor should be "sequence-first, text-second";
43
+ 2. **Arm on / off `MDCG_SCOPE_SELECT` ties (66 vs 66)** ⇒ the +11 comes from **material shape**,
44
+ not from the bucket-selection algorithm.
45
+ - **Merge coverage**: all 75/75 questions contain a topic group with ≥2 entries (mean 28.6/question).
46
+ - **Boundary**: the remaining 4 questions are "rescheduled final value" and "multi-element
47
+ composition" — they still need entity/slot extraction; groups here are **bucket-level heuristics**,
48
+ not a four-column state table. The full 714 was not re-run (75 is the time subset).
49
+
50
+ ### Fixed: `info(full=true)` 60-second timeout from disk index counting (#863)
51
+
52
+ - The full surface parsed a 60.4 MB `_index.json` on every call; inside a process already holding
53
+ a 34k-node index this caused memory pressure and hit the 60s tool timeout. Now counted with an
54
+ `(mtime, size)` cache: 0.77s first call, 0.000s afterwards, auto-invalidated on external writes.
55
+
56
+ ### Fixed: `validity=True` silently disabled bucket recall (#856)
57
+
58
+ - `bucketscope._is_expired` used `time.*` without `import time` ⇒ `NameError` swallowed by the
59
+ outer `except`, killing the whole bucket-recall path. The old guard was a false green.
60
+ Also fixed `fill_rest` bypassing the validity gate.
61
+
62
+ ### Fixed: cross-day bucket rotation ran only one round (#857)
63
+
64
+ - With 9 matches and `cap=8`, days yielding 0–1 items could never fill the cap (only 6 returned).
65
+ Now multi-round (≤3 rounds plus an idle-progress check).
66
+
67
+ ### Fixed: read surface silently dropped `condition_space` / `semantic` (#811)
68
+
69
+ ### Gates and tooling
70
+
71
+ - `check_publish_smoke.py` wired into CI (#807): static → tracked-files → **behavioral** gates.
72
+ - `cogmap check` decoupled from the git remote owner (#835); forks no longer fail.
73
+ - Tick failures now carry a traceback summary (#804).
74
+ - dependabot: paused `@deepseek-ai/{cordis,schemastery}` (pinned to `~3.18.4` / `4.0.5` upstream).
75
+
11
76
  ## [0.10.1] - 2026-11-11
12
77
 
13
78
  ### Time-retrieval fixes (#849 / #850 / #851 / #852 / #853 / #855 / #858 / #859)