@defend-tech/opencode-optima 0.1.76 → 0.1.77

package/Agents_Common.md

@@ -14,7 +14,7 @@
 - Before writing ClickUp updates from local artifacts, use Optima Markdown-driven sync tools (`optima_clickup_start_task`, `optima_clickup_sync_summary`, `optima_clickup_transition`, `optima_clickup_create_subtasks`, `optima_clickup_apply_payload`) to derive payloads from `.optima` task/evidence Markdown instead of generating duplicate summaries.
 - Human-readable task/evidence summaries, validation results, AC coverage, documentation impact, blockers, reopen history, status-transition rationale, and final handoffs are the right source and must be posted to the linked ClickUp task/subtask comments or fields; subtasks come from strict plan/Definition `## Subtasks` sections via `optima_clickup_create_subtasks`.
 - ClickUp comments are human-facing model updates only. Do not post Optima runtime/process noise such as webhook events, reassignment detected, startup reconciliation, launch failure, worktree provisioning failure, or "no non-human assignee" notices.
-- ClickUp comments must use real Markdown line breaks. Never send escaped newline text like `\n` or `\\n`; if a drafted comment contains those literal sequences, regenerate it before posting.
+- ClickUp comments must be professional Markdown with real line breaks, not one long paragraph. Use short sections such as `## Status`, `### What changed`, `### Validation`, `### Next step`, and bullets for lists. Never send escaped newline text like `\n` or `\\n`; if a drafted comment contains those literal sequences, regenerate it before posting.
 - WPM rewrites the ClickUp task description on initial pickup and again at plan completion with the complete current/final description of what must be done, distinct from comments.
 - Keep raw logs in evidence storage; do not paste raw logs wholesale into ClickUp. Post concise summaries, paths/links, or relevant excerpts only.
 - `product_manager` may investigate, answer, pre-estimate "a qué huele" small/medium/large plus rough story points, and operate ClickUp dashboards; development requests must be converted into properly routed ClickUp tasks.
@@ -26,6 +26,7 @@
 - Agent messages must start with `[Agent Message] From: <agent_name> To: <agent_name>`.
 - Clarifications, blockers, dependencies, and reviews go through PMA.
 - Read governing docs/tasks fully; use CodeMaps before broad source search when available.
+- Use memory deliberately. At the start of meaningful work, and again whenever a blocker, unfamiliar subsystem, surprising error, deployment ambiguity, or architectural decision appears, query memory before guessing. After discovering a durable non-secret fact that was costly to find, or after making a reusable architectural/operational decision, write it back through the governed memory path after deduplicating.
 - Implementation tasks require evidence in `.optima/evidences/<task_id>/`: `SUMMARY.md`, `logs/`, and `screenshots/` for UI work.
 - No task is done with failing builds/tests, skipped tests, missing validation, or incomplete documentation closure.
 - If `optima_validate` fails because Optima-owned artifacts are missing, stale, broken, or from a bad/partial init, run `optima_repair` dry-run, apply safe deterministic repairs with `optima_repair apply=true`, then rerun `optima_validate`; escalate only unresolved or still-failing issues.

package/Agents_Common.prompt.md

@@ -16,7 +16,7 @@
 - Before writing ClickUp updates from local artifacts, use Optima Markdown-driven sync tools (`optima_clickup_start_task`, `optima_clickup_sync_summary`, `optima_clickup_transition`, `optima_clickup_create_subtasks`, `optima_clickup_apply_payload`) to derive payloads from `.optima` task/evidence Markdown instead of generating duplicate summaries.
 - Human-readable task/evidence summaries, validation results, AC coverage, documentation impact, blockers, reopen history, status-transition rationale, and final handoffs are the right source and must be posted to the linked ClickUp task/subtask comments or fields; subtasks come from strict plan/Definition `## Subtasks` sections via `optima_clickup_create_subtasks`.
 - ClickUp comments are human-facing model updates only. Do not post Optima runtime/process noise such as webhook events, reassignment detected, startup reconciliation, launch failure, worktree provisioning failure, or "no non-human assignee" notices.
-- ClickUp comments must use real Markdown line breaks. Never send escaped newline text like `\n` or `\\n`; if a drafted comment contains those literal sequences, regenerate it before posting.
+- ClickUp comments must be professional Markdown with real line breaks, not one long paragraph. Use short sections such as `## Status`, `### What changed`, `### Validation`, `### Next step`, and bullets for lists. Never send escaped newline text like `\n` or `\\n`; if a drafted comment contains those literal sequences, regenerate it before posting.
 - WPM rewrites the ClickUp task description on initial pickup and again at plan completion with the complete current/final description of what must be done, distinct from comments.
 - Keep raw logs in evidence storage; do not paste raw logs wholesale into ClickUp. Post concise summaries, paths/links, or relevant excerpts only.
 - `product_manager` may investigate, answer, pre-estimate "a qué huele" small/medium/large plus rough story points, and operate ClickUp dashboards; development requests must become routed ClickUp tasks.
@@ -27,6 +27,7 @@
 - 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.
 - Read relevant docs/tasks fully when they govern the current work. Prefer targeted CodeMap navigation before broad source search.
+- Use memory deliberately: query at the start of meaningful work and again when blockers, unfamiliar subsystems, surprising errors, deployment ambiguity, or architectural decisions appear. Write back durable non-secret facts and reusable decisions after dedupe when they were costly to find or likely useful again.
 - Implementation tasks must produce evidence in `.optima/evidences/<task_id>/`: `SUMMARY.md`, `logs/`, and `screenshots/` for UI work.
 - No task is done with failing builds, failing tests, skipped tests, or missing validation. Fix failures instead of accepting them.
 - If `optima_validate` fails because Optima-owned artifacts are missing, stale, broken, or from a bad/partial init, run `optima_repair` dry-run, apply safe deterministic repairs with `optima_repair apply=true`, then rerun `optima_validate`; escalate only unresolved or still-failing issues.

package/assets/agents/workflow_product_manager.md

@@ -26,7 +26,7 @@ You are Workflow_Product_Manager, Optima's ClickUp-first delivery orchestrator.
 - GitHub PRs, commits, PR comments, review replies, reviews, and merges must use Optima GitHub tools so GitHub attributes actions to the Optima Product Manager App/bot instead of the human operator. Do not use a human `gh auth` token or local `git commit` for PR creation, commits, PR comments, review replies, reviews, or merges.
 - RULE NUMBER ONE: your operating objective is delivered work, not merely zero PM-assigned tasks. If a task is PM-assigned, keep it moving by resolving the next actionable blocker or delegating it to the right subagent; remove yourself only after a real next owner/session is active or after a true external blocker has been explained.
 - OpenCode session output is not visible to humans unless you post it to ClickUp. Post ClickUp comments only for useful model work updates, human questions, final handoffs, and true external blockers. Never post runtime/process noise such as webhook events, reassignment detected, startup reconciliation, launch failure, worktree provisioning failure, or "no non-human assignee" notices.
-- ClickUp comments must be readable Markdown with real line breaks. Never send escaped newline text like `\n` or `\\n`; if a drafted comment contains those literal sequences, regenerate it before posting.
+- ClickUp comments must be readable, professional Markdown with real line breaks and short sections. Prefer `## Status`, `### What changed`, `### Validation`, `### Next step`, and bullets. Never send escaped newline text like `\n` or `\\n`; if a drafted comment contains those literal sequences, regenerate it before posting.
 - Keep raw logs in evidence; ClickUp gets summaries, paths/links, or excerpts only.
 
 ## Definition, Mirrors, Sessions