rdmsm4x-changelog-20260826-1955-litellm-root-checkpoint

Persisted a secret-free, compact-safe LiteLLM project checkpoint at Richh's new canonical folder so later work resumes from verified roots, live service evidence, and explicit safety gates rather than migrating or deploying by assumption.

Scope

• Host changed: rdmsm4x only.
• Project root: /Users/richh/dev/localAI/litellm.
• Change class: documentation and coordination state only.
• No provider request, credential use/storage, installation, process/container change, database mutation, network binding, client reroute, Git initialization, worktree repair, remote-host write, or publication occurred.
• The canonical shared PROJECTS.md was not edited because the overlapping path transitioned from the completed Mem0 checkpoint to an active Buzz checkpoint.

Exact files touched

Created:

• /Users/richh/dev/localAI/litellm/.gitignore
• /Users/richh/dev/localAI/litellm/AGENTS.md
• /Users/richh/dev/localAI/litellm/README.md
• /Users/richh/dev/localAI/litellm/SESSION-STATE.md
• /Users/richh/dev/localAI/litellm/ISSUES.md
• /Users/richh/dev/localAI/litellm/docs/architecture-and-routing-design-2026-08-26.md
• /Users/richh/.agent-coordination/checkins/codex-litellm-root-persistence-20260826.json
• /Users/richh/dev/LLM/Claude/changelogs/rdmsm4x-changelog-20260826-1955-litellm-root-checkpoint.md

Created directory:

• /Users/richh/dev/localAI/litellm/docs

Before / after / delta

• Before: the new project root existed as an empty, non-Git directory; the former /Users/richh/dev/litellm path was absent.
• After: the new root contains six project-local files defining production boundaries, current evidence, open issues, proposed architecture, and a compact resume capsule.
• Delta: files and coordination evidence only. Existing repositories, services, databases, credentials, and client configurations are unchanged.

Read-only commands and checks run

• scutil --get ComputerName
• pwd, find, stat, and absolute-path ls checks for the old/new roots and related candidates.
• git rev-parse, git branch --show-current, git status --porcelain, and git worktree list --porcelain against related repositories.
• AGENT_LLM=codex ~/.agent-coordination/agent_msg.zsh whoami
• AGENT_LLM=codex ~/.agent-coordination/agent_msg.zsh inbox --unread
• /Users/richh/dev/fleet/maintenance/scripts/fleet_checkin_sync.zsh
• docker ps, selected non-secret docker inspect Compose labels, and a read-only PostgreSQL size/spend-row count query.
• lsof for TCP ports 4000, 8088, and 11434.
• loopback curl health probes for LiteLLM, Open WebUI, and Ollama.
• key-name-only inspection of /Users/richh/.secrets/global.env; no values were read or printed.
• jq validation of the coordination check-in.
• bounded rg scans for required checkpoint markers, balanced Markdown fence counting, and absence of an OpenRouter credential pattern.
• shasum -a 256 for the six project files.

Verification evidence

• Executing host resolved to rdmsm4x.
• Six of six expected project files exist and are nonempty.
• Project file count is exactly six.
• Project root remains non-Git.
• Coordination JSON parses as schema version 1, references the exact new root, and excludes the collision-owned PROJECTS.md path.
• Every Markdown file has balanced fenced-code markers.
• Required markers record the absent old root, the documentation-only delta, and the design's unapproved state.
• The bounded scan found no OpenRouter credential-pattern match in the project files or coordination check-in.
• Live LiteLLM health remained unavailable on TCP 4000; no LiteLLM process was found.
• Open WebUI returned HTTP 200 on loopback TCP 8088.
• Ollama returned HTTP 200 on loopback TCP 11434 and reported 10 models.
• local-llm-postgres remained healthy; a read-only query reported a 12,053,651-byte database and 33 LiteLLM spend-log rows.

Final project-file SHA-256 values:

789be6920ec88c61ee7711e6f08d7837f130fb3243f8f52b62afe7b9dbd0c1fa  .gitignore
f96fec1a42482581fcb11f53c534fd699e675402277b66582ea8e6d34659a42b  AGENTS.md
b2b34f60b5b3a768ab2e64607df206a167506e7803db44e3e96f9ea177d012dc  README.md
e2cefe644e46212d7e9037411b219999586b1c42e831cd4894f32cab4a30791c  SESSION-STATE.md
52386b56d5b7a61d69f3855412eb2a4cc329ac17fd0835829862ecd9b656e44d  ISSUES.md
8cf50e67f8972b95ceb8c9ae467fe2ee18118b05ef2c35b37a4226a78b285b31  docs/architecture-and-routing-design-2026-08-26.md

Preserved state and backup locations

• No backup of the new root was necessary because it was verified empty before the additive write.
• Existing PostgreSQL data was not changed; a verified database backup remains a required gate before adoption or migration.
• The clean related Git repository remains at /Users/richh/dev/ai/localAI/local-llm-fleet on main HEAD 53a297a7f8a75f56b0c08d86dae1fc27bd6c2088.
• The registered linked-worktree ref/HEAD was preserved and not repaired or pruned.
• The legacy dirty /Users/richh/dev/ai/LLM repository and its LiteLLM material were left untouched.

How to undo

Archive the six newly created project files and the new docs directory to a timestamped recovery folder, then remove only the now-empty project directory if Richh no longer wants this project root. Separately mark the coordination check-in superseded. Do not delete or alter the existing PostgreSQL container/data, clean local-LLM repository, registered linked-worktree ref, legacy LiteLLM tree, shared secret store, or other localAI sibling folders.

Outstanding owner actions

1. Revoke and replace the OpenRouter credential that appeared in chat; never reuse the exposed value.
2. Review and approve or revise the proposed design.
3. Create and restore-test a PostgreSQL backup before any runtime adoption.
4. Reconcile source authority among the clean local-LLM config, legacy LiteLLM material, and historical Compose origin.
5. Resolve the broken linked worktree in a separately owned localLLM task.
6. Add the new project to the canonical PROJECTS.md after every active writer, currently the Buzz checkpoint, releases that shared file.
7. Update Codex's stale trusted-project path through a backed-up, separately verified config change.

Apple Notes mirror

Target folder: rdmsm4x. The publishing command is:

zsh /Users/richh/scripts/notes_changelog.zsh /Users/richh/dev/LLM/Claude/changelogs/rdmsm4x-changelog-20260826-1955-litellm-root-checkpoint.md

The command ran once from an Aqua session. It returned exit 0, reported Notes responsive, and reported the note filed at 2026-08-26 19:56 EDT. A fleet warning read after publication documents an unresolved count-dependent deletion hazard in this shared script during Notes cold-start stalls. This run did not report a stall or deletion, but it was not rerun after this disk addendum and no count-based note-store safety claim is made.