codeforge-dev 1.5.8 → 1.8.0

package/.devcontainer/README.md

@@ -1,34 +1,21 @@
-# CodeForge DevContainer
+# CodeForge Usage Guide
 
-[![License: GPL-3.0](https://img.shields.io/badge/License-GPL%203.0-blue.svg)](https://www.gnu.org/licenses/gpl-3.0)
-[![npm version](https://img.shields.io/npm/v/codeforge-dev.svg)](https://www.npmjs.com/package/codeforge-dev)
-
-A curated development environment optimized for AI-powered coding with Claude Code. CodeForge comes pre-configured with language servers, code intelligence tools, and official Anthropic plugins to streamline your development workflow.
-
-## Prerequisites
-
-- **Docker Desktop** (or compatible container runtime like Podman)
-- **VS Code** with the [Dev Containers extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers), or **GitHub Codespaces**
-- **Claude Code authentication** - see [Authentication](#authentication) section
+Everything you need to know once you're inside the devcontainer.
 
 ## Quick Start
 
-1. **Open in Container**
-   - VS Code: Open the folder, then select "Reopen in Container" from the command palette
-   - Codespaces: Create a new codespace from this repository
-
-2. **Authenticate** (first time only)
+1. **Authenticate** (first time only)
    ```bash
    claude
    ```
    Follow the prompts to authenticate via browser or API key.
 
-3. **Start Claude Code**
+2. **Start Claude Code**
    ```bash
    cc
    ```
 
-## Authentication
+## Claude Code Authentication
 
 Claude Code supports multiple authentication methods. On first run, you'll be prompted to choose:
 
@@ -57,11 +44,39 @@ Authentication credentials are stored in `/workspaces/.claude/` and persist acro
 
 For more options, see the [Claude Code documentation](https://docs.anthropic.com/en/docs/claude-code).
 
-## GitHub CLI Authentication
+## GitHub & NPM Authentication
 
-GitHub CLI (`gh`) is pre-installed for repository operations like pushing code, creating pull requests, and accessing private repositories.
+### Automatic Auth via `.secrets` (Recommended)
+
+CodeForge can automatically configure GitHub CLI, git identity, and NPM auth on every container start. Copy the template and fill in your tokens:
+
+```bash
+cp .devcontainer/.secrets.example .devcontainer/.secrets
+```
+
+Edit `.devcontainer/.secrets`:
+
+```bash
+GH_TOKEN=ghp_your_token_here
+GH_USERNAME=your-github-username
+GH_EMAIL=your-email@example.com
+NPM_TOKEN=npm_your_token_here
+```
+
+On the next container start (or rebuild), `setup-auth.sh` will:
+- Authenticate `gh` CLI and configure git credential helper
+- Set `git config --global user.name` and `user.email`
+- Set NPM registry auth token
+
+The `.secrets` file is gitignored at two levels (root `.*` + `.devcontainer/.gitignore`) and will never be committed.
+
+**Environment variable fallback**: For Codespaces or CI, set `GH_TOKEN`, `GH_USERNAME`, `GH_EMAIL`, and/or `NPM_TOKEN` as environment variables (e.g., via Codespaces secrets or `localEnv` in `devcontainer.json`). Environment variables take precedence over `.secrets` file values.
+
+Disable automatic auth by setting `SETUP_AUTH=false` in `.devcontainer/.env`.
 
-### Interactive Login (Recommended)
+### Interactive Login (Alternative)
+
+GitHub CLI (`gh`) is pre-installed for repository operations like pushing code, creating pull requests, and accessing private repositories.
 
 ```bash
 gh auth login
@@ -98,7 +113,28 @@ Expected output shows your authenticated account and token scopes.
 
 GitHub CLI credentials are automatically persisted across container rebuilds. The container is configured to store credentials in `/workspaces/.gh/` (via `GH_CONFIG_DIR`), which is part of the bind-mounted workspace.
 
-**You only need to authenticate once.** After running `gh auth login`, your credentials will survive container rebuilds and be available in future sessions.
+**You only need to authenticate once.** After running `gh auth login` or configuring `.secrets`, your credentials will survive container rebuilds and be available in future sessions.
+
+## Using Claude Code
+
+### The `cc` Command
+
+The `cc` command is an alias that launches Claude Code with the project's system prompt and plan-mode permissions. For Agent Teams split-pane support, use the **"Claude Teams (tmux)"** terminal profile in VS Code (dropdown next to the `+` button) or connect via `connect-external-terminal.sh`.
+
+```bash
+cc                    # Start Claude Code in current directory
+cc "explain this"     # Start with an initial prompt
+```
+
+### Direct CLI
+
+For more control, use the `claude` command directly:
+
+```bash
+claude                        # Basic invocation
+claude --help                 # View all options
+claude --resume               # Resume previous session
+```
 
 ## Available Tools
 
@@ -109,6 +145,7 @@ GitHub CLI credentials are automatically persisted across container rebuilds. Th
 | Node.js LTS | JavaScript runtime |
 | TypeScript | Via Node.js |
 | Go | Latest stable via devcontainer feature |
+| Bun | Fast JavaScript runtime and toolkit |
 
 ### Package Managers
 | Tool | Description |
@@ -126,7 +163,12 @@ GitHub CLI credentials are automatically persisted across container rebuilds. Th
 | `jq` | JSON processor |
 | `curl` | HTTP client |
 | `tmux` | Terminal multiplexer for Agent Teams split-pane sessions |
-| `biome` | Fast JS/TS/JSON/CSS formatter |
+| `biome` | Fast JS/TS/JSON/CSS formatter and linter |
+| `ruff` | Fast Python linter and formatter (replaces Black + Flake8) |
+| `shfmt` | Shell script formatter |
+| `dprint` | Pluggable formatter for Markdown, YAML, TOML, Dockerfile |
+| `shellcheck` | Static analysis tool for shell scripts |
+| `hadolint` | Dockerfile linter |
 | `agent-browser` | Headless browser automation for AI agents |
 
 ### Code Intelligence
@@ -143,56 +185,65 @@ GitHub CLI credentials are automatically persisted across container rebuilds. Th
 | `claude` | Claude Code CLI |
 | `cc` | Wrapper with auto-configuration |
 | `ccusage` | Token usage analyzer |
-| `ccstatusline` | Status line for sessions |
+| `ccburn` | Visual token burn rate tracker with pace indicators |
+| `ccstatusline` | Status bar display (integrated into Claude Code, not standalone CLI) |
 | `claude-monitor` | Real-time usage tracking |
 
-## Using Claude Code
-
-### The `cc` Command
-
-The `cc` command is an alias that launches Claude Code with the project's system prompt and plan-mode permissions. For Agent Teams split-pane support, use the **"Claude Teams (tmux)"** terminal profile in VS Code (dropdown next to the `+` button) or connect via `connect-external-terminal.sh`.
-
-```bash
-cc                    # Start Claude Code in current directory
-cc "explain this"     # Start with an initial prompt
-```
-
-### Direct CLI
-
-For more control, use the `claude` command directly:
-
-```bash
-claude                        # Basic invocation
-claude --help                 # View all options
-claude --resume               # Resume previous session
-```
-
 ## Configuration
 
 ### Environment Variables
 
-Edit `.devcontainer/.env` to customize behavior:
+Copy `.devcontainer/.env.example` to `.devcontainer/.env` and customize:
 
 | Variable | Default | Description |
 |----------|---------|-------------|
 | `CLAUDE_CONFIG_DIR` | `/workspaces/.claude` | Claude configuration directory |
-| `SETUP_CONFIG` | `true` | Copy config files during setup |
-| `OVERWRITE_CONFIG` | `true` | Overwrite existing configs |
-| `SETUP_ALIASES` | `true` | Add `cc` alias to shell |
-| `SETUP_PLUGINS` | `true` | Install official plugins |
+| `SETUP_CONFIG` | `true` | Copy config files during setup (per `file-manifest.json`) |
+| `SETUP_ALIASES` | `true` | Add `cc`/`claude`/`ccraw` aliases to shell |
+| `SETUP_AUTH` | `true` | Configure Git/NPM auth from `.secrets` |
+| `SETUP_PLUGINS` | `true` | Install official plugins + register marketplace |
+| `SETUP_UPDATE_CLAUDE` | `true` | Auto-update Claude Code on container start |
+| `SETUP_PROJECTS` | `true` | Auto-detect projects for VS Code Project Manager |
+| `PLUGIN_BLACKLIST` | `""` | Comma-separated plugin names to skip |
 
 ### Claude Code Settings
 
-Default settings are in `.devcontainer/config/settings.json`. These are copied to `/workspaces/.claude/settings.json` on first run.
+Default settings are in `.devcontainer/config/defaults/settings.json`. File copying is controlled by `config/file-manifest.json`, which specifies per-file overwrite behavior (`"if-changed"`, `"always"`, or `"never"`).
+
+To add a custom config file, append an entry to `file-manifest.json`:
+```json
+{
+  "src": "my-config.json",
+  "dest": "${WORKSPACE_ROOT}",
+  "overwrite": "if-changed"
+}
+```
 
 Key defaults:
 - **Model**: Claude Opus 4-6
 - **Default mode**: Plan (prompts before executing)
-- **Max output tokens**: 128,000
+- **Max output tokens**: 64,000
+
+### Keybindings
+
+Default keybindings are in `.devcontainer/config/defaults/keybindings.json` (empty by default — Claude Code defaults apply). Customize by adding entries to the `bindings` array.
+
+**VS Code Terminal Passthrough**: `Ctrl+P` and `Ctrl+F` are configured to pass through to the terminal (via `terminal.integrated.commandsToSkipShell`) so Claude Code receives them. Other VS Code shortcuts that conflict with Claude Code:
+
+| Shortcut | VS Code Action | Claude Code Action |
+|----------|---------------|-------------------|
+| `Ctrl+G` | Go to Line | `chat:externalEditor` |
+| `Ctrl+S` | Save File | `chat:stash` |
+| `Ctrl+T` | Open Symbol | `app:toggleTodos` |
+| `Ctrl+O` | Open File | `app:toggleTranscript` |
+| `Ctrl+B` | Toggle Sidebar | `task:background` |
+| `Ctrl+R` | Open Recent | `history:search` |
+
+For conflicting shortcuts, use Meta (Alt) variants or add custom keybindings.
 
 ### System Prompt
 
-The default system prompt is in `.devcontainer/config/main-system-prompt.md`. Override it by creating a `.claude/system-prompt.md` in your project directory.
+The default system prompt is in `.devcontainer/config/defaults/main-system-prompt.md`. Override it by creating a `.claude/system-prompt.md` in your project directory.
 
 ## Custom Features
 
@@ -200,25 +251,90 @@ CodeForge includes several custom devcontainer features:
 
 | Feature | Description |
 |---------|-------------|
+| `tmux` | Terminal multiplexer with Catppuccin theme for Agent Teams |
+| `agent-browser` | Headless browser automation for AI agents |
 | `claude-monitor` | Real-time token usage monitoring with ML predictions |
 | `ccusage` | Usage analytics CLI |
-| `ccstatusline` | Compact powerline status display |
+| `ccburn` | Visual token burn rate tracker with pace indicators |
+| `ccstatusline` | Status bar display (integrated into Claude Code, not standalone CLI) |
 | `ast-grep` | Structural code search using AST patterns |
 | `tree-sitter` | Parser with JS/TS/Python grammars |
 | `lsp-servers` | Pyright and TypeScript language servers |
-| `tmux` | Terminal multiplexer with Catppuccin theme for Agent Teams |
 | `biome` | Fast JS/TS/JSON/CSS formatter (global install) |
+| `notify-hook` | Desktop notifications on Claude completion |
+| `mcp-qdrant` | Qdrant vector database MCP server (optional) |
+| `mcp-reasoner` | Enhanced AI reasoning MCP server (optional) |
+
+## Agents & Skills
+
+The `code-directive` plugin includes specialized agent definitions and coding reference skills.
+
+### Custom Agents (17)
+
+Agent definitions in `plugins/devs-marketplace/plugins/code-directive/agents/` provide enhanced behavior when spawned via the `Task` tool. The `redirect-builtin-agents.py` hook transparently swaps built-in agent types to these custom agents.
+
+| Agent | Purpose |
+|-------|---------|
+| `architect` | System design and implementation planning |
+| `bash-exec` | Command execution specialist |
+| `claude-guide` | Claude Code feature guidance |
+| `debug-logs` | Log analysis and error diagnosis |
+| `dependency-analyst` | Dependency analysis and upgrades |
+| `doc-writer` | Documentation authoring |
+| `explorer` | Fast codebase search and navigation |
+| `generalist` | General-purpose multi-step tasks |
+| `git-archaeologist` | Git history forensics |
+| `migrator` | Code migration and upgrades |
+| `perf-profiler` | Performance profiling |
+| `refactorer` | Code refactoring with regression checks |
+| `researcher` | Research and information gathering |
+| `security-auditor` | Security vulnerability analysis |
+| `spec-writer` | Specification and requirements authoring |
+| `statusline-config` | ccstatusline configuration |
+| `test-writer` | Test authoring with pass verification |
+
+### Skills (16)
+
+Skills in `plugins/devs-marketplace/plugins/code-directive/skills/` provide domain-specific coding references:
+
+`claude-agent-sdk` · `claude-code-headless` · `debugging` · `docker` · `docker-py` · `fastapi` · `git-forensics` · `performance-profiling` · `pydantic-ai` · `refactoring-patterns` · `security-checklist` · `skill-building` · `specification-writing` · `sqlite` · `svelte5` · `testing`
+
+## Project Manager
+
+The `setup-projects.sh` script auto-detects projects under `/workspaces/` and maintains a `projects.json` file for the [Project Manager](https://marketplace.visualstudio.com/items?itemName=alefragnani.project-manager) VS Code extension. It watches for new projects via `inotifywait` and updates the project list automatically.
 
 ## Essential Gotchas
 
 - **Authentication required**: Run `claude` once to authenticate before using `cc`
 - **Plan mode default**: The container starts in "plan" mode, which prompts for approval before making changes
-- **Project-local config**: Config files are auto-copied to `.claude/` on container start via `setup-config.sh`
-- **GitHub auth persists**: Run `gh auth login` once; credentials survive container rebuilds (stored in `/workspaces/.gh/`)
+- **Config is managed by manifest**: `config/file-manifest.json` controls which files are copied and when — default `overwrite: "if-changed"` uses sha256 comparison. Persistent changes go in `.devcontainer/config/defaults/settings.json`
+- **GitHub auth persists**: Run `gh auth login` once or configure `.secrets`; credentials survive container rebuilds
 - **Agent Teams needs tmux**: Split panes only work inside tmux. Use the "Claude Teams (tmux)" VS Code terminal profile or `connect-external-terminal.sh` from WezTerm/iTerm2
 
+## Troubleshooting
+
+Common issues and solutions. For detailed troubleshooting, see [docs/troubleshooting.md](docs/troubleshooting.md).
+
+| Problem | Solution |
+|---------|----------|
+| `cc: command not found` | Run `source ~/.bashrc` or open a new terminal |
+| `claude` fails during startup | Background update may be in progress — wait 10s and retry |
+| GitHub push fails | Run `gh auth status` to check authentication |
+| Plugin not loading | Check `enabledPlugins` in `config/defaults/settings.json` |
+| Feature not installed | Check `devcontainer.json` for `"version": "none"` |
+| Tool version/status | Run `cc-tools` to list all tools with version info |
+| Full health check | Run `check-setup` to verify setup status |
+
 ## Further Reading
 
+**CodeForge Documentation**:
+- [Configuration Reference](docs/configuration-reference.md) — all env vars and config options
+- [Plugin System](docs/plugins.md) — plugin architecture and per-plugin docs
+- [Optional Features](docs/optional-features.md) — mcp-qdrant, mcp-reasoner, splitrail
+- [Keybinding Customization](docs/keybindings.md) — resolving VS Code conflicts
+- [Troubleshooting](docs/troubleshooting.md) — common issues and solutions
+
+**External**:
 - [Claude Code Documentation](https://docs.anthropic.com/en/docs/claude-code)
 - [Dev Containers Specification](https://containers.dev/)
 - [GitHub CLI Manual](https://cli.github.com/manual/)

package/.devcontainer/config/defaults/keybindings.json

@@ -0,0 +1,5 @@
+{
+  "$schema": "https://www.schemastore.org/claude-code-keybindings.json",
+  "$docs": "https://code.claude.com/docs/en/keybindings",
+  "bindings": []
+}

package/.devcontainer/config/{main-system-prompt.md → defaults/main-system-prompt.md}

@@ -25,7 +25,7 @@ When in <normal_mode>:
 8. <response_guidelines>
 
 If rules conflict, follow the highest-priority rule for the active mode
-and explicitly note the conflict.
+and explicitly note the conflict. Never silently violate a higher-priority rule.
 </rule_precedence>
 
 <operating_modes>
@@ -121,7 +121,13 @@ Main thread:
 Subagents (via `Task`):
 - Information gathering only
 - Report findings; never decide or modify
-- Types: `Explore` (fast search), `Plan` (design), `general-purpose` (complex), `Bash` (commands)
+- Core types (auto-redirected to enhanced custom agents):
+  - `Explore` → `explorer` (fast codebase search, haiku, read-only)
+  - `Plan` → `architect` (implementation planning, opus, read-only)
+  - `general-purpose` → `generalist` (multi-step tasks, inherit model)
+  - `Bash` → `bash-exec` (command execution, sonnet)
+  - `claude-code-guide` → `claude-guide` (Claude Code/SDK/API help, haiku)
+  - `statusline-setup` → `statusline-config` (status line setup, sonnet)
 
 Agent Teams (when enabled):
 - CRITICAL: Limit to 3-5 active teammates maximum based on task complexity
@@ -145,6 +151,55 @@ Failure handling:
 - Surface errors clearly; never hide failures
 </orchestration>
 
+<specialist_agents>
+Specialist agents are available as teammates via the Task tool. Prefer
+delegating to a specialist over doing the work yourself when the task
+matches their domain.
+
+Agents:
+- researcher — codebase & web research (sonnet, read-only)
+- test-writer — writes test suites (opus, auto-verify)
+- refactorer — safe code transformations (opus, tests after every edit)
+- security-auditor — OWASP audit & secrets scan (sonnet, read-only)
+- doc-writer — README, API docs, docstrings (opus)
+- migrator — framework upgrades & version bumps (opus)
+- git-archaeologist — git history investigation (haiku, read-only)
+- dependency-analyst — outdated/vulnerable deps (haiku, read-only)
+- spec-writer — EARS requirements & acceptance criteria (opus, read-only)
+- perf-profiler — profiling & benchmarks (sonnet, read-only)
+- debug-logs — log analysis & diagnostics (sonnet, read-only)
+
+Skills (auto-suggested, also loadable via Skill tool):
+- fastapi, sqlite, svelte5, docker, docker-py, pydantic-ai
+- testing, debugging, claude-code-headless, claude-agent-sdk
+- skill-building, refactoring-patterns, security-checklist
+- git-forensics, specification-writing, performance-profiling
+
+Built-in agent redirect:
+All 6 built-in agent types (Explore, Plan, general-purpose, Bash,
+claude-code-guide, statusline-setup) are automatically redirected to
+enhanced custom agents via a PreToolUse hook. You can use either the
+built-in name or the custom name — the redirect is transparent.
+
+Team construction:
+When building agent teams, prefer custom agents over generic
+`generalist` teammates when the task aligns with a specialist's
+domain. Custom agents carry frontloaded skills, safety hooks, and
+tailored instructions that make them more effective and safer than
+a generalist agent doing the same work.
+
+Example team compositions:
+- Feature build: researcher (investigate) + test-writer (tests) + doc-writer (docs)
+- Security hardening: security-auditor (find issues) + dependency-analyst (deps)
+- Codebase cleanup: refactorer (transform) + test-writer (coverage gaps)
+- Migration project: researcher (research guides) + migrator (execute)
+- Performance work: perf-profiler (measure) + refactorer (optimize)
+
+When a user's request clearly falls within a specialist's domain,
+suggest delegation. Do not force it — the user may prefer to work
+directly.
+</specialist_agents>
+
 <structural_search>
 Prefer structural tools over text search when syntax matters:
 
@@ -258,6 +313,7 @@ Verify before assuming:
   or approach — ASK. Do not pick a default.
 - Do not assume file paths — read the filesystem to confirm.
 - Do not assume platform capabilities — research first.
+- Never fabricate file paths, API signatures, tool behavior, or external facts. Verify or ask.
 
 Read before writing:
 - Before creating or modifying any file, read the target directory and
@@ -286,6 +342,11 @@ No silent deviations:
   before doing something different.
 - Never silently substitute an easier approach.
 - Never silently skip a step because it seems hard or uncertain.
+
+When an approach fails:
+- Diagnose the cause before retrying.
+- Try an alternative strategy; do not repeat the failed path.
+- Surface the failure and revised approach to the user.
 </execution_discipline>
 
 <code_directives>
@@ -335,6 +396,78 @@ offset = len(header) + 1  # null terminator in legacy format
 offset = len(header) + 1  # add one to header length
 </documentation>
 
+<specification_management>
+Specs and project-level docs live in `.specs/` at the project root.
+
+You (the orchestrator) own spec creation and maintenance. Agents do not update
+specs directly — they flag when specs need attention, and you handle it.
+
+Folder structure:
+```
+.specs/
+├── roadmap.md              # What each version delivers and why (≤150 lines)
+├── lessons-learned.md      # Workflow anti-patterns
+├── ci-cd.md                # CI/CD pipeline, environments, deploy process
+├── v0.1.0.md               # Feature spec (single file per version if ≤200 lines)
+├── v0.2.0/                 # Version folder when multiple specs needed
+│   ├── overview.md         # Parent linking sub-specs (≤50 lines)
+│   └── feature-name.md     # Sub-spec per feature (≤200 lines each)
+```
+
+Spec rules:
+- ≤200 lines per spec file. Split by feature boundary if larger; link via
+  a parent overview (≤50 lines). Monolithic specs rot — no AI context window
+  can use a 4,000-line spec.
+- Reference files, don't reproduce them. Write "see `src/engine/db/migrations/002.sql`
+  lines 48-70" — never paste full schemas, SQL DDL, or type definitions. The
+  code is the source of truth; duplicated snippets go stale.
+- Each spec is independently loadable. Include version, status, last-updated,
+  intent, key file paths, and acceptance criteria in every spec file.
+
+Standard template:
+```
+# Feature: [Name]
+**Version:** v0.X.0
+**Status:** implemented | partial | planned
+**Last Updated:** YYYY-MM-DD
+
+## Intent
+## Acceptance Criteria
+## Key Files
+## Schema / Data Model (reference only — no inline DDL)
+## API Endpoints (table: Method | Path | Description)
+## Requirements (EARS format: FR-1, NFR-1)
+## Dependencies
+## Out of Scope
+## Implementation Notes (as-built deviations — post-implementation only)
+## Discrepancies (spec vs reality gaps)
+```
+
+As-built workflow (after implementing a feature):
+1. Find the feature spec: Glob `.specs/**/*.md`
+2. Set status to "implemented" or "partial"
+3. Check off acceptance criteria with passing tests
+4. Add Implementation Notes for any deviations
+5. Update file paths if they changed
+6. Update Last Updated date
+If no spec exists and the change is substantial, create one or note "spec needed."
+
+Document types — don't mix:
+- Roadmap (`.specs/roadmap.md`): what each version delivers and why. No
+  implementation detail — that belongs in feature specs. Target: ≤150 lines.
+- Feature spec (`.specs/v*.md` or `.specs/vX.Y.0/*.md`): how a feature works.
+  ≤200 lines.
+- CI/CD (`.specs/ci-cd.md`): pipeline stages, environments, deploy process,
+  and automation config. Keep declarative — reference workflow files, don't
+  reproduce them.
+- Lessons learned (`.specs/lessons-learned.md`): workflow anti-patterns.
+
+After a version ships, update feature specs to as-built status. Delete or
+merge superseded planning artifacts — don't accumulate snapshot documents.
+
+Delegate spec writing to the spec-writer agent when creating new specs.
+</specification_management>
+
 <code_standards>
 Files:
 - Small, focused, single reason to change

package/.devcontainer/config/{settings.json → defaults/settings.json}

@@ -9,19 +9,30 @@
     "ANTHROPIC_DEFAULT_HAIKU_MODEL": "claude-haiku-4-5-20251001",
     "BASH_DEFAULT_TIMEOUT_MS": "240000",
     "BASH_MAX_TIMEOUT_MS": "600000",
-    "CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC": "true",
-    "CLAUDE_CODE_MAX_OUTPUT_TOKENS": "128000",
+    "CLAUDE_CODE_MAX_OUTPUT_TOKENS": "64000",
     "MAX_MCP_OUTPUT_TOKENS": "10000",
     "MAX_THINKING_TOKENS": "63999",
     "MCP_TIMEOUT": "120000",
     "MCP_TOOL_TIMEOUT": "30000",
-    "CLAUDE_AUTOCOMPACT_PCT_OVERRIDE": 95,
+    "CLAUDE_AUTOCOMPACT_PCT_OVERRIDE": "95",
     "CLAUDE_CODE_SHELL": "zsh",
-    "FORCE_AUTOUPDATE_PLUGINS": true,
+    "FORCE_AUTOUPDATE_PLUGINS": "1",
+
     "ENABLE_TOOL_SEARCH": "auto:5",
     "CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1",
     "CLAUDE_CODE_EFFORT_LEVEL": "high",
-    "CLAUDE_CODE_ENABLE_TASKS": "true"
+    "CLAUDE_CODE_ENABLE_TASKS": "true",
+    "CLAUDE_CODE_DISABLE_AUTO_MEMORY": "0",
+    "ENABLE_CLAUDE_CODE_SM_COMPACT": "1",
+    "CLAUDE_CODE_FORCE_GLOBAL_CACHE": "1",
+    "CLAUDE_CODE_PLAN_MODE_INTERVIEW_PHASE": "true",
+    "CLAUDE_CODE_PLAN_V2_AGENT_COUNT": "3",
+    "CLAUDE_CODE_PLAN_MODE_REQUIRED": "true",
+
+    "CLAUDE_CODE_MAX_TOOL_USE_CONCURRENCY": "5",
+    "CLAUDE_CODE_MAX_RETRIES": "1",
+    "BASH_MAX_OUTPUT_LENGTH": "15000",
+    "TASK_MAX_OUTPUT_LENGTH": "64000"
   },
   "teammateMode": "auto",
   "effortLevel": "high",
@@ -45,7 +56,15 @@
     "command": "/usr/local/bin/ccstatusline-wrapper"
   },
   "enabledPlugins": {
-    "frontend-design@claude-code-plugins": true
+    "frontend-design@claude-code-plugins": true,
+    "codeforge-lsp@devs-marketplace": true,
+    "ticket-workflow@devs-marketplace": true,
+    "notify-hook@devs-marketplace": true,
+    "dangerous-command-blocker@devs-marketplace": true,
+    "protected-files-guard@devs-marketplace": true,
+    "auto-formatter@devs-marketplace": true,
+    "auto-linter@devs-marketplace": true,
+    "code-directive@devs-marketplace": true
   },
   "autoUpdatesChannel": "latest"
 }

package/.devcontainer/config/file-manifest.json

@@ -0,0 +1,20 @@
+[
+  {
+    "src": "defaults/settings.json",
+    "dest": "${CLAUDE_CONFIG_DIR}",
+    "enabled": true,
+    "overwrite": "if-changed"
+  },
+  {
+    "src": "defaults/keybindings.json",
+    "dest": "${CLAUDE_CONFIG_DIR}",
+    "enabled": true,
+    "overwrite": "if-changed"
+  },
+  {
+    "src": "defaults/main-system-prompt.md",
+    "dest": "${CLAUDE_CONFIG_DIR}",
+    "enabled": true,
+    "overwrite": "if-changed"
+  }
+]

package/.devcontainer/devcontainer.json

@@ -12,6 +12,11 @@
     "TMPDIR": "/workspaces/.tmp"
   },
 
+  // Feature install order: external runtimes first (Node, uv, Go, Bun),
+  // then Claude Code (needs Node), then custom features.
+  // npm-dependent features (agent-browser, ccusage, ccburn, biome, lsp-servers)
+  // must come after Node. uv-dependent features (ruff, claude-monitor) must
+  // come after uv. notify-hook is last (lightweight, no dependencies).
   "overrideFeatureInstallOrder": [
     "ghcr.io/devcontainers/features/node",
     "ghcr.io/devcontainers/features/github-cli",
@@ -24,10 +29,16 @@
     "./features/agent-browser",
     "./features/claude-monitor",
     "./features/ccusage",
+    "./features/ccburn",
     "./features/ccstatusline",
     "./features/ast-grep",
     "./features/tree-sitter",
     "./features/lsp-servers",
+    "./features/ruff",
+    "./features/shfmt",
+    "./features/dprint",
+    "./features/shellcheck",
+    "./features/hadolint",
     "./features/biome",
     "./features/notify-hook"
   ],
@@ -56,6 +67,11 @@
       "installer": "uv",
       "username": "automatic"
     },
+    "./features/ccburn": {
+      "version": "latest",
+      "shells": "both",
+      "username": "automatic"
+    },
     "./features/ccstatusline": {
       "username": "automatic"
     },
@@ -63,6 +79,16 @@
     "./features/tree-sitter": {},
     "./features/lsp-servers": {},
     "./features/agent-browser": {},
+    "./features/ruff": {
+      "version": "latest",
+      "username": "automatic"
+    },
+    "./features/shfmt": {},
+    "./features/dprint": {
+      "username": "automatic"
+    },
+    "./features/shellcheck": {},
+    "./features/hadolint": {},
     "./features/biome": {},
     "./features/notify-hook": {
       "enableBell": true,
@@ -89,14 +115,24 @@
         },
         "terminal.integrated.defaultProfile.linux": "bash",
         "terminal.integrated.enableBell": true,
+        "terminal.integrated.commandsToSkipShell": [
+          "-workbench.action.quickOpen",
+          "-workbench.action.terminal.focusFind"
+        ],
         "remote.extensionKind": {
           "wenbopan.vscode-terminal-osc-notifier": ["ui"]
-        }
+        },
+        "projectManager.git.baseFolders": ["/workspaces"],
+        "projectManager.git.maxDepthRecursion": 1,
+        "projectManager.showProjectNameInStatusBar": true,
+        "projectManager.openInNewWindowWhenClickingInStatusBar": false,
+        "projectManager.projectsLocation": "/workspaces/.config/project-manager"
       },
       "extensions": [
         "wenbopan.vscode-terminal-osc-notifier",
         "GitHub.vscode-github-actions",
-        "fabiospampinato.vscode-todo-plus"
+        "fabiospampinato.vscode-todo-plus",
+        "alefragnani.project-manager"
       ]
     }
   },