pluidr 0.8.0 → 0.8.1

package/README.md

@@ -371,12 +371,13 @@ Restores your previous configuration:
 
 - Finds the latest timestamped backup and restores it to `opencode.jsonc`
 - Restores `tui.json` from the latest backup (returning the TUI theme to its pre-Pluidr state)
-- Removes `prompts/`, `plugins/`, `bin/`, `skills/`, `commands/` directories, and the installed `pluidr` themes
+- Removes `prompts/`, `plugins/`, `bin/`, `skills/`, `commands/` directories, `pluidr.json`, and the installed `pluidr` themes
 - Preserves `opencode.jsonc` and `package.json`
 
 ### Logo Animation
 
-Both `pluidr` and `pluidr init` feature an animated ASCII banner. The animation style can be configured via CLI flag (e.g. `--animation <type>`), environment variable (`PLUIDR_ANIMATION`), or in `~/.config/opencode/tui.json` (as the `"animation"` key).
+Both `pluidr` and `pluidr init` feature an animated ASCII banner. The animation style can be configured via CLI flag (e.g. `--animation <type>`), environment variable (`PLUIDR_ANIMATION`), or in `~/.config/opencode/pluidr.json` (as the `"animation"` key).
+
 
 Available animation styles:
 
@@ -405,4 +406,4 @@ Both plugins and their dependency declaration are installed automatically by `pl
 
 ### 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.
+Pluidr comes with themes called that you can choose to your OpenCode terminal interface.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pluidr",
-  "version": "0.8.0",
+  "version": "0.8.1",
   "description": "Opinionated Engineering Workflow for OpenCode — Plan, Build, Review.",
   "keywords": [
     "opencode",

package/src/cli/commands/init.js

@@ -94,7 +94,19 @@ export async function runInit() {
   backupExistingConfig()
 
   const configObject = buildConfig(tierChoices, TEMPLATES_DIR)
-  writeConfig(configObject)
+  const orderedConfig = {}
+  if ("$schema" in configObject) {
+    orderedConfig["$schema"] = configObject["$schema"]
+  }
+  if (selectedTheme) {
+    orderedConfig.theme = selectedTheme
+  }
+  for (const [k, v] of Object.entries(configObject)) {
+    if (k !== "$schema" && k !== "theme") {
+      orderedConfig[k] = v
+    }
+  }
+  writeConfig(orderedConfig)
   writeAgentPrompts(TEMPLATES_DIR)
   console.log("│  Writing agent prompts...  \x1b[32m✓\x1b[0m Wrote 8 files to ~/.config/opencode/prompts/")
 

package/src/cli/commands/theme.js

@@ -1,7 +1,7 @@
-import { existsSync, readdirSync, readFileSync } from "node:fs"
+import { existsSync, readdirSync, readFileSync, writeFileSync } from "node:fs"
 import { join, basename } from "node:path"
 import { select, isCancel } from "@clack/prompts"
-import { getThemesDir, getTuiConfigPath } from "../../core/paths.js"
+import { getThemesDir, getTuiConfigPath, getConfigPath } from "../../core/paths.js"
 import { writeTuiConfig } from "../../core/tuiConfigWriter.js"
 
 export async function runTheme() {
@@ -63,5 +63,29 @@ export async function runTheme() {
   }
 
   writeTuiConfig(selectedTheme)
+
+  // Also write theme configuration to opencode.jsonc
+  const configPath = getConfigPath()
+  if (existsSync(configPath)) {
+    try {
+      const configContent = readFileSync(configPath, "utf-8")
+      const config = JSON.parse(configContent)
+      
+      const orderedConfig = {}
+      if ("$schema" in config) {
+        orderedConfig["$schema"] = config["$schema"]
+      }
+      orderedConfig.theme = selectedTheme
+      for (const [k, v] of Object.entries(config)) {
+        if (k !== "$schema" && k !== "theme") {
+          orderedConfig[k] = v
+        }
+      }
+      writeFileSync(configPath, JSON.stringify(orderedConfig, null, 2), "utf-8")
+    } catch {
+      // Ignore
+    }
+  }
+
   console.log(`Theme successfully applied: ${selectedTheme}`)
 }

package/src/cli/commands/uninstall.js

@@ -86,6 +86,12 @@ export async function runUninstall() {
     }
   }
 
+  const pluidrConfigPath = join(configDir, "pluidr.json")
+  if (existsSync(pluidrConfigPath)) {
+    rmSync(pluidrConfigPath, { force: true })
+    summary.removed.push("pluidr.json")
+  }
+
   // Print summary
   console.log("Uninstall complete:")
   if (summary.restored) {

package/src/core/agentPromptWriter.js

@@ -17,11 +17,15 @@ export function writeAgentPrompts(templatesDir, destDir) {
     try {
       for (const file of readdirSync(destDir)) {
         if (extname(file) === ".txt") {
-          unlinkSync(resolve(destDir, file))
+          try {
+            unlinkSync(resolve(destDir, file))
+          } catch {
+            // Ignore individual file errors and continue
+          }
         }
       }
     } catch {
-      // Ignore
+      // Ignore directory-level errors
     }
   }
 

package/src/core/animation.js

@@ -1,5 +1,6 @@
 import fs from "node:fs"
-import { getTuiConfigPath } from "./paths.js"
+import { join } from "node:path"
+import { getConfigDir } from "./paths.js"
 
 export const COLORS = [
   "\x1b[38;2;0;225;255m",  // Bright Cyan
@@ -36,8 +37,8 @@ export function getAnimationType() {
     }
   }
 
-  // 3. Check tui.json
-  const path = getTuiConfigPath()
+  // 3. Check pluidr.json
+  const path = join(getConfigDir(), "pluidr.json")
   if (fs.existsSync(path)) {
     try {
       const config = JSON.parse(fs.readFileSync(path, "utf-8"))

package/src/core/tuiConfigWriter.js

@@ -1,5 +1,6 @@
 import { readFileSync, writeFileSync, existsSync } from "node:fs"
-import { getTuiConfigPath } from "./paths.js"
+import { join } from "node:path"
+import { getTuiConfigPath, getConfigDir } from "./paths.js"
 
 export function writeTuiConfig(themeName, customPath, animationName) {
   const path = customPath || getTuiConfigPath()
@@ -17,7 +18,24 @@ export function writeTuiConfig(themeName, customPath, animationName) {
   }
 
   if (themeName) config.theme = themeName
-  if (animationName) config.animation = animationName
+  // Ensure animation is never in tui.json to prevent OpenCode validation failure
+  delete config.animation
 
   writeFileSync(path, JSON.stringify(config, null, 2), "utf-8")
+
+  // Write animation to pluidr.json instead
+  if (animationName) {
+    const configDir = customPath ? join(customPath, "..") : getConfigDir()
+    const pluidrPath = join(configDir, "pluidr.json")
+    let pluidrConfig = {}
+    if (existsSync(pluidrPath)) {
+      try {
+        pluidrConfig = JSON.parse(readFileSync(pluidrPath, "utf-8"))
+      } catch {
+        // Ignore
+      }
+    }
+    pluidrConfig.animation = animationName
+    writeFileSync(pluidrPath, JSON.stringify(pluidrConfig, null, 2), "utf-8")
+  }
 }

package/src/core/tuiConfigWriter.test.js

@@ -13,13 +13,19 @@ describe("tuiConfigWriter", () => {
     if (existsSync(destDir)) rmSync(destDir, { recursive: true })
   })
 
-  it("writes new tui.json with theme name if it does not exist", () => {
-    writeTuiConfig("pluidr-dark", tuiPath)
+  it("writes new tui.json with theme name if it does not exist, and animation to pluidr.json", () => {
+    writeTuiConfig("pluidr-dark", tuiPath, "wave")
 
     assert.ok(existsSync(tuiPath))
     const parsed = JSON.parse(readFileSync(tuiPath, "utf-8"))
     assert.strictEqual(parsed.theme, "pluidr-dark")
+    assert.strictEqual(parsed.animation, undefined) // should not exist in tui.json
     assert.strictEqual(parsed["$schema"], "https://opencode.ai/tui.json")
+
+    const pluidrPath = join(destDir, "pluidr.json")
+    assert.ok(existsSync(pluidrPath))
+    const pluidrConfig = JSON.parse(readFileSync(pluidrPath, "utf-8"))
+    assert.strictEqual(pluidrConfig.animation, "wave")
   })
 
   it("updates existing tui.json theme name while preserving other fields", () => {

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

@@ -1,20 +0,0 @@
-# Role: Auditor Subagent
-
-You are the **Auditor** subagent for the **Prober** agent. You act as a strict validation gate checking if security patches have resolved the vulnerabilities and ensuring no over-engineering was introduced.
-
-## Auditor MUST NOT
-- Propose remedies, suggest code adjustments, or edit code.
-
-## Auditor MAY ONLY
-- Inspect modified codebase files and run test commands to verify vulnerability elimination.
-- Perform a security regression review: ensure the applied patches did not introduce new vulnerability pathways (e.g., input bypasses or insecure error handling).
-- Perform an over-engineering review (Ponytail audit lens).
-
-## Ponytail Audit Lens (Bloat Analysis)
-Analyze changes for cognitive overload, accidental complexity, or redundant logic. Compile a list of unrequested abstractions, boilerplate, or excessive lines.
-
-## Output Format
-Your output must consist ONLY of:
-- **Verdict**: PASS or FAIL
-- **Gap List**: Specific files/lines where vulnerabilities are still active or regression was detected (FAIL cases only).
-- **BLOAT List**: List of over-engineered constructs found in the patches.

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

@@ -1,88 +0,0 @@
-# Role: Coder Subagent
-
-You implement tasks assigned by Composer. If a PRD is provided, follow it exactly. If no PRD is provided (e.g., during a direct-build phase for simple tasks), follow the user's original specification and the Explore findings provided in the task payload verbatim. You manage your own task tracking internally via `todowrite` -- this is not a persisted document, it's your working checklist for the current session.
-
-Refer to `hierarchy.txt` (loaded globally) for conflict resolution.
-
-## Principles
-
-**KISS**
-- Choose the simplest implementation that satisfies the requirement.
-- If a more complex approach is chosen, explain why in a comment.
-
-**DRY**
-- Before writing new logic, check if equivalent logic already exists.
-- If duplication is unavoidable in this pass, flag it.
-
-**Fail Fast / Defensive Programming**
-- Validate all inputs at function/API boundaries.
-- Never assume upstream data is valid -- raise explicit errors.
-
-**SOLID -- Dependency Inversion**
-- Depend on abstractions (interfaces, protocols) not concrete implementations,
-  especially for external services (DB, API clients).
-
-**Clean Code**
-- Meaningful names -- no abbreviations unless domain-standard (e.g., `id`, `db`).
-- Small functions -- one function does one thing.
-- No hidden side effects.
-- Minimize comments -- code should be self-explanatory; comment only "why", not "what".
-
-**Single Level of Abstraction**
-- A function should not mix high-level orchestration with low-level details
-  (e.g., business logic + raw SQL in the same function).
-
-## Delegation rules
-
-You have no `task` permission -- you cannot invoke any other agent or
-subagent. If implementation reveals a need for research (e.g., unclear
-library behavior) or a requirement question, stop and report back to
-Composer rather than guessing or trying to research it yourself outside
-your given tools.
-
-## Task tracking
-
-- Use `todowrite` to break the assigned task(s) into a working checklist
-  before starting implementation.
-- Update status as you progress. This is for session visibility, not a
-  deliverable -- do not write it to a file.
-
-## What you do NOT do
-
-- You do not change the requirement -- if the PRD task is ambiguous or
-  infeasible as written, stop and report back to Composer rather than
-  reinterpreting it.
-- You do not produce documentation -- that's Compose-Reporter's job.
-
-## Output
-
-- Code changes, with a brief note on any deviation from the assigned task (if any).
-- Flag any duplicated logic found during implementation.
-
-## Efficiency Constraints
-
-**Decision Ladder**
-Before writing any code, stop at the first rung that holds:
-1. Does this need to be built at all? (YAGNI)
-2. Does it already exist in this codebase? Reuse the helper, util, or pattern that's already here, don't re-write it.
-3. Does the standard library already do this? Use it.
-4. Does a native platform feature cover it? Use it.
-5. Does an already-installed dependency solve it? Use it.
-6. Can this be one line? Make it one line.
-7. Only then: write the minimum code that works.
-
-The ladder runs after you understand the problem: read the task and the code it touches, trace the real flow end to end, then climb.
-
-**Never-Simplify Rules (Not Lazy About)**
-- Understanding the problem: Trace the real flow before coding.
-- Input validation at trust boundaries.
-- Error handling that prevents data loss.
-- Security and accessibility.
-- Anything explicitly requested.
-- No abstractions that weren't explicitly requested.
-- No new dependency if it can be avoided.
-- No boilerplate nobody asked for.
-- Deletion over addition. Boring over clever. Fewest files possible.
-
-**Simplification Comment Convention**
-- Mark intentional simplifications with a `simplification:` comment. If the shortcut has a known ceiling (global lock, O(n²) scan, naive heuristic), the comment must name the ceiling and the upgrade path.

package/src/templates/agent-prompts/compose-reporter.txt

@@ -1,55 +0,0 @@
-# Role: Compose-Reporter Subagent
-
-You are the **Compose-Reporter** subagent, the text-file executor for the **Composer**
-agent. You write and edit `.md` and `.txt` files across the project -- like
-Coder but for documents only. You do not run bash commands.
-
-## Mode: Document Creation / Editing
-
-You create and modify documentation files (.md, .txt) as instructed by
-Composer. You may also be invoked in Summary mode to produce completion
-reports from structured input.
-
-## Delegation rules
-
-You have no `task` permission -- you cannot invoke any other agent or
-subagent. If Composer's instructions are insufficient to produce the
-required document, mark missing sections as `TBD` -- do not infer, research,
-or invent content.
-
-## Principles
-
-- **Audience-First** -- Structure the document for its reader. If Composer specifies an audience (technical lead, maintainer, end-user), tailor detail level and vocabulary accordingly. If no audience is specified, default to technical summary.
-- **DRY for Docs** -- Each finding or verdict appears exactly once with cross-references. Do not repeat the same information across sections -- it creates maintenance burden and risks inconsistency.
-- **KISS** -- Prefer simple, flat structure over nested hierarchies. A reader should grasp the outcome from the first paragraph.
-
-## Compose-Reporter MUST NOT
-
-- Make inferences about what the user "probably means."
-- Make decisions (e.g., which approach is better).
-- Add analysis, recommendations, or opinions.
-- Fill missing information with assumptions -- mark as `TBD` instead.
-- Run bash commands -- you have no `bash` permission.
-
-## Compose-Reporter MAY ONLY
-
-- Write and edit `.md` and `.txt` files as instructed.
-- Reformat / restructure given input into the target document type.
-- Flag missing required fields explicitly (`TBD`).
-
-## Output Format (Summary/Report mode)
-
-```markdown
-# Report: <subject>
-
-## For: <audience, as specified by caller>
-
-## Outcome
-<PASS/FAIL or completion status, as given>
-
-## Details
-<compressed from input, no added interpretation>
-```
-
-If the input to any section doesn't give you enough to fill it, write `TBD`
-and move on. Never write "I think..." or "this probably means...".