@ihyeon/flow-qa 0.2.7 → 0.2.8

package/README.ko.md

@@ -16,7 +16,7 @@ CLI와 `127.0.0.1` 전용 웹 UI를 제공합니다. UI는 영어로 시작하
 Node.js 24.x(24.22.1 이상) 또는 26.12.1 이상이 필요합니다. 브라우저는 첫 웹 실행 전에 설치합니다.
 
 ```sh
-npm install -g @ihyeon/flow-qa@0.2.7
+npm install -g @ihyeon/flow-qa@0.2.8
 flow-qa browser install
 flow-qa ui --demo
 ```

package/README.md

@@ -16,7 +16,7 @@ Flow QA is available as a CLI and a web UI bound to `127.0.0.1`. Provide a targe
 Node.js 24.x (24.22.1 or later) or 26.12.1 or later is required. Install Chromium before the first web run:
 
 ```sh
-npm install -g @ihyeon/flow-qa@0.2.7
+npm install -g @ihyeon/flow-qa@0.2.8
 flow-qa browser install
 flow-qa ui --demo
 ```

package/dist/src/ui/public/app.js

@@ -143,7 +143,16 @@
     const reqTitle = el('h3', '', t('app.requirements')); host.append(reqTitle);
     const reqList = el('ol', 'compact-list'); for (const req of suite.requirements || []) reqList.append(el('li', '', `${req.id} · ${req.text}`)); host.append(reqList);
     host.append(el('h3', 'case-title', t('app.caseSteps')));
-    for (const [index, item] of (suite.cases || []).entries()) {
+    const cases = suite.cases || [];
+    if (cases.length) {
+      const actions = el('div', 'actions');
+      const expand = el('button', 'button quiet', t('scenario.expandCases')); expand.type = 'button'; expand.id = 'expand-cases';
+      expand.addEventListener('click', () => host.querySelectorAll('details.case-review').forEach((detail) => { detail.open = true; }));
+      const collapse = el('button', 'button quiet', t('scenario.collapseCases')); collapse.type = 'button'; collapse.id = 'collapse-cases';
+      collapse.addEventListener('click', () => host.querySelectorAll('details.case-review').forEach((detail) => { detail.open = false; }));
+      actions.append(expand, collapse); host.append(actions);
+    }
+    for (const [index, item] of cases.entries()) {
       const detail = el('details', 'case-review'); detail.open = openCases ? !!openCases[index] : index === 0;
       detail.append(el('summary', '', `${item.id} · ${item.title}${item.questions?.length ? ` · ${t('app.caseBlocked')}` : ''}`));
       detail.append(el('p', 'hint', t('app.linkedRequirements', { ids: (item.requirementIds || []).join(', ') || t('app.none') })));

package/dist/src/ui/public/i18n.js

@@ -36,6 +36,8 @@
     'scenario.prompt': ['Download generation prompt', '생성 프롬프트 다운로드'],
     'scenario.reviewTitle': ['Review cases', '케이스 검토'],
     'scenario.reviewHelp': ['Open each case to inspect its actions and expected results.', '각 케이스를 펼쳐 행동과 기대 결과를 살펴보세요.'],
+    'scenario.expandCases': ['Expand all cases', '케이스 모두 펼치기'],
+    'scenario.collapseCases': ['Collapse all cases', '케이스 모두 접기'],
     'scenario.importFiles': ['Import case files', '케이스 파일 가져오기'],
     'scenario.importJson': ['TC JSON', 'TC JSON'],
     'scenario.importMarkdown': ['Source Markdown (optional)', '원본 Markdown (선택)'],

package/docs/mobile.md

@@ -9,7 +9,7 @@ Choose **Mobile** on the scenario screen, describe the flow, and generate or dow
 With the installed CLI:
 
 ```sh
-npm install -g @ihyeon/flow-qa@0.2.7
+npm install -g @ihyeon/flow-qa@0.2.8
 flow-qa init ./my-qa
 # Write your mobile flow in my-qa/flows/my-flow.md first.
 flow-qa plan flows/my-flow.md --platform mobile --prompt-only --workspace ./my-qa

package/docs/releases.md

@@ -2,6 +2,15 @@
 
 The alpha entries below are historical release records. They document earlier package versions and checks.
 
+## 0.2.8: expand and collapse all case details
+
+Adds Expand all cases and Collapse all cases to Scenario case review. The controls appear when cases are available and change only the case details. Individual toggles, the first-case-open default on loading, and expansion state across language changes and navigation remain available. Bulk actions preserve the draft, JSON editor disclosure, review confirmation, and execution readiness.
+
+Locally verified on macOS with Node.js 24.22.1 on 2026-10-28: 92 tests, type checking, UI syntax and design-system audit, and real Chromium checks for empty and loaded reviews, bulk and individual toggles, mixed expansion state across language changes, keyboard activation, navigation, unchanged draft/review state, and a 390px viewport. Existing UI and demo checks, package validation, and a fresh tarball installation with three passing browser cases also passed. No model calls were used.
+
+- Package: [`@ihyeon/flow-qa@0.2.8`](https://www.npmjs.com/package/@ihyeon/flow-qa/v/0.2.8)
+- Release: [GitHub 0.2.8](https://github.com/hyeonse-swing/flow-qa/releases/tag/v0.2.8)
+
 ## 0.2.7: filter run history by status
 
 Adds a Run status selector to run history for passed, failed, blocked, error, and interrupted reports. All statuses restores the loaded list, and a separate message explains when the selected status has no matches. The selected status stays through navigation, language changes, and automatic report updates. This filters the UI's existing most recent 50 reports and preserves the open report, downloads, and scenario review state.

package/docs/ui.md

@@ -7,7 +7,7 @@ Describe a user flow, review cases, and configure a target when ready to run. We
 Node.js 24.x (24.22.1 or later) or 26.12.1 or later is required. Node 25 is unsupported. Upgrade the Node runtime and restart any running UI process; updating Flow QA alone does not patch Node. Install Flow QA and start the web demo:
 
 ```sh
-npm install -g @ihyeon/flow-qa@0.2.7
+npm install -g @ihyeon/flow-qa@0.2.8
 flow-qa browser install
 flow-qa ui --demo
 ```
@@ -30,7 +30,7 @@ The UI starts in **English**, regardless of browser language. Switch to **한국
 
 1. **Scenario:** Choose Web or Mobile and describe the initial state, actions, screen elements, and expected results. No target is required yet. If a planner is ready, ask it to create cases. Without a model, download the planning prompt and paste a JSON response from an AI you already use.
 2. **Connections:** When ready, register a target name and web URL, or choose iOS/Android and enter an installed app's bundle/package ID and device. Planner and execution agent models have separate settings. Saving settings does not start an app or model request.
-3. **Review and save cases:** Expand each case to read preconditions, actions, expected results, and unresolved questions. Editing the JSON keeps the linked flow; if that source flow changes, design the cases again. Planning and running are separate actions. Editing inputs or connection settings alone does not call a model.
+3. **Review and save cases:** Expand each case, or use **Expand all cases**, to read preconditions, actions, expected results, and unresolved questions. **Collapse all cases** returns to the case titles. Editing the JSON keeps the linked flow; if that source flow changes, design the cases again. Planning and running are separate actions. Editing inputs or connection settings alone does not call a model.
 4. **Run QA:** Review the saved case file, select a matching web/mobile target, and check the review confirmation before running. If the file or target settings change after review, reload and review them again. Fixed steps need no agent model. `act` and `assertAgent` require a compatible agent; missing models and unresolved questions are reported as blocked cases.
 5. **Case library and Run history:** Save cases as new files, search by title, suite ID, or file name, and load them again. Filter run history by status, then open run details to see each case, attempt, and evidence; download the Markdown or JSON report.
 
@@ -46,6 +46,10 @@ From version `0.2.2`, the UI requests the browser's leave-page confirmation when
 
 From version `0.2.4`, loading a suite from the library or importing valid case files also asks before replacing unsaved scenario or case content. **New JSON draft** asks before clearing unsaved JSON and keeps the scenario text. Cancel keeps the current content and selected import files. Unchanged saved cases and ordinary navigation between screens do not prompt; invalid imports still show their validation error without replacing anything.
 
+### Expand or collapse case review
+
+From version `0.2.8`, **Expand all cases** and **Collapse all cases** control the case details in Scenario. Individual case titles still toggle their own details. Language changes and navigation preserve which cases are open; loading a new suite keeps the original first-case-open default. These controls only change the view: they do not approve cases, modify the draft, or change the JSON editor disclosure. Review confirmation is still required before execution.
+
 ### Search saved cases
 
 From version `0.2.6`, **Case library** filters saved suites as you type in **Search saved suites**. Search matches part of a title, suite ID, or file name, ignores letter case and surrounding whitespace, and supports Korean text. Clear the field to show all suites. The query stays while navigating, changing language, or receiving updated saved cases; it resets when the page reloads. Search covers the listed top-level case files, not individual steps or source Markdown.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ihyeon/flow-qa",
-  "version": "0.2.7",
+  "version": "0.2.8",
   "license": "MIT",
   "author": "Hyeonse Im",
   "repository": {