Created the canonical privacy-gated local-LLM benchmark lane, committed it, and deployed its exact dashboard to the protected development site.

Scope and canonical files

• Canonical worktree: /Users/richh/dev/_worktrees/codex-local-llm-20260823/local-llm-fleet.
• Branch/commit: codex/local-llm-dashboard-20260823 at 5f3ae74 (Add privacy-gated local LLM fleet benchmarks).
• Added benchmark/model installer and dashboard generator scripts, six sanitized JSON artifacts, tests, and dashboard/index.html.
• Deployed the exact HTML to /Users/richh/dataroo.net/wiki/localLLM/index.html; this was a new route, so no prior file required backup.
• Reconciled the managed Claude/Codex/Gemini path blocks and fixed Datacloud MCP extension paths from absent 0.7.2 to installed 0.9.1; backup: /Users/richh/.agent-coordination/backups/gemini-mcp-path-20260823T024402.
• Repaired an empty Gemini MCP JSON to {"mcpServers": {}}; backup: /Users/richh/.agent-coordination/backups/gemini-mcp-empty-repair-20260823T024534.

Maintenance, models, and benchmarks

• Completed /Users/richh/dev_update.zsh; no outdated formulae or greedy casks remained. brew doctor reports only the expected macOS 27 Tier-2 notice.
• Verified Claude Code 2.1.241 via its exact cask path, Codex 0.149.0, agy 1.1.19, Antigravity 2.9.1, Antigravity IDE 2.5.5, and Ollama 0.32.15.
• Installed and benchmarked qwen3.8:27b-mlx on the M4 Max/128 GB host with deterministic synthetic prompts.
• Commands: python3 -m unittest discover -s tests -v (45 passed), swift test --scratch-path /tmp/local-llm-swift-test-20260823 (10 passed), and python3 tools/policy_check.py --json . ([]).

Deployment verification

• Source and deployed SHA-256 both equal c68266538815f8c56ee77c6b21779c495d94f7aa3655666b0d1819bb442c52c4.
• wiki-server served 11,839 bytes internally and contained the required GPUs selected 1/4 disclosure.
• Docker services were running and healthy; https://dev.dataroo.net/localLLM/ returned HTTP 401 without existing Basic-auth credentials, confirming the protected route.
• Six-host topology audit passed and provider account stores remained separate.

Undo

• Revert source changes with a normal git revert 5f3ae74 on the task branch after review; do not reset the canonical repository.
• Remove the new deployed route only after an owner decision, or replace it with a reviewed prior artifact if one is later added.
• Restore Gemini configuration from the dated backups above if the current installed extension regresses.

Outstanding owner actions

• Complete per-host Ollama sign-in in the proper account lanes if desired.
• Review and push the local canonical commits when ready; this run did not publish Git branches remotely.