memgarden 0.12.2__tar.gz

memgarden-0.12.2/.github/workflows/release.yml

@@ -0,0 +1,167 @@
+name: release
+
+# 打 tag 时由 CI 构建并发布 wheel，同时生成构建出处凭证（provenance attestation）。
+#
+# 为什么不在本机编好再传：哈希锁只能证明「装进镜像的字节 = Release 上那份字节」，
+# 证明不了「这份字节是由公开 tag 的源码编出来的」。本机编 + 手工上传时，有仓库
+# 权限的人可以传一个跟源码对不上的 wheel，别人看源码看不出问题。
+#
+# 由 tag 触发的 CI 编译 + GitHub 签发的 attestation 把这一环补上：凭证里绑定了
+# 仓库、workflow、commit 和产物摘要，任何人都能用
+#   gh attestation verify <wheel> --repo teleport-computer/memgarden
+# 独立验证这个 wheel 确实由这个仓库的这个 commit 编出来。
+
+on:
+  push:
+    tags: ["v*"]
+  workflow_dispatch:
+    inputs:
+      tag:
+        description: "要重新发布的 tag（不填则用当前 ref）"
+        required: false
+
+permissions:
+  contents: write        # 建 Release、传产物
+  id-token: write        # 换取 OIDC token 用于签发凭证
+  attestations: write    # 写 attestation
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          ref: ${{ github.event.inputs.tag || github.ref }}
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+
+      - name: Install uv
+        run: pipx install uv
+
+      - name: Tag 与 pyproject 版本必须一致
+        # 不一致就停：否则会出现「tag 是 v0.1.3、wheel 却是 0.1.2」这种
+        # 凭证与产物名对不上的情况，验证方无从判断该信哪个。
+        run: |
+          TAG="${GITHUB_REF_NAME#v}"
+          PKG=$(grep -m1 '^version = ' pyproject.toml | cut -d'"' -f2)
+          CORE=$(grep -m1 '^version = ' packages/agent-protocol-core/pyproject.toml | cut -d'"' -f2)
+          echo "tag=$TAG  memgarden=$PKG  agent-protocol-core=$CORE"
+          test "$TAG" = "$PKG" || { echo "::error::tag $TAG 与 memgarden 版本 $PKG 不一致"; exit 1; }
+          test "$TAG" = "$CORE" || { echo "::error::tag $TAG 与 agent-protocol-core 版本 $CORE 不一致"; exit 1; }
+
+      - name: 跑测试
+        # 发一个测试不过的包出去比不发更糟 —— 装它的人会以为它是可用的。
+        # --extra dev 才会带上 pytest（本机 venv 里碰巧有，CI 是干净环境）
+        run: uv run --extra dev pytest tests/ -q
+
+      - name: 示例必须能脱离宿主跑通
+        # 这是包对外的核心承诺（无 io、无 API key、无网络），
+        # 发版时验一次，比等使用者发现便宜得多。
+        run: uv run python examples/quickstart.py
+
+      - name: 构建两个包
+        run: |
+          uv build
+          (cd packages/agent-protocol-core && uv build)
+          # out/ 给 Release 和 attestation（两个包一起）；
+          # out-core/ 和 out-mem/ 给 PyPI —— **必须分开**，见下面 publish 那两个 job。
+          mkdir -p out out-core out-mem
+          cp dist/* out/
+          cp packages/agent-protocol-core/dist/* out/
+          cp packages/agent-protocol-core/dist/* out-core/
+          cp dist/* out-mem/
+
+      - name: 传产物给发布 job
+        uses: actions/upload-artifact@v4
+        with:
+          name: dists
+          path: |
+            out-core/
+            out-mem/
+
+      - name: 生成构建出处凭证
+        uses: actions/attest-build-provenance@v1
+        with:
+          subject-path: "out/*"
+
+      - name: 记录产物摘要
+        # 打进 job 日志，方便对照 Release 页和宿主 lock 里的哈希。
+        run: |
+          echo "### 产物摘要" >> "$GITHUB_STEP_SUMMARY"
+          echo '```' >> "$GITHUB_STEP_SUMMARY"
+          sha256sum out/* >> "$GITHUB_STEP_SUMMARY"
+          echo '```' >> "$GITHUB_STEP_SUMMARY"
+          sha256sum out/*
+
+      - name: 发布到 Release
+        env:
+          GH_TOKEN: ${{ github.token }}
+        run: |
+          TAG="${GITHUB_REF_NAME}"
+          if gh release view "$TAG" >/dev/null 2>&1; then
+            gh release upload "$TAG" out/* --clobber
+          else
+            gh release create "$TAG" out/* --title "memgarden $TAG" --generate-notes
+          fi
+
+  # --------------------------------------------------------------------------
+  # PyPI 发布拆成两个 job，各带一个 environment
+  #
+  # ## 为什么必须拆
+  #
+  # PyPI 的 Trusted Publisher 是按「owner + 仓库 + workflow + environment」匹配的。
+  # 两个包在**同一个仓库、同一个 workflow**里，如果都不填 environment，
+  # 两条配置除了项目名完全一样 —— PyPI 判为歧义，直接拒绝注册第二条：
+  #
+  #     A pending trusted publisher matching this configuration has already
+  #     been registered for a different project name.
+  #
+  # 加上不同的 environment，两条配置就能区分开了。
+  #
+  # ## 顺带解决了发布顺序
+  #
+  # memgarden 依赖 agent-protocol-core 的**精确版本**。core 先发（needs 保证），
+  # 否则 PyPI 上会短暂存在一个装不上的 memgarden。
+  #
+  # ## 仓库里仍然不存 token
+  #
+  # 走 OIDC。id-token: write 是每个 job 各自声明的 —— 顶层的 permissions
+  # 不会自动传给这里。
+
+  publish-core:
+    needs: build
+    runs-on: ubuntu-latest
+    environment: pypi-core
+    permissions:
+      id-token: write
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: dists
+      - name: 发布 agent-protocol-core 到 PyPI
+        # 没配 PyPI 侧时这一步会失败，**失败方向是安全的**：发不出去，
+        # 而不是用错凭据发出去。Release 已经在 build job 里发完了，不受影响。
+        continue-on-error: true
+        uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          packages-dir: out-core/
+          skip-existing: true
+
+  publish-memgarden:
+    needs: publish-core      # core 必须先在 PyPI 上，否则 memgarden 装不上
+    runs-on: ubuntu-latest
+    environment: pypi-memgarden
+    permissions:
+      id-token: write
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: dists
+      - name: 发布 memgarden 到 PyPI
+        continue-on-error: true
+        uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          packages-dir: out-mem/
+          skip-existing: true

memgarden-0.12.2/.github/workflows/tests.yml

@@ -0,0 +1,74 @@
+name: tests
+
+# 每次 push / PR 都跑。发版 workflow 也会再跑一次 —— 那次是发版前的最后一道闸，
+# 不是重复：Release 是不可回收的，测试不过的包发出去，装它的人会以为它可用。
+
+on:
+  push:
+    branches: ["main"]
+  pull_request:
+
+permissions:
+  contents: read
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+      - run: pipx install uv
+      - name: 契约测试 + 纯度守卫
+        # --extra dev 才会带上 pytest（本机 venv 里碰巧有，CI 是干净环境）
+        run: uv run --extra dev pytest tests/ -q
+      - name: 示例必须能脱离宿主跑通
+        # 「无 io、无 API key、无网络」是这个包对外的核心承诺。
+        # 只跑单测证明不了它 —— 单测本来就在仓库里跑。
+        run: uv run python examples/quickstart.py
+      - name: 不花钱的四层 eval（挑卡 / 落库闸 / 语言 / 语料自查）
+        # 这不是重复单测。单测证明"函数按写的那样跑"；这几层证明"跑出来的结果是对的"。
+        # 半年里最贵的三次事故都属于后者：管道全通、单测全绿，而用户召不回自己的
+        # 记忆、花园自己翻了语言、真记忆被闸门静默吃掉。
+        run: uv run --extra dev python evals/run.py --baseline evals/baseline.json
+
+      - name: 落卡质量 eval（真模型）
+        # 没 key 就 SKIP 并明说 —— 提示词行为的 bug 只有真模型能暴露，
+        # 单测把 agent stub 掉了，什么都验不到。
+        env:
+          DEEPSEEK_API_KEY: ${{ secrets.EVAL_DEEPSEEK_API_KEY }}
+        run: uv run --extra dev python evals/capture.py --provider deepseek --model deepseek-chat
+      - name: 装完之后 CLI 真的能敲
+        # [project.scripts] 写错、入口 import 不到，只有真装一次才发现 ——
+        # 而「装完能不能用」正是别人愿不愿意继续读下去的门槛。
+        run: |
+          # 旧版本 wheel 留在 dist 里会让 pip 解析打架
+          rm -rf dist packages/agent-protocol-core/dist
+          # **两个包都要构建** —— 根目录的 uv build 只出主包，
+          # 而 memgarden 依赖同源的 agent-protocol-core。漏掉它就装不上。
+          uv build
+          (cd packages/agent-protocol-core && uv build)
+          mkdir -p /tmp/wheels
+          cp dist/*.whl /tmp/wheels/
+          cp packages/agent-protocol-core/dist/*.whl /tmp/wheels/
+          python -m venv /tmp/cli-check
+          # --no-index 是必须的：agent-protocol-core 没发到 PyPI，
+          # 不加的话 pip 会去索引上找它、找不到就整个装失败。
+          /tmp/cli-check/bin/pip install --no-index --find-links /tmp/wheels memgarden
+          # ① 命令能敲（[project.scripts] 写错只有真装一次才发现）
+          /tmp/cli-check/bin/memgarden manifest > /dev/null
+          # ② 能当库用，且**只 import 顶层** —— 这是对外承诺的接入方式
+          /tmp/cli-check/bin/python -c "from memgarden import GardenComponent, CaptureRequest"
+          echo "CLI + SDK OK"
+
+      - name: wheel 能构建，且带许可证
+        run: |
+          uv build
+          python - <<'PY'
+          import zipfile, glob, sys
+          whl = glob.glob("dist/*.whl")[0]
+          names = zipfile.ZipFile(whl).namelist()
+          assert any("LICENSE" in n for n in names), f"wheel 里没有 LICENSE：{whl}"
+          print(f"OK {whl} 带许可证")
+          PY

memgarden-0.12.2/.gitignore

@@ -0,0 +1,6 @@
+__pycache__/
+*.pyc
+.venv/
+.pytest_cache/
+*.db
+dist/

memgarden-0.12.2/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.