densemem 2.6.6rc12__tar.gz

densemem-2.6.6rc12/.gitignore

@@ -0,0 +1,70 @@
+# Dependencies
+node_modules/
+bun.lockb
+
+# Build outputs
+dist/
+build/
+user-dist/
+*.tsbuildinfo
+
+# Environment files
+.env
+.env.local
+.env.*.local
+# Local Docker Compose overrides
+docker-compose.override.yml
+
+# IDE
+.vscode/
+.idea/
+*.swp
+*.swo
+
+# OS
+.DS_Store
+Thumbs.db
+
+# Logs
+logs/
+*.log
+npm-debug.log*
+bun-debug.log*
+
+# Test
+coverage/
+coverage.out
+.nyc_output/
+tests/uat/test-results/
+tests/uat/playwright-report/
+web/test-results/
+web/playwright-report/
+
+# Temporary
+tmp/
+temp/
+*.tmp
+
+# VCP
+.vcp
+
+# Claude Code local state
+.claude/scheduled_tasks.lock
+.claude/settings.local.json
+
+# Editor backups
+*.bak
+telemetry-scrape-token
+prometheus.yml
+# Codex local state and credentials; only the staging-test workflow is shared.
+.codex/*
+.claude
+.mcp.json
+# Python package development and validation
+__pycache__/
+*.py[cod]
+*.egg-info/
+.venv/
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/

densemem-2.6.6rc12/LICENSE

@@ -0,0 +1,201 @@
+                                 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.

densemem-2.6.6rc12/PKG-INFO

@@ -0,0 +1,188 @@
+Metadata-Version: 2.5
+Name: densemem
+Version: 2.6.6rc12
+Summary: Typed async and sync clients for Dense-Mem MCP
+Project-URL: Source, https://github.com/markhuangai/dense-mem/tree/fbca1dc3969b8e49078dcd67a0b6f368d137995e
+Project-URL: Repository, https://github.com/markhuangai/dense-mem
+Project-URL: Documentation, https://github.com/markhuangai/dense-mem/wiki/Framework-Integrations
+Project-URL: Issues, https://github.com/markhuangai/dense-mem/issues
+License-Expression: Apache-2.0
+License-File: LICENSE
+Classifier: Development Status :: 4 - Beta
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Typing :: Typed
+Requires-Python: <3.15,>=3.11
+Requires-Dist: httpx<1,>=0.28.1
+Requires-Dist: mcp<2,>=1.30.0
+Description-Content-Type: text/markdown
+
+# densemem Python client
+
+The Dense-Mem Python core client uses the official MCP SDK. It supports Python
+3.11–3.14 and MCP SDK 1.30 through the compatible 1.x line. This package is being
+prepared for release; PyPI publication is pending. Install a verified wheel:
+
+~~~bash
+python -m pip install /path/to/densemem-VERSION-py3-none-any.whl
+~~~
+
+ADK and LangChain adapters/extras will arrive with issues #220 and #221.
+The core installs neither framework.
+
+## Authentication and operations
+
+~~~python
+from densemem import DenseMemClient
+
+client = DenseMemClient("https://memory.example.com/teams/TEAM_UUID/mcp", token=api_key)
+tools = await client.list_tools()
+~~~
+
+Pass exactly one of token or token_provider. A provider is an async callable
+returning a caller-owned access token. The client resolves it once per operation;
+it does not acquire or refresh OAuth credentials. Use an authenticated team URL
+or /mcp. Credentials belong only in the bearer header, never the URL. Configure
+transport trust through the environment's certificate store when using a private CA.
+
+Each call owns its SDK session, initialization and transport cleanup. The default
+190-second total deadline allows the server's bounded 180-second write processing.
+A shorter positive finite timeout is supported through the timeout constructor
+argument. The synchronous SyncDenseMemClient exposes the same methods and rejects
+use inside an active event loop.
+
+Methods are initialize, list_tools, remember, ingest_session, recall_memory and
+trace_memory. Requests/results are typed dictionaries with py.typed. Server
+validation and authenticated discovery remain authoritative. Current-server
+compatibility is dense-mem.v2.6.8, including server-supported historical terminal
+replay versions; this does not promise compatibility with older deployments.
+
+## Complete Remember request and safe replay
+
+~~~python
+from densemem import RememberRequest
+
+request: RememberRequest = {
+    "idempotency_key": retained_operation_key,
+    "evidence": [
+        {
+            "content": "Dense-Mem stores durable memory in PostgreSQL.",
+            "source_type": "manual",
+            "source": "Python core example",
+            "metadata": {"origin": "python-example"},
+        }
+    ],
+    "relationships": [
+        {
+            "ref": "durable-store",
+            "subject": {"name": "Dense-Mem", "entity_kind": "project"},
+            "predicate": {"proposed_key": "stores_durable_memory_in"},
+            "object": {"entity": {"name": "PostgreSQL", "entity_kind": "product"}},
+            "polarity": "+",
+            "evidence_indices": [0],
+        }
+    ],
+}
+result = await client.remember(request)
+~~~
+
+Create the operation key once for a deliberate new operation, and retain this
+entire request before sending it. For a replay, resend this unchanged request,
+including metadata and key. Never rotate a key to bypass a conflict. The client
+never retries automatically or fills in keys/defaults. Remember requires at least
+one proposal citing every evidence item. The client does not infer Relationships.
+
+Inspect evidence and relationship_results: completed processing can include
+not_stored proposals and remediation. Returned warnings remain visible. Recall
+results preserve server order, equivalent IDs, conflicts, topic communities,
+hypotheses, provenance, search states and degradations. These frontiers do not
+establish new factual support. Trace requires a returned relationship_id.
+
+## Exact private session ingestion
+
+~~~python
+from densemem import SessionRequest
+
+request: SessionRequest = {
+    "idempotency_key": retained_session_operation_key,
+    "framework": "generic",
+    "app_name": "python-example",
+    "user_id": "external-user-1",
+    "session_id": "session-1",
+    "events": [
+        {
+            "event_id": "user-event-1",
+            "text": "  Ari uses Go. café 🧭\n",
+            "occurred_at": "2026-10-11T12:00:00Z",
+        }
+    ],
+}
+result = await client.ingest_session(request)
+~~~
+
+Send only exact user-authored events. Event IDs/text/timestamps are immutable;
+the server owns chunking and extraction. External identifiers are provenance,
+never authorization or private-space selection. The server must enable session
+ingestion and the credential must have a writable private binding; discovery
+hides unavailable tools. Remember retains its separate proposal requirements.
+Session semantic acceptance is atomic across the request. A no-fact completed
+result with search_state not_required is valid.
+
+## Failures and unknown outcomes
+
+DenseMemAuthenticationError reports token acquisition or HTTP 401/403 failures.
+DenseMemTransportError reports network/HTTP failure. DenseMemProtocolError
+reports MCP/response failure. DenseMemOperationError preserves actionable public
+errors and failed receipts in result, with code, reason_code, retryable,
+next_action, remediation, correlation_id and submission_id when returned.
+DenseMemTimeoutError reports deadlines. DenseMemCancelledError subclasses
+asyncio.CancelledError and preserves a returned cancellation receipt if present.
+
+A local timeout, disconnect or cancellation can lose a response after a commit.
+An absent receipt means unknown outcome, not a fabricated failed submission.
+Recovery uses only the unchanged original request/key. There is no polling,
+status tool, background readiness loop or automatic new-key recovery.
+
+SDK 1.30 negotiates protocol 2025-11-25. Local cancellation closes the client's
+resources; the server can continue processing under this older protocol and may
+commit or reach its bounded deadline. Cancellation does not prove that a write
+was prevented. Retain the unchanged request/key for recovery.
+
+## Development and release
+
+Run packages/python/scripts/check.sh for lint/type/async tests, installed-wheel
+checks, reproducible wheel/sdist builds, vulnerability scanning and SBOM. Run
+packages/python/scripts/matrix.sh with a new output directory for the Python
+version matrix, and scripts/e2e.sh python_client for real server boundaries.
+The example scripts require DENSEMEM_ENDPOINT, DENSEMEM_TOKEN and a retained
+DENSEMEM_OPERATION_KEY. Keep the exact request unchanged when rerunning them.
+
+The server prerelease and stable-release workflows call publish-python to build
+and verify artifacts after their release gates pass, then upload through their own
+top-level publishing jobs. Manual recovery uploads directly from publish-python;
+the reusable invocation never uploads to PyPI. Only tags whose exact source belongs
+to merged main are eligible;
+PR branches cannot publish. Python shares the server release version: v2.6.6-rc.10
+becomes 2.6.6rc10 and v2.6.6 becomes 2.6.6. The checkout's 0.0.0 version is for local
+development; release builds stamp the selected tag's version and exact Source URL
+into artifact metadata without changing Git history.
+
+Change detection compares packages/python with the last successfully published
+Python source recorded on PyPI. Unchanged prereleases are skipped, and publishing
+a final version after a Python RC does not require another code change. Incomplete
+uploads remain eligible; retries verify every existing artifact's SHA-256 before
+uploading missing files. The manual publish-python workflow accepts the same shared
+tag for recovery. Never overwrite an existing version or silently accept different
+bytes; a broken prerelease may be yanked through a separate maintainer action.
+
+Verify control of the densemem PyPI name and register trusted publishers for
+markhuangai/dense-mem, workflows release-rc.yml, release.yml and publish-python.yml,
+each with environment pypi. For a new project, configure one pending publisher for
+the first publishing workflow; after it creates the project, register the other
+two as normal project publishers before using those paths. PyPI does not support
+reusable workflows as trusted publishers. This repository does not register
+publishers or change account settings. Release builds retain the
+installed-wheel/version matrix, reproducibility,
+vulnerability scan, SBOM and provenance gates.

densemem-2.6.6rc12/README.md

@@ -0,0 +1,167 @@
+# densemem Python client
+
+The Dense-Mem Python core client uses the official MCP SDK. It supports Python
+3.11–3.14 and MCP SDK 1.30 through the compatible 1.x line. This package is being
+prepared for release; PyPI publication is pending. Install a verified wheel:
+
+~~~bash
+python -m pip install /path/to/densemem-VERSION-py3-none-any.whl
+~~~
+
+ADK and LangChain adapters/extras will arrive with issues #220 and #221.
+The core installs neither framework.
+
+## Authentication and operations
+
+~~~python
+from densemem import DenseMemClient
+
+client = DenseMemClient("https://memory.example.com/teams/TEAM_UUID/mcp", token=api_key)
+tools = await client.list_tools()
+~~~
+
+Pass exactly one of token or token_provider. A provider is an async callable
+returning a caller-owned access token. The client resolves it once per operation;
+it does not acquire or refresh OAuth credentials. Use an authenticated team URL
+or /mcp. Credentials belong only in the bearer header, never the URL. Configure
+transport trust through the environment's certificate store when using a private CA.
+
+Each call owns its SDK session, initialization and transport cleanup. The default
+190-second total deadline allows the server's bounded 180-second write processing.
+A shorter positive finite timeout is supported through the timeout constructor
+argument. The synchronous SyncDenseMemClient exposes the same methods and rejects
+use inside an active event loop.
+
+Methods are initialize, list_tools, remember, ingest_session, recall_memory and
+trace_memory. Requests/results are typed dictionaries with py.typed. Server
+validation and authenticated discovery remain authoritative. Current-server
+compatibility is dense-mem.v2.6.8, including server-supported historical terminal
+replay versions; this does not promise compatibility with older deployments.
+
+## Complete Remember request and safe replay
+
+~~~python
+from densemem import RememberRequest
+
+request: RememberRequest = {
+    "idempotency_key": retained_operation_key,
+    "evidence": [
+        {
+            "content": "Dense-Mem stores durable memory in PostgreSQL.",
+            "source_type": "manual",
+            "source": "Python core example",
+            "metadata": {"origin": "python-example"},
+        }
+    ],
+    "relationships": [
+        {
+            "ref": "durable-store",
+            "subject": {"name": "Dense-Mem", "entity_kind": "project"},
+            "predicate": {"proposed_key": "stores_durable_memory_in"},
+            "object": {"entity": {"name": "PostgreSQL", "entity_kind": "product"}},
+            "polarity": "+",
+            "evidence_indices": [0],
+        }
+    ],
+}
+result = await client.remember(request)
+~~~
+
+Create the operation key once for a deliberate new operation, and retain this
+entire request before sending it. For a replay, resend this unchanged request,
+including metadata and key. Never rotate a key to bypass a conflict. The client
+never retries automatically or fills in keys/defaults. Remember requires at least
+one proposal citing every evidence item. The client does not infer Relationships.
+
+Inspect evidence and relationship_results: completed processing can include
+not_stored proposals and remediation. Returned warnings remain visible. Recall
+results preserve server order, equivalent IDs, conflicts, topic communities,
+hypotheses, provenance, search states and degradations. These frontiers do not
+establish new factual support. Trace requires a returned relationship_id.
+
+## Exact private session ingestion
+
+~~~python
+from densemem import SessionRequest
+
+request: SessionRequest = {
+    "idempotency_key": retained_session_operation_key,
+    "framework": "generic",
+    "app_name": "python-example",
+    "user_id": "external-user-1",
+    "session_id": "session-1",
+    "events": [
+        {
+            "event_id": "user-event-1",
+            "text": "  Ari uses Go. café 🧭\n",
+            "occurred_at": "2026-10-11T12:00:00Z",
+        }
+    ],
+}
+result = await client.ingest_session(request)
+~~~
+
+Send only exact user-authored events. Event IDs/text/timestamps are immutable;
+the server owns chunking and extraction. External identifiers are provenance,
+never authorization or private-space selection. The server must enable session
+ingestion and the credential must have a writable private binding; discovery
+hides unavailable tools. Remember retains its separate proposal requirements.
+Session semantic acceptance is atomic across the request. A no-fact completed
+result with search_state not_required is valid.
+
+## Failures and unknown outcomes
+
+DenseMemAuthenticationError reports token acquisition or HTTP 401/403 failures.
+DenseMemTransportError reports network/HTTP failure. DenseMemProtocolError
+reports MCP/response failure. DenseMemOperationError preserves actionable public
+errors and failed receipts in result, with code, reason_code, retryable,
+next_action, remediation, correlation_id and submission_id when returned.
+DenseMemTimeoutError reports deadlines. DenseMemCancelledError subclasses
+asyncio.CancelledError and preserves a returned cancellation receipt if present.
+
+A local timeout, disconnect or cancellation can lose a response after a commit.
+An absent receipt means unknown outcome, not a fabricated failed submission.
+Recovery uses only the unchanged original request/key. There is no polling,
+status tool, background readiness loop or automatic new-key recovery.
+
+SDK 1.30 negotiates protocol 2025-11-25. Local cancellation closes the client's
+resources; the server can continue processing under this older protocol and may
+commit or reach its bounded deadline. Cancellation does not prove that a write
+was prevented. Retain the unchanged request/key for recovery.
+
+## Development and release
+
+Run packages/python/scripts/check.sh for lint/type/async tests, installed-wheel
+checks, reproducible wheel/sdist builds, vulnerability scanning and SBOM. Run
+packages/python/scripts/matrix.sh with a new output directory for the Python
+version matrix, and scripts/e2e.sh python_client for real server boundaries.
+The example scripts require DENSEMEM_ENDPOINT, DENSEMEM_TOKEN and a retained
+DENSEMEM_OPERATION_KEY. Keep the exact request unchanged when rerunning them.
+
+The server prerelease and stable-release workflows call publish-python to build
+and verify artifacts after their release gates pass, then upload through their own
+top-level publishing jobs. Manual recovery uploads directly from publish-python;
+the reusable invocation never uploads to PyPI. Only tags whose exact source belongs
+to merged main are eligible;
+PR branches cannot publish. Python shares the server release version: v2.6.6-rc.10
+becomes 2.6.6rc10 and v2.6.6 becomes 2.6.6. The checkout's 0.0.0 version is for local
+development; release builds stamp the selected tag's version and exact Source URL
+into artifact metadata without changing Git history.
+
+Change detection compares packages/python with the last successfully published
+Python source recorded on PyPI. Unchanged prereleases are skipped, and publishing
+a final version after a Python RC does not require another code change. Incomplete
+uploads remain eligible; retries verify every existing artifact's SHA-256 before
+uploading missing files. The manual publish-python workflow accepts the same shared
+tag for recovery. Never overwrite an existing version or silently accept different
+bytes; a broken prerelease may be yanked through a separate maintainer action.
+
+Verify control of the densemem PyPI name and register trusted publishers for
+markhuangai/dense-mem, workflows release-rc.yml, release.yml and publish-python.yml,
+each with environment pypi. For a new project, configure one pending publisher for
+the first publishing workflow; after it creates the project, register the other
+two as normal project publishers before using those paths. PyPI does not support
+reusable workflows as trusted publishers. This repository does not register
+publishers or change account settings. Release builds retain the
+installed-wheel/version matrix, reproducibility,
+vulnerability scan, SBOM and provenance gates.

densemem-2.6.6rc12/examples/remember.py

@@ -0,0 +1,46 @@
+import asyncio
+import os
+
+from densemem import DenseMemClient, RememberRequest, RememberResult
+
+
+def make_request(key: str) -> RememberRequest:
+    return {
+        "idempotency_key": key,
+        "evidence": [
+            {
+                "content": "Dense-Mem stores durable memory in PostgreSQL.",
+                "source_type": "manual",
+                "source": "Python core example",
+                "metadata": {"origin": "python-example"},
+            }
+        ],
+        "relationships": [
+            {
+                "ref": "durable-store",
+                "subject": {"name": "Dense-Mem", "entity_kind": "project"},
+                "predicate": {"proposed_key": "stores_durable_memory_in"},
+                "object": {"entity": {"name": "PostgreSQL", "entity_kind": "product"}},
+                "polarity": "+",
+                "evidence_indices": [0],
+            }
+        ],
+    }
+
+
+async def run(client: DenseMemClient, key: str) -> RememberResult:
+    request = make_request(key)
+    result = await client.remember(request)
+    replay = await client.remember(request)
+    assert replay == result
+    await client.recall_memory({"query": "Dense-Mem durable memory PostgreSQL", "limit": 5})
+    for proposal in result["relationship_results"]:
+        for split in proposal["splits"]:
+            await client.trace_memory({"relationship_id": split["relationship_id"]})
+    return result
+
+
+if __name__ == "__main__":
+    client = DenseMemClient(os.environ["DENSEMEM_ENDPOINT"], token=os.environ["DENSEMEM_TOKEN"])
+    result = asyncio.run(run(client, os.environ["DENSEMEM_OPERATION_KEY"]))
+    print(result["processing_state"])