claudekit-cli 1.0.0 → 1.1.0

package/.claude/commands/docs/summarize.md

@@ -1,10 +0,0 @@
----
-description: Analyze the codebase and update documentation
----
-
-Use `docs-manager` agent to analyze the codebase and update `docs/codebase-summary.md`
-
-## Notes:
-- Use `docs/` directory as the source of truth for documentation.
-
-**IMPORTANT**: **Do not** start implementing.

package/.claude/commands/docs/update.md

@@ -1,21 +0,0 @@
----
-description: Analyze the codebase and update documentation
----
-
-Use `docs/` directory as the source of truth for documentation.
-Use `docs-manager` agent to analyze the codebase and update documentation:
-- `README.md`: Update README
-- `docs/project-overview-pdr.md`: Update project overview and PDR (Product Development Requirements)
-- `docs/codebase-summary.md`: Update codebase summary
-- `docs/code-standards.md`: Update codebase structure and code standards
-- `docs/system-architecture.md`: Update system architecture
-- `docs/project-roadmap.md`: Update project roadmap
-- `docs/deployment-guide.md` [optional]: Update deployment guide
-- `docs/design-guidelines.md` [optional]: Update design guidelines
-
-## Additional requests
-<additional_requests>
-  $ARGUMENTS
-</additional_requests>
-
-**IMPORTANT**: **Do not** start implementing.

package/.claude/commands/fix/ci.md

@@ -1,11 +0,0 @@
----
-description: Analyze Github Actions logs and fix issues
----
-## Github Actions URL
-<url>$ARGUMENTS</url>
-
-## Workflow
-- Use the `planer-researcher` to read the github actions logs, analyze and find the root causes of the issues, then provide a detailed plan for implementing the fixes.
-- Use proper developer agents to implement the plan.
-- Use `tester` agent to run the tests, make sure it works, then report back to main agent.
-- If there are issues or failed tests, ask main agent to fix all of them and repeat the process until all tests pass.

package/.claude/commands/fix/fast.md

@@ -1,12 +0,0 @@
----
-description: Analyze and fix the issue [FAST]
----
-
-Analyze and fix this issue:
-<issue>$ARGUMENTS</issue>
-
-## Workflow
-
-- If the user provides a screenshots or videos, use `eyes_analyze` tool from Human MCP to describe as detailed as possible the issue, make sure developers can predict the root causes easily based on the description.
-- Use `tester` agent to test the fix and make sure it works, then report back to main agent.
-- If there are issues or failed tests, ask main agent to fix all of them and repeat the process until all tests pass.

package/.claude/commands/fix/hard.md

@@ -1,18 +0,0 @@
----
-description: Use subagents to plan and fix hard issues
----
-
-Ultrathink to plan & start fixing these issues follow the Orchestration Protocol, Core Responsibilities, Subagents Team and Development Rules: 
-<issues>$ARGUMENTS</issues>
-
-## Workflow:
-
-If the user provides a screenshots or videos, use `eyes_analyze` tool from Human MCP to describe as detailed as possible the issue, make sure developers can predict the root causes easily based on the description.
-
-1. Use `planner` subagent and `researcher` subagent to create a implementation plan with TODO tasks in `./plans` directory.
-2. Then use general agent (main agent) to implement the plan step by step.
-3. Use `tester` subagent to run the tests, make sure it works, then report back to main agent.
-4. If there are issues or failed tests, use `debugger` subagent to find the root cause of the issues, then ask main agent to fix all of them and 
-5. Repeat the process until all tests pass or no more issues are reported.
-6. After finishing, delegate to `code-reviewer` subagent to review code. If there are critical issues, ask main agent to improve the code and test everything again.
-7. Report back to user with a summary of the changes and explain everything briefly.

package/.claude/commands/fix/logs.md

@@ -1,16 +0,0 @@
----
-description: Analyze logs and fix issues
----
-
-Use `debugger` agent to analyze the `./logs.txt` file, identify root causes of any errors or issues and respond with a report and solution.
-So the main agent can fix them.
-
-## Rules
-
-- Use `debugger` agent to read and analyze the entire `./logs.txt` file
-- Identify all errors, warnings, and potential issues
-- Determine the root causes of each issue
-- Fix all identified problems systematically based on the report
-- Verify fixes by running appropriate commands
-- Re-analyze logs after fixes to ensure issues are resolved
-

package/.claude/commands/fix/test.md

@@ -1,18 +0,0 @@
----
-description: Run test suite and fix issues
----
-
-## Reported Issues:
-<issue>
- $ARGUMENTS
-</issue>
-
-## Workflow:
-1. First use `tester` subagent to compile the code and fix all syntax errors if any.
-2. Then use `tester` subagent to run the tests.
-3. If there are issues or failed tests, use `debugger` subagent to find the root cause of the issues.
-4. Then use `planner` subagent to create a implementation plan with TODO tasks in `./plans` directory.
-5. Then implement the plan step by step.
-6. Use `tester` subagent to run the tests after implementing the plan, make sure it works, then report back to main agent.
-7. After finishing, delegate to `code-reviewer` agent to review code. If there are critical issues, ask main agent to improve the code and test everything again.
-8. Repeat this process until all tests pass and no more errors are reported.

package/.claude/commands/fix/types.md

@@ -1,10 +0,0 @@
----
-description: Fix type errors
----
-
-Run `bun run typecheck` and fix all type errors.
-
-## Rules
-
-- Fix all of type errors and repeat the process until there are no more type errors.
-- Do not use `any` just to pass the type check.

package/.claude/commands/git/cm.md

@@ -1,5 +0,0 @@
----
-description: Stage all files and create a commit.
----
-Use `git-manager` agent to stage all files and create a commit.
-**IMPORTANT: DO NOT push the changes to remote repository**

package/.claude/commands/git/cp.md

@@ -1,4 +0,0 @@
----
-description: Stage, commit and push all code in the current branch
----
-Use `git-manager` agent to stage all files, create a meaningful commit based on the changes and push to remote repository.

package/.claude/commands/integrate/polar.md

@@ -1,42 +0,0 @@
----
-description: Implement payment integration with Polar.sh
----
-
-Think harder to plan & start implementing payment integration with [Polar.sh](https://polar.sh/docs/llms-full.txt) follow the Orchestration Protocol, Core Responsibilities, Subagents Team and Development Rules: 
-<tasks>$ARGUMENTS</tasks>
-
-## Workflow:
-
-### Fullfill the request
-
-* If you don't have any questions, skip this step and go to `Planning` step.
-* If you have any questions, ask the user to clarify them.
-* Ask 1 question at a time, wait for the user to answer before moving to the next question.
-* Repeat this process until you have all the information you need to proceed.
-
-### Planning
-
-1. Use `planner` subagent to read the Polar.sh docs and create a implementation plan with TODO tasks in `./plans` directory.
-2. Ask user to review and approve the plan, if the user requests to change the plan, repeat the previous step until the user approves the plan.
-
-### Implementation
-
-1. When user approves the plan, use **general agent (main agent)** to implement the plan step by step.
-2. Run type checking and compile the code to make sure there are no syntax errors.
-
-### Testing & Code Review
-
-5. Write the tests for the plan, make sure you don't use fake data just to pass the tests, tests should be real and cover all possible cases.
-6. Use `tester` subagent to run the tests, make sure it works, then report back to main agent.
-7. If there are issues or failed tests, use `debugger` subagent to find the root cause of the issues, then ask main agent to fix all of them and 
-8. Repeat the process until all tests pass or no more issues are reported. Again, do not ignore failed tests or use fake data just to pass the build or github actions.
-9.  When all tests pass, delegate to `code-reviewer` subagent to review code. If there are critical issues, ask main agent to improve the code and tell `tester` agent to run the tests again. Repeat the process until all tests pass.
-10. When all code is reviewed, the tasks are completed, report back to user with a summary of the changes and explain everything briefly, ask user to review the changes and approve them.
-
-### Documentation
-
-11. If user approves the changes, use `docs-manager` subagent to update the docs if needed.
-
-### Final Report
-
-12. Report back to user with a summary of the changes and explain everything briefly, guide user to get started and suggest the next steps.

package/.claude/commands/plan/ci.md

@@ -1,12 +0,0 @@
----
-description: Analyze Github Actions logs and provide a plan to fix the issues
----
-## Github Actions URL
- $ARGUMENTS
-
-Use the `planer-researcher` to read the github actions logs, analyze and find the root causes of the issues, then provide a detailed plan for implementing the fixes.
-
-**Output:**
-Provide at least 2 implementation approaches with clear trade-offs, and explain the pros and cons of each approach, and provide a recommended approach.
-
-**IMPORTANT:** Ask the user for confirmation before implementing.

package/.claude/commands/plan/two.md

@@ -1,13 +0,0 @@
----
-description: Research & create an implementation plan with 2 approaches
----
-
-Use the `planner` subagent to plan for this task:
-<task>
- $ARGUMENTS
-</task>
-
-**Output:**
-Provide at least 2 implementation approaches with clear trade-offs, and explain the pros and cons of each approach, and provide a recommended approach.
-
-**IMPORTANT**: **Do not** start implementing.

package/.claude/commands/plan.md

@@ -1,10 +0,0 @@
----
-description: Research, analyze, and create an implementation plan
----
-
-Use the `planner` subagent to plan for this task:
-<task>
- $ARGUMENTS
-</task>
-
-**IMPORTANT**: **Do not** start implementing.

package/.claude/commands/scout.md

@@ -1,29 +0,0 @@
----
-description: Scout given directories to respond to the user's requests
-argument-hint: [user-prompt] [scale]
----
-
-## Purpose
-
-Search the codebase for files needed to complete the task using a fast, token efficient agent.
-
-## User's requests & target directories
-<user_requests>$ARGUMENTS</user_requests>
-
-## Variables
-
-USER_PROMPT: $1
-SCALE: $2 (defaults to 3)
-RELEVANT_FILE_OUTPUT_DIR: `plans/scouts/`
-
-## Workflow:
-- Write a prompt for 'SCALE' number of agents to the Task tool that will immediately call the Bash tool to run these commands to kick off your agents to conduct the search:
-  - `gemini -p "[prompt]" --model gemini-2.5-flash-preview-09-2025`
-  - `opencode run "[prompt]" --model opencode/grok-code` (if count > 3)
-
-**How to prompt the agents:**
-- IMPORTANT: Kick these agents off in parallel using the Task tool, analyze and divide folders for each agent to scout intelligently and quickly.
-- IMPORTANT: These agents are calling OTHER agentic coding tools to search the codebase. DO NOT call any search tools yourself.
-- IMPORTANT: That means with the Task tool, you'll immediately call the Bash tool to run the respective agentic coding tool (gemini, opencode, claude, etc.)
-- IMPORTANT: Instruct the agents to quickly search the codebase for files needed to complete the task. This isn't about a full blown search, just a quick search to find the files needed to complete the task.
-- Instruct the subagent to use a timeout of 3 minutes for each agent's bash call. Skip any agents that don't return within the timeout, don't restart them.

package/.claude/commands/test.md

@@ -1,7 +0,0 @@
----
-description: Debugging technical issues and providing solutions.
----
-
-Use the `tester` subagent to run tests locally and analyze the summary report.
-
-**IMPORTANT**: **Do not** start implementing.

package/.claude/commands/watzup.md

@@ -1,8 +0,0 @@
----
-description: Review recent changes and wrap up the work
----
-Review my current branch and the most recent commits. 
-Provide a detailed summary of all changes, including what was modified, added, or removed. 
-Analyze the overall impact and quality of the changes.
-
-**IMPORTANT**: **Do not** start implementing.

package/.claude/hooks/telegram_notify.sh

@@ -1,136 +0,0 @@
-#!/bin/bash
-
-# Telegram Notification Hook for Claude Code (Project-Specific)
-# This hook sends a notification to Telegram when Claude finishes a task
-
-set -euo pipefail
-
-# Read JSON input from stdin
-INPUT=$(cat)
-
-# Extract relevant information from the hook input
-HOOK_TYPE=$(echo "$INPUT" | jq -r '.hookType // "unknown"')
-PROJECT_DIR=$(echo "$INPUT" | jq -r '.projectDir // ""')
-TIMESTAMP=$(date '+%Y-%m-%d %H:%M:%S')
-SESSION_ID=$(echo "$INPUT" | jq -r '.sessionId // ""')
-PROJECT_NAME=$(basename "$PROJECT_DIR")
-
-# Configuration - these will be set via environment variables
-TELEGRAM_BOT_TOKEN="${TELEGRAM_BOT_TOKEN:-}"
-TELEGRAM_CHAT_ID="${TELEGRAM_CHAT_ID:-}"
-
-# Validate required environment variables
-if [[ -z "$TELEGRAM_BOT_TOKEN" ]]; then
-    echo "Error: TELEGRAM_BOT_TOKEN environment variable not set" >&2
-    exit 1
-fi
-
-if [[ -z "$TELEGRAM_CHAT_ID" ]]; then
-    echo "Error: TELEGRAM_CHAT_ID environment variable not set" >&2
-    exit 1
-fi
-
-# Function to send Telegram message
-send_telegram_message() {
-    local message="$1"
-    local url="https://api.telegram.org/bot${TELEGRAM_BOT_TOKEN}/sendMessage"
-    
-    # Escape special characters for JSON
-    local escaped_message=$(echo "$message" | jq -Rs .)
-    
-    local payload=$(cat <<EOF
-{
-    "chat_id": "${TELEGRAM_CHAT_ID}",
-    "text": ${escaped_message},
-    "parse_mode": "Markdown",
-    "disable_web_page_preview": true
-}
-EOF
-)
-    
-    curl -s -X POST \
-        -H "Content-Type: application/json" \
-        -d "$payload" \
-        "$url" > /dev/null
-}
-
-# Generate summary based on hook type
-case "$HOOK_TYPE" in
-    "Stop")
-        # Extract tool usage summary
-        TOOLS_USED=$(echo "$INPUT" | jq -r '.toolsUsed[]?.tool // empty' | sort | uniq -c | sort -nr)
-        FILES_MODIFIED=$(echo "$INPUT" | jq -r '.toolsUsed[]? | select(.tool == "Edit" or .tool == "Write" or .tool == "MultiEdit") | .parameters.file_path // empty' | sort | uniq)
-        
-        # Count operations
-        TOTAL_TOOLS=$(echo "$INPUT" | jq '.toolsUsed | length')
-        
-        # Build summary message
-        MESSAGE="🚀 *DevPocket Task Completed*
-        
-📅 *Time:* ${TIMESTAMP}
-📁 *Project:* ${PROJECT_NAME}
-🔧 *Total Operations:* ${TOTAL_TOOLS}
-🆔 *Session:* ${SESSION_ID:0:8}...
-
-*Tools Used:*"
-
-        if [[ -n "$TOOLS_USED" ]]; then
-            MESSAGE="${MESSAGE}
-\`\`\`
-${TOOLS_USED}
-\`\`\`"
-        else
-            MESSAGE="${MESSAGE}
-None"
-        fi
-
-        if [[ -n "$FILES_MODIFIED" ]]; then
-            MESSAGE="${MESSAGE}
-
-*Files Modified:*"
-            while IFS= read -r file; do
-                if [[ -n "$file" ]]; then
-                    # Show relative path from project root
-                    relative_file=$(echo "$file" | sed "s|^${PROJECT_DIR}/||")
-                    MESSAGE="${MESSAGE}
-• ${relative_file}"
-                fi
-            done <<< "$FILES_MODIFIED"
-        fi
-        
-        MESSAGE="${MESSAGE}
-
-📍 *Location:* \`${PROJECT_DIR}\`"
-        ;;
-        
-    "SubagentStop")
-        SUBAGENT_TYPE=$(echo "$INPUT" | jq -r '.subagentType // "unknown"')
-        MESSAGE="🤖 *DevPocket Subagent Completed*
-
-📅 *Time:* ${TIMESTAMP}
-📁 *Project:* ${PROJECT_NAME}
-🔧 *Agent Type:* ${SUBAGENT_TYPE}
-🆔 *Session:* ${SESSION_ID:0:8}...
-
-Specialized agent completed its task.
-
-📍 *Location:* \`${PROJECT_DIR}\`"
-        ;;
-        
-    *)
-        MESSAGE="📝 *DevPocket Code Event*
-
-📅 *Time:* ${TIMESTAMP}
-📁 *Project:* ${PROJECT_NAME}
-📋 *Event:* ${HOOK_TYPE}
-🆔 *Session:* ${SESSION_ID:0:8}...
-
-📍 *Location:* \`${PROJECT_DIR}\`"
-        ;;
-esac
-
-# Send the notification
-send_telegram_message "$MESSAGE"
-
-# Log the notification (optional)
-echo "Telegram notification sent for $HOOK_TYPE event in project $PROJECT_NAME" >&2

package/.claude/send-discord.sh

@@ -1,64 +0,0 @@
-#!/bin/bash
-
-# Usage: ./send-discord.sh 'Your message here'
-# Note: Remember to escape the string
-
-# Load environment variables from .env file
-if [[ -f .env ]]; then
-    echo "Loading .env file..."
-    set -a  # automatically export all variables
-    source .env
-    set +a  # turn off automatic export
-    echo "✅ Environment loaded, DISCORD_WEBHOOK_URL=$(echo ${DISCORD_WEBHOOK_URL:0:50}...)"
-else
-    echo "Warning: .env file not found"
-fi
-
-message="$1"
-    
-if [[ -z "$DISCORD_WEBHOOK_URL" ]]; then
-    echo "⚠️  Discord notification skipped: DISCORD_WEBHOOK_URL not set"
-    exit 1
-fi
-
-# Prepare message for Discord (Discord markdown supports \n)
-discord_message="$message"
-
-# Discord embeds for richer formatting
-payload=$(cat <<EOF
-{
-"embeds": [{
-    "title": "🤖 Claude Code Session Complete",
-    "description": "$discord_message",
-    "color": 5763719,
-    "timestamp": "$(date -u +%Y-%m-%dT%H:%M:%S.000Z)",
-    "footer": {
-        "text": "DevPocket API • $(basename "$(pwd)")"
-    },
-    "fields": [
-        {
-            "name": "⏰ Session Time",
-            "value": "$(date '+%H:%M:%S')",
-            "inline": true
-        },
-        {
-            "name": "📂 Project",
-            "value": "$(basename "$(pwd)")",
-            "inline": true
-        }
-    ]
-}]
-}
-EOF
-)
-
-curl -s -X POST "$DISCORD_WEBHOOK_URL" \
-    -H "Content-Type: application/json" \
-    -d "$payload" >/dev/null 2>&1
-
-if [[ $? -eq 0 ]]; then
-    echo "✅ Discord notification sent"
-else
-    echo "❌ Failed to send Discord notification"
-    exit 1
-fi

package/.claude/settings.json

@@ -1,7 +0,0 @@
-{
-	"statusLine": {
-		"type": "command",
-		"command": ".claude/statusline.sh",
-		"padding": 0
-	}
-}

package/.claude/statusline.sh

@@ -1,143 +0,0 @@
-#!/bin/bash
-# Generated by cc-statusline (https://www.npmjs.com/package/@chongdashu/cc-statusline)
-# Custom Claude Code statusline - Created: 2025-08-19T05:45:09.773Z
-# Theme: detailed | Colors: true | Features: directory, git, model, usage, session, tokens
-
-input=$(cat)
-
-# ---- color helpers (TTY-aware, respect NO_COLOR) ----
-use_color=1
-[ -t 1 ] || use_color=0
-[ -n "$NO_COLOR" ] && use_color=0
-
-C() { if [ "$use_color" -eq 1 ]; then printf '\033[%sm' "$1"; fi; }
-RST() { if [ "$use_color" -eq 1 ]; then printf '\033[0m'; fi; }
-
-# ---- basic colors ----
-dir_color() { if [ "$use_color" -eq 1 ]; then printf '\033[1;36m'; fi; }    # cyan
-model_color() { if [ "$use_color" -eq 1 ]; then printf '\033[1;35m'; fi; }  # magenta  
-version_color() { if [ "$use_color" -eq 1 ]; then printf '\033[1;33m'; fi; } # yellow
-rst() { if [ "$use_color" -eq 1 ]; then printf '\033[0m'; fi; }
-
-# ---- time helpers ----
-to_epoch() {
-  ts="$1"
-  if command -v gdate >/dev/null 2>&1; then gdate -d "$ts" +%s 2>/dev/null && return; fi
-  date -u -j -f "%Y-%m-%dT%H:%M:%S%z" "${ts/Z/+0000}" +%s 2>/dev/null && return
-  python3 - "$ts" <<'PY' 2>/dev/null
-import sys, datetime
-s=sys.argv[1].replace('Z','+00:00')
-print(int(datetime.datetime.fromisoformat(s).timestamp()))
-PY
-}
-
-fmt_time_hm() {
-  epoch="$1"
-  if date -r 0 +%s >/dev/null 2>&1; then date -r "$epoch" +"%H:%M"; else date -d "@$epoch" +"%H:%M"; fi
-}
-
-progress_bar() {
-  pct="${1:-0}"; width="${2:-10}"
-  [[ "$pct" =~ ^[0-9]+$ ]] || pct=0; ((pct<0))&&pct=0; ((pct>100))&&pct=100
-  filled=$(( pct * width / 100 )); empty=$(( width - filled ))
-  printf '%*s' "$filled" '' | tr ' ' '='
-  printf '%*s' "$empty" '' | tr ' ' '-'
-}
-
-# git utilities
-num_or_zero() { v="$1"; [[ "$v" =~ ^[0-9]+$ ]] && echo "$v" || echo 0; }
-
-# ---- basics ----
-if command -v jq >/dev/null 2>&1; then
-  current_dir=$(echo "$input" | jq -r '.workspace.current_dir // .cwd // "unknown"' 2>/dev/null | sed "s|^$HOME|~|g")
-  model_name=$(echo "$input" | jq -r '.model.display_name // "Claude"' 2>/dev/null)
-  model_version=$(echo "$input" | jq -r '.model.version // ""' 2>/dev/null)
-else
-  current_dir="unknown"
-  model_name="Claude"; model_version=""
-fi
-
-# ---- git colors ----
-git_color() { if [ "$use_color" -eq 1 ]; then printf '\033[1;32m'; fi; }
-rst() { if [ "$use_color" -eq 1 ]; then printf '\033[0m'; fi; }
-
-# ---- git ----
-git_branch=""
-if git rev-parse --git-dir >/dev/null 2>&1; then
-  git_branch=$(git branch --show-current 2>/dev/null || git rev-parse --short HEAD 2>/dev/null)
-fi
-
-# ---- usage colors ----
-usage_color() { if [ "$use_color" -eq 1 ]; then printf '\033[1;35m'; fi; }
-cost_color() { if [ "$use_color" -eq 1 ]; then printf '\033[1;36m'; fi; }
-session_color() { 
-  rem_pct=$(( 100 - session_pct ))
-  if   (( rem_pct <= 10 )); then SCLR='1;31'
-  elif (( rem_pct <= 25 )); then SCLR='1;33'
-  else                          SCLR='1;32'; fi
-  if [ "$use_color" -eq 1 ]; then printf '\033[%sm' "$SCLR"; fi
-}
-
-# ---- ccusage integration ----
-session_txt=""; session_pct=0; session_bar=""
-cost_usd=""; cost_per_hour=""; tpm=""; tot_tokens=""
-
-if command -v jq >/dev/null 2>&1; then
-  blocks_output=$(npx ccusage@latest blocks --json 2>/dev/null || ccusage blocks --json 2>/dev/null)
-  if [ -n "$blocks_output" ]; then
-    active_block=$(echo "$blocks_output" | jq -c '.blocks[] | select(.isActive == true)' 2>/dev/null | head -n1)
-    if [ -n "$active_block" ]; then
-      cost_usd=$(echo "$active_block" | jq -r '.costUSD // empty')
-      cost_per_hour=$(echo "$active_block" | jq -r '.burnRate.costPerHour // empty')
-      tot_tokens=$(echo "$active_block" | jq -r '.totalTokens // empty')
-      
-      # Session time calculation
-      reset_time_str=$(echo "$active_block" | jq -r '.usageLimitResetTime // .endTime // empty')
-      start_time_str=$(echo "$active_block" | jq -r '.startTime // empty')
-      
-      if [ -n "$reset_time_str" ] && [ -n "$start_time_str" ]; then
-        start_sec=$(to_epoch "$start_time_str"); end_sec=$(to_epoch "$reset_time_str"); now_sec=$(date +%s)
-        total=$(( end_sec - start_sec )); (( total<1 )) && total=1
-        elapsed=$(( now_sec - start_sec )); (( elapsed<0 ))&&elapsed=0; (( elapsed>total ))&&elapsed=$total
-        session_pct=$(( elapsed * 100 / total ))
-        remaining=$(( end_sec - now_sec )); (( remaining<0 )) && remaining=0
-        rh=$(( remaining / 3600 )); rm=$(( (remaining % 3600) / 60 ))
-        end_hm=$(fmt_time_hm "$end_sec")
-        session_txt="$(printf '%dh %dm until reset at %s (%d%%)' "$rh" "$rm" "$end_hm" "$session_pct")"
-        session_bar=$(progress_bar "$session_pct" 10)
-      fi
-    fi
-  fi
-fi
-
-# ---- render statusline ----
-printf '📁 %s%s%s' "$(dir_color)" "$current_dir" "$(rst)"
-# git display
-if [ -n "$git_branch" ]; then
-  printf '  🌿 %s%s%s' "$(git_color)" "$git_branch" "$(rst)"
-fi
-printf '  🤖 %s%s%s' "$(model_color)" "$model_name" "$(rst)"
-if [ -n "$model_version" ] && [ "$model_version" != "null" ]; then
-  printf '  🏷️ %s%s%s' "$(version_color)" "$model_version" "$(rst)"
-fi
-# session time
-if [ -n "$session_txt" ]; then
-  printf '  ⌛ %s%s%s' "$(session_color)" "$session_txt" "$(rst)"
-  printf '  %s[%s]%s' "$(session_color)" "$session_bar" "$(rst)"
-fi
-# cost
-if [ -n "$cost_usd" ] && [[ "$cost_usd" =~ ^[0-9.]+$ ]]; then
-  if [ -n "$cost_per_hour" ] && [[ "$cost_per_hour" =~ ^[0-9.]+$ ]]; then
-    printf '  💵 %s$%.2f ($%.2f/h)%s' "$(cost_color)" "$cost_usd" "$cost_per_hour" "$(rst)"
-  else
-    printf '  💵 %s$%.2f%s' "$(cost_color)" "$cost_usd" "$(rst)"
-  fi
-fi
-# tokens
-if [ -n "$tot_tokens" ] && [[ "$tot_tokens" =~ ^[0-9]+$ ]]; then
-  if [ -n "$tpm" ] && [[ "$tpm" =~ ^[0-9.]+$ ]] && false; then
-    printf '  📊 %s%s tok (%.0f tpm)%s' "$(usage_color)" "$tot_tokens" "$tpm" "$(rst)"
-  else
-    printf '  📊 %s%s tok%s' "$(usage_color)" "$tot_tokens" "$(rst)"
-  fi
-fi