chore(release): 3.7.1

[igorls]

Summary

Prepare the 3.7.1 patch release on develop. Version sources, lock, README badge, OpenClaw skill, and changelog all agree on 3.7.1.

This is the version-bump PR only. After review and merge here, promote with a second PR: develop → main (same path as #2129). Do not push the bump or the tag directly to main.

In 3.7.1 (already on develop via #2228)

• mempalace mine hangs forever on a named pipe in the mined directory (sweep, init, compress and split too) #2221 — ingest never hangs on a named pipe / non-regular file
• fix(miner): close four re-mine safety gaps in process_file #2088 / A failed upsert sub-batch marks the file fully mined, so the retry never happens #2122 / fix(miner): retry after partial batch upsert failure #2151 — project re-mine completeness (chunk_total, same-fstat mtime, purge abort, partial-batch cleanup)
• mine --mode convos: file-level already-filed tracking can silently skip individual exchanges from an already-mined transcript #2183 — conversation mine completeness parity
• _get_client() reconnect leaves the stale Chroma segment live: a peer writer's persist destroys already-indexed records (index count goes backwards) #2002 / ChromaBackend._client() inode/mtime reopen rebuilds without a chromadb system-cache reset (parallel to #2002) #2028 — drop chromadb SharedSystemClient cache on reconnect (no HNSW rewind)
• Palace write lock not released on SIGTERM/SIGHUP (only registered via atexit) #2205 — SIGTERM/SIGHUP releases the palace writer lease

Version sources (must match)

Source	Version
mempalace/version.py	3.7.1
pyproject.toml	3.7.1
.claude-plugin/marketplace.json	3.7.1
.claude-plugin/plugin.json	3.7.1
.codex-plugin/plugin.json	3.7.1

Entry-point check: mempalace-mcp = mempalace.mcp_server:main still matches plugin configs.

After this lands on develop

1. Open develop → main as a normal PR (branch protection, reviews, CI). Title e.g. Release v3.7.1 — promote develop to main.
2. Merge that PR through the usual checks — no force-push, no admin bypass.
3. On GitHub: Releases → Draft a new release
   • Target: main
   • Tag: v3.7.1 (must match version.py)
   • Notes: fold from CHANGELOG.md [3.7.1]
4. Publish the release. publish.yml builds, then waits for pypi environment approval.

Test plan

• Five version sources agree
• Changelog folded: Unreleased empty, [3.7.1] — 2026-08-12 + compare links
• README badge + OpenClaw skill + uv.lock package version bumped
• version-guard.yml green on this PR
• CI green (lint / linux / macos / windows)

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.