osborn 0.9.231 → 0.9.232

package/dist/claude-llm.js

@@ -896,9 +896,12 @@ export const VERIFIER_CHAIN = {
             'at most 2 fix rounds, after which surface the outcome to the user rather than looping.',
     },
     researcher: {
-        afterReminder: 'The researcher sub-agent just finished. Before you finalize, use the Task tool to dispatch the ' +
-            '`reasoner` gate to judge whether the research is complete and well-sourced for the original ' +
-            'question. If it returns NEEDS-MORE, send the researcher back — at most 2 rounds, then surface.',
+        afterReminder: 'The researcher sub-agent just finished. Before you finalize, you MUST now use the Task tool to ' +
+            'dispatch the `reasoner` GATE to judge whether the research is complete and well-sourced for the ' +
+            'original question — it returns GATE: PASS or GATE: NEEDS-MORE. ' +
+            'If it returns NEEDS-MORE, dispatch the `researcher` again with the gaps it named and then re-gate — ' +
+            'at most 2 rounds, after which surface the outcome to the user rather than looping. ' +
+            "This is the research analogue of writer→reviewer: don't rely on the findings until an independent agent has vetted them.",
     },
 };
 const RESEARCH_TOOLS = [

package/dist/prompts/direct-mode-research.md

@@ -113,9 +113,9 @@ THE SUB-AGENTS:
   · NEVER use the SDK's built-in 'general-purpose' agent — it is not configured for this project and will hit write blocks. Always pick researcher, reasoner, writer, tester, or reviewer explicitly.
 
 DIVISION OF LABOR — follow this chain by default for any substantive or code task:
-  researcher (gather facts) → planner (step plan for multi-step work) → THEN dispatch writer AND tester IN THE SAME STEP, in parallel: the writer executes the plan while the tester writes tests from the spec, blind to the implementation (TDD) → after the writer returns, RUN the tester's tests against the new code AND dispatch the reviewer on the diff → on test-FAIL or REJECT, send the writer back to fix and re-verify (at most 2 rounds) → you synthesize and speak.
-For a quick factual query: researcher only → you speak.
-NEVER skip the tester+reviewer verification after a code change — and dispatch the tester IN PARALLEL with the writer (not after), so tests are written independently of the code.
+  researcher (gather facts) → after the researcher returns on a substantive question, dispatch the `reasoner` GATE to judge whether the research is complete and well-sourced (GATE: PASS / NEEDS-MORE); on NEEDS-MORE send the researcher back with the named gaps and re-gate (at most 2 rounds) → planner (step plan for multi-step work) → THEN dispatch writer AND tester IN THE SAME STEP, in parallel: the writer executes the plan while the tester writes tests from the spec, blind to the implementation (TDD) → after the writer returns, RUN the tester's tests against the new code AND dispatch the reviewer on the diff → on test-FAIL or REJECT, send the writer back to fix and re-verify (at most 2 rounds) → you synthesize and speak.
+For a quick factual lookup: researcher only → you speak (a trivial lookup needs no gate).
+NEVER skip verification — it is symmetric across both flows: the reasoner GATE after substantive research, and the tester+reviewer after a code change. Both are the same pattern (generate → an INDEPENDENT agent verifies before you rely on it). Dispatch the tester IN PARALLEL with the writer (not after) so tests are written independently of the code.
 You may OVERRIDE this chain at any time — stop a running agent, inject, or reorder — because you can see each task's live state. The chain is the default, not a cage.
 Surfacing findings and communicating to the user is YOUR job, not a sub-agent's.
 </turn-shape>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "osborn",
-  "version": "0.9.231",
+  "version": "0.9.232",
   "description": "Voice AI coding assistant - local agent that connects to Osborn frontend",
   "type": "module",
   "bin": {