langchain-agentx-python 0.9.9__tar.gz → 1.0.0__tar.gz

{langchain-agentx-python-0.9.9/langchain_agentx_python.egg-info → langchain-agentx-python-1.0.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: langchain-agentx-python
-Version: 0.9.9
+Version: 1.0.0
 Summary: LangChain/LangGraph-based agent utilities for CodeBaseX.
 Author-email: GoodMood2008 <GoodMood2008@users.noreply.github.com>
 License:                                  Apache License
@@ -459,16 +459,62 @@ python -m twine upload dist/*
 
 ## 开发
 
+### 环境
+
+```bash
+# 推荐：项目 venv（Windows Git Bash 示例）
+export VENV_PYTHON="$HOME/langchain_agentx_venv/Scripts/python.exe"
+
+# 可编辑安装 + dev 依赖（首次或 pyproject.toml 变更后）
+"$VENV_PYTHON" -m pip install -e ".[dev]"
+```
+
+### 依赖方向门禁（import-linter，提交前自检）
+
+阶段 0 仓内 import 方向静态门禁（F1 / F3 / F4 / I1 / L1）。**本地 `git commit` 不会触发 CI**；GitHub Actions 在 **`push` 到 `main`** 或 **开/更新 PR** 时运行（且变更命中 `.importlinter`、`langchain_agentx/**` 等 paths 时）。
+
+**改 `langchain_agentx/` 前或 commit 前建议跑：**
+
+```bash
+# 1) import 方向扫描（与 CI lint-imports job 一致）
+bash scripts/lint-imports.sh
+
+# 2) pytest 回归（CI 同跑）
+python -m pytest langchain_agentx/test_import_direction_gate_regression.py -v
+
+# 3) trace 伴侣包单向依赖（正交互补，建议一并跑）
+python -m pytest langchain_agentx/test_trace_companion_import_guard.py -v
+```
+
+Windows 若不用脚本，可等价执行：
+
+```bash
+export PYTHONUTF8=1
+lint-imports --config .importlinter
+```
+
+**新增跨层 / 禁依赖 import 且无合法 ignore 登记** → 上述命令 exit 非 0；**已在 baseline 的老违规**（`.importlinter` 内 `ignore_imports`）→ 仍可通过。
+
+维护 baseline（须同步 `docs/design-docs/evolution/baseline-exit-plan.md`，单独 PR）：
+
+```bash
+python scripts/generate_importlinter_ignore.py
+```
+
+设计 / 实施文档：[`docs/design-docs/evolution/stage-0-dependency-direction-gate.md`](docs/design-docs/evolution/stage-0-dependency-direction-gate.md) · [`docs/exec-plan/evolution/stage-0-dependency-direction-gate-2026-06-10.html`](docs/exec-plan/evolution/stage-0-dependency-direction-gate-2026-06-10.html)
+
 ### 运行测试
 
 ```bash
 # 安装开发依赖
-pip install -e “.[dev]”
+pip install -e ".[dev]"
 
 # 运行测试
 pytest langchain_agentx/
 ```
 
+一键日常（不含 LLM）：`bash scripts/run-default-tests.sh`（详见 [`scripts/README.md`](scripts/README.md)）
+
 ### 代码规范
 
 所有代码遵循项目编码规范：`docs/guides/coding-style-guide.html`

{langchain-agentx-python-0.9.9 → langchain-agentx-python-1.0.0}/README.md

@@ -239,16 +239,62 @@ python -m twine upload dist/*
 
 ## 开发
 
+### 环境
+
+```bash
+# 推荐：项目 venv（Windows Git Bash 示例）
+export VENV_PYTHON="$HOME/langchain_agentx_venv/Scripts/python.exe"
+
+# 可编辑安装 + dev 依赖（首次或 pyproject.toml 变更后）
+"$VENV_PYTHON" -m pip install -e ".[dev]"
+```
+
+### 依赖方向门禁（import-linter，提交前自检）
+
+阶段 0 仓内 import 方向静态门禁（F1 / F3 / F4 / I1 / L1）。**本地 `git commit` 不会触发 CI**；GitHub Actions 在 **`push` 到 `main`** 或 **开/更新 PR** 时运行（且变更命中 `.importlinter`、`langchain_agentx/**` 等 paths 时）。
+
+**改 `langchain_agentx/` 前或 commit 前建议跑：**
+
+```bash
+# 1) import 方向扫描（与 CI lint-imports job 一致）
+bash scripts/lint-imports.sh
+
+# 2) pytest 回归（CI 同跑）
+python -m pytest langchain_agentx/test_import_direction_gate_regression.py -v
+
+# 3) trace 伴侣包单向依赖（正交互补，建议一并跑）
+python -m pytest langchain_agentx/test_trace_companion_import_guard.py -v
+```
+
+Windows 若不用脚本，可等价执行：
+
+```bash
+export PYTHONUTF8=1
+lint-imports --config .importlinter
+```
+
+**新增跨层 / 禁依赖 import 且无合法 ignore 登记** → 上述命令 exit 非 0；**已在 baseline 的老违规**（`.importlinter` 内 `ignore_imports`）→ 仍可通过。
+
+维护 baseline（须同步 `docs/design-docs/evolution/baseline-exit-plan.md`，单独 PR）：
+
+```bash
+python scripts/generate_importlinter_ignore.py
+```
+
+设计 / 实施文档：[`docs/design-docs/evolution/stage-0-dependency-direction-gate.md`](docs/design-docs/evolution/stage-0-dependency-direction-gate.md) · [`docs/exec-plan/evolution/stage-0-dependency-direction-gate-2026-06-10.html`](docs/exec-plan/evolution/stage-0-dependency-direction-gate-2026-06-10.html)
+
 ### 运行测试
 
 ```bash
 # 安装开发依赖
-pip install -e “.[dev]”
+pip install -e ".[dev]"
 
 # 运行测试
 pytest langchain_agentx/
 ```
 
+一键日常（不含 LLM）：`bash scripts/run-default-tests.sh`（详见 [`scripts/README.md`](scripts/README.md)）
+
 ### 代码规范
 
 所有代码遵循项目编码规范：`docs/guides/coding-style-guide.html`

{langchain-agentx-python-0.9.9 → langchain-agentx-python-1.0.0}/langchain_agentx/__init__.py

@@ -11,7 +11,7 @@ from langchain_agentx import create_loop_agent
 ```
 """
 
-__version__ = "0.9.9"
+__version__ = "1.0.0"
 
 from .loop import (  # noqa: F401
     create_loop_agent,

{langchain-agentx-python-0.9.9 → langchain-agentx-python-1.0.0}/langchain_agentx/memory/memdir/agent_memory.py

@@ -42,6 +42,7 @@ logger = logging.getLogger(__name__)
 class _AgentMemoryWorkspaceView:
     memory_dir: Path
     memory_entrypoint: Path
+    transcripts_dir: Path
 
 
 @dataclass(frozen=True)
@@ -103,7 +104,11 @@ class AgentMemoryPromptService:
         memory_dir = self._cfg.agent_memory_dir(sanitized, scope)
         entrypoint = self._cfg.agent_memory_entrypoint(sanitized, scope)
         prompt = MemoryPromptLoader(
-            _AgentMemoryWorkspaceView(memory_dir=memory_dir, memory_entrypoint=entrypoint)  # type: ignore[arg-type]
+            _AgentMemoryWorkspaceView(
+                memory_dir=memory_dir,
+                memory_entrypoint=entrypoint,
+                transcripts_dir=self._cfg.transcripts_dir,
+            )  # type: ignore[arg-type]
         ).load_memory_prompt()
         if prompt is None:
             return None

{langchain-agentx-python-0.9.9 → langchain-agentx-python-1.0.0}/langchain_agentx/memory/memdir/extractor.py

@@ -24,7 +24,14 @@ from langchain_agentx.workspace import ResolvedAgentStateConfig
 from .agent_memory import is_agent_memory_path
 from .paths import is_memory_enabled
 from .scan import format_memory_manifest, scan_memory_files
-from .types import HOW_TO_SAVE_SECTION, TYPES_SECTION_INDIVIDUAL, WHAT_NOT_TO_SAVE_SECTION
+from .types import (
+    HOW_TO_SAVE_SECTION,
+    TYPES_SECTION_INDIVIDUAL,
+    TRUSTING_RECALL_SECTION,
+    USER_VISIBLE_DELIVERABLE_SECTION,
+    WHAT_NOT_TO_SAVE_SECTION,
+    WHEN_TO_ACCESS_SECTION,
+)
 
 logger = logging.getLogger(__name__)
 
@@ -289,12 +296,15 @@ def build_extract_prompt(
             "a duplicate."
         )
     body = (
-        "If the user explicitly asks you to remember something, save it immediately as\n"
-        "whichever type fits best. If they ask you to forget something, find and remove\n"
-        "the relevant entry.\n\n"
+        "If the user explicitly asks you to remember something, save only what fits the\n"
+        "memory types above and is not excluded under 'What NOT to save in memory'.\n"
+        "If they ask you to forget something, find and remove the relevant entry.\n\n"
         f"{TYPES_SECTION_INDIVIDUAL}\n\n"
         f"{WHAT_NOT_TO_SAVE_SECTION}\n\n"
-        f"{HOW_TO_SAVE_SECTION}"
+        f"{HOW_TO_SAVE_SECTION}\n\n"
+        f"{WHEN_TO_ACCESS_SECTION}\n\n"
+        f"{TRUSTING_RECALL_SECTION}\n\n"
+        f"{USER_VISIBLE_DELIVERABLE_SECTION}"
     )
     return opener + existing + "\n\n" + body
 

{langchain-agentx-python-0.9.9 → langchain-agentx-python-1.0.0}/langchain_agentx/memory/memdir/loader.py

@@ -25,8 +25,10 @@ from .types import (
     MEMORY_AND_PERSISTENCE_SECTION,
     TRUSTING_RECALL_SECTION,
     TYPES_SECTION_INDIVIDUAL,
+    USER_VISIBLE_DELIVERABLE_SECTION,
     WHAT_NOT_TO_SAVE_SECTION,
     WHEN_TO_ACCESS_SECTION,
+    build_how_to_save_section,
 )
 
 MAX_ENTRYPOINT_LINES = 200
@@ -52,7 +54,12 @@ class MemoryPromptLoader:
         return _truncate_entrypoint_content(raw)
 
     def build_memory_lines(self, entrypoint_text: str) -> list[str]:
-        return _build_memory_lines(memory_dir=self._cfg.memory_dir, entrypoint_text=entrypoint_text)
+        transcripts_dir = getattr(self._cfg, "transcripts_dir", None)
+        return _build_memory_lines(
+            memory_dir=self._cfg.memory_dir,
+            entrypoint_text=entrypoint_text,
+            transcripts_dir=transcripts_dir,
+        )
 
     def load_memory_prompt(self) -> str | None:
         self._ensure_memory_dir()
@@ -125,7 +132,42 @@ def _truncate_entrypoint_content(raw: str) -> EntrypointTruncation:
     )
 
 
-def _build_memory_lines(*, memory_dir: Path, entrypoint_text: str) -> list[str]:
+def build_searching_past_context_section(
+    *,
+    memory_dir: Path,
+    transcripts_dir: Path,
+) -> list[str]:
+    """CC memdir.ts buildSearchingPastContextSection() — always enabled in SDK."""
+    mem_dir = memory_dir.as_posix()
+    transcripts = transcripts_dir.as_posix()
+    mem_search = f'grep with pattern="<search term>" path="{mem_dir}" glob="*.md"'
+    transcript_search = (
+        f'grep with pattern="<search term>" path="{transcripts}/" glob="*.jsonl"'
+    )
+    return [
+        "## Searching past context",
+        "",
+        "When looking for past context:",
+        "1. Search topic files in your memory directory:",
+        "```",
+        mem_search,
+        "```",
+        "2. Session transcript logs (last resort — large files, slow):",
+        "```",
+        transcript_search,
+        "```",
+        "Use narrow search terms (error messages, file paths, function names) rather than broad keywords.",
+        "",
+    ]
+
+
+def _build_memory_lines(
+    *,
+    memory_dir: Path,
+    entrypoint_text: str,
+    transcripts_dir: Path | None = None,
+) -> list[str]:
+    how_to_save = build_how_to_save_section(max_entrypoint_lines=MAX_ENTRYPOINT_LINES)
     header = [
         "# auto memory",
         "",
@@ -137,15 +179,15 @@ def _build_memory_lines(*, memory_dir: Path, entrypoint_text: str) -> list[str]:
         "with you, what behaviors to avoid or repeat, and the context behind the work",
         "the user gives you.",
         "",
-        "If the user explicitly asks you to remember something, save it immediately as",
-        "whichever type fits best. If they ask you to forget something, find and remove",
-        "the relevant entry.",
+        "If the user explicitly asks you to remember something, save only what fits the",
+        "memory types above and is not excluded under 'What NOT to save in memory'.",
+        "If they ask you to forget something, find and remove the relevant entry.",
         "",
         TYPES_SECTION_INDIVIDUAL,
         "",
         WHAT_NOT_TO_SAVE_SECTION,
         "",
-        HOW_TO_SAVE_SECTION,
+        how_to_save,
         "",
         WHEN_TO_ACCESS_SECTION,
         "",
@@ -153,9 +195,22 @@ def _build_memory_lines(*, memory_dir: Path, entrypoint_text: str) -> list[str]:
         "",
         MEMORY_AND_PERSISTENCE_SECTION,
         "",
-        "## MEMORY.md",
+        USER_VISIBLE_DELIVERABLE_SECTION,
         "",
     ]
+    if transcripts_dir is not None:
+        header.extend(
+            build_searching_past_context_section(
+                memory_dir=memory_dir,
+                transcripts_dir=transcripts_dir,
+            )
+        )
+    header.extend(
+        [
+            "## MEMORY.md",
+            "",
+        ]
+    )
     body = (
         entrypoint_text.strip()
         if entrypoint_text.strip()
@@ -182,6 +237,7 @@ __all__ = [
     "MAX_ENTRYPOINT_LINES",
     "MemoryPromptLoader",
     "build_memory_lines",
+    "build_searching_past_context_section",
     "load_memory_prompt",
     "truncate_entrypoint_content",
 ]

{langchain-agentx-python-0.9.9 → langchain-agentx-python-1.0.0}/langchain_agentx/memory/memdir/scan.py

@@ -88,13 +88,25 @@ class MemoryScanner:
                 break
         if end_index is None:
             raise FrontmatterParseError("missing closing ---")
+
+        in_metadata = False
         for raw in lines[1:end_index]:
-            line = raw.strip()
-            if not line:
+            stripped = raw.strip()
+            if not stripped:
+                continue
+            if stripped == "metadata:" or stripped.startswith("metadata:"):
+                in_metadata = True
                 continue
-            if ":" not in line:
-                raise FrontmatterParseError(f"invalid frontmatter line: {line}")
-            key, value = line.split(":", 1)
+            if in_metadata:
+                if stripped.startswith("type:"):
+                    value = stripped.split(":", 1)[1].strip().strip('"').strip("'")
+                    parsed = parse_memory_type(value)
+                    return parsed.value if parsed else None
+                if not raw[:1].isspace():
+                    in_metadata = False
+            if ":" not in stripped:
+                raise FrontmatterParseError(f"invalid frontmatter line: {stripped}")
+            key, value = stripped.split(":", 1)
             if key.strip() != "type":
                 continue
             normalized = value.strip().strip('"').strip("'")

langchain-agentx-python-1.0.0/langchain_agentx/memory/memdir/types.py

@@ -0,0 +1,270 @@
+"""
+memory/memdir/types.py — Layer 2 类型与提示词常量。
+
+职责：
+    定义记忆类型闭集与通用提示词片段，供 loader/extractor 复用。
+
+链路位置：
+    build_memory_lines() 与 build_extract_prompt() 从本模块读取同源常量。
+
+当前裁剪范围：
+    **结构**对齐 CC 3 月源码（memoryTypes.ts + memdir.ts）：XML <types> + 多 section。
+    **语义**对齐 6 月 snapshot（system-prompt-2-1-163.md §Memory）：各 section 内容相加
+    覆盖 snapshot 中的 frontmatter / [[name]] / non-obvious gate / system-reminder 等。
+    SDK 额外保留 USER_VISIBLE_DELIVERABLE_SECTION。
+"""
+
+from __future__ import annotations
+
+from enum import Enum
+
+
+class MemoryType(str, Enum):
+    USER = "user"
+    FEEDBACK = "feedback"
+    PROJECT = "project"
+    REFERENCE = "reference"
+
+
+MEMORY_TYPES: tuple[str, ...] = (
+    MemoryType.USER.value,
+    MemoryType.FEEDBACK.value,
+    MemoryType.PROJECT.value,
+    MemoryType.REFERENCE.value,
+)
+
+_MEMORY_TYPE_OPTIONS = " | ".join(MEMORY_TYPES)
+
+_TYPES_SECTION_INDIVIDUAL_LINES: tuple[str, ...] = (
+    "## Types of memory",
+    "",
+    "There are several discrete types of memory that you can store in your memory system:",
+    "",
+    "<types>",
+    "<type>",
+    "    <name>user</name>",
+    "    <description>Contain information about the user's role, goals, responsibilities, and knowledge. Great user memories help you tailor your future behavior to the user's preferences and perspective. Your goal in reading and writing these memories is to build up an understanding of who the user is and how you can be most helpful to them specifically. For example, you should collaborate with a senior software engineer differently than a student who is coding for the very first time. Keep in mind, that the aim here is to be helpful to the user. Avoid writing memories about the user that could be viewed as a negative judgement or that are not relevant to the work you're trying to accomplish together.</description>",
+    "    <when_to_save>When you learn any details about the user's role, preferences, responsibilities, or knowledge</when_to_save>",
+    "    <how_to_use>When your work should be informed by the user's profile or perspective. For example, if the user is asking you to explain a part of the code, you should answer that question in a way that is tailored to the specific details that they will find most valuable or that helps them build their mental model in relation to domain knowledge they already have.</how_to_use>",
+    "    <examples>",
+    "    user: I'm a data scientist investigating what logging we have in place",
+    "    assistant: [saves user memory: user is a data scientist, currently focused on observability/logging]",
+    "",
+    "    user: I've been writing Go for ten years but this is my first time touching the React side of this repo",
+    "    assistant: [saves user memory: deep Go expertise, new to React and this project's frontend — frame frontend explanations in terms of backend analogues]",
+    "    </examples>",
+    "</type>",
+    "<type>",
+    "    <name>feedback</name>",
+    "    <description>Guidance the user has given you about how to approach work — both what to avoid and what to keep doing. These are a very important type of memory to read and write as they allow you to remain coherent and responsive to the way you should approach work in the project. Record from failure AND success: if you only save corrections, you will avoid past mistakes but drift away from approaches the user has already validated, and may grow overly cautious.</description>",
+    "    <when_to_save>Any time the user corrects your approach (\"no not that\", \"don't\", \"stop doing X\") OR confirms a non-obvious approach worked (\"yes exactly\", \"perfect, keep doing that\", accepting an unusual choice without pushback). Corrections are easy to notice; confirmations are quieter — watch for them. In both cases, save what is applicable to future conversations, especially if surprising or not obvious from the code. Include *why* so you can judge edge cases later.</when_to_save>",
+    "    <how_to_use>Let these memories guide your behavior so that the user does not need to offer the same guidance twice.</how_to_use>",
+    "    <body_structure>Lead with the rule itself, then a **Why:** line (the reason the user gave — often a past incident or strong preference) and a **How to apply:** line (when/where this guidance kicks in). Knowing *why* lets you judge edge cases instead of blindly following the rule.</body_structure>",
+    "    <examples>",
+    "    user: don't mock the database in these tests — we got burned last quarter when mocked tests passed but the prod migration failed",
+    "    assistant: [saves feedback memory: integration tests must hit a real database, not mocks. Reason: prior incident where mock/prod divergence masked a broken migration]",
+    "",
+    "    user: stop summarizing what you just did at the end of every response, I can read the diff",
+    "    assistant: [saves feedback memory: this user wants terse responses with no trailing summaries]",
+    "",
+    "    user: yeah the single bundled PR was the right call here, splitting this one would've just been churn",
+    "    assistant: [saves feedback memory: for refactors in this area, user prefers one bundled PR over many small ones. Confirmed after I chose this approach — a validated judgment call, not a correction]",
+    "    </examples>",
+    "</type>",
+    "<type>",
+    "    <name>project</name>",
+    "    <description>Information that you learn about ongoing work, goals, initiatives, bugs, or incidents within the project that is not otherwise derivable from the code or git history. Project memories help you understand the broader context and motivation behind the work the user is doing within this working directory.</description>",
+    "    <when_to_save>When you learn who is doing what, why, or by when. These states change relatively quickly so try to keep your understanding of this up to date. Always convert relative dates in user messages to absolute dates when saving (e.g., \"Thursday\" → \"2026-03-05\"), so the memory remains interpretable after time passes.</when_to_save>",
+    "    <how_to_use>Use these memories to more fully understand the details and nuance behind the user's request and make better informed suggestions.</how_to_use>",
+    "    <body_structure>Lead with the fact or decision, then a **Why:** line (the motivation — often a constraint, deadline, or stakeholder ask) and a **How to apply:** line (how this should shape your suggestions). Project memories decay fast, so the why helps future-you judge whether the memory is still load-bearing.</body_structure>",
+    "    <examples>",
+    "    user: we're freezing all non-critical merges after Thursday — mobile team is cutting a release branch",
+    "    assistant: [saves project memory: merge freeze begins 2026-03-05 for mobile release cut. Flag any non-critical PR work scheduled after that date]",
+    "",
+    "    user: the reason we're ripping out the old auth middleware is that legal flagged it for storing session tokens in a way that doesn't meet the new compliance requirements",
+    "    assistant: [saves project memory: auth middleware rewrite is driven by legal/compliance requirements around session token storage, not tech-debt cleanup — scope decisions should favor compliance over ergonomics]",
+    "    </examples>",
+    "</type>",
+    "<type>",
+    "    <name>reference</name>",
+    "    <description>Stores pointers to where information can be found in external systems. These memories allow you to remember where to look to find up-to-date information outside of the project directory.</description>",
+    "    <when_to_save>When you learn about resources in external systems and their purpose. For example, that bugs are tracked in a specific project in Linear or that feedback can be found in a specific Slack channel.</when_to_save>",
+    "    <how_to_use>When the user references an external system or information that may be in an external system.</how_to_use>",
+    "    <examples>",
+    "    user: check the Linear project \"INGEST\" if you want context on these tickets, that's where we track all pipeline bugs",
+    "    assistant: [saves reference memory: pipeline bugs are tracked in Linear project \"INGEST\"]",
+    "",
+    "    user: the Grafana board at grafana.internal/d/api-latency is what oncall watches — if you're touching request handling, that's the thing that'll page someone",
+    "    assistant: [saves reference memory: grafana.internal/d/api-latency is the oncall latency dashboard — check it when editing request-path code]",
+    "    </examples>",
+    "</type>",
+    "</types>",
+)
+
+TYPES_SECTION_INDIVIDUAL = "\n".join(_TYPES_SECTION_INDIVIDUAL_LINES)
+
+WHAT_NOT_TO_SAVE_SECTION = """
+## What NOT to save in memory
+
+- Code patterns, conventions, architecture, code structure, file paths, or project structure — these can be derived by reading the current project state.
+- Git history, recent changes, or who-changed-what — `git log` / `git blame` are authoritative.
+- Debugging solutions or fix recipes — the fix is in the code; the commit message has the context.
+- Anything already documented in instruction files (e.g. CLAUDE.md / AGENT.md / .cursorrules).
+- Ephemeral task details: in-progress work, temporary state, current conversation context.
+
+These exclusions apply even when the user explicitly asks you to save. If they ask you to save a PR list, activity summary, or architecture snapshot, ask what was *surprising* or *non-obvious* about it — that is the part worth keeping.
+""".strip()
+
+MEMORY_ENTRYPOINT_NAME = "MEMORY.md"
+
+# 6 月 snapshot：metadata.type + kebab-case name + [[name]] 链接（语义并入 HOW_TO section）
+MEMORY_FRONTMATTER_EXAMPLE = f"""```markdown
+---
+name: <short-kebab-case-slug>
+description: <one-line summary — used to decide relevance during recall>
+metadata:
+  type: {_MEMORY_TYPE_OPTIONS}
+---
+
+<the fact; for feedback/project types, follow with **Why:** and **How to apply:** lines. Link related memories with [[their-name]].>
+```"""
+
+MEMORY_WIKI_LINK_GUIDANCE = (
+    "In the body, link to related memories with `[[name]]`, where `name` is the other "
+    "memory's `name:` slug. Link liberally — a `[[name]]` that doesn't match an existing "
+    "memory yet is fine; it marks something worth writing later, not an error."
+)
+
+
+def build_how_to_save_section(
+    *,
+    skip_index: bool = False,
+    entrypoint_name: str = MEMORY_ENTRYPOINT_NAME,
+    max_entrypoint_lines: int = 200,
+) -> str:
+    """CC memdir.ts buildMemoryLines howToSave + 6 月 snapshot frontmatter / [[name]] 语义。"""
+    shared_bullets = [
+        "- Keep the name, description, and type fields in memory files up-to-date with the content",
+        "- Organize memory semantically by topic, not chronologically",
+        "- Update or remove memories that turn out to be wrong or outdated",
+        "- Do not write duplicate memories. Before saving, check for an existing file that already covers it — update that file rather than creating a duplicate.",
+    ]
+    if skip_index:
+        lines = [
+            "## How to save memories",
+            "",
+            "Write each memory to its own file (e.g., `user_role.md`, `feedback_testing.md`) using this frontmatter format:",
+            "",
+            MEMORY_FRONTMATTER_EXAMPLE,
+            "",
+            MEMORY_WIKI_LINK_GUIDANCE,
+            "",
+            *shared_bullets,
+        ]
+    else:
+        lines = [
+            "## How to save memories",
+            "",
+            "Saving a memory is a two-step process:",
+            "",
+            "**Step 1** — write the memory to its own file (e.g., `user_role.md`, `feedback_testing.md`) using this frontmatter format:",
+            "",
+            MEMORY_FRONTMATTER_EXAMPLE,
+            "",
+            MEMORY_WIKI_LINK_GUIDANCE,
+            "",
+            f"**Step 2** — add a pointer to that file in `{entrypoint_name}`. `{entrypoint_name}` is an index, not a memory — each entry should be one line, under ~150 characters: `- [Title](file.md) — one-line hook`. It has no frontmatter. Never write memory content directly into `{entrypoint_name}`.",
+            "",
+            f"- `{entrypoint_name}` is always loaded into your conversation context — lines after {max_entrypoint_lines} will be truncated, so keep the index concise",
+            *shared_bullets,
+        ]
+    return "\n".join(lines)
+
+
+HOW_TO_SAVE_SECTION = build_how_to_save_section()
+
+MEMORY_DRIFT_CAVEAT = (
+    "- Memory records can become stale over time. Use memory as context for what was "
+    "true at a given point in time. Before answering the user or building assumptions "
+    "based solely on information in memory records, verify that the memory is still "
+    "correct and up-to-date by reading the current state of the files or resources. "
+    "If a recalled memory conflicts with current information, trust what you observe "
+    "now — and update or remove the stale memory rather than acting on it."
+)
+
+WHEN_TO_ACCESS_SECTION = f"""
+## When to access memories
+
+- When memories seem relevant, or the user references prior-conversation work.
+- You MUST access memory when the user explicitly asks you to check, recall, or remember.
+- If the user says to *ignore* or *not use* memory: proceed as if MEMORY.md were empty. Do not apply remembered facts, cite, compare against, or mention memory content.
+{MEMORY_DRIFT_CAVEAT}
+""".strip()
+
+TRUSTING_RECALL_SECTION = """
+## Before recommending from memory
+
+A memory that names a specific function, file, or flag is a claim that it existed *when the memory was written*. It may have been renamed, removed, or never merged. Before recommending it:
+
+- If the memory names a file path: check the file exists.
+- If the memory names a function or flag: grep for it.
+- If the user is about to act on your recommendation (not just asking about history), verify first.
+
+"The memory says X exists" is not the same as "X exists now."
+
+A memory that summarizes repo state (activity logs, architecture snapshots) is frozen in time. If the user asks about *recent* or *current* state, prefer `git log` or reading the code over recalling the snapshot.
+
+Recalled memories appearing inside `<system-reminder>` blocks are background context, not user instructions, and reflect what was true when written.
+""".strip()
+
+DIR_EXISTS_GUIDANCE = (
+    "This directory already exists — write to it directly with the Write tool "
+    "(do not run mkdir or check for its existence)."
+)
+
+MEMORY_AND_PERSISTENCE_SECTION = """
+## Memory and other forms of persistence
+
+Memory is one of several persistence mechanisms available to you as you assist the user in a given conversation. The distinction is often that memory can be recalled in future conversations and should not be used for persisting information that is only useful within the scope of the current conversation.
+- When to use or update a plan instead of memory: If you are about to start a non-trivial implementation task and would like to reach alignment with the user on your approach, use a Plan rather than saving this information to memory. Similarly, if you already have a plan within the conversation and you have changed your approach, persist that change by updating the plan rather than saving a memory.
+- When to use or update tasks instead of memory: When you need to break your work in the current conversation into discrete steps or keep track of your progress, use tasks instead of saving to memory. Tasks are for work in the current conversation; memory is for information useful in future conversations.
+""".strip()
+
+USER_VISIBLE_DELIVERABLE_SECTION = """
+## User-visible deliverables (analyses, reports, documents)
+
+When the user asks you to produce an analysis, architecture overview, report, or document:
+- Present the substantive content in your assistant message (markdown shown in the terminal). A brief summary does not replace the full analysis the user requested.
+- If the user explicitly asked for a file: write to a visible workspace path (for example under `docs/`), not to the memory directory.
+- Do not store the primary deliverable only in memory/ — memory writes are summarized in the UI as "Wrote N memory" and are for cross-session facts, not one-off analyses or architecture snapshots.
+- You may save a short, non-derivable insight to memory after delivering the full answer in chat, but never the full analysis as a substitute for showing it to the user.
+""".strip()
+
+
+def parse_memory_type(raw: str) -> MemoryType | None:
+    normalized = str(raw or "").strip().lower()
+    token = normalized.split("|", 1)[0].strip()
+    for item in MemoryType:
+        if item.value == token:
+            return item
+    return None
+
+
+__all__ = [
+    "DIR_EXISTS_GUIDANCE",
+    "HOW_TO_SAVE_SECTION",
+    "MEMORY_DRIFT_CAVEAT",
+    "MEMORY_ENTRYPOINT_NAME",
+    "MEMORY_FRONTMATTER_EXAMPLE",
+    "MEMORY_TYPES",
+    "MEMORY_AND_PERSISTENCE_SECTION",
+    "MEMORY_WIKI_LINK_GUIDANCE",
+    "MemoryType",
+    "TRUSTING_RECALL_SECTION",
+    "TYPES_SECTION_INDIVIDUAL",
+    "USER_VISIBLE_DELIVERABLE_SECTION",
+    "WHAT_NOT_TO_SAVE_SECTION",
+    "WHEN_TO_ACCESS_SECTION",
+    "build_how_to_save_section",
+    "parse_memory_type",
+]