@capagents/forgeqe 2.2.8 → 2.2.10

package/docs/MODEL_ROUTING.md

@@ -15,7 +15,9 @@ llm:
   routing: auto        # off (the default for existing projects) | shadow | auto
 ```
 
-`forgeqe init` writes `routing: auto` for new projects. `shadow` decides and logs each pick in the session log
+`forgeqe init` writes `routing: auto` for new projects. With no `routing` line, it is on while the active profile is
+GitHub Copilot: Copilot cannot run ForgeQE's agent and Scribe, so the router finds them another configured model, and
+Copilot keeps driving the browser. `routing: off` turns that off too. `shadow` decides and logs each pick in the session log
 (`model.route`) but changes nothing, so you can see what the router would do before you let it. Shadow still runs the
 live checks and the rating call described below.
 

package/docs/user-guide.html

@@ -1842,7 +1842,9 @@ model can do: ForgeQE finds out.</p>
   models_file: ./llms.json
   routing: auto        # off (the default for existing projects) | shadow | auto
 </code></pre>
-<p><code>forgeqe init</code> writes <code>routing: auto</code> for new projects. <code>shadow</code> decides and logs each pick in the session log
+<p><code>forgeqe init</code> writes <code>routing: auto</code> for new projects. With no <code>routing</code> line, it is on while the active profile is
+GitHub Copilot: Copilot cannot run ForgeQE's agent and Scribe, so the router finds them another configured model, and
+Copilot keeps driving the browser. <code>routing: off</code> turns that off too. <code>shadow</code> decides and logs each pick in the session log
 (<code>model.route</code>) but changes nothing, so you can see what the router would do before you let it. Shadow still runs the
 live checks and the rating call described below.</p>
 <p>See the picks:</p>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@capagents/forgeqe",
-  "version": "2.2.8",
+  "version": "2.2.10",
   "description": "ForgeQE: a browser agent CLI that runs goals and test cases in local Chrome or Chromium, or BrowserStack and TestMu AI/LambdaTest when configured, and turns passing runs into tests in your repo",
   "license": "SEE LICENSE IN LICENSE",
   "repository": {