@promptctl/cc-candybar 1.56.1 → 1.56.2

package/plugin/commands/candybar.md

@@ -12,34 +12,34 @@ allowed-tools:
 
 # CC Candybar Setup Wizard
 
-You are running an interactive setup wizard to configure the cc-candybar statusline for Claude Code. Follow these steps in order, using AskUserQuestion for each decision point.
+You are running an interactive setup wizard to configure the cc-candybar statusline for Claude Code. Follow the steps in order, using AskUserQuestion at each decision point.
 
-## Important Notes
+## Operating rules
 
-- Do not skip steps or combine questions.
-- Always wait for the user's response before moving to the next step.
-- Track the user's choices in variables throughout the wizard.
-- The final config is written as JSON to `~/.config/cc-candybar/config.json`.
-- Do NOT use the Agent tool or Explore subagents. All information you need is in this document.
-- Do NOT read source code from the cc-candybar package. Use only the instructions below.
-- IMPORTANT: After running any Bash or Read tool, repeat the key output as text in your response. Some users have a collapsed UI mode where tool outputs require a click to expand. Always relay important results (like version numbers, previews, or file contents) in your text so the user can see them without expanding.
+- One question per step. Wait for the user's answer before moving on. Do not skip or combine steps.
+- Track the user's choices as four variables: `charset`, `theme`, `style`, `preset`. Every later command and the final config are built from exactly those four.
+- Do NOT use the Agent tool or Explore subagents. Everything you need is in this document.
+- Do NOT read source code from the cc-candybar package. Run only the subcommands this document names (`install`, `check`) and the plugin's preview script against it.
+- IMPORTANT: After running any Bash or Read tool, repeat the key output as text in your response. Some users have a collapsed UI mode where tool outputs need a click to expand. Relay versions, option names, file paths, and command results in your text so the user sees them without expanding.
+- Two things this wizard never does, however natural they feel in the moment: it never edits `~/.claude/settings.json` by hand (Step 9's installer writes that entry), and it never carries its own list of theme names (Step 3's preview output is the list).
 
 ## Step 1: Check Node.js
 
-Run this command to check if Node.js 18+ is available:
+The runtime needs Node.js **20.19 or later within the 20.x line, or 22.12 or later**. Run:
 
 ```bash
 node --version 2>/dev/null || echo "not_installed"
+node -e 'const [a,b]=process.versions.node.split(".").map(Number);process.exit((a===20&&b>=19)||(a>=22&&(a>22||b>=12))?0:1)' 2>/dev/null && echo "version_ok" || echo "version_too_old_or_missing"
 ```
 
-Tell the user the detected version in your text response.
+Tell the user the detected version in your text.
 
-### If Node.js is NOT installed or version is below 18
+### If the second line printed `version_too_old_or_missing`
 
 Display:
 
 ````markdown
-CC Candybar requires **Node.js 18+** to run.
+CC Candybar requires **Node.js 20.19+ (20.x line) or 22.12+**.
 
 Install it from https://nodejs.org or via your package manager:
 
@@ -47,7 +47,7 @@ Install it from https://nodejs.org or via your package manager:
 # macOS
 brew install node
 
-# Ubuntu/Debian
+# Ubuntu/Debian (NodeSource)
 curl -fsSL https://deb.nodesource.com/setup_22.x | sudo -E bash -
 sudo apt-get install -y nodejs
 ```
@@ -58,346 +58,212 @@ Then ask:
 - **Question**: "Install Node.js or check again?"
 - **Header**: "Node.js"
 - **Options**:
-  - "I installed it, check again" -> Re-run the version check from the top of Step 1
-  - "Exit wizard" -> Tell them to install Node.js 18+ and exit
+  - "I installed it, check again" -> Re-run Step 1 from the top
+  - "Exit wizard" -> Tell them to install a supported Node.js and rerun `/candybar`, then stop
 
-### If Node.js 18+ IS installed
+### If it printed `version_ok`
 
-Continue to the next step.
+Continue to Step 2.
 
 ## Step 2: Nerd Font Detection
 
 > [!IMPORTANT]
-> You cannot display nerd font glyphs properly in your text output.
+> You cannot display nerd font glyphs in your text output.
 > You MUST run the cat command below and let the terminal render it.
-> After running it, tell the user to expand the bash output if they cannot see the icons.
+> After running it, tell the user to expand the bash output if they cannot see the glyphs.
 
 ```bash
 cat ${CLAUDE_PLUGIN_ROOT}/templates/nerd-fonts-sample.txt
 ```
 
-After running the command, tell the user: "Check the bash output above for Nerd Font icons (folder, code, branch, robot). You may need to click/expand the bash output to see them."
+Tell the user: "Check the bash output above. The powerline line should show arrow-shaped joiners between the words and the capsule line should show half-circle caps around them. You may need to click/expand the bash output to see them."
 
 Then ask:
 
-- **Question**: "Can you see the icons clearly (folder, code, branch, robot)?"
+- **Question**: "Do the powerline arrows and capsule half-circles render as shapes?"
 - **Header**: "Nerd Font"
 - **Options**:
-  - "Yes, I can see them" -> Set `charset=unicode`. Continue to Step 3
-  - "No, I see boxes or blank spaces" -> Set `charset=text`. Continue to Step 3
+  - "Yes, I see arrows and half-circles" -> Set `charset=unicode`
+  - "No, I see boxes, blanks, or question marks" -> Set `charset=ascii`
 
-## Step 3: Theme Selection
-
-Show a preview of all six themes using the bundled preview script.
+## Step 3: Theme
 
 > [!IMPORTANT]
 > You cannot render ANSI escape codes in your text output.
 > You MUST run the preview command below and let the terminal display the result.
+> Do NOT describe what the themes look like. Let the user see them.
 > After running, tell the user to expand the bash output if they cannot see the previews.
 
 ```bash
 ${CLAUDE_PLUGIN_ROOT}/bin/preview.sh --compare-themes --charset=${charset}
 ```
 
-After running the command, display the theme list and tell the user to check the bash output above for previews:
-
-````markdown
-**Available themes:**
-
-1. **dark** -- Dark background, high contrast (default)
-2. **light** -- Light background for light terminals
-3. **nord** -- Cool blue palette inspired by Arctic colors
-4. **tokyo-night** -- Modern dark theme with vibrant accents
-5. **rose-pine** -- Soft, muted palette with rose and pine tones
-6. **gruvbox** -- Warm retro colors with earthy tones
-````
+The output is one block per theme: a label line of the theme's name followed by a colon, then that theme's rendered bar. That label list is the theme list; there is no other. List the labeled names in your text (names only, in the order printed) and tell the user the previews are in the bash output above.
 
 Then ask:
 
-- **Question**: "Which theme? Type a name or pick from the list."
+- **Question**: "Which theme? Pick one or type any name from the preview."
 - **Header**: "Theme"
-- **Options**:
-  - "dark" -> Set `chosen_theme=dark`
-  - "light" -> Set `chosen_theme=light`
-  - "nord" -> Set `chosen_theme=nord`
-  - "tokyo-night" -> Set `chosen_theme=tokyo-night`
+- **Options**: the first four labeled names from the preview output, each -> Set `theme=<that name>`
 
-If the user types "rose-pine" or "gruvbox" (or any valid theme name) in the free text field, accept that as their choice. Valid themes: dark, light, nord, tokyo-night, rose-pine, gruvbox.
+If the user types a name in the free text field, accept it only if the preview labeled it; otherwise show the labeled names again and re-ask. Set `theme`.
 
-## Step 4: Style Selection
-
-Show a preview of all four styles using the bundled preview script.
+## Step 4: Style
 
 > [!IMPORTANT]
 > You cannot render ANSI escape codes or nerd font glyphs in your text output.
 > You MUST run the preview command below and let the terminal display the result.
-> Do NOT attempt to describe what the styles look like. Let the user see them.
+> Do NOT describe what the styles look like. Let the user see them.
 > After running, tell the user to expand the bash output if they cannot see the previews.
 
 ```bash
-${CLAUDE_PLUGIN_ROOT}/bin/preview.sh --compare-styles --theme=${chosen_theme} --charset=${charset}
+${CLAUDE_PLUGIN_ROOT}/bin/preview.sh --compare-styles --theme=${theme} --charset=${charset}
 ```
 
-After running the command, tell the user: "The four style previews are in the bash output above. Expand it if needed."
+Tell the user: "The three style previews are in the bash output above, each under its name. Expand it if needed."
 
 Then ask:
 
-- **Question**: "Which style do you prefer?"
+- **Question**: "Which style?"
 - **Header**: "Style"
 - **Options**:
-  - "minimal" -> Set `chosen_style=minimal`
-  - "powerline" -> Set `chosen_style=powerline`
-  - "capsule" -> Set `chosen_style=capsule`
-  - "tui" -> Set `chosen_style=tui`
-
-If the user chose `charset=text`, add a note that powerline and capsule use text fallback separators.
-
-**If the user chose "tui":** skip Steps 5 and 6 and continue to Step 4b for TUI layout selection.
-
-## Step 4b: TUI Layout Selection
+  - "powerline" -> Set `style=powerline`
+  - "capsule" -> Set `style=capsule`
+  - "plain" -> Set `style=plain`
 
-> [!NOTE]
-> This step only applies if the user chose "tui" style in Step 4. Otherwise skip to Step 5.
+## Step 5: Preset
 
-Show a preview of all three TUI layouts using the bundled preview script.
+The preset is the bar's arrangement: which segments, on how many rows.
 
 > [!IMPORTANT]
+> You cannot render ANSI escape codes or nerd font glyphs in your text output.
 > You MUST run the preview command below and let the terminal display the result.
+> Do NOT describe what the presets look like. Let the user see them.
 > After running, tell the user to expand the bash output if they cannot see the previews.
 
 ```bash
-${CLAUDE_PLUGIN_ROOT}/bin/preview.sh --compare-tui-layouts --theme=${chosen_theme} --charset=${charset}
+${CLAUDE_PLUGIN_ROOT}/bin/preview.sh --compare-presets --theme=${theme} --style=${style} --charset=${charset}
 ```
 
-After running the command, tell the user: "The three TUI layout previews are in the bash output above. Expand it if needed."
-
-Display the three TUI layout presets:
-
-````markdown
-**Choose a TUI layout:**
-
-1. **Compact** — Git + context window only
-   Minimal footprint. Model name in the title bar. Clean and focused.
-
-2. **Standard** — Git + context + block usage with progress bars
-   Model and directory in the title bar. Good default for most users.
-
-3. **Full** — Git, context, block, session, and daily cost
-   Title bar with model and directory. Footer with weekly usage and response time.
-   Maximum information density.
-````
-
-Then ask:
-
-- **Question**: "Which TUI layout?"
-- **Header**: "TUI Layout"
-- **Options**:
-  - "Compact" -> Set `chosen_tui_layout=compact`
-  - "Standard" -> Set `chosen_tui_layout=standard`
-  - "Full" -> Set `chosen_tui_layout=full`
-
-After selection, skip Steps 5 and 6 (always skipped for TUI). If "Compact" or "Standard", also skip Step 7 (no budget needed). If "Full", continue to Step 7.
-
-### TUI preset to template mapping
-
-- `compact` -> `config-tui-compact.json`
-- `standard` -> `config-tui-standard.json`
-- `full` -> `config-tui-full.json`
-
-## Step 5: Segment Selection
-
-> [!NOTE]
-> Skip this step if the user chose "tui" style.
-
-Display the three presets:
+Tell the user the previews are in the bash output above, then display:
 
 ````markdown
-**Choose a segment preset:**
-
-1. **Essential** -- Directory, git, model, context window
-   Clean and lightweight. Just the basics.
-
-2. **Standard** -- Essential + session cost, daily cost tracking
-   Adds cost visibility without clutter. Good default for most users.
-
-3. **Full** -- Standard + block usage, metrics, version, weekly usage
-   Everything on. For users who want maximum information density.
-````
-
-Then ask:
-
-- **Question**: "Which segment preset?"
-- **Header**: "Segments"
-- **Options**:
-  - "Essential" -> Set `chosen_preset=essential`
-  - "Standard" -> Set `chosen_preset=standard`
-  - "Full" -> Set `chosen_preset=full`
-
-### Preset to template mapping
-
-Each preset has a corresponding template config file in `${CLAUDE_PLUGIN_ROOT}/templates/`:
-
-- `essential` -> `config-essential.json`
-- `standard` -> `config-standard.json`
-- `full` -> `config-full.json`
-
-For TUI templates, see Step 4b.
+**Presets:**
 
-## Step 6: Bar Display Style
-
-> [!NOTE]
-> Skip this step if the user chose "tui" style. Default to `text` if skipped.
-
-Display the available bar styles for progress indicators (used by context, block, and weekly segments):
-
-````markdown
-**Bar display styles** (for context window, block usage, and weekly usage):
-
-1. **text** -- Numbers only, no bar (default). Example: `65,000 (61%)`
-2. **bar** -- Classic bar. Example: `▓▓▓▓▓░░░░░ 50%`
-3. **blocks** -- Block fill. Example: `█████░░░░░ 50%`
-4. **dots** -- Dot fill. Example: `●●●●●○○○○○ 50%`
-5. **geometric** -- Geometric. Example: `▰▰▰▰▰▱▱▱▱▱ 50%`
-6. **line** -- Line style. Example: `━━━━━┄┄┄┄┄ 50%`
+1. **default** -- Two rows: an identity row (directory, git, toolbar) over a status row (model, context window, cache timer, 5-hour block usage, weekly usage). Good default.
+2. **compact** -- One row (directory, git, context window) with no cell padding. For narrow terminals and split panes.
+3. **verbose** -- The default's two rows plus pull-request, burn-rate, token-speed and token-sparkline segments. Maximum information.
 ````
 
 Then ask:
 
-- **Question**: "Which bar style for progress indicators?"
-- **Header**: "Display Style"
+- **Question**: "Which preset?"
+- **Header**: "Preset"
 - **Options**:
-  - "text" -> Set `chosen_bar_style=text`
-  - "bar" -> Set `chosen_bar_style=bar`
-  - "blocks" -> Set `chosen_bar_style=blocks`
-  - "dots" -> Set `chosen_bar_style=dots`
+  - "default" -> Set `preset=default`
+  - "compact" -> Set `preset=compact`
+  - "verbose" -> Set `preset=verbose`
 
-If the user types "geometric", "line", "filled", "squares", "capped", "ball", or "blocks-line" in the free text field, accept that as their choice. All valid display styles: text, ball, bar, blocks, blocks-line, capped, dots, filled, geometric, line, squares.
+## Step 6: Existing config
 
-Apply `chosen_bar_style` to the `displayStyle` field of context, block, and weekly segments in the config.
+The config file is `~/.config/cc-candybar/config.json5`. A `config.json` beside it at the same location is a collision the bar warns about, so check for both:
 
-## Step 7: Budget
-
-> [!NOTE]
-> Skip this step if the user chose "Essential" preset, or TUI "Compact" or "Standard" layout. Only TUI "Full" layout uses a budget placeholder.
+```bash
+test -f ~/.config/cc-candybar/config.json5 && echo "json5_exists" || echo "json5_not_found"
+test -f ~/.config/cc-candybar/config.json && echo "json_exists" || echo "json_not_found"
+```
 
-Ask the user about their daily budget for cost tracking:
+If neither exists, continue to Step 7. If either exists, name the file(s) found and ask:
 
-- **Question**: "Set a daily spending budget? (used by the today segment for percentage warnings)"
-- **Header**: "Budget"
+- **Question**: "Found an existing cc-candybar config. What should I do?"
+- **Header**: "Existing Config"
 - **Options**:
-  - "$25/day" -> Set `today_budget=25`
-  - "$50/day" -> Set `today_budget=50`
-  - "$100/day" -> Set `today_budget=100`
-  - "No budget" -> Set `today_budget=null` (omit amount from config)
+  - "Replace it" -> If `config.json` exists, run `mv ~/.config/cc-candybar/config.json ~/.config/cc-candybar/config.json.bak.${stamp}` so the bar does not warn about the two files colliding. Continue to Step 7 (which overwrites `config.json5`).
+  - "Back it up first" -> Run `cp ~/.config/cc-candybar/config.json5 ~/.config/cc-candybar/config.json5.bak.${stamp}` if `config.json5` exists. Then proceed exactly as "Replace it".
+  - "Keep it and exit" -> Tell the user nothing was changed and stop.
 
-## Step 8: Write Configuration
-
-### Check for existing config
+Every backup name carries `${stamp}`, so a later wizard run never overwrites an earlier backup. Compute it as the first line of the same Bash call as the `cp`/`mv` (shell variables do not survive between calls), and name the backup path(s) in your text afterwards:
 
 ```bash
-test -f ~/.config/cc-candybar/config.json && echo "exists" || echo "not_found"
+stamp=$(date -u +%Y%m%dT%H%M%SZ)
 ```
 
-If it exists, ask:
-
-- **Question**: "Found existing ~/.config/cc-candybar/config.json. What should I do?"
-- **Header**: "Existing Config"
-- **Options**:
-  - "Replace it" -> Continue
-  - "Back it up first" -> Run `cp ~/.config/cc-candybar/config.json ~/.config/cc-candybar/config.json.bak` then continue
-  - "Keep it and exit" -> Exit the wizard
+## Step 7: Write the config
 
-### Build and write the config
+1. Read the template with the Read tool:
 
-1. **Pick the template file.** Based on the user's choices:
-   - Non-TUI styles: `config-essential.json`, `config-standard.json`, or `config-full.json` (from Step 5)
-   - TUI style: `config-tui-compact.json`, `config-tui-standard.json`, or `config-tui-full.json` (from Step 4b)
+   ```text
+   ${CLAUDE_PLUGIN_ROOT}/templates/config.json
+   ```
 
-2. **Read the template** using the Read tool:
+2. Replace the four placeholders in the template content:
 
-```text
-${CLAUDE_PLUGIN_ROOT}/templates/<template-file>
-```
+   | Placeholder | Replace with |
+   |-------------|--------------|
+   | `replace:THEME` | `theme` (the name chosen in Step 3) |
+   | `replace:STYLE` | `style` (`powerline`, `capsule`, or `plain`) |
+   | `replace:CHARSET` | `charset` (`unicode` or `ascii`) |
+   | `replace:PRESET` | `preset` (`default`, `compact`, or `verbose`) |
 
-1. **Replace placeholders** in the template content:
+3. Write the result to `~/.config/cc-candybar/config.json5` with the Write tool (create the directory if needed). Do NOT read or merge with any existing config; the file is replaced whole.
 
-   | Placeholder | Replace with |
-   |-------------|-------------|
-   | `replace:THEME` | The chosen theme (e.g., `tokyo-night`) |
-   | `replace:STYLE` | The chosen style (e.g., `capsule`). Not present in TUI templates. |
-   | `replace:CHARSET` | `unicode` or `text` |
-   | `replace:BAR_STYLE` | The chosen bar style (e.g., `blocks`). Default `text` if Step 6 was skipped. Not present in TUI templates. |
-   | `replace:TODAY_BUDGET` | The budget number (e.g., `50`). Only present in non-TUI standard/full and TUI full templates. **Important:** replace `"replace:TODAY_BUDGET"` (including the surrounding quotes) with the bare number so the result is `"amount": 50` not `"amount": "50"`. |
+## Step 8: Verify
 
-1. **Handle "No budget"**: If the user chose "No budget" in Step 7, remove the entire `"amount": "replace:TODAY_BUDGET",` line (including the trailing comma) from the budget section. If Step 7 was skipped (essential preset, or TUI compact/standard), do not modify the budget section.
+Check that the written config loads:
 
-1. **Write the result** to `~/.config/cc-candybar/config.json` using the Write tool. Do NOT read or merge with any existing config.
+```bash
+npx -y @promptctl/cc-candybar@latest check ~/.config/cc-candybar/config.json5
+```
 
-## Step 9: Update settings.json
+Exit 0 and a `✓` line mean the config loads. A `✗` block names the problem: show it to the user verbatim and stop. Do not continue to the installer, the preview or the success message, and do not claim the setup worked.
 
-Read `~/.claude/settings.json` if it exists. Add or update ONLY the `statusLine` key:
+## Step 9: Install the runtime
 
-```json
-{
-  "statusLine": {
-    "type": "command",
-    "command": "npx -y @promptctl/cc-candybar@latest"
-  }
-}
+```bash
+npx -y @promptctl/cc-candybar@latest install
 ```
 
-If the file does not exist, create it with only the statusLine configuration.
-If it exists, preserve ALL other settings (hooks, permissions, plugins, etc.) and only add or update the `statusLine` key.
+This stages the runtime and writes the `statusLine` entry into `~/.claude/settings.json` itself. Relay the command's output in your text. If it exits non-zero, show the error and stop; do not open settings.json to finish the job by hand.
 
-Use the Read tool to load the existing file, merge the statusLine key, and Write to save it back.
+Exit 0 has two outcomes, told apart by the output:
 
-## Step 10: Test Installation
+- A line beginning `Updated ` followed by the settings path: settings.json was written. Continue to Step 10.
+- `Skipping settings.json update: existing statusLine.command appears customized.` followed by a `Current:` line: the installer found a statusLine command it did not write and left it alone. Relay the `Current:` command in your text, then ask:
+  - **Question**: "Your settings.json already has a statusLine command. Replace it with cc-candybar?"
+  - **Header**: "statusLine"
+  - **Options**:
+    - "Replace it with cc-candybar" -> Run `npx -y @promptctl/cc-candybar@latest install --force`, relay its output, and continue to Step 10.
+    - "Keep my existing statusLine" -> Continue to Step 10; the success message says the bar is not wired up.
 
-Run a test with sample data to verify the statusline renders:
+## Step 10: Preview
 
 > [!IMPORTANT]
-> You MUST run this command and tell the user to check the output.
+> You cannot render ANSI escape codes or nerd font glyphs in your text output.
+> You MUST run the preview command below and let the terminal display the result.
+> After running, tell the user to expand the bash output if they cannot see the preview.
 
 ```bash
-${CLAUDE_PLUGIN_ROOT}/bin/preview.sh --theme=${chosen_theme} --style=${chosen_style} --charset=${charset}
+${CLAUDE_PLUGIN_ROOT}/bin/preview.sh --theme=${theme} --style=${style} --charset=${charset} --preset=${preset}
 ```
 
-Tell the user: "Check the bash output above for your statusline preview. Expand it if needed."
+Tell the user: "Your statusline is in the bash output above. Expand it if needed."
 
-If it produced output, tell the user the setup is working.
+## Step 11: Success message
 
-## Step 11: Success Message
-
-Display:
+Display the message below. The `~/.claude/settings.json` line under **Files written** belongs there only if Step 9 printed `Updated `. If the user kept their existing statusLine, drop that line and make item 1 of **What now**: "Your existing statusLine was left in place, so the bar will not appear until `statusLine.command` in `~/.claude/settings.json` points at cc-candybar. Rerun `/candybar` and choose Replace to have the installer do it."
 
 ````markdown
 Setup complete.
 
-**Files created/updated:**
-- `~/.config/cc-candybar/config.json` (candybar config)
-- `~/.claude/settings.json` (claude settings)
+**Files written:**
+- `~/.config/cc-candybar/config.json5` (your candybar config)
+- `~/.claude/settings.json` (`statusLine` entry, written by the installer)
 
 **What now:**
 1. Restart Claude Code if the statusline does not appear.
-2. Run `/candybar` any time to reconfigure.
-3. Edit `~/.config/cc-candybar/config.json` by hand for advanced options.
+2. The bar has its own settings menu: click `☰ ▸` on the bar to switch theme, look, style, wrap, padding and preset live. Tick `persist?` there to make a choice the durable default.
+3. Hand edits to `~/.config/cc-candybar/config.json5` hot-reload; no restart needed.
+4. Run `/candybar` any time to rerun this wizard.
 
 Documentation: https://github.com/promptctl/cc-candybar
 ````
-
-**If the user chose TUI style**, also display:
-
-````markdown
-**Customizing your TUI grid layout:**
-
-Edit `display.tui` in `~/.config/cc-candybar/config.json` to fine-tune:
-
-- **Box style** — Add `"box": "rounded"` to change borders. Presets: `rounded`, `square`, `heavy`, `double`, `dashed`, `heavy-dashed`, `mixed`, `ascii`, `invisible`
-- **Title/footer** — Edit `title.left`, `title.right`, `footer.left`, `footer.right` using `{segment.part}` tokens (e.g. `{model.icon}`, `{dir}`, `{weekly.pct}`)
-- **Grid areas** — Rearrange cells in `breakpoints[].areas`. Use `.` for empty cells, `---` for dividers. Repeat a name across adjacent cells to span columns
-- **Custom colors** — Add `colors.custom` entries with dot-notation keys (e.g. `"context.bar": { "fg": "#4a9eff" }`)
-- **Responsive breakpoints** — Add breakpoints for different terminal widths. The engine picks the largest `minWidth` that fits
-- **Column sizing** — `"auto"` (fit content), `"1fr"` (fill remaining), or a fixed number like `"20"`
-
-See the TUI Grid Layout section in the README for the full reference.
-````

package/plugin/templates/config.json

@@ -0,0 +1,8 @@
+{
+  "globals": {
+    "palette": "replace:THEME",
+    "style": "replace:STYLE",
+    "charset": "replace:CHARSET",
+    "preset": "replace:PRESET"
+  }
+}

package/plugin/templates/nerd-fonts-sample.txt

@@ -1,5 +1,7 @@
-Can you see these icons clearly?
+Can you see these joiner glyphs clearly?
 
-  folder    code    branch   󰚩 robot
+  powerline:  one  two  three
+  capsule:     one    two 
 
-If you see boxes or blank spaces instead of icons, choose "No" below.
+If you see boxes, blank spaces, or question marks instead of arrow and
+half-circle shapes, choose "No" below.

package/plugin/templates/config-essential.json

@@ -1,36 +0,0 @@
-{
-  "theme": "replace:THEME",
-  "display": {
-    "style": "replace:STYLE",
-    "charset": "replace:CHARSET",
-    "colorCompatibility": "auto",
-    "autoWrap": true,
-    "padding": 1,
-    "lines": [
-      {
-        "segments": {
-          "directory": { "enabled": true, "style": "fish" },
-          "git": { "enabled": true },
-          "model": { "enabled": true }
-        }
-      },
-      {
-        "segments": {
-          "context": {
-            "enabled": true,
-            "showPercentageOnly": false,
-            "displayStyle": "replace:BAR_STYLE",
-            "autocompactBuffer": 33000
-          }
-        }
-      }
-    ]
-  },
-  "budget": {
-    "session": { "warningThreshold": 80 }
-  },
-  "modelContextLimits": {
-    "sonnet": 1000000,
-    "opus": 200000
-  }
-}

package/plugin/templates/config-full.json

@@ -1,55 +0,0 @@
-{
-  "theme": "replace:THEME",
-  "display": {
-    "style": "replace:STYLE",
-    "charset": "replace:CHARSET",
-    "colorCompatibility": "auto",
-    "autoWrap": true,
-    "padding": 1,
-    "lines": [
-      {
-        "segments": {
-          "directory": { "enabled": true, "style": "fish" },
-          "git": { "enabled": true },
-          "model": { "enabled": true },
-          "session": { "enabled": true, "type": "tokens", "costSource": "calculated" }
-        }
-      },
-      {
-        "segments": {
-          "today": { "enabled": true, "type": "cost" },
-          "block": { "enabled": true, "displayStyle": "replace:BAR_STYLE" },
-          "weekly": { "enabled": true, "displayStyle": "replace:BAR_STYLE" },
-          "context": {
-            "enabled": true,
-            "showPercentageOnly": false,
-            "displayStyle": "replace:BAR_STYLE",
-            "autocompactBuffer": 33000
-          }
-        }
-      },
-      {
-        "segments": {
-          "metrics": {
-            "enabled": true,
-            "showResponseTime": false,
-            "showLastResponseTime": false,
-            "showDuration": true,
-            "showMessageCount": true,
-            "showLinesAdded": false,
-            "showLinesRemoved": false
-          },
-          "version": { "enabled": true }
-        }
-      }
-    ]
-  },
-  "budget": {
-    "session": { "warningThreshold": 80 },
-    "today": { "amount": "replace:TODAY_BUDGET", "warningThreshold": 80 }
-  },
-  "modelContextLimits": {
-    "sonnet": 1000000,
-    "opus": 200000
-  }
-}