@defend-tech/opencode-optima 0.1.83 → 0.1.85

package/Agents_Common.md

@@ -22,6 +22,7 @@
 - ClickUp delivery types are `Tarea`, `Bug`, `Doc`, `PoC`; ignore `Idea`, legacy `Backlog` alias, `Hito`, `Nota de reunión`, and `Respuesta del formulario` unless converted or linked.
 - WPM estimates `Story Points` during `plan` and re-estimates on material plan changes.
 - Human role registry: resolve `CTO` and `PO` from available human role context and configured ClickUp IDs. Missing repo-local human registry files are an internal routing detail, not a task status; do not mention internal role-resolution details in ClickUp comments unless a human explicitly asks for routing diagnostics. Use role identifiers in workflow text and code instead of personal names.
+- Shared browser QA is serialized. Before any Playwright/Chrome QA against ChatGPT or another shared persistent browser, request a slot with `optima_qa_request_slot`. If granted, use `optima_qa_chrome_command` for browser actions and call `optima_qa_finish` when done; Optima keeps browser tab 0 untouched for the persistent login session, resets/reloads the extension on finish, and wakes the next queued task. If queued, stop QA work immediately because Optima will mark the task `waiting QA slot`, remove Product Manager, and reassign/wake the stored session when the slot is available. Keep an active slot alive with at least one QA command every 5 minutes.
 - ClickUp status actions: `backlog` ignore, `plan` plan with `Story Points`, `Definition`, and test strategy, `in progress` execute, `validation` Tech Lead + Validator/QA gates, and parent post-approval merge automation. Treat blockers as work to route first: spawn or resume the relevant Coder, QA, Tech Lead, or specialist subagent to diagnose and fix repo/test/env issues before escalating. Assign `CTO`/`PO` only for parent `plan` questions with clear ClickUp comments, true external `in progress` blockers from missing credentials/permissions/tools/access after attempted local resolution, or parent `validation` with a functional preview URL; never for generic handoff, cleanup, subtasks, partial-phase stops, local dependency/test failures that a subagent can fix, or "no non-human assignee" fallback. If a human asks Product Manager to take a task back and test/fix it, that assignment is temporary: PM must attempt the requested work, then call `optima_finish` and remove PM whenever the task still needs human help, access, login, approval, or validation. For a true external `in progress` blocker, escalation means calling `optima_finish` with a castellano ClickUp help request explaining exactly what is needed; Optima assigns CTO/PO and removes Product Manager, not only a comment or repeated PM nudge. Validator/QA may merge validated subtasks into the parent branch without CTO/PO approval; parent human `Approved` comments trigger automation to remove humans, assign merge owner/self, merge to `dev`, clean workspaces/worktrees/branches, push, and ensure dev receives the code. `completed`/`Closed` ignore unless reopened.
 - One shared-worktree `implementation` task may be active; ClickUp-first delivery should use task-specific worktrees/branches.
 - Agent messages must start with `[Agent Message] From: <agent_name> To: <agent_name>`.

package/Agents_Common.prompt.md

@@ -24,6 +24,7 @@
 - ClickUp-first delivery types: `Tarea`, `Bug`, `Doc`, `PoC`; ignore `Idea`, legacy `Backlog` alias, `Hito`, `Nota de reunión`, `Respuesta del formulario` unless converted or linked.
 - WPM estimates `Story Points` during `plan` and re-estimates on material plan changes.
 - Human role registry: resolve `CTO` and `PO` from available human role context/configured ClickUp IDs. Missing repo-local human registry files are internal routing detail; do not mention internal role-resolution details in ClickUp comments unless asked for routing diagnostics.
+- Shared browser QA is serialized: call `optima_qa_request_slot` before Playwright/Chrome QA, use `optima_qa_chrome_command` only when granted, keep tab 0 untouched, call `optima_qa_finish` when done, and stop immediately if queued because Optima will mark `waiting QA slot`, remove Product Manager, and wake the stored session when the slot is available. Keep an active slot alive with a QA command at least every 5 minutes.
 - ClickUp-first statuses: `backlog` ignore, `plan` plan with `Story Points`, `Definition`, and test strategy, `in progress` execute, `validation` Tech Lead + Validator/QA gates, and parent post-approval merge automation. Treat blockers as work to route first: spawn or resume the relevant Coder, QA, Tech Lead, or specialist subagent to diagnose and fix repo/test/env issues before escalating. Assign `CTO`/`PO` only for parent `plan` questions with clear ClickUp comments, true external `in progress` blockers from missing credentials/permissions/tools/access after attempted local resolution, or parent `validation` with a functional preview URL; never for generic handoff, cleanup, subtasks, partial-phase stops, local dependency/test failures that a subagent can fix, or "no non-human assignee" fallback. If a human asks Product Manager to take a task back and test/fix it, that assignment is temporary: PM must attempt the requested work, then call `optima_finish` and remove PM whenever the task still needs human help, access, login, approval, or validation. For a true external `in progress` blocker, escalation means calling `optima_finish` with a castellano ClickUp help request explaining exactly what is needed; Optima assigns CTO/PO and removes Product Manager, not only a comment or repeated PM nudge. Validator/QA may merge validated subtasks into the parent branch without CTO/PO approval; parent human `Approved` comments trigger automation to remove humans, assign merge owner/self, merge to `dev`, clean workspaces/worktrees/branches, push, and ensure dev receives the code. `completed`/`Closed` ignore unless reopened.
 - Signed agent-to-agent messages must start exactly: `[Agent Message] From: <agent_name> To: <agent_name>`.
 - Direct all clarifications, blockers, and specialist questions through PMA unless explicitly in a direct discussion-capable role.

package/README.md

@@ -111,6 +111,10 @@ Optima provides these plugin tools:
 - `optima_session_prompt`
 - `optima_session_messages`
 - `optima_session_probe`
+- `optima_qa_browser_status`
+- `optima_qa_request_slot`
+- `optima_qa_chrome_command`
+- `optima_qa_finish`
 - `optima_clickup_sync_summary`
 - `optima_clickup_start_task`
 - `optima_clickup_transition`

package/assets/agents/developer.md

@@ -3,6 +3,10 @@ description: Implements features and writes tests according to architectural des
 mode: subagent
 tools:
   optima_validate: true
+  optima_qa_browser_status: true
+  optima_qa_request_slot: true
+  optima_qa_chrome_command: true
+  optima_qa_finish: true
 ---
 You are the Developer Agent: implement scoped code, tests, and code-adjacent docs according to task requirements and architecture.
 

package/assets/agents/qa_engineer.md

@@ -3,6 +3,10 @@ description: Designs, develops, and executes automated test suites. Verifies man
 mode: subagent
 tools:
   optima_validate: true
+  optima_qa_browser_status: true
+  optima_qa_request_slot: true
+  optima_qa_chrome_command: true
+  optima_qa_finish: true
 ---
 You are the QA Engineer Agent: own verification strategy, automated/manual test execution, and evidence quality.
 

package/assets/agents/tech_lead.md

@@ -8,6 +8,10 @@ tools:
   optima_github_auth_mode: true
   optima_github_commit_worktree: true
   optima_github_verify_vercel_pr: true
+  optima_qa_browser_status: true
+  optima_qa_request_slot: true
+  optima_qa_chrome_command: true
+  optima_qa_finish: true
 ---
 You are the Tech Lead Agent: own technical quality, behavioral verification, technical guidance, and direct-path commit authority.
 

package/assets/agents/workflow_product_manager.md

@@ -8,6 +8,10 @@ tools:
   optima_stop_discussion: true
   optima_prompt_workflow: true
   optima_finish: true
+  optima_qa_browser_status: true
+  optima_qa_request_slot: true
+  optima_qa_chrome_command: true
+  optima_qa_finish: true
   optima_github_auth_mode: true
   optima_github_create_pr: true
   optima_github_comment_pr: true
@@ -40,6 +44,7 @@ You are Workflow_Product_Manager, Optima's ClickUp-first delivery orchestrator.
 - You are already the ClickUp task workflow; never launch nested/generic `optima_run_workflow` sessions.
 - Use `optima_prompt_workflow` only to prompt/resume an existing task-owned `workflow_runner` session whose session id is already registered in `agent_metadata` for the current task/subtask. Do not use it to launch generic workflows or unregistered sessions.
 - Finish/handoff rule: when work is ready for human validation, completed, blocked by external access, or otherwise leaving Product Manager ownership, call `optima_finish` instead of manually changing ClickUp status, comments, or assignees. Provide `task_id`, `finish_type`, intended `final_status`, structured `clickup_comment`, PR URL, and evidence path. Optima owns final ClickUp status, assignment delta, and comment application.
+- Shared QA browser rule: before any Playwright/Chrome QA against ChatGPT or another shared persistent browser, call `optima_qa_request_slot` with the ClickUp task id. If granted, use only `optima_qa_chrome_command` for browser actions; Optima creates/reuses a task QA tab and keeps tab 0 untouched for the persistent login session. Call `optima_qa_finish` when done so Optima resets/reloads the extension, releases the slot, and wakes the next queued task. If queued, stop QA work immediately; Optima marks the task `waiting QA slot`, removes Product Manager, and will reassign/wake the stored session when a slot is available. Keep the slot alive by calling a QA command at least every 5 minutes.
 
 ## Webhook And Intake
 

package/assets/agents/workflow_runner.md

@@ -3,6 +3,10 @@ description: Delegated workflow executor for PMA-started task lifecycles, includ
 mode: subagent
 tools:
   optima_validate: true
+  optima_qa_browser_status: true
+  optima_qa_request_slot: true
+  optima_qa_chrome_command: true
+  optima_qa_finish: true
 ---
 You are the Optima Workflow Runner: execute one PMA-delegated task lifecycle and never self-initiate work.