litclaude-ai 0.3.0 → 0.3.1

package/CHANGELOG.md

@@ -1,5 +1,14 @@
 # Changelog
 
+## 0.3.1 - 2026-06-14 — neon-HUD truecolor detection on Windows Terminal / WSL2
+
+- Fix the `[🔥LITCLAUDE]` HUD falling back to flat 256-color magenta in Windows Terminal under WSL2.
+  `supportsTruecolor` now also recognizes `WT_SESSION` (Windows Terminal, including WSL2, renders
+  24-bit color but does not export `COLORTERM` into the shell), common 24-bit terminal programs
+  (`TERM_PROGRAM` = vscode/hyper/wezterm/ghostty/iTerm.app), and direct-color terminfo entries
+  (`TERM` matching `-direct`/`truecolor`). Terminals that export `COLORTERM=truecolor|24bit` are
+  unchanged; genuine 256-color terminals still get the magenta fallback.
+
 ## 0.3.0 - 2026-06-14 — LitClaude rebrand + lit-family vocab + neon HUD
 
 - Rename `ulw`/`ultra*` trigger vocabulary to the **lit family**: `lit`, `litwork`, `lit-loop`,

package/README.md

@@ -9,7 +9,7 @@
 </p>
 <p align="center">
   <img src="https://img.shields.io/badge/npm-litclaude--ai-cb3837" />
-  <img src="https://img.shields.io/badge/version-0.3.0-2ea44f" />
+  <img src="https://img.shields.io/badge/version-0.3.1-2ea44f" />
   <img src="https://img.shields.io/badge/Claude%20Code-plugin-blueviolet" />
   <img src="https://img.shields.io/badge/license-MIT-blue" />
 </p>
@@ -22,10 +22,10 @@
 > `litclaude@litclaude-ai`, so normal `claude` launches can load the
 > LitClaude skills and hooks without a long `--plugin-dir` command.
 
-This checkout is prepared as `litclaude-ai@0.3.0` for personal install
+This checkout is prepared as `litclaude-ai@0.3.1` for personal install
 convenience. The repo can remain quiet; preparing npm package metadata here does
 not imply public repo promotion, marketplace publication, or advertisement.
-Future package releases still require explicit user approval. The v0.3.0
+Future package releases still require explicit user approval. The v0.3.1
 release materials preserve the v0.2.2 Dynamic workflow hardening work, add the
 lit-family vocab rename and neon HUD on top of v0.2.2, describe LitClaude in
 its own terms, and do not claim that npm publication has completed.
@@ -93,7 +93,7 @@ directory, the normal install command works:
 
 ```bash
 cd /tmp
-npx --yes litclaude-ai@0.3.0 install
+npx --yes litclaude-ai@0.3.1 install
 ```
 
 Validate the installed plugin:
@@ -106,7 +106,7 @@ The installer also sets Claude Code's `statusLine` command to the packaged
 LitClaude HUD. A typical no-color render starts like:
 
 ```text
-[🔥LITCLAUDE v0.3.0] | O4.8 │ ctx [▎░░] 9%/1000k │ 5h [▏░] 4% ↻2h15m │ 1w [▊░] 35% ↻3d6h │ git main +3 ✓
+[🔥LITCLAUDE v0.3.1] | O4.8 │ ctx [▎░░] 9%/1000k │ 5h [▏░] 4% ↻2h15m │ 1w [▊░] 35% ↻3d6h │ git main +3 ✓
 ```
 
 The `↻` suffix is a compact rate-limit reset countdown. It is separated from

package/README_ko-KR.md

@@ -9,7 +9,7 @@
 </p>
 <p align="center">
   <img src="https://img.shields.io/badge/npm-litclaude--ai-cb3837" />
-  <img src="https://img.shields.io/badge/version-0.3.0-2ea44f" />
+  <img src="https://img.shields.io/badge/version-0.3.1-2ea44f" />
   <img src="https://img.shields.io/badge/Claude%20Code-plugin-blueviolet" />
   <img src="https://img.shields.io/badge/license-MIT-blue" />
 </p>
@@ -26,11 +26,11 @@
 > 설치되므로, 매번 긴 `--plugin-dir` 없이 일반 `claude` 실행에서
 > LitClaude skill과 hook을 불러올 수 있습니다.
 
-현재 checkout은 `litclaude-ai@0.3.0` 배포 준비용으로 정리되어 있습니다. 목적은
+현재 checkout은 `litclaude-ai@0.3.1` 배포 준비용으로 정리되어 있습니다. 목적은
 다른 PC에서도 빠르게 설치하기 위한 개인용 package metadata를 갖추는 것입니다.
 npm package metadata를 준비했다고 해서 홍보, 공개 저장소 운영, Claude
 marketplace 등록을 의미하지는 않습니다. 새 버전 배포는 항상 별도의 명시적
-승인 후에 진행합니다. v0.3.0 release material은 v0.2.2 Dynamic workflow
+승인 후에 진행합니다. v0.3.1 release material은 v0.2.2 Dynamic workflow
 hardening을 보존하고, lit-family vocab rename과 neon HUD를 추가하며,
 LitClaude 자체의 표현으로 정리되어 있습니다. npm publish가 완료됐다고
 주장하지 않습니다.
@@ -98,7 +98,7 @@ checkout을 먼저 해석해서 `sh: litclaude-ai: command not found`로 실패
 
 ```bash
 cd /tmp
-npx --yes litclaude-ai@0.3.0 install
+npx --yes litclaude-ai@0.3.1 install
 ```
 
 설치 상태를 확인합니다.
@@ -111,7 +111,7 @@ installer는 Claude Code의 `statusLine` command도 packaged LitClaude HUD로
 설정합니다. 색상을 제거한 예시는 다음처럼 시작합니다.
 
 ```text
-[🔥LITCLAUDE v0.3.0] | O4.8 │ ctx [▎░░] 9%/1000k │ 5h [▏░] 4% ↻2h15m │ 1w [▊░] 35% ↻3d6h │ git main +3 ✓
+[🔥LITCLAUDE v0.3.1] | O4.8 │ ctx [▎░░] 9%/1000k │ 5h [▏░] 4% ↻2h15m │ 1w [▊░] 35% ↻3d6h │ git main +3 ✓
 ```
 
 `↻` 표시는 rate-limit reset까지 남은 시간을 짧게 보여주는 countdown입니다.

package/RELEASE_CHECKLIST.md

@@ -1,8 +1,9 @@
 # LitClaude Release Checklist
 
-Status: `litclaude-ai@0.3.0` is the current release candidate for the lit-family vocab rename and neon HUD.
-`package.json` is aligned to `0.3.0`, and
-`plugins/litclaude/.claude-plugin/plugin.json` is aligned to `0.3.0`.
+Status: `litclaude-ai@0.3.1` is the current release candidate — a patch that fixes neon-HUD truecolor
+detection on Windows Terminal / WSL2 (and other 24-bit terminals that do not export `COLORTERM`).
+`package.json` is aligned to `0.3.1`, and
+`plugins/litclaude/.claude-plugin/plugin.json` is aligned to `0.3.1`.
 
 This release carries the v0.2.2 Dynamic workflow hardening surfaces:
 `/dynamic-workflow`, `workflow-check --json`, native `/goal` fallback guidance,
@@ -51,8 +52,8 @@ No npm publication is required for this track.
 Before requesting publication approval, confirm these artifacts from the current
 checkout:
 
-- `package.json` version is `0.3.0`.
-- `plugins/litclaude/.claude-plugin/plugin.json` version is `0.3.0`.
+- `package.json` version is `0.3.1`.
+- `plugins/litclaude/.claude-plugin/plugin.json` version is `0.3.1`.
 - `plugins/litclaude/commands/dynamic-workflow.md` documents subagent delegation.
 - `node bin/litclaude-ai.js workflow-check --json` reports `status: pass`.
 - `node bin/litclaude-ai.js workflow-check --json` reports

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "litclaude-ai",
-  "version": "0.3.0",
+  "version": "0.3.1",
   "description": "Claude Code-native workflow distribution.",
   "type": "module",
   "bin": {

package/plugins/litclaude/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "litclaude",
   "description": "Claude Code-native workflow plugin.",
-  "version": "0.3.0",
+  "version": "0.3.1",
   "author": {
     "name": "LitClaude contributors"
   },

package/plugins/litclaude/lib/hud-accent-palette.mjs

@@ -34,8 +34,19 @@ const NEON_BRAND = "LITCLAUDE";
 const NEON_START = [255, 45, 149]; // #ff2d95 hot pink
 const NEON_END = [0, 229, 255]; // #00e5ff electric cyan
 
-export const supportsTruecolor = (env = process.env) =>
-  /truecolor|24bit/iu.test(String(env.COLORTERM || ""));
+export const supportsTruecolor = (env = process.env) => {
+  // The portable signal: terminals that export COLORTERM=truecolor|24bit.
+  if (/truecolor|24bit/iu.test(String(env.COLORTERM || ""))) return true;
+  // Windows Terminal (including WSL2) renders 24-bit color but does NOT export
+  // COLORTERM into the shell — it advertises itself via WT_SESSION instead.
+  // Without this, WSL2 users get the 256-color magenta fallback by mistake.
+  if (env.WT_SESSION) return true;
+  // 24-bit terminal emulators that may not set COLORTERM in every shell.
+  if (/\b(?:vscode|hyper|wezterm|ghostty|iterm\.app)\b/iu.test(String(env.TERM_PROGRAM || ""))) return true;
+  // terminfo direct-color / truecolor entries (e.g. xterm-direct, *-truecolor).
+  if (/-direct|truecolor/iu.test(String(env.TERM || ""))) return true;
+  return false;
+};
 
 export const litBrandPrefix = (version, { noColor = false, truecolor = false } = {}) => {
   const label = `[🔥${NEON_BRAND} v${version}]`;