@capagents/forgeqe 2.3.13 → 2.3.15

package/HOW_TO_USE.md

@@ -614,19 +614,22 @@ The slash commands control the session and show a few things directly (`/help` l
 | `/stop` | Stop what is running (or press Esc) |
 | `/rerun [last\|run]` | Run a passed run again as recorded, without ForgeQE's agent (the last one, a run folder, or its goal) |
 | `/headed on\|off` | Show the browser window (live profiles) |
+| `/theme light\|dark\|auto` | Colours for a light or a dark terminal. ForgeQE asks the terminal which it is when it starts and follows it when it changes (auto); a terminal that does not say is drawn dark. `FORGEQE_THEME=light` (or `dark`) sets it at start; `/theme` alone says which is in use |
 | `/details [on\|off]` | Show everything the agents do while they work: the browser agent's reasoning, page memory, engine logs, every file the coding agent reads (off by default: step results, files written, test results, problems). `--verbose` or `FORGEQE_VERBOSE=1` starts with it on, for `start`, `run`, `suite`, `code`, and `heal` too |
 | `/model` | Pick the model from the profiles in `llms.json` (or click the model ▾ in the status line; Tab switches to the next one) |
 | `/profile <name>` | Switch LLM profile (or press Tab); the agent restarts with it |
 | `/env [name]` | The test environments in `env.yaml` and their apps, or switch to one |
 | `/logs [shots]` | Save this session's log and runs in one archive to share (`shots`: with screenshots) |
 | `/features` | What ForgeQE can do, and what each capability still needs here |
-| `/runs`, `/reports` | The runs and reports in the reports folder, newest first |
-| `/jobs` | The scheduled jobs: when each runs next, and how its last run ended |
-| `/knowledge` | The product knowledge the agents read (`.forgeqe/knowledge`) |
-| `/memory` | Page memory: the sites and pages ForgeQE remembers, and their flows |
-| `/guardrails` | The rules every agent follows here |
-| `/doctor` | Check what ForgeQE needs: programs, sign-ins, and the services it reaches |
-| `/settings` | `forgeqe.yaml`: where it is and what it sets, opened to edit |
+| `/runs` | The Runs page: every run with its result, steps and what page memory replayed; the week as a chart; click a run (or ↑↓) to see how it ended and every step it took: by page memory or the model, the page, what it did, how long it took, and the step that failed with its error. enter opens its report, f its folder, r runs it again |
+| `/reports` | The Reports page: every report ForgeQE wrote here (suites, pipelines, `/report`), newest first, each with **open ↗** to view it in the browser and a short summary of the chosen one. / searches by title, kind and summary (esc clears). A single run's report is on the Runs page. f opens its folder, b builds a new report |
+| `/jobs` | The Jobs screen: every scheduled job with its next run, last result and recent runs; the week's runs as a chart; the chosen job's runs and output. ↑↓ choose, r runs now, p pauses or resumes, s stops, l opens the log, esc goes back |
+| `/knowledge` | The Knowledge page: what ForgeQE has kept here as it works (run history, page memory, defect history, the code it wrote and how much is still there, product knowledge, visual baselines, watched pipelines), each with its entries |
+| `/skills` | The Skills page: every skill with the agents that use it and where it comes from; enter or **open ↗** opens its SKILL.md (`/skills <name>` shows one in the chat) |
+| `/memory` | The Page memory page: each site with its pages, elements and flows; the chosen site's pages and flows |
+| `/guardrails` | The Guardrails page: every rule and the file it is in. o opens the file to edit |
+| `/doctor` | The Doctor page: what ForgeQE needs on this machine, with the fix for what is missing. r also checks the model, the trackers and every service ForgeQE reaches |
+| `/settings` | The Settings page: the model, config file, trackers, environments, folders, domain and notifications, each opening where it is changed |
 | `/home` | Back to the start screen; the session stays |
 | `/docs` | The user guide |
 | `/generated` | How much of this repository's code ForgeQE wrote, and how much is still there |
@@ -764,7 +767,7 @@ Over the conversation: **Files** (each file read ◉, written ✚, or edited ✎
 
 **Setup checklist.** Until everything is set up, the start screen shows how many of the five things most features rest on are set up: **Model** (a live model profile), **Coding agent**, **Work items** (Azure DevOps, Jira, TestRail, Zephyr, qTest, or Xray), **Domain**, and **Notifications**. In a terminal 110 columns or wider it is the sidebar's **Get set up**: each finished item with what it found, and the next one as a card with **▸ Set up** (its steps in the chat; for **Work items**, it runs `/auth`) and **skip**. A skipped item is kept in `.forgeqe/setup.json` and not asked about again. Narrower, it is one **Setup** line with **▸ how to set up** and **skip**. The checks are the same ones `/features` uses, so the two always agree.
 
-**Sidebar and rail.** The sidebar has three groups. **Work**: **Home**, **This session** (once you have asked something), **Runs**, **Reports**, **Jobs**, and **Defects** (with a tracker set up). **Knowledge**: **Page memory**, **Test cases** (with a tracker), **Guardrails**, **Product** (the knowledge files) and **Skills**. **System**: **Models**, **Sign in**, **Environments**, **Doctor**, **Settings**, **Help** and **Docs**. Each shows how many there are and opens its list (`/runs`, `/reports`, `/jobs`, `/memory`, `/guardrails`, `/knowledge`, `/skills`, `/doctor`, `/settings`, `/help`, `/docs`); **Defects** and **Test cases** put a request in the composer, since the agent reads them from the tracker. Narrower than 110 columns, and beside the chat at every width, the sidebar folds to a rail of its icons, so the start screen is always one click away: **Home** (or `/home`) shows it with the session still open, and **▸ Back to the session** or any request returns to it.
+**Sidebar and rail.** The sidebar has three short groups. **Work**: **Home**, **This session** (once you have asked something), **Runs**, **Reports** and **Jobs**. **Knowledge**: **Knowledge** (history and what ForgeQE has kept), **Page memory**, **Test cases**, **Guardrails** and **Skills**. **System**: **Settings** and **Doctor**. Each opens a page in the chat's place, laid out for what it shows, with its keys at the foot: tables to move through with ↑↓, and **open ↗** links that open a report or a skill in the browser. **Test cases** lives in your tracker, so its page offers the requests that fetch it and puts the one you choose in the composer to read before sending, beside the suite files in the repository. esc goes back. Models, sign-ins and environments are a command away (`/model`, `/auth`, `/env`; `/help` lists them all), and **? help** and **docs ↗** are at the top right of the start screen. Beside the chat the sidebar is a column with its labels from 194 columns, and a rail of its icons below that, so the start screen is always one click away: **Home** (or `/home`) shows it with the session still open, and **▸ Back to the session** or any request returns to it.
 
 **Needs you and Today.** Once there are runs, the start screen shows what needs you (runs that failed this week and have not passed since, and jobs whose last run failed, each with **open** and **rerun**) and what ran today. The greeting says how many runs there were today and how many failed. The model is in the composer beside **⏎ Send**: click it to change it. The status line shows the branch, the tracker, and when the next scheduled job runs.
 
@@ -3050,6 +3053,7 @@ Signing in stays `/auth` and `forgeqe login`; `forgeqe bi export` and `forgeqe l
 | `/stop` or Esc | Stop what is running |
 | `/rerun [last\|run]` | Run a passed run again as recorded, without ForgeQE's agent |
 | `/headed on\|off` | Show the browser window |
+| `/theme light\|dark\|auto` | Colours for a light or a dark terminal. ForgeQE asks the terminal which it is when it starts and follows it when it changes (auto); a terminal that does not say is drawn dark. `FORGEQE_THEME=light` (or `dark`) sets it at start; `/theme` alone says which is in use |
 | `/details [on\|off]` | Show everything the agents do while they work: the browser agent's reasoning, page memory, engine logs, every file the coding agent reads (off by default: step results, files written, test results, problems). `--verbose` or `FORGEQE_VERBOSE=1` starts with it on, for `start`, `run`, `suite`, `code`, and `heal` too |
 | `/model`, or click the model ▾ in the status line | Pick the model from the profiles in `llms.json` |
 | `/profile <name>` or Tab | Switch the model profile |

package/README.md

@@ -58,7 +58,7 @@ npm trust github @capagents/forgeqe --file forgeqe-release.yml --repo javed0211/
 
 and on pypi.org, under `forgeqe-cli` → Publishing, add a GitHub trusted publisher: owner `javed0211`, repository
 `cli-agents`, workflow `forgeqe-release.yml`, no environment. A new npm trust that has not published within 2 days
-expires, so do it just before the first release.
+expires, so do it just before the first release. Keep the workflow's file name: the registries trust it by name, and a renamed file cannot publish until each is told.
 
 ## Privacy