Fix CodeRabbit review issues: localEnv forwarding, docs, README accuracy

- Use ${localEnv:TERM:xterm-256color} in remoteEnv to preserve host TERM
  (e.g., xterm-kitty) instead of unconditionally overriding it
- Document TERM and COLORTERM in CLAUDE.md Environment section
- Update kitty-terminfo README to clarify VS Code vs non-VS Code behavior
- Update CHANGELOG to reflect all fixes

Author: AnExiledDev

.devcontainer/CHANGELOG.md

@@ -11,9 +11,11 @@
 - **Regex lookbehinds** — replaced alternation inside lookbehinds (`(?<=[\s(]|^)` and `(?<=commit |merge |...)`) with non-capturing groups containing individual lookbehinds (`(?:(?<=[\s(])|^)` and `(?:(?<=commit )|(?<=merge )|...)`) for PCRE2 compatibility
 
 #### Terminal Color Support
-- **devcontainer.json** — added `TERM=xterm-256color` and `COLORTERM=truecolor` to `remoteEnv`; Docker defaults to `TERM=xterm` (8 colors) which caused Claude Code and other CLI tools to downgrade rendering
+- **devcontainer.json** — added `TERM` and `COLORTERM=truecolor` to `remoteEnv`; Docker defaults to `TERM=xterm` (8 colors) which caused Claude Code and other CLI tools to downgrade rendering
+- **devcontainer.json** — `TERM` uses `${localEnv:TERM:xterm-256color}` to forward the host terminal type (e.g., `xterm-kitty`) instead of unconditionally overriding it
 - **setup-aliases.sh** — added terminal color defaults to managed shell block so tmux panes, `docker exec`, and SSH sessions also get 256-color and truecolor support
-- **kitty-terminfo/README.md** — updated documentation to reflect container terminal color defaults
+- **kitty-terminfo/README.md** — updated documentation to reflect `localEnv` forwarding and clarify behavior across VS Code vs non-VS Code entry points
+- **CLAUDE.md** — documented `TERM` and `COLORTERM` environment variables in the Environment section
 
 ### Removed
 

.devcontainer/CLAUDE.md

@@ -79,6 +79,8 @@ Rules in `config/defaults/rules/` deploy to `.claude/rules/` on every container
 | `CLAUDE_CONFIG_DIR` | `/workspaces/.claude` |
 | `ANTHROPIC_MODEL` | `claude-opus-4-6` |
 | `WORKSPACE_ROOT` | `/workspaces` |
+| `TERM` | `${localEnv:TERM:xterm-256color}` (via `remoteEnv` — forwards host TERM, falls back to 256-color) |
+| `COLORTERM` | `truecolor` (via `remoteEnv` — enables 24-bit color support) |
 
 All experimental feature flags are in `settings.json` under `env`. Setup steps controlled by boolean flags in `.env`.
 

.devcontainer/devcontainer.json

@@ -10,7 +10,7 @@
 		"CLAUDE_CONFIG_DIR": "/workspaces/.claude",
 		"GH_CONFIG_DIR": "/workspaces/.gh",
 		"TMPDIR": "/workspaces/.tmp",
-		"TERM": "xterm-256color",
+		"TERM": "${localEnv:TERM:xterm-256color}",
 		"COLORTERM": "truecolor",
 		"CLAUDECODE": null
 	},

.devcontainer/features/kitty-terminfo/README.md

@@ -16,7 +16,7 @@ Downloads and compiles the official kitty terminfo entry from the [Kitty termina
 
 The container defaults to `TERM=xterm-256color` with `COLORTERM=truecolor`, which provides full 256-color and 24-bit truecolor support for all terminals.
 
-For Kitty users: if your host terminal forwards `TERM=xterm-kitty` into the container, the installed terminfo ensures full Kitty-specific capability support (correct `bce` behavior, status line, etc.). If not forwarded, `xterm-256color` provides equivalent color rendering.
+For Kitty users: the `devcontainer.json` `remoteEnv` uses `${localEnv:TERM:xterm-256color}`, which forwards your host `TERM` into VS Code sessions. If your host sets `TERM=xterm-kitty`, the installed terminfo ensures full Kitty-specific capability support (correct `bce` behavior, status line, etc.). For non-VS Code entry points (tmux, `docker exec`, SSH), `setup-aliases.sh` upgrades `TERM=xterm` to `xterm-256color` but preserves any other value. If no Kitty TERM is forwarded, `xterm-256color` provides equivalent color rendering.
 
 ```bash
 # Verify installation