You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Sanitized real-workspace regression fixtures for memory cleanup migration behavior.
17
+
18
+
### Changed
11
19
12
-
- Unified quality gate for compaction memory candidates and cleanup checks.
20
+
- Unified memory quality rules in a shared quality gate for compaction memory candidates and cleanup checks.
13
21
- Rewritten compaction memory prompt to reduce over-production of low-quality memories.
14
-
- Conservative one-time quality cleanup migration (`2026-04-28-quality-cleanup`) that supersedes only high-confidence garbage patterns: progress snapshots, raw errors, commit/CI snapshots, temporary status notes, active file snapshots, code/API signatures, path-heavy entries, and empty entries.
15
-
- Soft heuristic failures (`bad_feedback`, `bad_decision`) are intentionally excluded from automatic migration cleanup to protect durable declarative memories such as branding rules, API facts, release rules, and architecture decisions.
- Changed quality cleanup migration to be conservative: it supersedes only high-confidence garbage patterns, including progress snapshots, raw errors, commit/CI snapshots, temporary status notes, active file snapshots, code/API signatures, path-heavy entries, and empty entries.
23
+
- Soft heuristic failures (`bad_feedback`, `bad_decision`) are intentionally excluded from automatic migration cleanup to protect durable declarative memories such as branding rules, API facts, release rules, user workflow preferences, and architecture decisions.
Copy file name to clipboardExpand all lines: RELEASE_NOTES.md
+49-17Lines changed: 49 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,37 +4,69 @@
4
4
5
5
### Memory Quality Cleanup
6
6
7
-
This minor release automatically improves memory quality for all existing users on upgrade. Low-quality compaction memories are identified and superseded without requiring manual cleanup.
7
+
This release improves automatic workspace memory quality without risking broad cleanup of useful existing memories.
8
+
9
+
The quality gate is now shared across compaction extraction and migration checks, the compaction prompt is stricter about what should become durable memory, and the one-time migration is intentionally conservative.
8
10
9
11
### What Changed
10
12
11
-
-**Unified quality gate**: All memory types (feedback, decision, project, reference) now share the same quality rules instead of only project entries having a quality check.
12
-
-**Hardened compaction prompt**: The model is explicitly instructed that most compactions should produce zero memories, with clear good/bad examples.
13
-
-**Auto-supersede migration**: On first load after upgrade, existing low-quality `compaction` memories are automatically marked as `superseded` with quality tags. Explicit and manual memories are never affected.
13
+
-**Unified quality rules**: memory quality checks now live in one shared module and apply consistently across feedback, decisions, project facts, and references.
14
+
-**Stricter compaction output**: the compaction prompt now tells the model to save fewer memories and prefer durable facts, user preferences, architecture decisions, and hard-to-rediscover references.
15
+
-**Conservative migration cleanup**: the `2026-04-28-quality-cleanup` migration only supersedes high-confidence garbage patterns, not every rejected memory.
16
+
-**Audit logs**: automatic migration cleanup writes local JSONL audit records so superseded entries can be inspected and restored.
17
+
-**Extraction rejection logs**: newly rejected compaction candidates are logged locally to help calibrate future quality rules.
18
+
-**Regression coverage**: migration behavior is tested against sanitized real-workspace patterns to prevent mass false positives from coming back.
14
19
15
20
### What Gets Cleaned Up
16
21
17
-
Low-quality memory patterns that are now rejected/superseded:
22
+
The migration may supersede existing `source: "compaction"` memories only when they match hard garbage patterns:
If a useful memory is superseded, inspect the migration audit log and restore the entry by changing its status back to `"active"` in the workspace's `workspace-memory.json`.
33
65
34
66
### Upgrade Notes
35
67
36
68
- No configuration changes required.
37
-
- Existing workspace memory files are automatically cleaned on first load.
0 commit comments