codeforge-dev 1.9.0 → 1.11.0

package/.devcontainer/features/ccms/README.md

@@ -0,0 +1,50 @@
+# ccms - Claude Code Message Searcher
+
+Installs [ccms](https://github.com/mkusaka/ccms), a high-performance CLI for searching Claude Code session JSONL files.
+
+## Features
+
+- SIMD-accelerated JSON parsing with parallel file processing
+- Boolean query syntax: AND, OR, NOT, regex, quoted literals
+- Filter by role (user/assistant/system), session ID, timestamp ranges, project paths
+- Interactive fzf-like TUI mode (when run without arguments)
+- Multiple output formats: text, JSON, JSONL
+- Shell completion for bash, zsh, fish
+
+## Options
+
+| Option | Type | Default | Description |
+|--------|------|---------|-------------|
+| `version` | string | `latest` | `latest` builds from main, `none` skips, or a git commit hash |
+| `username` | string | `automatic` | Container user to install for |
+
+## Dependencies
+
+Requires the Rust devcontainer feature:
+```json
+"ghcr.io/devcontainers/features/rust:1": {}
+```
+
+## Usage
+
+```bash
+# Search current project (recommended)
+ccms --project $(pwd) "query"
+
+# Filter by who said it
+ccms -r assistant "architecture decision"
+ccms -r user "auth approach"
+
+# Boolean queries
+ccms "error AND connection"
+ccms "(auth OR authentication) AND NOT test"
+
+# Time-scoped
+ccms --since "1 day ago" "recent work"
+
+# JSON output for scripting
+ccms -f json "query" -n 10
+
+# Interactive TUI
+ccms
+```

package/.devcontainer/features/ccms/devcontainer-feature.json

@@ -0,0 +1,21 @@
+{
+	"id": "ccms",
+	"version": "1.0.0",
+	"name": "ccms - Claude Code Message Searcher",
+	"description": "Installs ccms CLI for searching Claude Code session JSONL files with boolean queries, role filtering, and JSON output",
+	"maintainer": "AnExiledDev",
+	"documentationURL": "https://github.com/mkusaka/ccms",
+	"options": {
+		"version": {
+			"type": "string",
+			"description": "ccms version to install ('latest' builds from main, 'none' skips installation, or a git ref/commit hash)",
+			"default": "latest"
+		},
+		"username": {
+			"type": "string",
+			"description": "Container user to install for",
+			"default": "automatic"
+		}
+	},
+	"installsAfter": ["ghcr.io/devcontainers/features/rust:1"]
+}

package/.devcontainer/features/ccms/install.sh

@@ -0,0 +1,105 @@
+#!/bin/bash
+set -euo pipefail
+
+# === SETUP ===
+cleanup() {
+    :
+}
+trap cleanup EXIT
+
+# === IMPORT OPTIONS ===
+CCMS_VERSION="${VERSION:-latest}"
+USERNAME="${USERNAME:-automatic}"
+
+# Skip installation if version is "none"
+if [ "${CCMS_VERSION}" = "none" ]; then
+    echo "[ccms] Skipping installation (version=none)"
+    exit 0
+fi
+
+echo "[ccms] Starting ccms installation..."
+
+# === VALIDATE DEPENDENCIES ===
+# Source cargo env if available (Rust feature installs via rustup)
+if [ -f /usr/local/cargo/env ]; then
+    source /usr/local/cargo/env
+elif [ -f "${HOME}/.cargo/env" ]; then
+    source "${HOME}/.cargo/env"
+fi
+
+if ! command -v cargo &>/dev/null; then
+    echo "[ccms] ERROR: cargo is not available"
+    echo "  Ensure the Rust devcontainer feature is installed first:"
+    echo "  \"ghcr.io/devcontainers/features/rust:1\": {}"
+    exit 1
+fi
+
+echo "[ccms] Using cargo: $(cargo --version)"
+
+# === DETECT USER ===
+if [ "${USERNAME}" = "auto" ] || [ "${USERNAME}" = "automatic" ]; then
+    USERNAME=""
+    for CURRENT_USER in vscode node codespace; do
+        if id -u "${CURRENT_USER}" >/dev/null 2>&1; then
+            USERNAME=${CURRENT_USER}
+            break
+        fi
+    done
+    [ -z "${USERNAME}" ] && USERNAME=root
+elif [ "${USERNAME}" = "none" ] || ! id -u "${USERNAME}" >/dev/null 2>&1; then
+    USERNAME=root
+fi
+
+echo "[ccms] Installing for user: ${USERNAME}"
+
+# === INSTALL ===
+REPO_URL="https://github.com/mkusaka/ccms"
+
+if [ "${CCMS_VERSION}" = "latest" ]; then
+    echo "[ccms] Building from main branch..."
+    cargo install --git "${REPO_URL}" 2>&1 | tail -5
+else
+    echo "[ccms] Building from ref: ${CCMS_VERSION}..."
+    cargo install --git "${REPO_URL}" --rev "${CCMS_VERSION}" 2>&1 | tail -5
+fi
+
+# === ENSURE BINARY IS ON PATH ===
+# cargo install puts binaries in $CARGO_HOME/bin or ~/.cargo/bin
+# Symlink to /usr/local/bin so it's available to all users
+CARGO_BIN="${CARGO_HOME:-$HOME/.cargo}/bin/ccms"
+if [ -f "${CARGO_BIN}" ] && [ ! -f /usr/local/bin/ccms ]; then
+    ln -s "${CARGO_BIN}" /usr/local/bin/ccms
+    echo "[ccms] Symlinked ${CARGO_BIN} → /usr/local/bin/ccms"
+fi
+
+# === VERIFICATION ===
+echo "[ccms] Verifying installation..."
+if command -v ccms &>/dev/null; then
+    INSTALLED_VERSION=$(ccms --version 2>/dev/null || echo "unknown")
+    echo "[ccms] ✓ ccms installed: ${INSTALLED_VERSION}"
+else
+    echo "[ccms] WARNING: ccms not found on PATH after installation"
+    echo "  Binary location: ${CARGO_BIN}"
+    echo "  You may need to add cargo bin to PATH"
+fi
+
+# === SUMMARY ===
+echo ""
+echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
+echo "  ccms Installation Complete"
+echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
+echo ""
+echo "Configuration:"
+echo "  • User: ${USERNAME}"
+echo "  • Version: ${CCMS_VERSION}"
+echo "  • Binary: $(which ccms 2>/dev/null || echo "${CARGO_BIN}")"
+echo ""
+echo "Usage:"
+echo "  ccms \"query\"                    # Search all sessions"
+echo "  ccms --project \$(pwd) \"query\"   # Search current project"
+echo "  ccms -r user \"query\"            # Filter by role"
+echo "  ccms -f json \"query\" -n 10      # JSON output, limited"
+echo "  ccms --since \"1 day ago\" \"q\"    # Time-scoped search"
+echo "  ccms                            # Interactive TUI mode"
+echo ""
+echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"

package/.devcontainer/features/ccstatusline/install.sh

@@ -100,6 +100,9 @@ CONFIG_JSON=$(jq -n '{
         [
             {id: "cc-resume-session", type: "custom-command", commandPath: "/usr/local/bin/ccstatusline-session-resume", timeout: 500, preserveColors: false, maxWidth: 50, color: "cyan", backgroundColor: "bgBrightBlack"}
         ],
+        [
+            {id: "cc-cwd", type: "custom-command", commandPath: "/usr/local/bin/ccstatusline-cwd", timeout: 500, preserveColors: false, maxWidth: 40, color: "brightWhite", backgroundColor: "bgBrightBlack"}
+        ],
         [
             {id: "ccburn-compact", type: "custom-command", commandPath: "/usr/local/bin/ccburn-statusline", timeout: 8000, preserveColors: true, maxWidth: 80, color: "green", backgroundColor: "bgBlack"}
         ]
@@ -181,6 +184,24 @@ SESSION_EOF
 chmod +x /usr/local/bin/ccstatusline-session-resume
 echo "[ccstatusline] ✓ Session resume helper installed at /usr/local/bin/ccstatusline-session-resume"
 
+# Create CWD helper script for custom-command widget
+# Reads Claude Code JSON from stdin, outputs the last path segment of cwd
+echo "[ccstatusline] Creating CWD helper..."
+cat > /usr/local/bin/ccstatusline-cwd <<'CWD_EOF'
+#!/bin/bash
+# Reads Claude Code JSON from stdin, outputs basename of cwd
+# Used by ccstatusline custom-command widget
+CWD=$(jq -r '.cwd // empty' 2>/dev/null)
+if [ -n "$CWD" ]; then
+    basename "$CWD"
+else
+    echo "..."
+fi
+CWD_EOF
+
+chmod +x /usr/local/bin/ccstatusline-cwd
+echo "[ccstatusline] ✓ CWD helper installed at /usr/local/bin/ccstatusline-cwd"
+
 # Create wrapper script to protect configuration
 echo "[ccstatusline] Creating wrapper script..."
 cat > /usr/local/bin/ccstatusline-wrapper <<'WRAPPER_EOF'
@@ -302,7 +323,7 @@ echo ""
 echo "Configuration:"
 echo "  • Config file: ${CONFIG_FILE}"
 echo "  • User: ${USERNAME}"
-echo "  • Theme: Powerline (7 lines, 16 widgets, ANSI colors)"
+echo "  • Theme: Powerline (8 lines, 17 widgets, ANSI colors)"
 echo "  • Protected by: /usr/local/bin/ccstatusline-wrapper"
 echo ""
 echo "Display:"
@@ -312,7 +333,8 @@ echo "  Line 3: Git Branch | Git Changes | Git Worktree"
 echo "  Line 4: Session Clock | Session Cost | Block Timer"
 echo "  Line 5: Tokens Total | Version"
 echo "  Line 6: Session ID"
-echo "  Line 7: Burn Rate (ccburn compact)"
+echo "  Line 7: Working Directory"
+echo "  Line 8: Burn Rate (ccburn compact)"
 echo ""
 echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
 echo "  Next Steps"

package/.devcontainer/plugins/devs-marketplace/.claude-plugin/marketplace.json

@@ -90,7 +90,7 @@
 		},
 		{
 			"name": "code-directive",
-			"description": "17 custom agents, 16 coding skills, agent redirection, syntax validation, and skill auto-suggestion",
+			"description": "17 custom agents, 28 coding skills, agent redirection, syntax validation, and skill auto-suggestion",
 			"version": "1.0.0",
 			"source": "./plugins/code-directive",
 			"category": "development"
@@ -101,6 +101,13 @@
 			"version": "1.0.0",
 			"source": "./plugins/auto-code-quality",
 			"category": "development"
+		},
+		{
+			"name": "workspace-scope-guard",
+			"description": "Enforces working directory scope — blocks writes and warns on reads outside the project",
+			"version": "1.0.0",
+			"source": "./plugins/workspace-scope-guard",
+			"category": "safety"
 		}
 	]
 }

package/.devcontainer/plugins/devs-marketplace/plugins/code-directive/agents/architect.md

@@ -18,6 +18,7 @@ skills:
   - spec-new
   - spec-update
   - spec-init
+  - spec-review
 hooks:
   PreToolUse:
     - matcher: Bash
@@ -171,8 +172,9 @@ Based on your exploration:
    or update. Distinguish:
    - **Roadmap entry**: one-line description of what the version delivers (no
      implementation detail — that belongs in specs)
-   - **Feature spec**: ≤200 line file following the standard template (Version,
-     Status, Intent, Acceptance Criteria, Key Files, Schema, API, Dependencies)
+   - **Feature spec**: file following the standard template (Version,
+     Status, Intent, Acceptance Criteria, Key Files, Schema, API, Dependencies).
+     Aim for ~200 lines; split into sub-specs if significantly longer.
    - **As-built update**: if modifying an existing feature, identify which spec
      to update post-implementation
    Plans that mix roadmap-level and spec-level detail produce artifacts too
@@ -239,7 +241,7 @@ List the 3-7 files most critical for implementing this plan:
 - `/path/to/test_file.py` — Brief reason (e.g., "Test patterns to follow")
 
 ### Documentation Outputs
-- New spec: `.specs/vX.Y.0/feature-name.md` (≤200 lines)
+- New spec: `.specs/vX.Y.0/feature-name.md`
 - Updated spec: `.specs/vX.Y.0/existing-feature.md` — changes: [list]
 - Roadmap update: `.specs/roadmap.md` — add `[ ] feature` to vX.Y.0
 

package/.devcontainer/plugins/devs-marketplace/plugins/code-directive/agents/claude-guide.md

@@ -66,7 +66,7 @@ Direct model interaction via the Claude API (formerly Anthropic API). Covers Mes
 # Project-level configuration (relative to workspace root)
 .claude/settings.json        # Active settings
 .claude/keybindings.json     # Active keybindings
-.claude/system-prompt.md     # Active system prompt
+.claude/main-system-prompt.md # Active system prompt
 CLAUDE.md                    # Project instructions
 
 # DevContainer configuration

package/.devcontainer/plugins/devs-marketplace/plugins/code-directive/agents/doc-writer.md

@@ -160,9 +160,9 @@ For large codebases, focus on the public API surface rather than trying to docum
 
 Produce documentation that serves the target audience. Different doc types have different readers.
 
-**Sizing rule:** Documentation files consumed by AI (CLAUDE.md, specs, architecture docs)
-should be ≤200 lines each. Split large documents by concern. Each file should be
-independently useful without requiring other docs in the same context window.
+**Sizing guideline:** Documentation files consumed by AI (CLAUDE.md, specs, architecture docs)
+should aim for ~200 lines each. Split large documents by concern when practical. Each file
+should be independently useful without requiring other docs in the same context window.
 
 ## Documentation Types
 
@@ -267,10 +267,10 @@ Follow these principles in all documentation:
 - **Architecture docs requested**: Trace the system's component boundaries, data flows, and key decisions. Produce a document that would onboard a new developer effectively.
 - **No specific request**: Ask the user what documentation they need. If they point to a file or module, offer to add inline documentation to its public API.
 - **Behavior unclear**: If you read a function and cannot determine its exact behavior, document what you can verify and add a `TODO: verify — [specific question]` annotation so a human can fill in the gap.
-- **Version ships** (e.g., "consolidate v0.1.0 docs"): Read all build-time artifacts
-  for the version (architecture docs, decision records, phase plans). Consolidate
-  into a single as-built spec. Delete or merge superseded planning artifacts —
-  don't accumulate snapshot documents. Update the relevant spec in place.
+- **Milestone ships** (e.g., "consolidate milestone docs"): Read all build-time artifacts
+  for the milestone (architecture docs, decision records, phase plans). Consolidate
+  into as-built specs. Delete or merge superseded planning artifacts —
+  don't accumulate snapshot documents. Update the relevant specs in place.
 - **Always report** what was documented, what was verified versus assumed, and what needs human review.
 
 ## Output Format

package/.devcontainer/plugins/devs-marketplace/plugins/code-directive/agents/generalist.md

@@ -17,6 +17,7 @@ skills:
   - spec-update
   - spec-check
   - spec-init
+  - spec-review
 ---
 
 # Generalist Agent

package/.devcontainer/plugins/devs-marketplace/plugins/code-directive/agents/spec-writer.md

@@ -20,6 +20,8 @@ skills:
   - spec-update
   - spec-check
   - spec-init
+  - spec-refine
+  - spec-review
 ---
 
 # Spec Writer Agent
@@ -57,10 +59,13 @@ When uncertain, investigate first — read the code, check the docs — rather t
 - **NEVER** make assumptions about behavior without checking the codebase. Use `Read`, `Glob`, and `Grep` to understand the current system before specifying changes.
 - **NEVER** write vague requirements like "the system should be fast" or "the UI should be user-friendly." Every requirement must be specific, measurable, and testable.
 - **NEVER** combine multiple independent requirements into a single statement. One requirement per line — this makes requirements individually testable and trackable.
-- **NEVER** produce a specification exceeding 200 lines. If a feature requires
-  more, split it into independently loadable sub-specs (one per sub-feature)
-  with a parent overview file that links them. Monolithic specs rot faster
-  than they're consumed — no AI context window can use a 4,000-line spec.
+- **NEVER** present decisions as settled facts unless the user explicitly approved them. Tech choices, architecture decisions, scope boundaries, performance targets, and behavioral defaults that you chose without user input MUST go in `## Open Questions` with options and trade-offs — not in Requirements as decided items.
+- **ALL** requirements you generate MUST be tagged `[assumed]`. You never produce `[user-approved]` requirements — only `/spec-refine` does that after explicit user validation.
+- **ALL** specs you produce MUST carry `**Approval:** draft`. After presenting a draft, state: "This spec requires `/spec-refine` before implementation can begin. All requirements are marked [assumed] until user-approved."
+- **Aim for ~200 lines per spec.** When a spec grows beyond that, recommend
+  splitting into separate specs in the domain folder. Shorter specs are
+  easier to consume and maintain, but complex features sometimes need more
+  space — don't sacrifice completeness for an arbitrary cap.
 - **NEVER** reproduce source code, SQL schemas, or type definitions inline.
   Reference file paths instead (e.g., "see `src/engine/db/migrations/002.sql`
   lines 48-70"). The code is the source of truth; duplicated snippets go stale.
@@ -116,9 +121,10 @@ Write the specification using the formats below.
 3. **Write acceptance criteria** — Given/When/Then scenarios that define "done."
 4. **Define non-functional requirements** — Performance, security, accessibility where relevant.
 5. **List open questions** — Any unresolved decisions or unknowns that need stakeholder input.
-6. **Check length** — Count lines. If the draft exceeds 200 lines, split into
-   sub-specs by feature boundary. Create a parent overview (≤50 lines) linking
-   the sub-specs. Each sub-spec must be independently loadable.
+6. **Check length** — If the draft exceeds ~200 lines, consider whether it
+   would be clearer as separate specs in the domain folder. Each spec
+   should be independently loadable. If the length is justified by
+   complexity, note it and proceed.
 7. **Reference, don't reproduce** — Scan your draft for inline code blocks
    containing schemas, SQL, type definitions, or configuration. Replace with
    file path references and brief descriptions of what's there.
@@ -232,9 +238,10 @@ Present specifications in this structure:
 
 ```markdown
 # Feature: [Name]
-**Version:** v0.X.0
+**Domain:** [domain-name]
 **Status:** planned
 **Last Updated:** YYYY-MM-DD
+**Approval:** draft
 
 ## Intent
 [Problem statement + why — what exists now, what should change, who is affected]
@@ -258,18 +265,21 @@ Present specifications in this structure:
 ## Requirements
 
 ### Functional Requirements
-FR-1: [EARS requirement]
-FR-2: [EARS requirement]
+FR-1 [assumed]: [EARS requirement]
+FR-2 [assumed]: [EARS requirement]
 ...
 
 ### Non-Functional Requirements
-NFR-1: [EARS requirement]
-NFR-2: [EARS requirement]
+NFR-1 [assumed]: [EARS requirement]
+NFR-2 [assumed]: [EARS requirement]
 ...
 
 ## Dependencies
 - [External system or module this feature depends on]
 
+## Resolved Questions
+[Populated by `/spec-refine`. Decisions explicitly approved by the user.]
+
 ## Open Questions
 [Group related unknowns. For each question, provide:]
 1. [Question] — **Type**: missing info / ambiguous behavior / policy decision

package/.devcontainer/plugins/devs-marketplace/plugins/code-directive/hooks/hooks.json

@@ -40,6 +40,16 @@
 						"timeout": 3
 					}
 				]
+			},
+			{
+				"matcher": "",
+				"hooks": [
+					{
+						"type": "command",
+						"command": "python3 ${CLAUDE_PLUGIN_ROOT}/scripts/inject-cwd.py",
+						"timeout": 3
+					}
+				]
 			}
 		],
 		"Stop": [
@@ -49,7 +59,7 @@
 					{
 						"type": "command",
 						"command": "python3 ${CLAUDE_PLUGIN_ROOT}/scripts/advisory-test-runner.py",
-						"timeout": 65
+						"timeout": 20
 					},
 					{
 						"type": "command",