rdmbair15m5-changelog-20260831-1716-rdworkbench-mcp-retirement

Removed the final RDWorkbench MCP registrations from the canary because Tyrell.app is now the replacement, while preserving RDWorkbench data and all unrelated MCP state.

Scope

• Host: rdmbair15m5
• Fleet task: TASK-20260831-16
• Fleet verification: all six Macs

Exact files changed

• /Users/richh/.codex/config.toml — removed the rdworkbench MCP table only.
• /Users/richh/.claude.json — removed the rdworkbench MCP registration/references only.
• /Users/richh/Library/Application Support/MCPFleetRemoval/backups/20260831-1703/manifest.json
• Private pre-change backups beneath /Users/richh/Library/Application Support/MCPFleetRemoval/backups/20260831-1703/
• /Users/richh/.agent-coordination/checkins/codex-rdmbair15m5-rdworkbench-mcp-removal-20260831.json
• /Users/richh/dev/_handoff/rdworkbench-mcp-removal/ — transformer, tests, report, and changelog staging.
• iCloud operating PROJECTS.md — added the 2026-08-31 retirement milestone.

Commands run

• Python transformer unit tests and py_compile.
• Transformer --dry-run, canary --apply, and idempotent second --dry-run.
• Fresh codex mcp list, claude mcp list, and agy mcp list checks.
• Six-host semantic config, manifest, alternate MCP path, project .mcp.json, and runtime-process probes over authenticated SSH.
• zsh ~/scripts/notes_changelog.zsh <this-file> for the Apple Notes copy.

Verification

• Focused transformer tests: 4/4 passed.
• Final six-host dry-run: zero changed files on 6/6.
• Fresh Codex and Claude listings: RDWorkbench absent, Tyrell present on 6/6.
• Fresh agy listings: RDWorkbench absent on 6/6; existing Tyrell placement preserved.
• No RDWorkbench MCP process or extra/project MCP config matched.
• Manifest mode 0600; backup directory mode 0700; both canary backup hashes match the manifest.

Backup and undo

• Backup root: /Users/richh/Library/Application Support/MCPFleetRemoval/backups/20260831-1703/
• Undo with the transformer --rollback against that manifest on rdmbair15m5; this intentionally restores RDWorkbench registration and should be used only if the retirement decision is reversed.

Outstanding owner actions

• None for MCP removal. Normal restart of already-open clients is sufficient if any UI cached an old registry; no active RDWorkbench MCP child remained at verification time.