feat(agent): align investigation reports and selected context

.opencode/tools/publish_execution_plan.ts

@@ -3,7 +3,7 @@ import { getInternalBridgeConfig } from "../internalBridge.js";
 import { newExecutionPlanSchema } from "../../src/routes/executionPlan.js";
 
 export default tool({
-  description: "Publish the current full execution plan and progress to TJWater Server. Plans may be updated multiple times during investigation; a plan-only publish is intermediate and does not finish the task unless it explicitly records Agent failure. Publish the relevant plan node before proposing an action, then republish the plan with the returned action_id before the final report. Preserve stable node IDs and completed evidence. A running or completed node may only depend on completed or skipped predecessors. Edges are dependencies or labeled conditional branches, never guessed from list order. Human actions stay waiting until externally confirmed. Evidence must identify synthetic inputs, tool results or human confirmation accurately. This records a plan, it does not execute actions.",
+  description: "Publish an optional legacy investigation description to TJWater Server. This display snapshot never schedules the Agent or controls event-investigation completion. Prefer the optional Mermaid diagram in publish_task_report for a human-facing investigation narrative. Existing plan validation still requires stable node IDs, factual evidence and explicit edges. Do not invent dependencies from list order or infer human completion. Reports and action proposals do not require this plan. Missing critical data ends the round with a final insufficient_data report. This tool only records explanatory information, it does not execute actions.",
   args: {
     request_id: tool.schema.string().describe("Stable UUID idempotency key for this plan revision"),
     schema: tool.schema.enum(["execution-plan@2"]),