feat: release MemoryMaster 4.5 governed core

[wolverin0]

Summary

• completes the governed-core remediation roadmap through Phase 4
• makes personal/local SQLite the production default; Qdrant is optional and Postgres/team is deferred
• hardens retrieval, lifecycle, capture, persistence, service boundaries, recovery, and dashboard governance
• prepares the verified 4.5.0 wheel/sdist publication path

Provenance

This two-commit production branch is derived from the audited remediation branch. Its final Git tree exactly matches 2cde4e3; the detailed atomic remediation history remains preserved on remediation/phase2-governed-core-20260712.

Local release evidence

• clean checkout: 84 focused release tests passed
• project Ruff passed
• generated release truth passed
• wheel and sdist built; Twine validation passed
• clean minimal CLI and MCP-extra wheel smokes passed
• Gitleaks 8.21.2: 797 reachable commits, zero unreviewed findings
• strict OSV audit: 36 minimal-profile dependencies, zero known vulnerabilities

Verification note

The monolithic local non-ML suite exceeded its 15-minute cap without captured failures. This PR must not merge until the split GitHub Linux/Windows matrix and required gates pass.

Deferred optional-profile evidence

Authenticated/TLS Qdrant, Postgres team mode, and Kubernetes/container proof remain explicitly documented as optional-profile BLOCKED-EXTERNAL items and do not describe the default SQLite package profile.

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
27665726	Triggered	Generic Password	d0490e9	docker-compose.postgres.yml	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[wolverin0]

Superseded by #188, which preserves the same audited final tree without the GitGuardian-tainted intermediate commit history.