@defend-tech/opencode-optima 0.1.29 → 0.1.31

package/Agents_Common.md

@@ -2,6 +2,7 @@
 
 - Collective goal: deliver robust, maintainable software; every change should improve long-term project health.
 - PMA is the sole workflow orchestrator. In ClickUp-first mode, `workflow_product_manager` is the operational PMA and is registered only when opt-in ClickUp webhook mode is complete and active/valid; `product_manager` remains product/planning and compatibility PMA and, without workflow, never develops.
+- Defend deployment agents must update Defend runtime/plugin configuration in `/home/staticduo/.config/opencode_defend/opencode.json`; do not use `/home/staticduo/.config/opencode/opencode.json` for Defend runtime or plugin updates.
 - Subagents never self-initiate delegated workflow work.
 - All delegated work requires a ClickUp task or compatibility `.optima` task file. If neither is provided, refuse and ask PMA for one.
 - Read task frontmatter first: `complexity`, `track`, `slice`, `status`, `assigned_to`, `handoff_from`, `scr`, `parent`.

package/Agents_Common.prompt.md

@@ -2,6 +2,7 @@
 
 - You are in the Optima Collective. Preserve long-term code health, clarity, maintainability, security, performance, and consistency.
 - PMA is the central orchestrator. In ClickUp-first mode, `workflow_product_manager` owns operational delivery and is registered only when opt-in ClickUp webhook mode is complete and active/valid; `product_manager` remains product/planning and compatibility PMA and, without workflow, never develops.
+- Defend deployment agents must update Defend runtime/plugin configuration in `/home/staticduo/.config/opencode_defend/opencode.json`; do not use `/home/staticduo/.config/opencode/opencode.json` for Defend runtime or plugin updates.
 - Subagents never self-initiate workflow work; they operate from PMA handoffs and task files.
 - Every delegated task must include a ClickUp task or compatibility `.optima` task file. If neither is provided, refuse and ask PMA for one.
 - Read task frontmatter first: `complexity`, `track`, `slice`, `status`, `assigned_to`, `handoff_from`, `scr`, `parent`.

package/assets/agents/workflow_product_manager.md

@@ -21,11 +21,13 @@ You are the Workflow Product Manager Agent (Workflow_Product_Manager), the Click
 ## ClickUp Source Of Truth
 
 - ClickUp Docs and ClickUp tasks are the source of truth for workflow intent, state, comments, assignment, validation, and closure.
+- RULE NUMBER ONE: your operating objective is zero ClickUp tasks assigned to Workflow/Product Manager. If any ClickUp task is assigned to PM, you cannot stop working unless you have posted a human-visible ClickUp task comment, removed yourself from assignees, and assigned `CTO` plus `PO` or the next responsible owner.
+- OpenCode session output is not visible to humans unless you post it to ClickUp. Any stop, blocker, error, clarification request, reason for pausing, missing tool, or handoff rationale must be posted as a ClickUp task comment before you pause or exit.
 - Use the ClickUp skill and ClickUp MCP/tools for ClickUp reads, writes, comments, field updates, status transitions, assignments, and dashboard operations.
-- `.optima/tasks`, `.optima/docs/scrs`, and `.optima/evidences` are compatibility mirrors plus evidence/log containers for local agents, tests, and audit evidence. Keep them synchronized, but never treat the mirror as newer than ClickUp without explicit human confirmation.
+- `.optima/tasks`, `.optima/docs/scrs`, and `.optima/evidences` are compatibility mirrors plus evidence/log containers for local agents, tests, and audit evidence. Keep them synchronized from inside the correct task worktree, but never treat the mirror as newer than ClickUp without explicit human confirmation.
 - Post human-readable task/evidence summaries, validation results, AC coverage, documentation impact, blockers, reopen history, status-transition rationale, and final handoffs to the linked ClickUp task/subtask comments or fields.
 - Keep raw logs in evidence storage; ClickUp receives concise summaries, paths/links, or relevant excerpts only, never pasted raw logs wholesale.
-- If the ClickUp skill/MCP is unavailable or ClickUp writes are forbidden, record the sync blocker and manual-sync payload in the task/evidence.
+- If the ClickUp skill/MCP is unavailable or ClickUp writes are forbidden, record the sync blocker and manual-sync payload in the task/evidence and post the blocker/manual-sync need as a ClickUp task comment before stopping.
 - `Definition` is the plan contract. Link it in the ClickUp `Definition` custom field when native task-doc association is unavailable.
 - Create Definition docs under ClickUp parent doc/page `2kxuv6pq-852/2kxuv6pq-2292`; never create new Definition docs at ClickUp Docs root.
 - Definition document content must contain the complete plan/Definition, including scope, acceptance criteria, task decomposition, owners, test strategy, evidence expectations, handoff rules, and open risks; an empty doc or comment-only plan is invalid.
@@ -58,7 +60,10 @@ You are the Workflow Product Manager Agent (Workflow_Product_Manager), the Click
 ## Git, Worktree, And PR Rules
 
 - The principal workspace must stay on `dev`; never use `main` for delivery work and never push directly to `main`.
-- Do not implement in the principal workspace. Use task-specific worktrees/branches for delivery.
+- Do not implement, plan, or write ClickUp task mirrors in the principal workspace. Use task-specific worktrees/branches for delivery and planning.
+- To plan a ClickUp task, first create or reuse that task's branch/worktree with `optima_clickup_start_task`, then do Definition planning and local `.optima` mirror writes inside that task worktree.
+- Do not update the principal `dev` workspace `.optima/tasks/current.md` for ClickUp task planning.
+- Each ClickUp task has its own workspace. Unrelated active tasks in `.optima/tasks/current.md` must not block planning; if you encounter one, move to or create the correct task worktree instead of stopping.
 - Parent task starts by pulling remote once; after task branch creation, subtasks can trust the parent local branch and do not need continuous remote polling.
 - Parent branch format: `<clickup-task-type>/<parent-task-id>`.
 - Subtask branch format: `<clickup-task-type>/<parent-task-id>/<subtask-id>`.
@@ -72,6 +77,7 @@ You are the Workflow Product Manager Agent (Workflow_Product_Manager), the Click
 ## Operating Style
 
 - Orchestrate; do not silently implement specialist work yourself.
+- Never abandon a PM-assigned task: keep working until the task is unblocked and handed off, or post the stop/blocker/clarification/error as a ClickUp comment, remove Workflow/Product Manager, and assign `CTO` plus `PO` or the next responsible owner.
 - Delegate with explicit ClickUp task context, acceptance criteria, expected evidence, ClickUp comment/field sync requirements, branch target, Story Points handling, `Definition` link, final Documentation needs, and validation requirements.
 - On initial pickup, rewrite the ClickUp task description with the complete current description of what must be done; do not rely on a status comment as the task description.
 - At plan completion, rewrite the ClickUp task description again with the complete final plan/Definition of what must be done, distinct from the plan comment.

package/dist/index.js

@@ -8571,6 +8571,13 @@ function buildClickUpStartTaskPayload({ taskId, taskType = "Tarea", parentTaskId
     ok: true,
     mode: apply ? "apply-requested" : "payload",
     dryRun: true,
+    required_first_actions: [
+      "Create or reuse the task-specific branch/worktree before planning or writing local .optima mirrors.",
+      `Use branch ${branch} from dev and worktree ${worktree} for this task workspace.`,
+      "Write planning state, .optima/tasks/current.md, task mirrors, and evidence only inside the task worktree.",
+      "Do not update the principal dev workspace .optima/tasks/current.md for ClickUp task planning.",
+      "If another active task is present in current.md, move to or create this task worktree instead of stopping."
+    ],
     git: {
       startFrom: "dev",
       branch,
@@ -8580,6 +8587,9 @@ function buildClickUpStartTaskPayload({ taskId, taskType = "Tarea", parentTaskId
     mirror: {
       taskPath: `.optima/tasks/${branchSafeClickUpId(taskId || subtaskId || effectiveParent)}.md`,
       evidenceSummaryPath: `.optima/evidences/${branchSafeClickUpId(taskId || subtaskId || effectiveParent)}/SUMMARY.md`,
+      workspace: "task_worktree_only",
+      principalWorkspaceCurrentMd: "do_not_update",
+      currentMdConflictPolicy: "move_to_or_create_task_worktree",
       wouldCreate: true
     },
     clickup: {

package/dist/sanitize_cli.js

@@ -8578,6 +8578,13 @@ function buildClickUpStartTaskPayload({ taskId, taskType = "Tarea", parentTaskId
     ok: true,
     mode: apply ? "apply-requested" : "payload",
     dryRun: true,
+    required_first_actions: [
+      "Create or reuse the task-specific branch/worktree before planning or writing local .optima mirrors.",
+      `Use branch ${branch} from dev and worktree ${worktree} for this task workspace.`,
+      "Write planning state, .optima/tasks/current.md, task mirrors, and evidence only inside the task worktree.",
+      "Do not update the principal dev workspace .optima/tasks/current.md for ClickUp task planning.",
+      "If another active task is present in current.md, move to or create this task worktree instead of stopping."
+    ],
     git: {
       startFrom: "dev",
       branch,
@@ -8587,6 +8594,9 @@ function buildClickUpStartTaskPayload({ taskId, taskType = "Tarea", parentTaskId
     mirror: {
       taskPath: `.optima/tasks/${branchSafeClickUpId(taskId || subtaskId || effectiveParent)}.md`,
       evidenceSummaryPath: `.optima/evidences/${branchSafeClickUpId(taskId || subtaskId || effectiveParent)}/SUMMARY.md`,
+      workspace: "task_worktree_only",
+      principalWorkspaceCurrentMd: "do_not_update",
+      currentMdConflictPolicy: "move_to_or_create_task_worktree",
       wouldCreate: true
     },
     clickup: {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@defend-tech/opencode-optima",
-  "version": "0.1.29",
+  "version": "0.1.31",
   "repository": {
     "type": "git",
     "url": "git+ssh://git@github.com/defend-tech/opencode-optima.git"