lobotomized-claude-code-updatelisted

# lobotomized-claude-code-update Upgrades a lobotomized Claude Code install in two gated stages. Stage 1 reports what would change and stops; Stage 2 performs the upgrade only after the user explicitly approves. The split exists because the upgrade touches three independently-versioned pieces plus an in-place binary patch - an unreviewed surprise here leaves the user with a broken `claude`. If the user has already seen a Stage 1 report in this conversation and approved it, skip straight to Stage 2. ## The stack Three pieces, version-pinned to each other: | Piece | Location | Upstream | |---|---|---| | Claude Code binary | `~/.local/share/claude/versions/`, installed via `claude install <version>` | Anthropic | | LCC overrides (~400 `.md` files) | `~/.tweakcc/lobotomized-claude-code/` | `skrabe/lobotomized-claude-code` | | tweakcc-fixed (the patcher) | wherever `skrabe/tweakcc-fixed` was cloned (README default `~/dev/tweakcc-fixed`) | `skrabe/tweakcc-fixed` | `~/.tweakcc/system-prompts` and `~/.tweakcc/system-reminders` are symlinks into the LCC clone. The patcher splices LCC's overrides into the CC binary's `cli.js` with `node <tweakcc-fixed>/dist/index.mjs --apply`. Use **skrabe's** tweakcc-fixed only. The npm `tweakcc-fixed` package (a different fork) and upstream `Piebald-AI/tweakcc` lack the `inlineBlobOverrides` and `systemReminderOverrides` mechanisms that the LCC `inline-*.md` and `system-reminders/*.md` overrides depend on - a different patcher silently disable