rdmsm4x-changelog-20260827-1605-mem0-status-published-to-dev-dataroo-net

Published a protected, sanitized Mem0 Local architecture and readiness page to dev.dataroo.net so the accepted runtime, privacy boundary, test evidence, and unfinished client gates have one durable operational reference.

Scope

• Host: rdmsm4x.
• Source project: /Users/richh/dev/sites/dev.dataroo.net.
• Isolated worktree: /Users/richh/dev/_worktrees/dev-dataroo-net/codex-mem0-dashboard-20260827.
• Branch: codex/mem0-dashboard-20260827.
• Release commit: ccfea216abb7db88d505c3a0dd6844b7946ad6a6.
• Protected route: https://dev.dataroo.net/mem0/.
• No authentication, Cloudflare, nginx, Mem0 runtime, model, client, credential, memory, or database configuration was changed.

Files changed

• /Users/richh/dev/_worktrees/dev-dataroo-net/codex-mem0-dashboard-20260827/sites/mem0-status/index.html
• /Users/richh/dev/_worktrees/dev-dataroo-net/codex-mem0-dashboard-20260827/sites/mem0-status/README.md
• /Users/richh/dev/_worktrees/dev-dataroo-net/codex-mem0-dashboard-20260827/sites/mem0-status/publish_mem0_status.zsh
• /Users/richh/dev/_worktrees/dev-dataroo-net/codex-mem0-dashboard-20260827/tests/test_mem0_status_dashboard.py
• /Users/richh/dataroo.net/wiki/mem0/index.html
• /Users/richh/.agent-coordination/checkins/codex-rdmsm4x-devsite-mem0-status-20260827.json
• /Users/richh/Library/Mobile Documents/com~apple~CloudDocs/Codex/projects/AGENTS.md principles/PROJECTS.md

Published content and privacy boundary

• Documents the loopback-only Mem0 API, private Qdrant collection, native loopback Ollama, authenticated SSH-stdio MCP bridge, explicit-literal infer=false default, deliberate infer=true path, accepted model digests, release evidence, recovery posture, client matrix, and remaining rollout gates.
• Contains no memory bodies, prompts, provider credentials, tokens, private filesystem paths, peer hostnames, or raw agent histories.
• Keeps the public route behind the existing Basic-auth boundary. No remote Mem0, Qdrant, MCP, or Ollama port was exposed.

Commands and verification

• Created the isolated Git worktree from site commit 4ea83f0a185b1cb7ebb0caa88555e19f86ab270b.
• Ran /usr/bin/python3 -m unittest -v tests.test_mem0_status_dashboard: 7 passed.
• Ran /usr/bin/python3 -m unittest discover -s tests -v: 37 passed.
• Ran zsh -n sites/mem0-status/publish_mem0_status.zsh: passed.
• Ran git diff --check: passed.
• Ran the one-command publisher after fixing its first verification-path defect.
• Verified source and deployed SHA-256 are identical: bcfc0d420104ceaa2222db02fb63f88987df03a887eb285e7adb140c22df4d12.
• Verified the local origin returned HTTP 200 with HTML at http://127.0.0.1:8787/mem0/.
• Verified the unauthenticated public route returned HTTP 401 at https://dev.dataroo.net/mem0/.
• Verified Mem0 health remained ok with mem0_shared_v1, 2,560 dimensions, and explicit_literal capture.
• Verified dataroo-wiki-server-1, dataroo-auth_proxy-1, mem0-api, and mem0-qdrant remained healthy.

Incidents and preserved evidence

• Invoking /Users/richh/dev/scripts/dr_export.py --help during read-only CLI inspection triggered that tool's normal site-shell refresh because it has no help handler. It reported one page added, 20 updated, 18 unchanged. The site-shell owner was notified through the fleet bus, no rollback was attempted, and the utility was not invoked again.
• The first Mem0 publisher run installed the new route but then stopped because status is a read-only zsh variable. There was no prior /mem0/ route, so no user data was overwritten or lost. The variable was renamed to http_status; the second run backed up the first install and completed the full atomic publish and verification path.

Backup and rollback

• Rollback record: /Users/richh/dev/_backups/devsite-mem0-status/20260827-160050/rollback.txt.
• Preserved previous route copy: /Users/richh/dev/_backups/devsite-mem0-status/20260827-160050/mem0.
• To undo: move /Users/richh/dataroo.net/wiki/mem0 aside, then move the preserved mem0 directory from the backup into /Users/richh/dataroo.net/wiki/mem0.
• The protected site and Mem0 services require no restart for this rollback.

Outstanding actions

• The documentation source remains on the isolated branch and is not merged or pushed; canonical source integration is a separate gate.
• The page correctly retains Codex fresh-session discovery, Claude Desktop restart, Antigravity canary, and one unreachable peer as incomplete states.
• The site-shell owner may reconcile the incidental shell refresh with their active source lane if needed.