memleaf 1.0.2__tar.gz → 1.0.3__tar.gz

{memleaf-1.0.2 → memleaf-1.0.3}/CHANGELOG.md

@@ -5,6 +5,34 @@ All notable changes to memleaf are documented here.
 ## Unreleased
 
 
+## 1.0.3 — 2026-10-10
+
+### Conversation-based result maintenance
+
+- Treat clearly reported assistant discoveries and executed results as
+  conversation evidence, without independently judging external business truth
+  or turning suggestions into user obligations.
+- Match the specific item rather than just its contact/customer; distinguish
+  replying, registering and assigning from completing the underlying work.
+  Maintain superseded current-state prose while preserving independent facts.
+- Let the existing semantic review remove a deadline misclassified as a state
+  effective time, only after the original source selection is validated.
+  Malformed, fabricated, unbound and historical citations remain protected.
+  Explicit future state changes retain their existing validation.
+- Guide Hermes deferred-tool discovery through its existing `tool_call` bridge;
+  an unavailable tool is not evidence that memory search found no matches.
+- Validation: 161 targeted deterministic checks passed, including nine new
+  boundary checks. An original saved proposal replay verified the time repair
+  with a fixed review verdict and no network. Six invented-dialogue scenarios
+  passed with the configured DeepSeek Flash route; validation used 14 calls and
+  27,999 observed tokens, including initial incomplete candidate selection and
+  one rejected review corrected before acceptance. No product model call or
+  retry was added, and existing call limits remain unchanged.
+- Original private-dialogue real-model replay requires destination approval and
+  was not performed. Production memories and host installation were not altered.
+  Historical date/responsibility assertions fail identically on the baseline
+  and are outside this patch; full historical-suite success is not claimed.
+
 ## 1.0.2 — 2026-10-08
 
 ### Reliable host recovery and Codex todo retrieval

{memleaf-1.0.2/src/memleaf.egg-info → memleaf-1.0.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: memleaf
-Version: 1.0.2
+Version: 1.0.3
 Summary: A local-first Markdown memory core for AI agents
 Author: memleaf contributors
 License-Expression: MIT
@@ -24,7 +24,7 @@ Dynamic: license-file
 
 [English](README.en.md) · [PyPI](https://pypi.org/project/memleaf/) · [GitHub](https://github.com/miffyblueboo/memleaf)
 
-> **稳定版：1.0.2。** 支持 Hermes 和 Codex；版本与兼容范围见[稳定性约定](docs/stability.md)。
+> **稳定版：1.0.3。** 支持 Hermes 和 Codex；版本与兼容范围见[稳定性约定](docs/stability.md)。
 > **Codex 可通过 `--profile host` 使用当前宿主模型完成记忆闭环，无需另配 Memleaf 模型 API Key。** 本地 Owner 仍需配置客户端身份、读写权限及来源信任；客户端主动调用工具，不代表每轮自动记忆。
 > host profile 支持独立于内容类型的 `actionable` 和结构化 `waiting_on`，每份 work 默认最多三次被接受的 submit；Memleaf 负责确定性校验、落盘与恢复。
 > 默认 `model` profile 和 Hermes 原生接入继续使用独立 Model Route，提炼与语义复核共用每份工作的最多五次模型请求。旧接口、现有记忆和默认入口保留，升级无需正式 Vault 迁移。Antigravity（反重力）当前不支持。

{memleaf-1.0.2 → memleaf-1.0.3}/README.en.md

@@ -4,7 +4,7 @@
 
 [中文](README.md) · [PyPI](https://pypi.org/project/memleaf/) · [GitHub](https://github.com/miffyblueboo/memleaf)
 
-> **Stable release: 1.0.2.** Hermes and Codex are supported; see the [stability policy](docs/stability.md) for compatibility scope.
+> **Stable release: 1.0.3.** Hermes and Codex are supported; see the [stability policy](docs/stability.md) for compatibility scope.
 > **Codex can complete the memory workflow with its current host model through `--profile host`, without a separate Memleaf model API key.** A local Owner still configures client identity, permissions and source trust. Clients invoke the tools deliberately; this does not enable automatic memory on every turn.
 > The host profile supports `actionable` independently of content type and structured `waiting_on`, with at most three accepted submits per work by default. Memleaf validates, persists and recovers deterministically.
 > The default `model` profile and native Hermes integration retain their independent Model Route and shared five-request extraction/review budget. Existing interfaces, memories and default entry points remain; no formal Vault migration is required. Antigravity is not supported.

{memleaf-1.0.2 → memleaf-1.0.3}/README.md

@@ -4,7 +4,7 @@
 
 [English](README.en.md) · [PyPI](https://pypi.org/project/memleaf/) · [GitHub](https://github.com/miffyblueboo/memleaf)
 
-> **稳定版：1.0.2。** 支持 Hermes 和 Codex；版本与兼容范围见[稳定性约定](docs/stability.md)。
+> **稳定版：1.0.3。** 支持 Hermes 和 Codex；版本与兼容范围见[稳定性约定](docs/stability.md)。
 > **Codex 可通过 `--profile host` 使用当前宿主模型完成记忆闭环，无需另配 Memleaf 模型 API Key。** 本地 Owner 仍需配置客户端身份、读写权限及来源信任；客户端主动调用工具，不代表每轮自动记忆。
 > host profile 支持独立于内容类型的 `actionable` 和结构化 `waiting_on`，每份 work 默认最多三次被接受的 submit；Memleaf 负责确定性校验、落盘与恢复。
 > 默认 `model` profile 和 Hermes 原生接入继续使用独立 Model Route，提炼与语义复核共用每份工作的最多五次模型请求。旧接口、现有记忆和默认入口保留，升级无需正式 Vault 迁移。Antigravity（反重力）当前不支持。

{memleaf-1.0.2 → memleaf-1.0.3}/docs/stability.md

@@ -30,15 +30,21 @@ scope. An internal protocol change may fence pending model responses and require
 an explicit recovery action; it must not silently reinterpret saved work, erase
 unresolved outcomes or reset consumed request budgets.
 
-## Upgrade to 1.0.2
+## Upgrade to 1.0.3
 
-The 1.0.2 release preserves the 1.0.0 public interfaces, existing Model Routes,
+The 1.0.3 release preserves the 1.0.0 public interfaces, existing Model Routes,
 default entry points and Markdown/history formats. The new host-model MCP route
 is optional and selected with `--profile host`; upgrading does not convert an
 existing Codex or Hermes connection to it. No formal Vault migration is required.
 The host contract identifier remains `memleaf-host-v2.0-rc1`; protocol identity
 and package release numbers are separate.
 
+Version 1.0.3 maintains clearly reported assistant results as conversation
+sources, improves item matching and separates deadlines from actual state
+effective times. It preserves source/permission checks and existing model-call
+limits. Updating the installed Hermes provider requires rerunning its installer;
+a package upgrade alone does not replace host plugin files.
+
 Version 1.0.2 fixes incomplete host freezing/recovery, multiline evidence
 serialization and Codex todo retrieval Hooks. Complete older frozen groups
 remain recoverable; incomplete groups and impossible saved receipts fail closed
@@ -110,3 +116,11 @@ For 1.0.2, 24 new deterministic regressions and all 152 existing host checks
 passed, including isolated installed-package and real stdio/Hook subprocess
 checks. No new real Codex/Hermes model session or production-Vault migration was
 performed for this patch; those scopes remain distinct from native package CI.
+
+For 1.0.3, 161 targeted deterministic checks passed. Six invented-dialogue
+scenarios passed through the configured DeepSeek Flash route, with 14 total
+validation requests and 27,999 observed tokens. The original saved-proposal
+replay used a fixed review verdict without network; it is not original-dialogue
+real-model acceptance. Original private-dialogue transmission remains subject
+to destination approval. Production-Vault and fresh native Hermes acceptance
+were not performed for this patch.

{memleaf-1.0.2 → memleaf-1.0.3}/pyproject.toml

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

{memleaf-1.0.2 → memleaf-1.0.3}/src/memleaf/__init__.py

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

{memleaf-1.0.2 → memleaf-1.0.3}/src/memleaf/body_preservation.py

@@ -78,14 +78,23 @@ def covered(row, original, coverage=None):
                 return False
         elif set(proof) == {"target", "old", "source"}:
             selection = proof["source"]
-            if not isinstance(selection, dict) or set(selection) != {"ref", "text"}:
+            if not isinstance(selection, dict) or set(selection) not in ({"ref", "text"}, {"ref", "text", "kind"}):
                 return False
             if not isinstance(selection["ref"], str):
                 return False
             event = evidence.get(selection.get("ref"))
             quote = selection.get("text")
-            # An assistant suggestion cannot authorize discarding user facts.
-            if (event is None or event.get("use") != "new" or event.get("role") != "user"
+            reported = selection.get("kind") == "reported_result"
+            # Only the existing semantic reviewer may classify an exact cited
+            # assistant result as a superseding observation. This does not
+            # authorize retraction, nor turn a suggestion into a user request.
+            role_allowed = event is not None and (
+                event.get("role") == "user" and "kind" not in selection
+                or event.get("role") == "assistant" and reported
+                and row["patch"].get("validity") != "retracted"
+                and any(e.get("role") == "user" and e.get("use") == "new"
+                        and e.get("ref") in row.get("evidence", []) for e in evidence.values()))
+            if (event is None or event.get("use") != "new" or not role_allowed
                     or event["ref"] not in row.get("evidence", [])
                     or not isinstance(quote, str) or not quote.strip() or quote not in event.get("text", "")):
                 return False

{memleaf-1.0.2 → memleaf-1.0.3}/src/memleaf/hermes_provider/_shared.py

@@ -313,6 +313,9 @@ def _scope_context(
         "this map. Use list_todos instead of relevance search for global current-todo questions. "
         "Search/list_todos return directories; read only the selected memory when needed for ordinary "
         "relevance queries; for global todo queries, read every matching todo item. A no-match result is valid.\n"
+        "Discover deferred memleaf tools with tool_search, then invoke the exact returned name through "
+        "tool_call: {\"calls\":[{\"name\":\"mcp__memleaf__search\",\"arguments\":{\"query\":\"business subject\"}}]}. "
+        "Put the turn token inside arguments when required below; never treat an unavailable tool as no-match.\n"
     )
     if host_bound:
         prefix += ("Hermes binds retrieval and retention identity at tool dispatch. "

{memleaf-1.0.2 → memleaf-1.0.3}/src/memleaf/hermes_provider/plugin.yaml

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

{memleaf-1.0.2 → memleaf-1.0.3}/src/memleaf/incremental_prompts.py

@@ -5,11 +5,12 @@ INCREMENTAL_SYSTEM = """从完整可见对话提炼长期记忆，返回严格 J
 先判断每个候选是否应该存在，再选操作与字段：
 - 用户明确撤回旧事实或偏好：UPDATE 原 target，patch.validity=retracted；撤回说明转入历史，不作为仍有效的偏好保留。用户明确给出替代事实/新偏好：UPDATE 原 target 为新的有效内容。撤回后“需要时另说”不代表已建立替代偏好。
 - user 的已确认事实、决定、持续目标、责任、期限、进展、偏好可保留。临时操作请求及普通应答不自动产生长期待办。
-- assistant 仅能解释已确认事实、报告有依据的已执行结果。assistant 的建议、计划、推测、额外安排不产生用户/第三人义务、承诺、偏好或期限；用户确认一件事不等于确认回复的其他建议。不要把“建议以后做”改写成“需要做”。
-- 逐分句核验正文：assistant 增加的原因、影响、条件或后续步骤，user 未确认则省略；其余已确认事实保留。
+- assistant 明确报告的查询发现、已执行结果和状态可作为对话事实，必须引用该 assistant 原文，不能归到 user 来源；不要求 user 再确认，也不自行查证外部业务真实性。assistant 的建议、计划、推测、额外安排不产生用户/第三人义务、承诺、偏好或期限；用户确认一件事不等于确认回复的其他建议。不要把“建议以后做”改写成“需要做”。
+- 逐分句核验正文：保留对话明确报告的事实，保持不确定性；assistant 的建议、推测和未执行步骤不能变成既成结果或用户决定。新增结果覆盖同一事项的旧状态，旧内容已过时则替换，不把新旧矛盾并列为当前事实。
 - use=new 是本轮变化依据；context、旧目标、explicit_writes 仅供比较，不能独立产生新事实。逐项核对证据是否支持拟写事实、归属、执行人和日期。
 
 比较 new 与目标 observed 的先后；已被较新 context/目标覆盖的变化不重放，无变化 NO_CHANGE，不借 context 清空 deadline。按身份/编号、主体、目标和业务上下文比较全部候选，包含已完成项和跨会话来源。补编号、纠正状态、补有依据的结构字段均 UPDATE 原目标；完整覆盖才 NO_CHANGE。独立新事项 CREATE；同一变化同步维护全部相关候选，旧职责不可遗漏。项目与独立任务各保留生命周期；确为同一事项的重复记录才 MERGE，不凭标题相似合并。保留其余有效旧事实，正文表达当前状态，不追加日志。
+更新前核对具体事项：同一个人或客户不代表同一封邮件、请求或工作。用户使用“那个/其他/都”等指代时，结合本轮完整回复确定范围；范围仍不明确则 DEFERRED，不能挑同名旧目标更新。回复邮件、登记问题、分配任务等操作完成，不等于邮件涉及的修复或被分配任务已经完成；各自只更新自己的生命周期。用户明确批量完成的范围应维护全部对应候选，不能仅因某一条无变化就忽略其余。
 
 动作：
 CREATE：action、非空 evidence、memory；memory 必填 type/scope/title/body。
@@ -33,7 +34,7 @@ scope 采用输入引用；通用为 global，归属未知为 unscoped；只有
 patch 只含 title/body/scope/status/actionable/assignee/deadline/validity；type 沿用目标。
 新增/变更非空 assignee 必须提供 responsibility_basis:{"assignee":{"ref":"e1","text":"确立执行人的原文"}}；放行级或对应 memory/patch 内均可，不能冲突。ref 必须在 evidence，text 是实际原文；新增用户执行责任必须引用 user 原文，assistant 不能赋予用户新义务。原文必须确立这个实际行动的责任，引用另一件事的请求不算。沿用无需重复引用；冗余引用仍须有效，但不刷新旧依据。
 
-日期：有明确期限时放 memory.deadline 或 patch.deadline:{"ref":"e1","text":"期限原文"}，不能只留正文。没有期限变更时省略 deadline。负责人交接、等待验收、尚未完成不能取消旧期限。取消期限用 {"ref":"e1","clear":true,"text":"取消期限原文"}；new 未取消时保留原期限。source_time 只用于解释相对日，不补造发生日；每个相对日按其自己的消息时间解析。无来源时间保持未知，不借处理时间。正文日期与期限、材料日期、发生日期区分；无日期也能记完成事实。CREATE/UPDATE 可给 effective:{"ref":"e1","text":"生效时间原文"}。
+日期：有明确期限时放 memory.deadline 或 patch.deadline:{"ref":"e1","text":"期限原文"}，不能只留正文。没有期限变更时省略 deadline。负责人交接、等待验收、尚未完成不能取消旧期限。取消期限用 {"ref":"e1","clear":true,"text":"取消期限原文"}；new 未取消时保留原期限。source_time 只用于解释相对日，不补造发生日；每个相对日按其自己的消息时间解析。无来源时间保持未知，不借处理时间。正文日期与期限、材料日期、发生日期区分；无日期也能记完成事实。effective 仅在原文明确该状态的实际生效/发生时间时提供 {"ref":"e1","text":"该时间的最小原文"}，否则省略；不能把任务截止日期或包含截止日期的整个请求作为操作完成的 effective。
 
 撤回沿用原 target，UPDATE.patch.validity=retracted，body 可空；说明可写 body，系统转存审计说明并清空有效正文。恢复用 validity=valid，需要较新明确依据和当前 body。
 request_kind=explicit_remember：所选 new 有保留授权，仍按用户实际要求选择内容并整理去重，不得 NO_MEMORY；独立不被要求保留的内容不强行建项。

{memleaf-1.0.2 → memleaf-1.0.3}/src/memleaf/incremental_semantics.py

@@ -16,8 +16,10 @@ REVIEW_SYSTEM = """核验拟写入的记忆及持续行动。original_input 是
 存在 body_omissions 时，keep:true 的 UPDATE/MERGE 必须逐项说明省略的去向；仅 body:true 不足以通过。body_omissions 按 item 列出拟议正文中不再原样出现的旧片段（比较辅助，不表示已经失效）。逐项核对完整含义，不能因主题相同、进展重复或用户未再次提及就删除。需要补回或修正文句时，直接在 decision 增加 body（修正后的完整正文字符串），field_support.body=true；不必复制 action、target、evidence，也不要把该 target 放入 updates。Core 沿用该候选的身份、证据和其他字段；已有 replace 方式仍可用，但不能同时使用 body 和 replace。对最终 UPDATE/MERGE（包括 body、replace 和 updates 修正）的剩余省略片段，在对应 decision/updates 项增加 body_coverage 数组：每项 {"target":"旧目标ref","old":"旧片段原文","body":"最终正文中完整承接该片段含义的逐字引文"}，或 {"target":"旧目标ref","old":"旧片段原文","source":{"ref":"new用户证据ref","text":"明确纠正/撤回该内容的逐字引文"}}。body 引文必须完整等价且真实存在于最终正文；不能只引用旧目标中的文字却忘了将它写入修正正文。source 不能引用旧上下文或助手建议。修正后原样保留的片段无需列入。MERGE 对所有被合并目标逐项核对，撤回整个目标也需明确用户依据。无法确认则 keep:false；不要猜测或提供主题相符但实际无关的引文。没有剩余省略时省略 body_coverage。
 每个 draft.items 都必须有且只有一个 decision，item 是从 0 开始的位置。keep 判断该事项本身是否由原文确立且持续值得保留。临时操作及助手额外建议不能产生用户长期待办，原话只证明另一个操作时 keep:false。独立事实不因其他候选有误而拒绝。
 keep:true 时，field_support 必须逐个列出候选 memory/patch 中的业务字段，每个布尔值判断该字段的拟议值是否受来源支持；不列 responsibility_basis、effective、at、reopen 等引用/控制字段。没有 replace 的 NO_CHANGE/DEFERRED/NO_MEMORY 的 field_support 为 {}。keep:false 时 field_support 为 {}。unverified_fields 是系统发现未能验证引用的可选责任字段，必须判为 false；不能补造引用。这不影响其他有依据的事实或任务。归属/客户尚未确定不自动表示行动被阻塞。
-不能仅检查引文存在：必须判断原话是否确立该具体行动、责任、状态和期限。assistant 的建议/计划不能赋予 user 新义务。转发、协调、记录不等于本人执行；支持旧任务不等于接受新安排。
-body 必须逐个事实分句核验；assistant 自行增加的原因、影响判断、条件或后续步骤不受 user 原话支持，不能因整段主题相符就判 true。剔除无依据分句，保留其余已确认事实，可用 replace 修正 CREATE 的 title/body；没有修正时 body:false。title 只标识事项，交期/发生日/进度放正文与结构字段；名称固有的年度等身份信息保留。UPDATE/NO_CHANGE 的旧标题仍含交期时，在现有 replace/updates 中一起维护。
+不能仅检查引文存在：必须判断原话是否确立该具体行动、责任、状态和期限。同名联系人/客户不证明是同一事项；核对具体对象、邮件主题、编号和请求范围，不能将回复/登记/分配完成扩大成另一项修复完成。批量完成应核对所有对应候选；对象范围不明确就保留未知。assistant 的建议/计划不能赋予 user 新义务。转发、协调、记录不等于本人执行；支持旧任务不等于接受新安排。
+body 必须逐个事实分句核验；assistant 明确报告的查询发现、已执行结果和状态是可用的对话来源，应引用该 assistant，不能伪装成 user 提供；不要求 user 再确认，不核验外部业务真假。建议、推测、原因分析或未执行后续步骤不能变成既成事实、用户决定或新义务。保留不确定性，剔除无依据分句，可用 replace 修正 CREATE 的 title/body；没有修正时 body:false。title 只标识事项，交期/发生日/进度放正文与结构字段；名称固有的年度等身份信息保留。UPDATE/NO_CHANGE 的旧标题仍含交期时，在现有 replace/updates 中一起维护。
+旧正文的事实状态被本轮 assistant 明确报告的新结果覆盖时，可用 body_coverage.source:{"ref":"new助手证据ref","text":"明确报告结果的逐字引文","kind":"reported_result"}，且该行 evidence 必须同时引用本轮 user 与 assistant。只用于替换同一事项的过时正文，不授权整条撤回、删除用户要求或采纳助手建议。不能为通过审查保留互相矛盾的新旧当前状态；无关旧事实仍须完整保留。
+仅当原候选行含 effective 控制字段时，才可在对应 decision 输出 effective_support（布尔值）；候选仅有 deadline 或正文日期时禁止输出该键。逐项核对 effective 是否表示实际状态生效时间。截止日、目标完成日或含日期的整个操作请求不证明实际生效时间，可用 effective_support:false 仅移除误分类的 effective；明确生效时间用 true 保留，不能为放行未来状态而丢弃。不能增加候选原本没有的 effective。
 尤其检查拟改 deadline：依赖条件、交接执行人、进度、尚未完成都不证明原期限已取消；只有明确取消/替换这个期限才支持变更。没有明确期限变化时 deadline:false，原期限沿用。卡点和等待条件仅在正文中维护，并清除已经解决的旧卡点。
 新引用只能来自 new；context 和旧目标只供比较，不能重新推动旧变化。候选若仅重新陈述旧目标已覆盖的内容，不应作为新 UPDATE。同一事项补充/纠正维护原目标，独立事项允许 CREATE，不能凭标题相似合并。
 逐字段判断后输出 decisions；对共同事实变更，检查所有候选记忆中是否仍有旧职责或旧状态，不能认可只更新一条而遗留冲突。确认 MERGE 各方确为同一事项且完整保留有效内容；独立生命周期的项目/任务不可合并。
@@ -176,7 +178,7 @@ def apply_review(request, response):
                 rejected.append(deepcopy(row))
         for decision in decisions:
             if (not isinstance(decision, dict) or not {"item", "keep", "field_support"} <= set(decision)
-                    or set(decision) - {"item", "keep", "field_support", "replace", "body", "body_coverage"}):
+                    or set(decision) - {"item", "keep", "field_support", "replace", "body", "body_coverage", "effective_support"}):
                 raise ValueError
             i = decision["item"]
             if type(i) is not int or not 0 <= i < len(rows) or i in positions or type(decision["keep"]) is not bool:
@@ -232,6 +234,23 @@ def apply_review(request, response):
             for name in data.get("unverified_fields", [[] for _ in rows])[i]:
                 if name in support:
                     support[name] = False
+            if "effective_support" in decision:
+                if (type(decision["effective_support"]) is not bool or "effective" not in row
+                        or row.get("action") not in {"CREATE", "UPDATE"} or not decision["keep"]):
+                    raise ValueError
+                if decision["effective_support"] is False:
+                    # Repair classification only after validating the original
+                    # source selection. Otherwise removing it would conceal a
+                    # malformed or fabricated citation from the row compiler.
+                    from .incremental_protocol import _selected
+                    evidence = {e["ref"]: e for e in data["original_input"]["evidence"]}
+                    try:
+                        _selected(row["effective"], evidence, row.get("evidence", []))
+                        fresh = evidence[row["effective"]["ref"]]["use"] == "new"
+                    except (ValueError, TypeError, KeyError):
+                        fresh = False
+                    if fresh:
+                        row.pop("effective")
             if isinstance(row, dict) and row.get("action") in {"NO_CHANGE", "NO_MEMORY", "DEFERRED"}:
                 continue  # Review cannot erase an unresolved control disposition.
             if not decision["keep"] or any(not support.get(k, True) for k in _REQUIRED.get(row["action"].upper(), set())):

{memleaf-1.0.2 → memleaf-1.0.3/src/memleaf.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: memleaf
-Version: 1.0.2
+Version: 1.0.3
 Summary: A local-first Markdown memory core for AI agents
 Author: memleaf contributors
 License-Expression: MIT
@@ -24,7 +24,7 @@ Dynamic: license-file
 
 [English](README.en.md) · [PyPI](https://pypi.org/project/memleaf/) · [GitHub](https://github.com/miffyblueboo/memleaf)
 
-> **稳定版：1.0.2。** 支持 Hermes 和 Codex；版本与兼容范围见[稳定性约定](docs/stability.md)。
+> **稳定版：1.0.3。** 支持 Hermes 和 Codex；版本与兼容范围见[稳定性约定](docs/stability.md)。
 > **Codex 可通过 `--profile host` 使用当前宿主模型完成记忆闭环，无需另配 Memleaf 模型 API Key。** 本地 Owner 仍需配置客户端身份、读写权限及来源信任；客户端主动调用工具，不代表每轮自动记忆。
 > host profile 支持独立于内容类型的 `actionable` 和结构化 `waiting_on`，每份 work 默认最多三次被接受的 submit；Memleaf 负责确定性校验、落盘与恢复。
 > 默认 `model` profile 和 Hermes 原生接入继续使用独立 Model Route，提炼与语义复核共用每份工作的最多五次模型请求。旧接口、现有记忆和默认入口保留，升级无需正式 Vault 迁移。Antigravity（反重力）当前不支持。