memleaf 0.2.49__tar.gz → 0.2.51__tar.gz

{memleaf-0.2.49 → memleaf-0.2.51}/CHANGELOG.md

@@ -2,6 +2,22 @@
 
 All notable changes to memleaf are documented here.
 
+## 0.2.51 — 2026-09-13
+
+- Publish the scope vocabulary in the B3 single-pass contract. The compact contract described `scopes` only as `nonempty string[]` and never named `project:<name>`, so a planner handed an empty `scope_registry` had exactly one value it could be sure was legal. A first message that plainly establishes a project -- "最近在弄个记账的小玩意儿，就扔家里那台 N100 上跑" -- was filed under `global`, producing the internally inconsistent `type=project` beside `scopes=["global"]`. The legacy summarize contract always carried this paragraph; B3 lost it, the same way it had lost the todo-field and date rules repaired in 0.2.48 and 0.2.50.
+- State the rule as an ownership decision rather than a permission. The first wording ("use a project scope only when the evidence establishes that project") was read as being about *topics*, and the model kept choosing `global`. The shipped wording says that a candidate concerning one distinct project the user is working on -- a `type=project` memory, or the work, decisions, state or deadlines belonging to that project -- is scoped to that project as `project:<name>`, named as the evidence names it, and that `global` is for a fact no single project owns: a standing personal preference, a machine-wide or tool-wide rule, or an environment fact. Nothing had to be built for this: new scope names are already accepted unregistered, `project:记账` is a legal key, and the commit path registers newly observed scopes on write.
+- Verification for this release used the real model and the real prompt builder. 102 tests pass with no model call, pinning the vocabulary, the directive phrasing and the `see SCOPES` reference from the compact contract. Against the live route, eight sentences were sent with an EMPTY memory library so the model had to CREATE and only the chosen scope was under test: three project-shaped sentences produced `project:记账`, `project:爬虫` and `project:NAS`, three global-shaped sentences produced `global`, a bare product mention ("我看了下 FastAPI 的文档") stayed `global` rather than claiming ownership, and someone else's project produced no memory at all. Two full passes agreed on all eight cases. Whether a longer or noisier turn keeps this discrimination is not measured, and the 23 memories already written as `global` are not re-scoped by this release.
+
+## 0.2.50 — 2026-09-13
+
+- Remove the six-item cap on the related-memory catalog. It contradicted the retrieval design outright. Retrieval injects the scope list and resolves the scope the planner selects; a Vault whose memories all carry one scope -- `global`, which is the common personal case and the only scope in an empty registry -- correctly resolves that scope to the whole library, and six rows then hid most of it. Measured on a real Vault of 18 memories, every one `global`: retrieval returned 19 rows, the cap kept 6, discarded 13, and the discarded rows marked the lookup unprovable, so every turn died with `incomplete B3 lookup cannot authorize a terminal decision`. Size, not count, is what the prompt budget is about, and the character ceiling already expresses it.
+- Derive that ceiling from the prompt budget instead of a round number, and downgrade it to a safety net. `_RELATED_MAX_CHARS` was 6000, which on the same Vault sat just below the whole library and so bound continuously; it is now 40000, chosen against `MAX_PROMPT_BYTES` (192 KiB) at the measured ~1.6 UTF-8 bytes per catalog row, which leaves well over 100 KiB for the contract, the current evidence and the native catalog and admits roughly 180 memories. It no longer expresses a working constraint, only the guarantee that the hard prompt limit cannot be reached.
+- Stop treating a trimmed body as a withheld record. A body shortened to fit the catalog budget is still projected -- its id, title, type and scopes are all present, so it can still be targeted and still rules out a duplicate CREATE -- yet it was recorded as withheld and made `lookup_complete` false. Only a record actually dropped from the projection can carry that weight now, whether by the ceiling or because it could not be projected at all. The 1600-character per-body bound is unchanged: it guards against one pathological memory consuming the whole catalog, and at the measured distribution (bodies average 146 characters, p90 194) it does not bind in normal use.
+- Defer the candidate that needs the missing proof instead of discarding the turn. Only a CREATE claims novelty, and only a complete lookup can prove it, so a CREATE under an incomplete lookup is now deferred with the protocol's own `lookup_incomplete` reason -- the vocabulary already declared it -- and recorded as `b3_candidate_deferred_count`. UPDATE and NO_CHANGE name a target that is in the supplied catalog by construction, so they remain provable and still commit. The turn-level failure that refused every terminal decision is gone.
+- Keep the extraction worker, the installer's host CLI probes and the adapter runner from opening a console window. All three ran on Windows without `CREATE_NO_WINDOW`; the worker asked for `DETACHED_PROCESS`, which does not help, because a console program still needs a console and Windows creates a visible one. Whenever the host had no console of its own -- the Hermes desktop app, for instance -- every captured turn put a stray terminal on the user's desktop. Measured on Windows 11 with Windows Terminal as the default host: `CREATE_NEW_PROCESS_GROUP | DETACHED_PROCESS` opened one new console window titled with the interpreter path, `CREATE_NO_WINDOW` opened none. The worker keeps its own process group so a Ctrl+C aimed at the parent's console does not take it down.
+
+Verification for this release used the reported production Vault. 100 tests pass with no model call, covering the item-count regression directly (an 18-memory and a 60-memory library must both stay complete), the trimmed-versus-withheld distinction, the still-fail-closed cases for a genuinely withheld local record and an unprojectable one, the incomplete-lookup deferral for CREATE, UPDATE and NO_CHANGE, the reconciler not treating a deferred member as a collision, and all three spawn sites. The real replay retried the four turns that had failed: the lookup reported `lookup_complete: true` with all 18 rows projected, two preview runs returned `execution_status: ok` with `coverage_status: complete`, the committed run processed all four previously failing turns and wrote six memories, and the Vault then reported `failed_sessions: 0`, `failed_turns: 0`, `retryable: false` with a clean audit. Compaction is still not wired to any automatic caller, so an active-memory ceiling remains absent in normal operation; that and the question of whether retrieval should select by relevance when several scopes exist are left open rather than assumed.
+
 ## 0.2.49 — 2026-09-13
 
 - Restore candidate-local deferral to the B3 single-pass path. v0.2.26 established that an invalid proposal receives bounded model correction and then explicit candidate-local deferral while "valid siblings proceed", and v0.2.34 required that "candidate-local deferral and idempotent partial retries" be preserved so unresolved ownership, target, evidence or timing never fabricates a write. The B3 planner had lost that property: the first proposal Core rejected raised out of the parser and discarded every other verdict in the turn, so one model slip cost the whole turn even when six other candidates were sound. A proposal that Core can attribute to a single candidate is now deferred with a B3 defer reason and the rest of the turn still commits. Nothing is written for a deferred candidate, no extra model call is made, and the turn stays retryable with its already-settled units intact.

{memleaf-0.2.49/src/memleaf.egg-info → memleaf-0.2.51}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: memleaf
-Version: 0.2.49
+Version: 0.2.51
 Summary: A local-first Markdown memory core for AI agents
 Author: memleaf contributors
 License-Expression: MIT
@@ -23,7 +23,7 @@ Dynamic: license-file
 
 [English](README.en.md) · [PyPI](https://pypi.org/project/memleaf/) · [GitHub](https://github.com/miffyblueboo/memleaf)
 
-> **版本：0.2.49。**
+> **版本：0.2.51。**
 > 记忆只从用户与 Agent 的可见对话提炼。Agent 已在回复中整理的事实、项目进展和明确待办可作为来源；邮件、附件、网页和终端等工具原文不进入记忆提炼。模型负责保留原话中的不确定性，现有记忆仅用于比较、去重和更新。Markdown 仍是唯一事实源。
 > **当前版本支持 Hermes 和 Codex。** Antigravity（反重力）不检测、不安装、不配置。
 

{memleaf-0.2.49 → memleaf-0.2.51}/README.en.md

@@ -4,7 +4,7 @@
 
 [中文](README.md) · [PyPI](https://pypi.org/project/memleaf/) · [GitHub](https://github.com/miffyblueboo/memleaf)
 
-> **Version: 0.2.49.**
+> **Version: 0.2.51.**
 > Automatic extraction now uses only the current turn's visible user input and final assistant reply. Raw tool output, attachments, web/file/terminal payloads and legacy tool-evidence bodies are not new source evidence; existing or retrieved memory remains comparison context rather than source authority. Background processing is persisted as a local job and can be checked through the read-only `process_status` MCP tool; failed work remains retryable and fail closed. The release also tightens source/date grounding, target reconciliation, duplicate/no-op handling and semantic review before writes. Markdown remains the sole source of truth with no SQLite runtime dependency. Acceptance covers deterministic regression suites and synthetic inputs; it does not claim real-mail or customer-business acceptance.
 > **The current release supports Hermes and Codex.** Antigravity is not detected, installed, or configured.
 

{memleaf-0.2.49 → memleaf-0.2.51}/README.md

@@ -4,7 +4,7 @@
 
 [English](README.en.md) · [PyPI](https://pypi.org/project/memleaf/) · [GitHub](https://github.com/miffyblueboo/memleaf)
 
-> **版本：0.2.49。**
+> **版本：0.2.51。**
 > 记忆只从用户与 Agent 的可见对话提炼。Agent 已在回复中整理的事实、项目进展和明确待办可作为来源；邮件、附件、网页和终端等工具原文不进入记忆提炼。模型负责保留原话中的不确定性，现有记忆仅用于比较、去重和更新。Markdown 仍是唯一事实源。
 > **当前版本支持 Hermes 和 Codex。** Antigravity（反重力）不检测、不安装、不配置。
 

{memleaf-0.2.49 → memleaf-0.2.51}/pyproject.toml

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

{memleaf-0.2.49 → memleaf-0.2.51}/src/memleaf/__init__.py

@@ -1,6 +1,6 @@
 """Local-first Markdown memory core for AI agents."""
 
-__version__ = "0.2.49"
+__version__ = "0.2.51"
 
 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.49 → memleaf-0.2.51}/src/memleaf/adapters/base.py

@@ -24,6 +24,7 @@ from pathlib import Path
 from typing import Any, Callable, Mapping, Sequence
 
 from ..locking import VaultLock, atomic_write_json, read_json
+from ..subprocess_flags import hidden_popen_kwargs
 
 
 @dataclass(frozen=True)
@@ -453,6 +454,7 @@ def _subprocess_runner(
         "errors": "strict",
         "env": dict(env),
     }
+    options.update(hidden_popen_kwargs())
     if input_text is not None:
         options["input"] = input_text
     return subprocess.run(list(argv), **options)

{memleaf-0.2.49 → memleaf-0.2.51}/src/memleaf/hermes_provider/plugin.yaml

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

{memleaf-0.2.49 → memleaf-0.2.51}/src/memleaf/installer.py

@@ -42,6 +42,7 @@ from .hermes_runtime import (
 )
 from .locking import atomic_write_json
 from .native_registration import ensure_hermes_native_sources
+from .subprocess_flags import hidden_popen_kwargs
 from .vault import Vault
 
 
@@ -357,6 +358,7 @@ def _run(
         "errors": "strict",
         "check": False,
     }
+    options.update(hidden_popen_kwargs())
     if timeout is not None:
         options["timeout"] = timeout
     return subprocess.run(command, **options)

{memleaf-0.2.49 → memleaf-0.2.51}/src/memleaf/planning_context.py

@@ -11,7 +11,7 @@ from .native_index import NativeIndexer
 from .retrieval import candidate_matches_query, filter_by_scope, normalize_term
 from .scope_state import project_scopes_for_domains
 from .scope_maintenance import ScopeMaintenanceError, scope_registry_projection
-from .process_common import ProcessingError, _RELATED_MAX_BODY_CHARS, _RELATED_MAX_CHARS, _RELATED_MAX_ITEMS, _SCOPE_CORRECTION_MARKER_RE, _SCOPE_DIRECTORY_MAX_CHARS, _SCOPE_DIRECTORY_MAX_ITEMS, _SCOPE_DIRECTORY_MAX_TITLE_CHARS, _TARGET_NOT_RELATED, _TARGET_SAME_USE, _TARGET_UNKNOWN, _invoke_native, _merge_related, _native_result, _safe_scope_background, _session_key
+from .process_common import ProcessingError, _RELATED_MAX_BODY_CHARS, _RELATED_MAX_CHARS, _SCOPE_CORRECTION_MARKER_RE, _SCOPE_DIRECTORY_MAX_CHARS, _SCOPE_DIRECTORY_MAX_ITEMS, _SCOPE_DIRECTORY_MAX_TITLE_CHARS, _TARGET_NOT_RELATED, _TARGET_SAME_USE, _TARGET_UNKNOWN, _invoke_native, _merge_related, _native_result, _safe_scope_background, _session_key
 
 
 class PlanningContext:
@@ -317,31 +317,35 @@ class PlanningContext:
         complete = True
 
         def _drop(item: Mapping[str, Any]) -> None:
-            """Record one related record that could not be projected verbatim.
+            """Record one related record that was withheld from the projection.
 
             ``complete`` answers one question only: can Core still prove that no
             **local** record was withheld, so that an absent UPDATE target and a
-            create-safe lookup remain provable?  Native sources are read-only
-            host files that are never an UPDATE or NO_CHANGE target and are only
-            ever referenced through ``shadow_native_ids``, so clipping one must
-            not make the whole lookup unprovable.  Treating a long host memory
-            file as a failed proof would block every automatic extraction with no
-            way for the user to recover except shrinking a file they own.
+            create-safe lookup remain provable?
+
+            Only a withheld record counts.  A body trimmed to fit is still
+            projected -- its identity, type and scopes are all present, so it can
+            still be targeted and still rules out a duplicate CREATE -- and
+            marking that as an unprovable lookup would make ordinary Vault growth
+            fail turns.
+
+            Native sources are read-only host files that are never an UPDATE or
+            NO_CHANGE target and are only ever referenced through
+            ``shadow_native_ids``, so clipping one must not make the whole lookup
+            unprovable either.  Treating a long host memory file as a failed
+            proof would block every automatic extraction with no way for the user
+            to recover except shrinking a file they own.
             """
 
             nonlocal complete
             if item.get("native") is not True:
                 complete = False
 
-        for index, value in enumerate(values):
-            if len(selected) >= _RELATED_MAX_ITEMS:
-                for item in values[index:]:
-                    _drop(item)
-                break
+        for value in values:
             body = value.get("body")
             if isinstance(body, str) and len(body) > _RELATED_MAX_BODY_CHARS:
+                # Trimmed, not withheld: the record keeps its identity.
                 value["body"] = body[: _RELATED_MAX_BODY_CHARS - 1].rstrip() + "…"
-                _drop(value)
             size = cls._related_payload_size(value)
             if size < 0:
                 _drop(value)
@@ -364,9 +368,10 @@ class PlanningContext:
                 if size < 0 or used + size + (1 if selected else 0) > _RELATED_MAX_CHARS:
                     _drop(value)
                     continue
+                # A priority target kept in reduced form is still projected, so
+                # its identity is not withheld and the proof survives.
                 value = minimal
                 additional = size + (1 if selected else 0)
-                _drop(value)
             selected.append(value)
             used += additional
         return selected, complete

{memleaf-0.2.49 → memleaf-0.2.51}/src/memleaf/process_common.py

@@ -259,15 +259,32 @@ _DIAGNOSTIC_SUMMARY_ALLOWED = frozenset(
 )
 
 
-_RELATED_MAX_ITEMS = 6
-
-
+# The comparison catalog is the only part of the B3 prompt that grows with the
+# Vault, so it needs a ceiling -- but the ceiling must be a safety net for the
+# prompt's own hard limit, never a constraint that decides whether a turn may
+# write.
+#
+# It used to be six items, which contradicted the retrieval design outright: a
+# Vault whose memories all carry one scope (``global``, the common personal
+# case, and the only scope in an empty registry) correctly resolves that scope
+# to the whole library, and six rows then hid most of it.  Withholding a local
+# record is also what marks the lookup unprovable, so a small item cap turned
+# ordinary growth into failing turns.
+#
+# The ceiling is now derived from the prompt budget instead of chosen as a round
+# number.  ``MAX_PROMPT_BYTES`` is 192 KiB; a catalog row measures about 1.6
+# UTF-8 bytes per character in practice, so 40000 characters is roughly 64 KiB,
+# leaving well over 100 KiB for the contract, the current evidence and the
+# native catalog.  That admits roughly 180 memories at the observed row size --
+# far beyond the point where compaction is meant to bring the active set down.
+_RELATED_MAX_CHARS = 40000
+
+
+# A single pathological body must not consume the whole catalog budget.  This
+# only ever fires on a memory far longer than an atomic fact.
 _RELATED_MAX_BODY_CHARS = 1600
 
 
-_RELATED_MAX_CHARS = 6000
-
-
 _SCOPE_DIRECTORY_MAX_ITEMS = 8
 
 

{memleaf-0.2.49 → memleaf-0.2.51}/src/memleaf/process_jobs.py

@@ -23,6 +23,7 @@ from typing import Any, Mapping
 from .locking import atomic_write_json, read_json
 from .extraction_budget import aggregate_extraction_metrics
 from .service import Memleaf
+from .subprocess_flags import hidden_popen_kwargs
 from .vault import Vault, safe_component
 
 
@@ -554,7 +555,10 @@ def _launch(vault: Vault, job_id: str) -> subprocess.Popen[Any]:
         "close_fds": True,
     }
     if os.name == "nt":
-        kwargs["creationflags"] = getattr(subprocess, "CREATE_NEW_PROCESS_GROUP", 0) | getattr(subprocess, "DETACHED_PROCESS", 0)
+        # A windowless child, not a detached one: see subprocess_flags.  The
+        # detached flag a previous release used opened a stray console window
+        # on the user's desktop for every captured turn.
+        kwargs.update(hidden_popen_kwargs())
     else:
         kwargs["start_new_session"] = True
     return subprocess.Popen(command, **kwargs)

{memleaf-0.2.49 → memleaf-0.2.51}/src/memleaf/single_pass_plan.py

@@ -104,7 +104,7 @@ def _enum_text(values: Iterable[str]) -> str:
 B3_COMPACT_CONTRACT = f"""B3 STRICT OUTPUT CONTRACT
 Root exactly: {{protocol_version,items,no_memory}}; protocol_version={PROTOCOL_VERSION}. No extra fields at any level.
 Decision exactly one of: {_enum_text(_DECISIONS)}. candidate_id: nonempty string, case-insensitively unique.
-CREATE exactly requires candidate_id,decision,evidence,type,scopes,memory; optional scope_source. type={_enum_text(MEMORY_TYPES)}; scopes=nonempty string[]. memory requires title+body.
+CREATE exactly requires candidate_id,decision,evidence,type,scopes,memory; optional scope_source. type={_enum_text(MEMORY_TYPES)}; scopes=nonempty string[]; see SCOPES. memory requires title+body.
 UPDATE exactly requires candidate_id,decision,evidence,target_memory_id,memory; optional scopes and scope_source; scope_source requires scopes. memory requires body; title optional.
 NO_CHANGE exactly requires candidate_id,decision,evidence,target_memory_id.
 DEFERRED exactly requires candidate_id,decision,evidence,reason; reason={_enum_text(_DEFER_REASONS)}.
@@ -125,6 +125,12 @@ Only current_evidence may establish new facts or changes. local_memory_catalog a
 TASK
 Extract every independently useful long-term memory. Keep independently retrievable/updateable topics separate and preserve entity, condition, polarity, uncertainty, ownership, state and meaning-critical numbers/codes. CREATE only when no supplied local memory represents the durable information; UPDATE only when current evidence proves a change to one supplied local memory; NO_CHANGE only when it adds no semantic change; DEFERRED for a durable candidate that cannot safely reach a terminal decision. Project ownership and platform/system names are separate judgments. Do not turn every negation into no_memory and do not use NO_CHANGE to hide ambiguity.
 
+SCOPES
+Legal values: global | domain:<name> | portfolio:<name> | project:<name> | unscoped. scopes is a nonempty array; at most one project:<name> per memory; unscoped must be the only value, and Core then records insufficient_context.
+When a candidate concerns one distinct project the user is working on -- a type=project memory, or the work, decisions, state or deadlines that belong to that project -- scope it to that project as project:<name>, using the name the evidence itself uses. The project does not need to be registered first; scope_registry only lists what already exists.
+Ground the name in this candidate's own cited evidence, or in a project scope explicitly supplied for this turn. A product, platform, system, vendor, notification source, comparison or implementation context is not ownership by name alone.
+Use global only for a fact that no single project owns: a standing personal preference, a machine-wide or tool-wide rule, or an environment fact. Never invent, translate or borrow a project name.
+
 DATES
 An evidence unit may carry an ISO-8601 UTC timestamp. Use it ONLY to resolve a relative, partial or yearless date that the unit's own text expresses; never borrow another unit's timestamp and never guess a missing year. The timestamp is an anchor, not content: never write its own date into a memory, and add no date the evidence text does not state. A date literal in a memory must appear in that memory's cited evidence, either verbatim or as the same month and day. Write due_date as YYYY-MM-DD. A todo declares status, and due_date only when its own evidence establishes a deadline: otherwise omit due_date, or set it to null when the deadline itself is still unresolved. Any memory carrying a date that no admitted evidence grounds is rejected and costs the whole turn, so defer instead of approximating.
 
@@ -490,6 +496,7 @@ def parse_single_pass_output(
     used_targets: set[str] = set()
     binding_rows: list[dict[str, Any]] = []
     prepared: list[tuple[dict[str, Any], Mapping[str, Any] | None]] = []
+    forced_defer: dict[str, str] = {}
 
     for item_index, raw_item in enumerate(items):
         item_path = f"items[{item_index}]"
@@ -549,11 +556,14 @@ def parse_single_pass_output(
                 path=item_path, rule="relationship", actual=raw_item,
                 expected_type="object", missing_fields=("scopes",),
             )
-        if decision in {"CREATE", "UPDATE", "NO_CHANGE"} and not lookup_complete:
-            raise ModelOutputError(
-                "incomplete B3 lookup cannot authorize a terminal decision",
-                validation_detail="other_schema_violation",
-            )
+        if decision == "CREATE" and not lookup_complete:
+            # Only a CREATE claims novelty, and only a complete lookup can prove
+            # it.  The candidate cannot be written, but nothing else in the turn
+            # depends on this proof, so it is deferred with the protocol's own
+            # reason instead of discarding every other verdict.  UPDATE and
+            # NO_CHANGE name a target that is in the supplied catalog by
+            # construction, so they stay provable without it.
+            forced_defer[candidate_key] = "lookup_incomplete"
         candidate_ids.add(candidate_key)
         claims = raw_item.get("evidence")
         if isinstance(claims, Mapping):
@@ -742,6 +752,21 @@ def parse_single_pass_output(
         candidate_id = item["candidate_id"]
         decision = item["decision"]
         evidence = [dict(claim) for claim in bindings[candidate_id]]
+        forced = forced_defer.get(candidate_id.casefold())
+        if forced is not None:
+            normalized_items.append({
+                "candidate_id": candidate_id,
+                "decision": "DEFERRED",
+                "reason": forced,
+                "evidence": evidence,
+            })
+            if deferrals is not None:
+                deferrals.append({
+                    "candidate_id": candidate_id,
+                    "reason": forced,
+                    "detail": forced,
+                })
+            continue
         normalized: dict[str, Any] = {
             "candidate_id": candidate_id,
             "decision": decision,

memleaf-0.2.51/src/memleaf/subprocess_flags.py

@@ -0,0 +1,43 @@
+"""Windows process-creation flags for child processes that must stay invisible.
+
+memleaf starts three kinds of child process: the detached extraction worker,
+host CLI probes, and host model-discovery commands.  None of them owns a
+window, and all of them can be started by a host that has no console of its
+own -- a Hermes desktop process, for example.  On Windows a console program
+started without an explicit flag in that situation gets a brand-new console
+window, which lands on the user's desktop as a stray terminal.
+
+``DETACHED_PROCESS`` looks like the right answer and is not: a console program
+still needs a console, and Windows creates a visible one for it.  Measured on
+Windows 11 with Windows Terminal as the default host, spawning this interpreter
+with ``CREATE_NEW_PROCESS_GROUP | DETACHED_PROCESS`` opened one new console
+window whose title was the interpreter path, while ``CREATE_NO_WINDOW`` opened
+none.  ``CREATE_NO_WINDOW`` is therefore used, combined with
+``CREATE_NEW_PROCESS_GROUP`` so the child keeps its own group and is not taken
+down by a Ctrl+C delivered to the parent's console.
+"""
+
+from __future__ import annotations
+
+import os
+import subprocess
+
+
+def hidden_process_flags() -> int:
+    """Return creation flags that keep a console child windowless on Windows."""
+
+    if os.name != "nt":
+        return 0
+    return getattr(subprocess, "CREATE_NO_WINDOW", 0) | getattr(
+        subprocess, "CREATE_NEW_PROCESS_GROUP", 0
+    )
+
+
+def hidden_popen_kwargs() -> dict[str, int]:
+    """Return ``Popen``/``run`` keyword arguments for a windowless child."""
+
+    flags = hidden_process_flags()
+    return {"creationflags": flags} if flags else {}
+
+
+__all__ = ["hidden_popen_kwargs", "hidden_process_flags"]

{memleaf-0.2.49 → memleaf-0.2.51/src/memleaf.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: memleaf
-Version: 0.2.49
+Version: 0.2.51
 Summary: A local-first Markdown memory core for AI agents
 Author: memleaf contributors
 License-Expression: MIT
@@ -23,7 +23,7 @@ Dynamic: license-file
 
 [English](README.en.md) · [PyPI](https://pypi.org/project/memleaf/) · [GitHub](https://github.com/miffyblueboo/memleaf)
 
-> **版本：0.2.49。**
+> **版本：0.2.51。**
 > 记忆只从用户与 Agent 的可见对话提炼。Agent 已在回复中整理的事实、项目进展和明确待办可作为来源；邮件、附件、网页和终端等工具原文不进入记忆提炼。模型负责保留原话中的不确定性，现有记忆仅用于比较、去重和更新。Markdown 仍是唯一事实源。
 > **当前版本支持 Hermes 和 Codex。** Antigravity（反重力）不检测、不安装、不配置。
 

{memleaf-0.2.49 → memleaf-0.2.51}/src/memleaf.egg-info/SOURCES.txt

@@ -77,6 +77,7 @@ src/memleaf/single_pass_memory_planner.py
 src/memleaf/single_pass_plan.py
 src/memleaf/source_policy.py
 src/memleaf/state_layout.py
+src/memleaf/subprocess_flags.py
 src/memleaf/summary_batch.py
 src/memleaf/target_reconciliation.py
 src/memleaf/turn_audit.py