@capagents/forgeqe 2.3.8 → 2.3.10

package/HOW_TO_USE.md

@@ -620,6 +620,9 @@ The slash commands control the session and show a few things directly (`/help` l
 | `/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`) |
 | `/generated` | How much of this repository's code ForgeQE wrote, and how much is still there |
 | `/init` | Set ForgeQE up in this folder: `forgeqe.yaml`, `llms.json`, editable prompts, skills, knowledge |
 | `/skills [name]` | The skills each agent can use, or one skill's instructions |
@@ -753,7 +756,9 @@ Over the conversation: **Files** (each file read ◉, written ✚, or edited ✎
 
 **Links.** Report folders, report files, and web addresses in the chat are links: Cmd-click (Ctrl-click on Windows and Linux) opens them in terminals that support links, such as VS Code, iTerm2, Windows Terminal, and recent GNOME Terminal. A path that no longer exists stays plain text.
 
-**Setup checklist.** Until everything is set up, the start screen's **Setup** line shows how many of the five things most features rest on are set up, and names the ones that are not: **Model** (a live model profile), **Coding agent**, **Work items** (Azure DevOps, Jira, TestRail, Zephyr, qTest, or Xray), **Domain**, and **Notifications**. **▸ how to set up** puts the steps for each missing one in the chat (for **Work items**, type `/auth`). The checks are the same ones `/features` uses, so the two always agree.
+**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 whose **▸ Set up** puts its steps in the chat (for **Work items**, it runs `/auth`). Narrower, it is one **Setup** line under the composer, and **▸ how to set up** gives the steps for every missing one. The checks are the same ones `/features` uses, so the two always agree.
+
+**Sidebar.** Under setup, **Work** opens **Runs**, **Reports**, **Jobs** and **Knowledge** (`/runs`, `/reports`, `/jobs`, `/knowledge`) with how many of each there are, and **Defects** (with a tracker set up) puts a request for the open defects in the composer. **System** opens **Features**, **Skills**, **Environments**, **Models**, **Sign in** and **Logs**. The status line shows the branch, the model (click it to change), the tracker, and when the next scheduled job runs.
 
 **Command palette.** Ctrl-P opens a palette of every action, command, profile, and example request; type a few letters to find one ("rr" finds *Refine my request*, "auth" finds the sign-in commands), ↑/↓ to choose, Enter to run it. Example requests are put in the prompt for you to edit, never sent straight away.