memleaf 0.2.12__tar.gz → 0.2.14__tar.gz

{memleaf-0.2.12 → memleaf-0.2.14}/CHANGELOG.md

@@ -2,6 +2,28 @@
 
 All notable changes to memleaf are documented here.
 
+## 0.2.14 — 2026-09-02
+
+- Reject a permanent-memory candidate that combines a durable project rule or
+  implementation-plan change with an independent dated todo, while preserving
+  multiple dated milestones that belong to one project plan.
+- Normalize explicit implementation plans and plan adjustments to `project`
+  without promoting adjacent mail, attachment, meeting, or archive records.
+- Keep the gate-selected type immutable through summarization for both CREATE
+  and UPDATE, preserve multiple legal update candidates, and expose the new
+  `mixed_future_use` diagnostic through the Hermes provider.
+
+## 0.2.13 — 2026-09-02
+
+- Preserve the full active project-plan body, stable title, and retrieval
+  metadata when a customer suggestion only adds constraints; explicit
+  replacements continue to replace conflicting state normally.
+- Reject attachment, document, presentation, material, and issue-list items
+  described only by transport metadata or a generic follow-up at both the gate
+  and summary boundaries.
+- Keep concrete attachment-backed actions eligible when they include a
+  remediation, owner, deadline, delivery rule, deployment, or migration.
+
 ## 0.2.12 — 2026-09-02
 
 - Remove empty ASCII or Chinese parentheses left after an absolute date is

{memleaf-0.2.12/src/memleaf.egg-info → memleaf-0.2.14}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: memleaf
-Version: 0.2.12
+Version: 0.2.14
 Summary: A local-first Markdown memory core for AI agents
 Author: memleaf contributors
 License-Expression: MIT
@@ -23,8 +23,8 @@ Dynamic: license-file
 
 [English](README.en.md) · [PyPI](https://pypi.org/project/memleaf/) · [GitHub](https://github.com/miffyblueboo/memleaf)
 
-> **当前版本：0.2.12。**
-> 核心库、Vault、stdio MCP Server、初始化 CLI、模型路由、提炼流程、受控检索协议和宿主适配器已经实现。memleaf 0.2.12 通过 PyPI 分发。
+> **当前版本：0.2.14。**
+> 核心库、Vault、stdio MCP Server、初始化 CLI、模型路由、提炼流程、受控检索协议和宿主适配器已经实现。memleaf 0.2.14 通过 PyPI 分发。
 > **当前版本支持 Hermes 和 Codex。** Antigravity（反重力）不检测、不安装、不配置。
 
 ## 项目定位

{memleaf-0.2.12 → memleaf-0.2.14}/README.en.md

@@ -4,8 +4,8 @@
 
 [中文](README.md) · [PyPI](https://pypi.org/project/memleaf/) · [GitHub](https://github.com/miffyblueboo/memleaf)
 
-> **Version: 0.2.12.**
-> The core library, Vault, stdio MCP server, initialization CLI, model routing, memory extraction, controlled retrieval protocol, and host adapters are implemented. memleaf 0.2.12 is distributed through PyPI.
+> **Version: 0.2.14.**
+> The core library, Vault, stdio MCP server, initialization CLI, model routing, memory extraction, controlled retrieval protocol, and host adapters are implemented. memleaf 0.2.14 is distributed through PyPI.
 > **The current release supports Hermes and Codex.** Antigravity is not detected, installed, or configured.
 
 ## Project scope

{memleaf-0.2.12 → memleaf-0.2.14}/README.md

@@ -4,8 +4,8 @@
 
 [English](README.en.md) · [PyPI](https://pypi.org/project/memleaf/) · [GitHub](https://github.com/miffyblueboo/memleaf)
 
-> **当前版本：0.2.12。**
-> 核心库、Vault、stdio MCP Server、初始化 CLI、模型路由、提炼流程、受控检索协议和宿主适配器已经实现。memleaf 0.2.12 通过 PyPI 分发。
+> **当前版本：0.2.14。**
+> 核心库、Vault、stdio MCP Server、初始化 CLI、模型路由、提炼流程、受控检索协议和宿主适配器已经实现。memleaf 0.2.14 通过 PyPI 分发。
 > **当前版本支持 Hermes 和 Codex。** Antigravity（反重力）不检测、不安装、不配置。
 
 ## 项目定位

{memleaf-0.2.12 → memleaf-0.2.14}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "memleaf"
-version = "0.2.12"
+version = "0.2.14"
 description = "A local-first Markdown memory core for AI agents"
 readme = "README.md"
 requires-python = ">=3.11"

{memleaf-0.2.12 → memleaf-0.2.14}/src/memleaf/__init__.py

@@ -1,6 +1,6 @@
 """Local-first Markdown memory core for AI agents."""
 
-__version__ = "0.2.12"
+__version__ = "0.2.14"
 
 from .config import DEFAULT_CONFIG, default_config, load_config, save_config
 from .frontmatter import FrontmatterError, dump_frontmatter, dump_yaml, load_yaml, parse_frontmatter

{memleaf-0.2.12 → memleaf-0.2.14}/src/memleaf/hermes_provider/__init__.py

@@ -94,6 +94,7 @@ _MODEL_VALIDATION_DETAILS = frozenset(
         "source_shape",
         "todo_fields",
         "relative_time",
+        "mixed_future_use",
         "other_schema_violation",
     }
 )

{memleaf-0.2.12 → memleaf-0.2.14}/src/memleaf/hermes_provider/plugin.yaml

@@ -1,5 +1,5 @@
 name: memleaf
-version: 0.2.12
+version: 0.2.14
 description: "Hermes-native external MemoryProvider for local-first Markdown memory shared with the memleaf MCP server."
 hooks:
   - prefetch

{memleaf-0.2.12 → memleaf-0.2.14}/src/memleaf/processing.py

@@ -34,6 +34,7 @@ from .prompts import (
     DUPLICATE_TARGET_CORRECTION,
     GATE_TYPE_CORRECTION,
     JSON_CORRECTION,
+    MIXED_FUTURE_USE_CORRECTION,
     MIXED_PROJECT_SCOPES_CORRECTION,
     RELATIVE_TIME_CORRECTION,
     GATE_SYSTEM,
@@ -65,6 +66,8 @@ from .validation import (
     parse_summarize_output,
     normalize_relative_calendar_text,
     is_aggregate_operational_text,
+    is_attachment_followup_only_text,
+    is_project_plan_text,
 )
 from .vault import safe_component
 
@@ -598,6 +601,8 @@ class Processor:
             return DUPLICATE_TARGET_CORRECTION
         if hint == "mixed_project_scopes":
             return MIXED_PROJECT_SCOPES_CORRECTION
+        if hint == "mixed_future_use":
+            return MIXED_FUTURE_USE_CORRECTION
         if stage == "gate" and hint == "update_target_type_mismatch":
             return UPDATE_TARGET_TYPE_CORRECTION
         if stage == "gate" and hint == "invalid_type":
@@ -1695,22 +1700,64 @@ class Processor:
 
     @staticmethod
     def _is_project_plan_title(value: Any) -> bool:
-        text = normalize_term(value) if isinstance(value, str) else ""
-        return any(
-            marker in text
-            for marker in ("实施计划", "项目计划", "implementation plan", "project plan")
-        )
+        return is_project_plan_text(value)
 
     @staticmethod
     def _is_adjacent_plan_record(value: Any) -> bool:
         text = normalize_term(value) if isinstance(value, str) else ""
-        return any(
+        return bool(text) and any(
             marker in text
             for marker in (
                 "已发送", "发送", "邮件", "附件", "存档", "会议", "启动会", "纪要",
                 "sent", "email", "mail", "attachment", "archive", "meeting", "minutes",
             )
+        ) and not is_project_plan_text(value)
+
+    @classmethod
+    def _merge_additive_project_plan_update(
+        cls,
+        candidate: Mapping[str, Any],
+        summary: Mapping[str, Any],
+        target: Memory | None,
+    ) -> dict[str, Any]:
+        """Preserve a full active plan when current evidence only adds constraints."""
+
+        result = dict(summary)
+        if (
+            target is None
+            or target.type != "project"
+            or not cls._is_project_plan_title(target.title)
+        ):
+            return result
+        candidate_text = str(candidate.get("memory", "")).casefold()
+        additive_markers = (
+            "建议", "补充", "增加", "新增", "追加", "还需", "同时", "纳入", "完善",
+            "suggest", "propose", "additional", "add ", "include",
+        )
+        replacement_markers = (
+            "改为", "变更为", "替换", "取消", "删除", "不再", "更新为", "调整为", "推迟至", "提前至",
+            "replace", "changed to", "no longer", "cancel", "remove", "instead", "moved to",
         )
+        if not any(marker in candidate_text for marker in additive_markers):
+            return result
+        if any(marker in candidate_text for marker in replacement_markers):
+            return result
+
+        old_body = target.body.strip()
+        new_body = str(result.get("body", "")).strip()
+        normalized_old = " ".join(old_body.casefold().split())
+        normalized_new = " ".join(new_body.casefold().split())
+        if old_body and normalized_old not in normalized_new:
+            result["body"] = f"{old_body}\n\n{new_body}" if new_body else old_body
+        result["title"] = target.title
+        for field in ("tags", "aliases", "keywords"):
+            merged: list[str] = []
+            for value in list(getattr(target, field)) + list(result.get(field, [])):
+                if isinstance(value, str) and value not in merged:
+                    merged.append(value)
+            if merged or field in result:
+                result[field] = merged
+        return result
 
     def _infer_update_target(
         self,
@@ -2140,6 +2187,8 @@ class Processor:
             # its own candidate; the aggregate shell itself is NO_CHANGE.
             if candidate.get("worth") and is_aggregate_operational_text(candidate.get("memory")):
                 continue
+            if candidate.get("worth") and is_attachment_followup_only_text(candidate.get("memory")):
+                continue
             candidate_scopes = list(candidate["scopes"])
             # An automatic candidate with no reliable project attribution is
             # retained as a retryable inbox turn, never silently promoted to
@@ -2286,20 +2335,13 @@ class Processor:
                         expected_scopes=candidate["scopes"],
                         expected_scope_source=candidate["scope_source"],
                         allow_no_change=True,
-                        expected_type=(
-                            candidate.get("type")
-                            if (
-                                gate_update_target is not None
-                                and gate_target_type == candidate.get("type")
-                            )
-                            else None
-                        ),
+                        # The summarize stage may not reinterpret a gate
+                        # candidate, including CREATE candidates.  Updates
+                        # additionally retain the active target's immutable
+                        # type below.
+                        expected_type=candidate.get("type"),
                         expected_update_memory_id=gate_update_target,
-                        expected_target_type=(
-                            gate_target_type
-                            if gate_target_type == candidate.get("type")
-                            else None
-                        ),
+                        expected_target_type=gate_target_type,
                     ),
                     diagnostic_context={
                         "source": turn.source,
@@ -2322,6 +2364,10 @@ class Processor:
                 continue
             if summary.get("decision") == NO_CHANGE_DECISION:
                 continue
+            if is_attachment_followup_only_text(
+                f"{summary.get('title', '')}\n{summary.get('body', '')}"
+            ):
+                continue
             if gate_update_target is not None:
                 summary_update_target = summary.get("update_memory_id")
                 if summary_update_target is None:
@@ -2338,6 +2384,8 @@ class Processor:
                 else:
                     summary = dict(summary)
                     summary["update_memory_id"] = gate_update_target
+                target = self.service.read(gate_update_target, include_history=False)
+                summary = self._merge_additive_project_plan_update(candidate, summary, target)
             if summary["scopes"] == ["unscoped"] or summary.get("scope_source") == "insufficient_context":
                 self._defer_candidate(
                     turn_ref,

{memleaf-0.2.12 → memleaf-0.2.14}/src/memleaf/prompts.py

@@ -108,6 +108,13 @@ be independently retrieved and updated. Prefer one coherent current-state memory
 over adjacent overlapping snapshots; do not use a score or fixed category rule.
 Most ordinary turns should produce zero or one candidate; multiple require
 genuinely independent future questions or actions.
+Never combine a durable project rule or implementation-plan change with an
+independent dated todo in one candidate. For example, a project plan/rule and
+"reply or investigate by YYYY-MM-DD" are two future uses: emit separate
+candidates, preserving each candidate's own evidence and project scope. A
+date that is an intrinsic milestone of the same implementation plan may remain
+inside that one project candidate. A candidate that combines these independent
+uses is invalid and must be split before summarization.
 Never persist an aggregate mailbox sweep, daily report, or "items to watch"
 digest as one cross-project memory. Inspect each item and split genuinely
 independent project risks or actionable todo items; if an item has no
@@ -115,6 +122,10 @@ independent future use, set worth=false. A one-off meeting with no durable
 decision or commitment, a request awaiting PM acceptance, and pending feedback
 or another intermediate status normally have worth=false. Keep an independent
 project risk or concrete future action even when it came from a digest.
+A PPT, attachment, material, document, or issue-list item described only as
+"needs follow-up/review/processing" has no independent action and normally has
+worth=false; keep it only when the evidence supplies a concrete remediation,
+owner, deadline, delivery rule, migration, or durable conclusion.
 An intermediate state such as a draft awaiting confirmation, preparation/
 processing status, temporary error, repeated confirmation, or unconfirmed
 suggestion normally has no independent future use and is worth=false. Keep one
@@ -151,6 +162,16 @@ same-use project targets remain, do not guess an update target. A candidate
 that still combines a mailbox or daily digest shell with counts/statuses is not
 atomic: set worth=false for the aggregate, and emit any independent concrete
 action as a separate candidate.
+If the same confirmed change applies to multiple same-project active memories,
+emit one candidate per independently changed memory and set each exact
+update_memory_id; never select one target and silently omit the others. Do not
+target adjacent sent-mail, attachment, meeting, or archive records unless the
+current evidence changes their own future-use topic.
+An explicit implementation plan, project implementation plan, or plan
+adjustment is type project. Do not label it fact merely because it came from
+an email or because no existing project memory was retrieved. Keep an actual
+todo as todo only when its future use is the action itself, not the durable
+plan it mentions.
 Return no prose, markdown fences, comments, or trailing text."""
 
 
@@ -182,7 +203,8 @@ still has a concrete future-use fact or action. If not, return exactly
 {"decision":"NO_CHANGE"}; this is the only no-write summary response. Use it
 for temporary delegation, waiting for feedback, a one-off meeting arrangement with
 no durable outcome/decision/project constraint, or a subject/attachment-only item
-without a concrete impact or conclusion.
+without a concrete impact or conclusion. Attachment sizes, mail/message IDs,
+and a generic "needs follow-up" phrase do not create such an impact.
 Explicit remember mode never permits NO_CHANGE and must return the normal summary
 object. When producing a normal automatic summary, copy the gate candidate's
 scopes exactly. scope_source may be omitted to inherit the gate value, but an
@@ -260,6 +282,16 @@ plan target over same-topic sent-mail, attachment/archive, or meeting records;
 the target type remains immutable. Never summarize a combined mailbox/daily
 digest shell with counts or statuses; return NO_CHANGE for that aggregate,
 while a separate atomic future-use action may still be summarized.
+If the current confirmed change applies to multiple same-project active
+memories, the gate will provide separate candidates and exact update targets;
+preserve each candidate's target and do not collapse them into one summary.
+Never combine a durable project rule or implementation-plan change with an
+independent dated todo in one summary. A plan/rule and a dated reply,
+investigation, submission, or follow-up are separate future uses; such output
+is invalid and must be retried as separate gate candidates. A date that is an
+intrinsic milestone of the same project plan may remain in its project summary.
+An explicit implementation plan or plan adjustment must use type project;
+preserve an existing update target's type when it is the same project plan.
 Return no prose, markdown fences, comments, or trailing text."""
 
 
@@ -320,6 +352,18 @@ MIXED_PROJECT_SCOPES_CORRECTION = (
 )
 
 
+MIXED_FUTURE_USE_CORRECTION = (
+    "Previous output violated: mixed_future_use. Keep every candidate and "
+    "summary atomic. Split a durable project rule or implementation-plan "
+    "change from an independent dated todo such as a reply, investigation, "
+    "submission, or follow-up; preserve each part's own evidence and project "
+    "scope. A date intrinsic to the same implementation plan may remain in "
+    "that project candidate. Return separate gate candidates or return "
+    "NO_CHANGE for a part with no independent future use. Return only the "
+    "strict JSON object."
+)
+
+
 DUPLICATE_TARGET_CORRECTION = (
     "Previous output violated: duplicate_update_target. Merge every candidate "
     "that refers to the same active memory target into one candidate for one "