opencode-ultra 0.7.4 → 0.7.5

package/dist/index.js

@@ -14926,7 +14926,7 @@ function buildEvolveMessage(ctx) {
   return `[evolve-mode] SELF-IMPROVEMENT CYCLE ACTIVATED.
 
 ## MISSION
-Compare opencode-ultra's current capabilities with other OpenCode plugins, then propose concrete improvements.
+Compare opencode-ultra's current capabilities with other OpenCode plugins, then propose concrete, implementation-ready improvements.
 This is NOT about installing other plugins. This is about LEARNING from the ecosystem and making opencode-ultra better.
 
 ## opencode-ultra CURRENT CAPABILITIES (auto-generated from source)
@@ -14934,21 +14934,15 @@ ${inventory}
 
 You already have the full capability list above. Do NOT try to read opencode-ultra source files \u2014 this inventory IS the source of truth.
 
-## PHASE 1: ECOSYSTEM RESEARCH (spawn_agent)
+## PHASE 1: ECOSYSTEM RESEARCH
 
-Research what other plugins offer:
-\`\`\`
-spawn_agent({
-  agents: [
-    {agent: "scout", prompt: "Search npm and GitHub for OpenCode 1.2.x plugins. For EACH interesting plugin: what features does it provide? What hooks, tools, or techniques does it use? Focus on UNIQUE capabilities. Return a structured feature inventory per plugin.", description: "Ecosystem scan"},
-    {agent: "librarian", prompt: "Search for OpenCode plugin best practices, architectural patterns, and advanced techniques. Look at oh-my-opencode, opencode-supermemory, opencode-dcp, opencode-rate-limit-fallback, opencode-worktree, opencode-mad. What patterns do they share? What's unique?", description: "Plugin patterns research"}
-  ]
-})
-\`\`\`
+Search npm and GitHub for OpenCode 1.2.x plugins. Use google_search, webfetch, or spawn_agent with scout/librarian agents.
+For EACH interesting plugin: what features does it provide? What hooks, tools, or techniques does it use?
+Focus on UNIQUE capabilities not already in the inventory above.
 
 ## PHASE 2: COMPARE
 
-Build a Feature Matrix using the capability list above and agent results.
+Build a Feature Matrix using the capability list above and research results.
 
 **RULE**: The "opencode-ultra" column MUST be Yes/No/Partial based on the inventory above. NEVER write "TBD", "unknown", or "\u4E0D\u660E".
 
@@ -14956,34 +14950,43 @@ Build a Feature Matrix using the capability list above and agent results.
 |---------|---------------|-----------------|------|
 | (feature) | Yes \u2014 (tool/hook name) | Which plugin | Covered / Missing / Partial |
 
-Focus on genuinely useful, feasible, complementary features.
-
 ## PHASE 3: PROPOSE
 
-For each Missing or Partial gap:
+For each Missing or Partial gap, write a structured proposal. Each proposal MUST include:
 
-## Improvement: [Feature Name]
-**Inspiration**: [Plugin name] \u2014 [what it does]
-**Current state**: [what opencode-ultra has now from the inventory]
-**Why**: [concrete benefit]
-**How**: [which file to modify, what to add]
-**Effort**: Low / Medium / High
-**Priority**: P0 / P1 / P2
+- **\u5BFE\u8C61\u30D5\u30A1\u30A4\u30EB\u3068\u95A2\u6570\u540D**: Which source file(s) and function(s) to modify or create
+- **\u73FE\u72B6\u306E\u554F\u984C\u70B9**: What's missing or broken, citing specific tools/hooks from the inventory
+- **\u5177\u4F53\u7684\u306A\u5909\u66F4\u5185\u5BB9**: What to add/modify (specific enough to implement in one session)
+- **\u671F\u5F85\u3055\u308C\u308B\u52B9\u679C**: Concrete benefit to the user
+- **Priority**: P0 (critical gap) / P1 (valuable) / P2 (nice-to-have)
+- **Effort**: Low (< 1 file) / Medium (2-4 files) / High (5+ files or new subsystem)
+
+Write each proposal as a JSONL line to \`.opencode/evolve-proposals.jsonl\`:
+\`\`\`
+{"title":"\u6A5F\u80FD\u540D","priority":"P0","effort":"Medium","inspiration":"\u53C2\u8003\u30D7\u30E9\u30B0\u30A4\u30F3","current_state":"\u73FE\u72B6\u306E\u554F\u984C","why":"\u671F\u5F85\u52B9\u679C","how":"\u5BFE\u8C61\u30D5\u30A1\u30A4\u30EB:\u95A2\u6570\u540D \u2014 \u5909\u66F4\u5185\u5BB9"}
+\`\`\`
 
-Sort by Priority then Effort.
+## PHASE 4: SCORE
 
-## PHASE 4: SAVE
+Use the \`evolve_score\` tool to score and rank ALL proposals:
+\`\`\`
+evolve_score({ markdown: "## Improvement: ...\\n**Priority**: ...\\n**Effort**: ...\\n**Why**: ..." })
+\`\`\`
+Include the score results and reasoning in the final output.
+
+## PHASE 5: SAVE
 \`\`\`
 ledger_save({
   name: "evolve-scan-YYYY-MM-DD",
-  content: "# Evolve Scan Results\\n\\n## Feature Matrix\\n...\\n## Proposals\\n..."
+  content: "# Evolve Scan Results\\n\\n## Feature Matrix\\n...\\n## Scored Proposals\\n..."
 })
 \`\`\`
 
 ## RULES
-- Use the capability inventory above as ground truth. No file reading needed.
-- Proposals must cite specific tools/hooks from the inventory for "Current state".
-- Present proposals to user for approval before implementation.`;
+- Use the capability inventory above as ground truth.
+- Do NOT use evolve_apply. Proposals only. Humans decide what to implement.
+- Sort final proposals by score descending.
+- Each proposal must be specific enough to implement in one coding session.`;
 }
 function buildSelfInventory(ctx) {
   const lines = [];
@@ -14999,8 +15002,7 @@ function buildSelfInventory(ctx) {
   lines.push("");
   lines.push("### Agents");
   for (const [name, def] of Object.entries(ctx.agents)) {
-    const shortModel = def.model.split("/").pop() ?? def.model;
-    lines.push(`- **${name}** (${shortModel}) \u2014 ${def.description}`);
+    lines.push(`- **${name}** \u2014 ${def.description}`);
   }
   lines.push("");
   lines.push("### Additional Features");

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "opencode-ultra",
-  "version": "0.7.4",
+  "version": "0.7.5",
   "description": "Lightweight OpenCode 1.2.x plugin — ultrawork mode, multi-agent orchestration, rules injection",
   "keywords": [
     "opencode",