@capagents/forgeqe 2.3.1 → 2.3.2

package/HOW_TO_USE.md

@@ -354,7 +354,7 @@ Copilot runs one SDK session per model request, with none of Copilot's own tools
 
 **In pipelines.** `forgeqe suite ... --no-code` uses only the browser engine. Set `COPILOT_GITHUB_TOKEN` to a fine-grained token with the Copilot Requests permission, stored as a pipeline secret. GitHub also documents the workflow's own `GITHUB_TOKEN` with `permissions: copilot-requests: write` for organization repositories whose Copilot policy allows it ([server tokens](https://docs.github.com/en/copilot/how-tos/copilot-sdk/auth/server-to-server-tokens)). A Copilot seat belongs to one person: prefer an organization-billed token over signing a shared pipeline in to someone's seat.
 
-GitHub Models, which ForgeQE used for the engine before, was [retired by GitHub](https://github.blog/changelog/2026-07-30-github-models-is-now-retired/) on July 30, 2026. A profile that still has `engine_model: "openai/..."` or `github_org` needs updating: drop `github_org`, and use a Copilot model id.
+GitHub Models, which ForgeQE used for the engine before, was [retired by GitHub](https://github.blog/changelog/2026-07-30-github-models-is-now-retired/) on July 30, 2026. A profile that still has `engine_model: "openai/..."` or `github_org` needs updating: drop `github_org`, and use a Copilot model id. A profile whose endpoint is GitHub Models (`models.github.ai`) is never called: remove it from `llms.json`. Copilot needs no `GITHUB_TOKEN` or `GH_TOKEN`; ForgeQE does not pass them to Copilot.
 
 **When something goes wrong.**
 
@@ -364,6 +364,7 @@ GitHub Models, which ForgeQE used for the engine before, was [retired by GitHub]
 | `The GitHub sign-in did not finish` | The browser sign-in was cancelled or denied. Run `forgeqe auth login copilot` again; with SAML single sign-on, authorize your organization when GitHub asks. |
 | `GitHub Copilot does not take classic tokens (ghp_)` | Sign in in the browser instead, or make a fine-grained token with the Copilot Requests permission, owned by your personal account. |
 | `GitHub Copilot did not accept the token` | The token has no Copilot Requests permission, has expired, or the account has no Copilot seat. |
+| `GitHub Copilot refused the sign-in` or `refused the token` (`Authorization error. Your credentials may be expired or invalid`) | Copilot received the credential and would not take it. A token wins over the browser sign-in: if `COPILOT_GITHUB_TOKEN` is set, or you once pasted a token, that is what was refused; remove it and run `forgeqe auth login copilot` in the browser. Otherwise sign in again. If it still fails and your seat comes from your company, a GitHub admin must allow Copilot CLI in the Copilot policies: the Copilot SDK runs on it. |
 | `… must be a Copilot model id`, `engine_model must be a Copilot model id` | Fix that field in `llms.json`: the sign-in lists the seat's models. A GitHub Models id such as `openai/gpt-4.1` is not a Copilot id; use `gpt-4.1`. |
 | `No model in llms.json can … right now` | Each model is listed with why it cannot be used and the fix. `forgeqe doctor` checks everything at once. |
 | `GitHub's Copilot SDK is not installed in the ForgeQE engine` | Run `forgeqe setup`. It installs the SDK from pypi.org; if that is blocked, `forgeqe doctor` says what to ask IT for. |