opencode-orchestrator 1.0.74 → 1.0.76

package/README.md

@@ -57,21 +57,29 @@ OpenCode Orchestrator executes a **Linear Strategy** through **Parallel Sessions
 
 ---
 
+---
+
 ## 🛠️ Technical Core
 
-### 📂 Session-Based Parallelism
-All operations are executed asynchronously in isolated sessions via the **SessionPool**. Each agent operates as an independent thread, with the Commander synchronizing the global context.
+### 🔄 Persistent-Autonomous Engine
+The orchestrator is built for **uninterrupted survival**. Using **Self-Healing Rehydration**, the system state is synced to disk (`.opencode/mission_loop.json`). Even if the plugin reloads or the process restarts, the orchestrator automatically resumes missions without losing context or agent roles.
 
-### 🧠 Hierarchical Memory
-Context is managed through a 4-tier structure (System, Project, Mission, Task). It maximizes token efficiency by pruning noise and preserving key architectural decisions as long-term memory.
+### 🚀 Zero-Payload Initiation (Turbo Mode)
+Leverages the `experimental.chat.system.transform` hook to inject comprehensive agent instructions on the server side. This reduces initial message size by **90%**, slashing latency and preventing payload-related hangs during `/task` invocation.
 
-### 🌳 Incremental State Loop
-The loop operates based on incremental updates to `.opencode/todo.md`. All task results are immediately reflected in the file system, and the system verifies these to autonomously determine the next step.
+### ⛓️ Deadlock-Free Async Pipeline
+A re-engineered execution flow that uses **Asynchronous Continuation triggers**. By utilizing a fire-and-forget strategy for prompt injections, the system eliminates traditional protocol deadlocks between the plugin hooks and the OpenCode server.
+
+### 📂 Session-Based Parallelism
+All operations are executed asynchronously in isolated sessions via the **SessionPool**. Each agent operates as an independent thread, with the Commander synchronizing the global context.
 
 ---
 
 ## 🛠️ Key Innovations
 
+### 🛡️ Self-Healing Mission Continuity
+Survival-first design. The orchestrator cross-checks in-memory state with on-disk artifacts at every step. If the plugin's memory is cleared, it re-activates mission flags and agent instructions automatically upon the next event.
+
 ### 🧠 Hierarchical Memory System
 Maintains focus across long-running projects using a 4-tier memory structure. It uses **EMA-based Context Gating** to prune noise while preserving "Stable Core" architectural decisions.
 
@@ -79,7 +87,7 @@ Maintains focus across long-running projects using a 4-tier memory structure. It
 Replaces monolithic file rewrites with atomic updates. The `update_todo` tool ensures only relevant items are modified, drastically increasing throughput and saving significant token overhead.
 
 ### 📊 Real-time TUI Monitor
-A live dashboard directly in your terminal. Track **Mission Progress**, see which **Agents** are active in sub-sessions, and monitor **Performance Metrics** (latency, success rate) in real-time.
+A live dashboard directly in your terminal. Track **Mission Progress**, see which **Agents** are active in sub-sessions, and monitor **Performance Metrics** (latency, success rate) through isolated API channels.
 
 ### 🧩 Modular Plugin SDK & Custom Agents
 Extend the engine without touching the core. Drop custom JS plugins into `.opencode/plugins/` to add new tools/hooks, or define niche agent roles in `.opencode/agents.json`.

package/dist/core/agents/session-pool.d.ts

@@ -6,8 +6,6 @@
  * - 90% reduction in session creation time (500ms → 50ms)
  * - Reduced OpenCode server load
  * - Faster parallel task startup
- *
- * @see ORCHESTRATOR_IMPROVEMENT_PLAN.md Section 5.2 - 제안 2.1
  */
 import type { PluginInput } from "@opencode-ai/plugin";
 import type { PooledSession, SessionPoolConfig, SessionPoolStats, ISessionPool } from "./interfaces/session-pool.interface.js";

package/dist/core/orchestrator/session-manager.d.ts

@@ -1,22 +1,17 @@
-/**
- * Session Manager
- *
- * Centralizes all direct access to the global `state` and session initialization logic.
- * Eliminates redundant state checks across hooks and handlers.
- */
 /**
  * Ensures a local session object exists in the plugin context map.
- * This is "Session State 1" (Plugin-local tracking).
+ * Now WITH disk-based rehydration for robustness.
  */
-export declare function ensureSessionInitialized(sessions: Map<string, any>, sessionID: string): any;
+export declare function ensureSessionInitialized(sessions: Map<string, any>, sessionID: string, directory?: string): any;
 /**
  * Activates the global mission state for a specific session.
  */
 export declare function activateMissionState(sessionID: string): void;
 /**
  * Checks if the mission is globally active and the session is enabled.
+ * CROSS-CHECK: Will return true if disk state confirms mission, even if in-memory 'missionActive' flag reset.
  */
-export declare function isMissionActive(sessionID: string): boolean;
+export declare function isMissionActive(sessionID: string, directory?: string): boolean;
 /**
  * Deactivates mission state (e.g., on cancellation or error).
  */