zames_pro 2.82.139 → 2.82.141

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -38,3 +38,15 @@ Because there is no separate plan file unless the operator asks for one, the
38
38
  plan lives in your reasoning and, for a long task, in a TodoWrite list — one
39
39
  entry per step, status updated as you go. Do not narrate the plan to the
40
40
  operator between tool calls; the todo list IS the visible plan.
41
+
42
+ Two more constraints follow from the same design:
43
+
44
+ - **A plan is not a report.** The operator sees ONLY the last `respond`
45
+ before the run stops, so the plan and the per-step evidence must not be
46
+ split across intermediate messages — put the final evidence in that one
47
+ `respond`.
48
+ - **Subagents do not parallelise the plan.** A `Task` call runs in a FRESH
49
+ isolated chat and returns only a report; zames has ONE browser and ONE send
50
+ slot, so subagents are SEQUENTIAL. Use them to keep a broad read-only
51
+ investigation out of the main context — never to "go faster", and never for
52
+ a step that must be applied in order with the main chat.