release: merge develop into main for v0.14.1

Author: DavidsonGomes

.claude/agents/compass-planner.md

@@ -46,7 +46,7 @@ You produce **two artifacts** in Phase 2 of the canonical workflow (see `.claude
 
 **Where to save:**
 
-- **Feature-scoped work** (non-trivial, named feature): save both to `workspace/features/{feature-slug}/`
+- **Feature-scoped work** (non-trivial, named feature): save both to `workspace/development/features/{feature-slug}/`
   - `[C]prd-{feature}.md`
   - `[C]plan-{feature}.md`
 - **Standalone/one-off work** (no feature name, small scope): save to `workspace/development/plans/[C]plan-{name}-{YYYY-MM-DD}.md` and skip the PRD
@@ -63,9 +63,9 @@ Use the template at `.claude/templates/dev-work-plan.md` for the plan. The PRD s
 |---|---|---|---|
 | Typo, rename, tiny bug | ❌ | ❌ (go direct to Bolt) | — |
 | Small bug fix, clear repro | ❌ | ✅ minimal | `workspace/development/plans/` |
-| Feature with clear acceptance criteria | ✅ (short) | ✅ | `workspace/features/{slug}/` |
-| New feature with ambiguity | ✅ (full) | ✅ | `workspace/features/{slug}/` |
-| High-stakes migration | ✅ (full) + RALPLAN-DR | ✅ | `workspace/features/{slug}/` |
+| Feature with clear acceptance criteria | ✅ (short) | ✅ | `workspace/development/features/{slug}/` |
+| New feature with ambiguity | ✅ (full) | ✅ | `workspace/development/features/{slug}/` |
+| High-stakes migration | ✅ (full) + RALPLAN-DR | ✅ | `workspace/development/features/{slug}/` |
 
 **Rule:** when in doubt, produce a short PRD. A 10-line PRD is infinitely better than a missing one.
 
@@ -115,13 +115,13 @@ Use the template at `.claude/templates/dev-work-plan.md` for the plan. The PRD s
 
 1. Always read your memory folder first: `.claude/agent-memory/compass-planner/`
 2. Read `.claude/rules/dev-phases.md` — you are the owner of Phase 2 (Planning)
-3. Check for a feature folder: is there a `workspace/features/{slug}/` for this work? If yes, read any prior artifacts (discovery, etc.) to inherit context
+3. Check for a feature folder: is there a `workspace/development/features/{slug}/` for this work? If yes, read any prior artifacts (discovery, etc.) to inherit context
 4. Classify intent: Trivial / Refactoring / Build from Scratch / Mid-sized
 5. For codebase facts, spawn `@scout-explorer` (in parallel with other research)
 6. Ask user only about: priorities, timelines, scope decisions, risk tolerance, preferences
 7. For non-trivial work, consult `@echo-analyst` first for gap analysis
 8. Produce the PRD first (if applicable), then the plan derived from it
-9. Save to the feature folder (`workspace/features/{slug}/`) or `workspace/development/plans/` per the table above
+9. Save to the feature folder (`workspace/development/features/{slug}/`) or `workspace/development/plans/` per the table above
 10. Display confirmation summary, wait for explicit "proceed"
 11. On approval, hand off to `@apex-architect` (Phase 3) for non-trivial features, or directly to `@bolt-executor` (Phase 4) for clear executable plans
 12. Update agent memory with patterns worth remembering

.claude/agents/helm-conductor.md

@@ -37,11 +37,11 @@ Read `dev-phases.md` at the start of every session. Your recommendations must al
 
 You don't have a dedicated working folder — you don't produce artifacts. You read from:
 
-- `workspace/features/` — all active feature folders
+- `workspace/development/features/` — all active feature folders
 - `workspace/development/plans/` — standalone plans not yet in feature folders
 - `workspace/development/stories/` — story files (if present)
 
-When you need to record a sequencing decision, append it to `workspace/features/{feature}/[C]helm-notes.md` in the relevant feature — short entries only.
+When you need to record a sequencing decision, append it to `workspace/development/features/{feature}/[C]helm-notes.md` in the relevant feature — short entries only.
 
 ## Identity
 
@@ -51,7 +51,7 @@ When you need to record a sequencing decision, append it to `workspace/features/
 
 ## How you operate
 
-1. **Read first, recommend second.** Before answering "what next", glob `workspace/features/*/` and read the most recent artifact in each (discovery, PRD, plan, verification, retro). You cannot sequence what you haven't seen.
+1. **Read first, recommend second.** Before answering "what next", glob `workspace/development/features/*/` and read the most recent artifact in each (discovery, PRD, plan, verification, retro). You cannot sequence what you haven't seen.
 
 2. **Respect the 6 phases.** Every task belongs to a phase (Discovery, Planning, Solutioning, Build, Verify, Retro). Name the phase when you recommend.
 
@@ -80,7 +80,7 @@ For the full rules, entry/exit criteria and skip conditions, read `.claude/rules
 
 ### "What should I work on next?"
 
-1. Read all `workspace/features/*/` folders. For each, determine the current phase (look at which artifacts exist).
+1. Read all `workspace/development/features/*/` folders. For each, determine the current phase (look at which artifacts exist).
 2. For each feature, identify the next action (next phase or a blocker).
 3. Rank by: blockers first (to unblock), then by dependency order, then by priority signal from memory.
 4. Recommend the top 1-3 with phase + owner + why.
@@ -93,7 +93,7 @@ For the full rules, entry/exit criteria and skip conditions, read `.claude/rules
 
 ### "Sprint planning for {period}"
 
-1. List candidate features (from `workspace/features/` or the user).
+1. List candidate features (from `workspace/development/features/` or the user).
 2. For each, identify which phases remain.
 3. Order by dependency.
 4. Propose a sequence: "Week 1: Feature A Phase 2-3, Feature B Phase 4. Week 2: Feature A Phase 4, Feature C Phase 1."

.claude/agents/mirror-retro.md

@@ -37,7 +37,7 @@ Beyond your own agent memory in `.claude/agent-memory/mirror-retro/`, you have *
 
 Your workspace folder: the **feature folder itself**. You write retros next to the other artifacts:
 
-- `workspace/features/{feature-slug}/[C]retro-{feature}-{YYYY-MM-DD}.md`
+- `workspace/development/features/{feature-slug}/[C]retro-{feature}-{YYYY-MM-DD}.md`
 
 For sprint-level retros spanning multiple features:
 

.claude/commands/helm-conductor.md

@@ -1,3 +1,3 @@
 Use the @helm-conductor agent to orchestrate the engineering cycle — sequence features, decide what to work on next, route tasks to the right specialist agent, or plan a sprint: $ARGUMENTS
 
-Helm is the conductor, not a worker. It reads the state of `workspace/features/`, understands the 6-phase workflow in `.claude/rules/dev-phases.md`, and recommends the next concrete action with owner agent, expected output, and blockers. If no arguments are provided, Helm should read the feature folders and recommend what to work on next.
+Helm is the conductor, not a worker. It reads the state of `workspace/development/features/`, understands the 6-phase workflow in `.claude/rules/dev-phases.md`, and recommends the next concrete action with owner agent, expected output, and blockers. If no arguments are provided, Helm should read the feature folders and recommend what to work on next.

.claude/rules/dev-phases.md

@@ -84,7 +84,7 @@ Call `@helm-conductor` when you have multiple active features or are unsure whic
 Every non-trivial piece of work lives in its own feature folder:
 
 ```
-workspace/features/{feature-slug}/
+workspace/development/features/{feature-slug}/
 ├── [C]discovery-{feature}.md       ← Phase 1 (Echo)
 ├── [C]prd-{feature}.md             ← Phase 2 (Compass)
 ├── [C]plan-{feature}.md            ← Phase 2 (Compass)
@@ -110,7 +110,7 @@ workspace/features/{feature-slug}/
 
 Before starting work, every engineering agent should check for prior artifacts in the active feature folder:
 
-1. **Is there a feature folder for this work?** Look for `workspace/features/{slug}/`
+1. **Is there a feature folder for this work?** Look for `workspace/development/features/{slug}/`
 2. **If yes**, read in order: discovery → PRD → plan → architecture → any prior reviews/verifications
 3. **Inherit** constraints, decisions, and open questions — don't re-litigate them
 4. **If unclear** which feature this is, ask the user or call `@helm-conductor`
@@ -129,7 +129,7 @@ When one agent hands off to another, the handoff includes:
 - **Expected output:** what the next agent should produce and where
 
 Example handoff:
-> "Compass → Bolt: plan saved to `workspace/features/dark-mode/[C]plan-dark-mode.md`. Architecture pending (Apex). Open question: token storage strategy (see plan §Open Questions). Expected: implementation against steps 1-5 + self-verification."
+> "Compass → Bolt: plan saved to `workspace/development/features/dark-mode/[C]plan-dark-mode.md`. Architecture pending (Apex). Open question: token storage strategy (see plan §Open Questions). Expected: implementation against steps 1-5 + self-verification."
 
 ---
 

.env.example

@@ -5,6 +5,32 @@
 # Edit this file with your API keys.
 # ============================================================
 
+# ── AI Provider Configuration ────────────────────────
+# EvoNexus supports multiple AI providers via OpenClaude.
+# Configure via dashboard (Providers page) or edit config/providers.json.
+# The active provider determines which CLI (claude or openclaude) is used.
+#
+# Anthropic (default): no extra config needed — uses native 'claude' CLI.
+#
+# OpenRouter (200+ models):
+#   CLAUDE_CODE_USE_OPENAI=1
+#   OPENAI_BASE_URL=https://openrouter.ai/api/v1
+#   OPENAI_API_KEY=sk-or-...
+#   OPENAI_MODEL=anthropic/claude-sonnet-4
+#
+# OpenAI:
+#   CLAUDE_CODE_USE_OPENAI=1
+#   OPENAI_API_KEY=sk-...
+#   OPENAI_MODEL=gpt-4.1
+#
+# Google Gemini:
+#   CLAUDE_CODE_USE_GEMINI=1
+#   GEMINI_API_KEY=...
+#   GEMINI_MODEL=gemini-2.5-pro
+#
+# Install openclaude for non-Anthropic providers:
+#   npm install -g @gitlawb/openclaude
+
 # ── Omie ERP ─────────────────────────────────────────
 # Omie API (omie.com.br → Settings → Integrations → API)
 OMIE_APP_KEY=

.gitignore

@@ -30,6 +30,9 @@ memory/**
 # ── Custom routines (user-specific, all in one place) ─
 ADWs/routines/custom/
 
+# ── Provider config (user-specific, has API keys) ─
+config/providers.json
+
 # ── Runtime data & logs ───────────────────
 backups/
 ADWs/logs/

ADWs/runner.py

@@ -124,37 +124,92 @@ def _log_to_file(log_name, prompt, stdout, stderr, returncode, duration, usage=N
             f.write(f"{'='*60}\nSTDERR:\n{'='*60}\n{stderr}\n")
 
 
+_ALLOWED_CLI_COMMANDS = frozenset({"claude", "openclaude"})
+
+
+def _spawn_cli(cli_command: str, prompt: str, agent: str | None, provider_env: dict) -> subprocess.Popen:
+    """Spawn a CLI process using only hardcoded command strings.
+
+    Uses a dictionary lookup so that the subprocess argument is always
+    a static string, satisfying semgrep/opengrep subprocess injection rules.
+    """
+    base_args = ["--print", "--dangerously-skip-permissions", "--output-format", "json"]
+    if agent:
+        base_args.extend(["--agent", agent])
+    base_args.append(prompt)
+
+    env = {**os.environ, **provider_env, "TERM": "dumb"}
+    popen_kwargs = dict(
+        stdout=subprocess.PIPE,
+        stderr=subprocess.PIPE,
+        text=True,
+        cwd=str(WORKSPACE),
+        env=env,
+    )
+
+    # Hardcoded dispatch — each branch uses a literal string for the executable
+    if cli_command == "openclaude":
+        return subprocess.Popen(["openclaude"] + base_args, **popen_kwargs)  # noqa: S603
+    else:
+        return subprocess.Popen(["claude"] + base_args, **popen_kwargs)  # noqa: S603
+_ALLOWED_ENV_VARS = frozenset({
+    "CLAUDE_CODE_USE_OPENAI", "CLAUDE_CODE_USE_GEMINI", "CLAUDE_CODE_USE_BEDROCK",
+    "CLAUDE_CODE_USE_VERTEX", "OPENAI_BASE_URL", "OPENAI_API_KEY", "OPENAI_MODEL",
+    "GEMINI_API_KEY", "GEMINI_MODEL", "AWS_REGION", "AWS_BEARER_TOKEN_BEDROCK",
+    "ANTHROPIC_VERTEX_PROJECT_ID", "CLOUD_ML_REGION",
+})
+
+
+def _get_provider_config() -> tuple[str, dict]:
+    """Read active provider CLI command and env vars from config/providers.json.
+
+    Only allowlisted CLI commands and env var names are returned.
+    """
+    config_path = WORKSPACE / "config" / "providers.json"
+    if not config_path.is_file():
+        return "claude", {}
+    try:
+        config = json.loads(config_path.read_text(encoding="utf-8"))
+        active = config.get("active_provider", "anthropic")
+        provider = config.get("providers", {}).get(active, {})
+        cli = provider.get("cli_command", "claude")
+        if cli not in _ALLOWED_CLI_COMMANDS:
+            cli = "claude"
+        env_vars = {
+            k: v for k, v in provider.get("env_vars", {}).items()
+            if v and k in _ALLOWED_ENV_VARS
+        }
+        return cli, env_vars
+    except (json.JSONDecodeError, OSError):
+        return "claude", {}
+
+
 def run_claude(prompt: str, log_name: str = "unnamed", timeout: int = 600, agent: str = None) -> dict:
     """
-    Execute Claude Code CLI with streaming output.
+    Execute AI CLI (claude or openclaude) with streaming output.
+
+    Uses the active provider from config/providers.json to determine
+    which binary to run and which env vars to inject.
 
     Args:
         prompt: The prompt to execute
         log_name: Name for logs
         timeout: Timeout in seconds
         agent: Agent name (.claude/agents/*.md) — if None, runs without agent
     """
-    cmd = ["claude", "--print", "--dangerously-skip-permissions", "--output-format", "json"]
+    cli_command, provider_env = _get_provider_config()
 
     if agent:
-        cmd.extend(["--agent", agent])
-
-    cmd.append(prompt)
-
-    agent_label = f"@{agent}" if agent else ""
-    console.print(f"  [step]▶[/step] {log_name} [dim]{agent_label}[/dim]", end="")
+        agent_label = f"@{agent}"
+    else:
+        agent_label = ""
+    provider_label = f"[{cli_command}]" if cli_command != "claude" else ""
+    console.print(f"  [step]▶[/step] {log_name} [dim]{agent_label} {provider_label}[/dim]", end="")
 
     start_time = datetime.now()
 
     try:
-        process = subprocess.Popen(
-            cmd,
-            stdout=subprocess.PIPE,
-            stderr=subprocess.PIPE,
-            text=True,
-            cwd=str(WORKSPACE),
-            env={**os.environ, "TERM": "dumb"},
-        )
+        process = _spawn_cli(cli_command, prompt, agent, provider_env)
 
         stdout_lines = []
         line_count = 0

CHANGELOG.md

@@ -5,6 +5,23 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.14.1] - 2026-04-11
+
+### Fixed
+
+- **`/api/overview` endpoint** — dropped from ~16s to ~29ms (≈500× faster). `_recent_reports` was rglob'ing the entire `workspace/` tree, which on an active install holds vendored third-party repos under `workspace/projects/` (mcp-dev-brasil, oh-my-claudecode, evoai-services, etc.) — 16.853 of 17.116 MD/HTML files (98.5%) lived there and had nothing to do with "recent reports". The scan now skips top-level `projects/` (vendored repos) and `meetings/` (raw Fathom transcripts), iterates remaining areas, and formats the `date` field from the actual `mtime` instead of `path.split("/")[-1][:10]` (which was returning garbage like `"README.md"`).
+- **Site typecheck errors** — `site/src/pages/Home.tsx` had 3 lucide icons (`MessageSquare`, `GitBranch`, `Database`) passing an invalid `title` prop. Wrapped them in `<span title="...">` to keep the hover tooltip and pass `tsc --noEmit`.
+- **Dashboard frontend build** — `dashboard/frontend/src/pages/Providers.tsx` was importing `type LucideIcon` without using it, which caused `make dashboard-app` to fail with `TS6133`. Unused import removed.
+- **Terminal startup garbage (WIP, 2 attempts included)** — on starting any agent terminal from the dashboard, bytes like `0?1;2c` / `000000` / `^[[0^[[0...` showed up in the prompt and status bar. Root cause is xterm.js auto-replying to terminal queries (DA1 `\x1b[c`, DA2 `\x1b[>c`, DSR `\x1b[5n`/`\x1b[6n`, window ops `\x1b[...t`) via `term.onData`, which the frontend was forwarding to the pty as if it were keyboard input. This release ships two defensive layers — passing `cols`/`rows` upfront on `start_claude` so the pty is born at the right size, and registering CSI handlers via `term.parser.registerCsiHandler({ final: 'c' | 'n' | 't' }, () => true)` to intercept queries at the parser level — plus a regex filter on `onData` as a second line of defense. **The bug is not fully resolved in this release.** Some payloads still slip through (likely via a non-CSI `triggerDataEvent` path that hasn't been pinned down yet). A debug log was added to `AgentTerminal.tsx` to capture the exact bytes in the next iteration.
+
+### Changed
+
+- **Feature folder convention** — `workspace/features/{slug}/` is now `workspace/development/features/{slug}/` across all engineering layer prompts (`.claude/rules/dev-phases.md`, `.claude/agents/compass-planner.md`, `.claude/agents/helm-conductor.md`, `.claude/commands/helm-conductor.md`, `.claude/agents/mirror-retro.md`, `docs/agents/engineering-layer.md`). Keeps all engineering artifacts (features, plans, architecture, reviews, verifications, retros) grouped under one development/ root.
+
+### Docs
+
+- **Multi-provider documentation** — README, `docs/introduction.md`, `docs/getting-started.md`, `docs/reference/env-variables.md`, `docs/dashboard/overview.md` updated with the OpenClaude-based multi-provider story introduced in v0.14.0. New `docs/dashboard/providers.md` documents the Providers page (supported providers, activation flow, security model with CLI + env var allowlists, logout warning). Site landing page replaces the "Full Control" feature card with "Multi-Provider, No Lock-In" highlighting the new capability.
+
 ## [0.14.0] - 2026-04-10
 
 ### Added