pluidr 0.7.2 → 0.7.4

package/README.md

@@ -12,11 +12,11 @@
 
 Pluidr installs **3 primary agents + 14 subagents** into OpenCode — each primary agent owns its exclusive subagents, scoped permissions, and enforced workflow rules. No shared subagents. No ad-hoc delegation.
 
-| Primary Agent | Model Tier | Purpose | Subagents |
-|---|---|---|---|
-| **Composer** | 🧠 Reasoning | Feature work — Explore → Plan → Build | Researcher, Plan-Writer, Plan-Checker, Coder, Tester, Reviewer, Compose-Reporter |
-| **Debugger** | 🧠 Reasoning | Bug investigation — Investigate → Fix → Report | Inspector, Fixer, Debug-Reporter |
-| **Prober** | 🧠 Reasoning | Security audit — Trace → Patch → Audit | Tracer, Patcher, Auditor, Probe-Reporter |
+| Primary Agent | Purpose | Subagents |
+|---|---|---|
+| **Composer** | Feature work — Explore → Plan → Build | Researcher, Plan-Writer, Plan-Checker, Coder, Tester, Reviewer, Compose-Reporter |
+| **Debugger** | Bug investigation — Investigate → Fix → Report | Inspector, Fixer, Debug-Reporter |
+| **Prober** | Security audit — Trace → Patch → Audit | Tracer, Patcher, Auditor, Probe-Reporter |
 
 ---
 
@@ -35,21 +35,20 @@ You describe a feature / idea
   │                                         │
   │  Delegate: Researcher                   │
   │  → deep codebase + web fact-finding     │
-  │  → confirmed_facts / inferred_facts /   │
-  │    unknowns / risks                     │
+  │  → confirmed-inferred facts / risks     │
   │                                         │
   │  Composer internally assesses:          │
   │  Is this feature simple or complex?     │
   └──────────┬──────────────────────────────┘
              │
-    ┌────────┴────────┐
-    │ Simple feature  │  Complex feature
-    ▼                 ▼
-GUARDRAIL GATE 1a  GUARDRAIL GATE 1b
-"Build directly?"  "Write a PRD?"
-    │                 │
-    │ Yes             │ Yes
-    │                 ▼
+    ┌────────┴───────────────┐
+    │ Simple feature         │  Complex feature
+    ▼                       ▼
+GUARDRAIL GATE 1a      GUARDRAIL GATE 1b
+"Build directly?"        "Write a PRD?"
+    │                        │
+    │ Yes                    │ Yes
+    │                        ▼
     │          ┌──────────────────────────────┐
     │          │  PLAN PHASE                  │
     │          │                              │
@@ -62,9 +61,9 @@ GUARDRAIL GATE 1a  GUARDRAIL GATE 1b
     │          │                              │
     │          │  PASS → GUARDRAIL GATE 2     │
     │          │  "Build from this PRD?"      │
-    │          └──────────┬───────────────────┘
-    │                     │ Yes
-    └──────────┬──────────┘
+    │          └─────────────┬────────────────┘
+    │                        │ Yes
+    └──────────┬─────────────┘
                ▼
   ┌────────────────────────────────────────────┐
   │  BUILD PHASE                               │
@@ -293,12 +292,6 @@ All agents resolve conflicts using this priority order (defined in `hierarchy.tx
 npm install -g pluidr
 ```
 
-Or run directly without installing:
-
-```sh
-npx pluidr init
-```
-
 ## Usage
 
 ### `pluidr`
@@ -328,6 +321,7 @@ Checks installation health and reports ✓/✗ for each component:
 - `opencode.jsonc` exists
 - All 18 prompt files present
 - Both plugin files present
+- `pluidr-contrast` theme configured
 - `package.json` with `@opencode-ai/plugin` dependency
 - squeeze binary available
 - Config is valid JSON
@@ -336,19 +330,20 @@ Exits with code `0` if all pass, `1` if any fail.
 
 ### `pluidr update`
 
-Checks the npm registry for a newer version of pluidr and prompts to install it.
+Checks the npm registry for a newer version of pluidr and prompts to automatically install the upgrade globally. If an update is successfully completed, the running CLI process exits to let you start fresh on the new version.
 
 ### `pluidr uninstall`
 
 Restores your previous configuration:
 
 - Finds the latest timestamped backup and restores it to `opencode.jsonc`
-- Removes `prompts/`, `plugins/`, and `bin/` directories
+- Restores `tui.json` from the latest backup (returning the TUI theme to its pre-Pluidr state)
+- Removes `prompts/`, `plugins/`, `bin/`, and `themes/pluidr-contrast.json` directories and files
 - Preserves `opencode.jsonc` and `package.json`
 
 ---
 
-## Bundled Plugins
+## Bundled Package
 
 ### `pluidr-flow`
 
@@ -363,3 +358,7 @@ Provides subagents with cross-session context access:
 Hooks into tool execution to rewrite bash commands through the `squeeze` binary, filtering verbose output and saving **60–90% of tokens** across all agents.
 
 Both plugins and their dependency declaration are installed automatically by `pluidr init` — no extra user action required. On OpenCode's first launch, the bundled Bun runtime installs `@opencode-ai/plugin` from the generated `package.json`.
+
+### Themes & Colors
+
+Pluidr comes with a pre-configured OLED high-contrast dark theme called **`pluidr-contrast`** that is automatically applied to your OpenCode terminal interface.

package/package.json

@@ -1,45 +1,45 @@
-{
-  "name": "pluidr",
-  "version": "0.7.2",
-  "description": "Opinionated Engineering Workflow for OpenCode — Explore, Plan, Build, Debug, and Security-Audit.",
-  "keywords": [
-    "opencode",
-    "workflow",
-    "engineering",
-    "pipeline",
-    "ai-agents",
-    "code-review",
-    "debugging",
-    "security-audit",
-    "security",
-    "planner",
-    "builder",
-    "cli"
-  ],
-  "license": "MIT",
-  "type": "module",
-  "scripts": {
-    "test": "node --test"
-  },
-  "bin": {
-    "pluidr": "bin/pluidr.js"
-  },
-  "repository": {
-    "type": "git",
-    "url": "git+https://github.com/funara/pluidr.git"
-  },
-  "homepage": "https://github.com/funara/pluidr#readme",
-  "bugs": {
-    "url": "https://github.com/funara/pluidr/issues"
-  },
-  "engines": {
-    "node": ">=18"
-  },
-  "files": [
-    "bin",
-    "src"
-  ],
-  "dependencies": {
-    "@clack/prompts": "^0.9"
-  }
-}
+{
+  "name": "pluidr",
+  "version": "0.7.4",
+  "description": "Opinionated Engineering Workflow for OpenCode — Plan, Build, Review.",
+  "keywords": [
+    "opencode",
+    "workflow",
+    "engineering",
+    "pipeline",
+    "ai-agents",
+    "code-review",
+    "debugging",
+    "security-audit",
+    "security",
+    "planner",
+    "builder",
+    "cli"
+  ],
+  "license": "MIT",
+  "type": "module",
+  "scripts": {
+    "test": "node --test"
+  },
+  "bin": {
+    "pluidr": "bin/pluidr.js"
+  },
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/funara/pluidr.git"
+  },
+  "homepage": "https://github.com/funara/pluidr#readme",
+  "bugs": {
+    "url": "https://github.com/funara/pluidr/issues"
+  },
+  "engines": {
+    "node": ">=18"
+  },
+  "files": [
+    "bin",
+    "src"
+  ],
+  "dependencies": {
+    "@clack/prompts": "^0.9"
+  }
+}

package/src/cli/commands/doctor.js

@@ -1,6 +1,6 @@
 import { existsSync, readFileSync, readdirSync } from "node:fs"
 import { join } from "node:path"
-import { getConfigDir, getConfigPath, getPromptsDir, getThemesDir } from "../../core/paths.js"
+import { getConfigDir, getConfigPath, getPromptsDir, getThemesDir, getTuiConfigPath } from "../../core/paths.js"
 import { findSqueezePath } from "../../core/squeezeInstaller.js"
 
 const EXPECTED_PROMPT_COUNT = 18
@@ -47,9 +47,30 @@ export function collectChecks() {
   }
   checks.push({ component: "plugin files", pass: pluginsFound === PLUGIN_FILES.length, detail: `${pluginsFound}/${PLUGIN_FILES.length}` })
 
-  // 3b. Custom theme exists
+  // 3b. Theme configuration verification
   const themeExists = existsSync(join(themesDir, "pluidr-contrast.json"))
-  checks.push({ component: "pluidr-contrast theme file", pass: themeExists })
+  const tuiConfigPath = getTuiConfigPath()
+  let tuiConfigValid = false
+  let tuiDetail = "missing mapping"
+  if (existsSync(tuiConfigPath)) {
+    try {
+      const content = readFileSync(tuiConfigPath, "utf-8")
+      const parsed = JSON.parse(content)
+      if (parsed.theme === "pluidr-contrast") {
+        tuiConfigValid = true
+        tuiDetail = ""
+      } else {
+        tuiDetail = `theme: ${parsed.theme || "none"}`
+      }
+    } catch {
+      tuiDetail = "corrupted tui.json"
+    }
+  }
+  checks.push({
+    component: themeExists && tuiConfigValid ? "pluidr-contrast theme configured" : "pluidr-contrast theme not configured",
+    pass: themeExists && tuiConfigValid,
+    detail: !themeExists ? "missing theme file" : tuiDetail
+  })
 
   // 4. package.json with @opencode-ai/plugin dependency
   let pkgValid = false

package/src/cli/commands/launch.js

@@ -7,7 +7,11 @@ import { runInit } from "./init.js"
 
 export async function runLaunch() {
   // 1. Update check
-  await checkAndPromptUpdate(version)
+  const updated = await checkAndPromptUpdate(version)
+  if (updated) {
+    console.log("Update successful. Please run pluidr again to start the new version.")
+    process.exit(0)
+  }
 
   // 2. Doctor check
   process.stdout.write("Running doctor...         ")

package/src/cli/commands/update.js

@@ -2,5 +2,8 @@ import { checkAndPromptUpdate } from "../../core/versionCheck.js"
 import { version } from "../../core/version.js"
 
 export async function runUpdate() {
-  await checkAndPromptUpdate(version)
+  const updated = await checkAndPromptUpdate(version)
+  if (updated) {
+    console.log("Update successful. Please run pluidr again to start the new version.")
+  }
 }

package/src/templates/agent-prompts/composer.txt

@@ -297,18 +297,8 @@ After presenting the Compose-Reporter's completion report to the user, you MUST:
    state returns to the starting point. The next user message triggers a
    fresh EXPLORE cycle.
 
-2. **Present handoff guidance** using the `question` tool:
-   - "Pipeline complete. What would you like to do next?"
-   - Options:
-     - "New feature / idea" — restart from EXPLORE (default path)
-     - "Bug / defect found" — suggest switching to Debugger tab
-     - "Iterate on this result" — re-enter EXPLORE with the current
-       result as context (treat as a new request)
-
-3. **If the user selects "Bug / defect found"**, respond with:
-   "For bugs and defects, switch to the Debugger tab — it uses
-   Brooks-Lint methodology for root-cause analysis. Debugger is
-   standalone and does not depend on Composer."
+2. **Ask naturally in text** (do NOT use the `question` tool):
+   Ask the user if they are finished or if they need to continue the session to iterate on this result. Keep it brief, conversational, and natural.
 
 Do NOT automatically start a new pipeline without user confirmation.
 Do NOT stay in BUILD phase after presenting the report — the pipeline

package/src/templates/agent-prompts/debugger.txt

@@ -59,17 +59,8 @@ After presenting the outcome to the user, you MUST:
    returns to the starting point. The next user message triggers a fresh
    debugging cycle.
 
-2. **Present handoff guidance** using the `question` tool:
-   - "Investigation complete. What would you like to do next?"
-   - Options:
-     - "New bug / defect" — start a fresh debugging cycle
-     - "Feature work" — suggest switching to Composer tab
-     - "Re-investigate" — re-enter with new information or context
-
-3. **If the user selects "Feature work"**, respond with:
-   "For feature work, switch to the Composer tab — it handles the full
-   Explore → Plan → Build pipeline. Composer is standalone and does not
-   depend on Debugger."
+2. **Ask naturally in text** (do NOT use the `question` tool):
+   Ask the user if they are finished or if they need to continue the session to investigate further or try another fix. Keep it brief, conversational, and natural.
 
 Do NOT automatically start a new investigation without user confirmation.
 Do NOT remain in a completed state without offering next steps.

package/src/templates/agent-prompts/prober.txt

@@ -60,16 +60,8 @@ After presenting the audit report to the user, you MUST:
 1. **Reset your internal state.** The audit is complete — your state returns to TRACE.
    The next user message triggers a fresh security audit cycle.
 
-2. **Present handoff guidance** using the `question` tool:
-   - "Security audit complete. What would you like to do next?"
-   - Options:
-     - "New security audit" — start a fresh TRACE cycle
-     - "Feature work" — suggest switching to Composer tab
-     - "Bug investigation" — suggest switching to Debugger tab
-
-3. **If the user selects "Feature work"**, respond with:
-   "For feature work, switch to the Composer tab — it handles the full
-   Explore → Plan → Build pipeline."
+2. **Ask naturally in text** (do NOT use the `question` tool):
+   Ask the user if they are finished or if they need to continue the session to run a new audit or review other areas. Keep it brief, conversational, and natural.
 
 Do NOT automatically start a new audit without user confirmation.
 Do NOT remain in a completed state without offering next steps.

package/src/templates/opencode.config.json

@@ -25,6 +25,7 @@
 
     "composer": {
       "mode": "primary",
+      "color": "#00b4cc",
       "temperature": 0.7,
       "description": "Full engineering workflow: Explore, Plan, Build — 3 phases, 7 subagents. Starts in Explore mode, transitions via guardrail gates.",
       "prompt": "{file:./prompts/composer.txt}",
@@ -55,6 +56,7 @@
 
     "debugger": {
       "mode": "primary",
+      "color": "#ff7039",
       "description": "Root-cause analysis via inspector/fixer/reporter. Standalone primary agent — does not depend on Composer. Pure orchestrator — all investigation, fixes, and reports delegated to subagents.",
       "prompt": "{file:./prompts/debugger.txt}",
       "permission": {
@@ -345,6 +347,7 @@
 
     "prober": {
       "mode": "primary",
+      "color": "#66ffbf",
       "temperature": 0.7,
       "description": "Standalone security and quality auditing agent. Recon and vuln trace, minimal patch application, validation gate.",
       "prompt": "{file:./prompts/prober.txt}",