@sun-asterisk/sungen 3.2.2 → 3.2.3-beta.3

package/src/orchestrator/templates/ai-instructions/claude-skill-api-design.md

@@ -1,62 +0,0 @@
----
-name: sungen-api-design
-description: The API-first design loop for an api unit (qa/api/<area> or qa/api/flows/<flow>) — discover the catalog, lay out the API viewpoints, generate @api/@cases/flow/@concurrent scenarios, then drive the sungen audit --area gate + reviewer + repair to a high businessDepth (≥0.7). Use when create-test/run-test detects an api unit (no selectors, no visual capture).
----
-
-# API design loop (driver-api · Orchestration + Harness)
-
-Use this when the unit is **api-first** — `qa/api/<area>/` or `qa/api/flows/<flow>/`. There are **no selectors and no visual capture**: the contract is the **named-endpoint catalog** (`api/apis.yaml`), referenced by `@api:<name>`. QA writes **no HTTP code**. Full annotation reference: the **API Steps** guide (`@api` / `@cases` / flows / `@concurrent` / `@hybrid`).
-
-## The loop (mirror of /sungen:design, API-native)
-
-### 1. Discover (no capture)
-Run `sungen context --area <name>` — it reads the catalog and prints the **endpoints** + the **generation units** (one `matrix` unit per endpoint, an `async` unit per mutating endpoint, a `flow` unit for an api flow). Read `qa/api/<name>/requirements/spec.md` if present. No `apis.yaml` yet? → `sungen api import <openapi|csv>` or `sungen api add --area <name>` first.
-
-### 2. API viewpoint overview (by method-profile)
-For each endpoint, cover its viewpoints — severity-weighted by method:
-
-| Profile | Endpoints | Must cover | Then |
-|---|---|---|---|
-| read | GET, HEAD | `contract` (status + body shape) | `pagination`/`filter` (list), `not-found` (by-id) |
-| mutating | POST/PUT/PATCH/DELETE | `contract`, `error` (validation/4xx/auth) | `idempotency` (`@concurrent`), `side-effect` (`@query`) |
-
-Bands: **~70%** success+failure matrix · **~20%** flows (auth/CRUD chains) · **~10%** async/idempotency.
-
-### 3. Generate (incremental — never the whole suite in one Write)
-- **Contract**: `@api:<name>` + `expect {{name.status}} is …` **and a body assertion** (`{{name.body.<path>}}`).
-- **Error matrix**: `@api:<name>(p={{p}}) @cases:<dataset>` — one scenario, a dataset of `input → expected status`.
-- **Flow**: ordered `@api` tags threading a prior response (`token={{login.body.token}}` → the catalog `Bearer :token` header; `id={{create.body.id}}` → a path param). Self-clean (delete what you create).
-- **Idempotency**: `@api:<name> @concurrent:N` + `expect {{name.ok_count}} is 1`, cross-checked with `@query` (the DB is the oracle).
-
-### 4. Gate + repair (always — businessDepth ≥ 0.7 is the bar)
-Run `sungen audit --area <name>`; read `gateStatus` + `findings`. Then the **semantic reviewer** (sungen-reviewer sub-agent, API criteria). Repair **both** (budget 3 rounds), re-audit until PASS:
-
-| Finding | Repair |
-|---|---|
-| `VIEWPOINT-API-CONTRACT` | the endpoint is invoked but its response is never asserted → add `expect {{name.status}}` + a `{{name.body.…}}` check |
-| `VIEWPOINT-API-ERROR` | a mutating endpoint has no failure scenario → add a `@cases` error matrix (or an explicit 4xx) |
-| `VIEWPOINT-API-IDEMPOTENCY` | a mutating endpoint has no race check → add `@concurrent:N` + a `@query` DB cross-check |
-| `VIEWPOINT-API-MANUAL-AUTOMATABLE` | a `@manual` scenario whose endpoint resolves is automatable → drop `@manual`, use `@api` (+ `@cases`); reserve `@manual` for genuine judgment cases |
-| **`DEPTH-FAIL`** (businessDepth < 0.7) | a **mutating success** scenario asserts only `status` → make it **prove the effect**: assert a response **body** field, a **`@query`** side-effect, or a **`@concurrent` `ok_count`** invariant. (An error/`@cases` scenario proving the status is correct — it is *not* depth-required.) |
-
-Stop when the gate PASSes + businessDepth ≥ 0.7, or the budget is exhausted → report residual gaps honestly (mark genuinely-unautomatable cases `@manual` with an oracle). Never fake a pass.
-
-### 5. Record + converge
-`sungen manifest --area <name>` (reuse) and ledger each phase; show the trace + the HUMAN-LOOP FOCUS. (Integrity `script-check`/`trace` for api: see run-test.)
-
-## Taxonomy (label scenarios correctly)
-
-| Class | What | Examples |
-|---|---|---|
-| **Functional** | single-endpoint behaviour | happy contract · error/validation (`@cases`) · boundary/edge |
-| **Functional — flow/integration** | multi-endpoint journeys | auth/CRUD lifecycle (`create → login → get → delete`), cross-endpoint invariants |
-| **Non-Functional** | performance · reliability · **security** · concurrency/idempotency | `@concurrent` race/idempotency |
-
-A flow (`create → login → delete`) is a **Functional integration** test, **not** non-functional — don't file it under "Non-Functional". Reserve non-functional for perf/security/concurrency.
-
-## Rules
-- **No HTTP, no selectors** — only `.feature` + the reviewed `apis.yaml` + `test-data`.
-- **Non-prod default** — a `production` datasource is refused unless `SUNGEN_ALLOW_PROD=1`.
-- **The DB is the oracle** for idempotency/side-effects — HTTP status alone can lie; pair `@api` with `@query`.
-- **`@parallel` + mutating endpoints** — give each scenario **isolated data** (a `{{$uuid}}` email, a `@cases` row, or its own created resource) and **self-clean** (delete what it created); shared inputs race under parallel execution.
-- **No dead data** — every `test-data` key must be bound into a scenario (`{{key}}`, a `@cases` dataset, or an override). `sungen audit`/the generate lint flag unreferenced keys.

package/src/orchestrator/templates/ai-instructions/claude-skill-capture-mode-figma-mcp.md

@@ -1,82 +0,0 @@
-# Capture mode: figma-mcp
-
-Pull **structured design data** (layout, typography, colors, component tree, design tokens) and a **PNG screenshot** from a Figma frame URL via the **Figma Dev Mode MCP**, so `sungen-tc-generation` can author Gherkin + test-data before a live domain exists. Use when the project is pre-launch or Figma is the source of truth and the live build lags the design.
-
-## Prerequisites
-
-- **Figma MCP server** (`https://mcp.figma.com/mcp`, HTTP transport) connected in `.mcp.json` — `sungen init` scaffolds this. On first use, Claude Code opens a browser for Figma OAuth. Official tools: `get_design_context`, `get_variable_defs`, `get_screenshot`.
-- Figma account signed in with access to the file. **Dev/Full seats** get per-minute rate limits; **Starter/View seats** get monthly tool-call limits.
-- A Figma URL with both **fileKey** and **nodeId**.
-
-If the MCP is not connected, **do not fail silently** — tell the user:
-> "Figma MCP not detected. Run `sungen init` to scaffold the config, or manually add `figma` with `url: https://mcp.figma.com/mcp` to `.mcp.json`. Then sign in when Claude Code prompts."
-
-Then stop.
-
-## Steps
-
-### 1. Resolve Figma URL
-
-Prefer in this order:
-1. `Figma URL` field in `requirements/spec.md` (Overview section)
-2. If empty/missing → `AskUserQuestion`: *"Paste the Figma frame URL"* (free text)
-
-Accept any of these shapes:
-```
-https://www.figma.com/file/<fileKey>/<title>?node-id=<nodeId>
-https://www.figma.com/design/<fileKey>/<title>?node-id=<nodeId>
-https://www.figma.com/proto/<fileKey>/<title>?node-id=<nodeId>
-```
-Parse: `fileKey` = segment after `/file/`, `/design/`, or `/proto/`; `nodeId` = the `node-id` query param (pass `-` or `:` through as-is). If `node-id` is missing, ask the user to select a frame in Figma and copy the **frame URL** (not the file root).
-
-### 2. Fetch design context
-
-Call **both** in parallel:
-```
-get_design_context({ fileKey, nodeId })
-get_variable_defs({ fileKey, nodeId })
-```
-`get_design_context` → layout, typography, colors, component structure, spacing. `get_variable_defs` → named design tokens.
-
-### 3. Fetch screenshot
-
-```
-get_screenshot({ fileKey, nodeId })
-```
-Save the PNG to `requirements/ui/figma-<sanitized-nodeId>.png` (replace `:` and `-` with `_`, e.g. `42-15` → `figma-42_15.png`).
-
-### 4. Write metadata dump
-
-Combine design context + variables into `requirements/ui/figma-meta.md`:
-```markdown
-# Figma Capture — <nodeId>
-**Source:** <full Figma URL>
-**Captured:** <ISO date>
-## Components
-<component names + variants>
-## Typography
-<font families, sizes, weights, line heights>
-## Colors
-<color tokens + raw hex>
-## Spacing & Layout
-<spacing tokens, auto-layout specs>
-## Text Content
-<visible text strings — used by tc-generation to populate test-data>
-```
-Consumed by `sungen-tc-generation` as a secondary source alongside `spec.md`.
-
-### 5. Report back
-
-> Captured Figma frame `<nodeId>`: Components N · Text strings M · Design tokens K · Screenshot `requirements/ui/figma-<nodeId>.png` · Metadata `requirements/ui/figma-meta.md`
-
-Then hand back to the calling command.
-
-## Error handling
-
-| Error | Action |
-|---|---|
-| MCP tool not available | Print setup instructions, stop, do not fall back silently |
-| `fileKey` missing from URL | Ask user to paste a valid frame URL |
-| `nodeId` missing from URL | Ask user to right-click a frame in Figma → *Copy link to selection* |
-| `get_design_context` 403 | Ask user to check Dev Mode seat on that file |
-| `get_screenshot` returns no image | Continue with metadata only; warn no PNG was captured |

package/src/orchestrator/templates/ai-instructions/claude-skill-capture-mode-figma-pat.md

@@ -1,117 +0,0 @@
-# Capture mode: figma-pat
-
-Figma URL → `spec_figma.md` envelope + LLM-synthesized narrative from cached raw node JSON. This mode is the active one when any of these is true: a sungen command was invoked with `--figma`, `requirements/spec_figma.md` exists, or the user says "generate from Figma".
-
-## Prerequisites
-
-- [ ] `sungen figma auth check` succeeds — PAT is stored and valid
-- [ ] Figma file URL is available (shared file or frame link)
-- [ ] If auth missing → run `sungen figma auth set` and follow the walkthrough
-
-**Never paste the PAT into any transcript, spec file, or commit.**
-
-## Two-Layer Architecture
-
-`spec_figma.md` has two layers separated by the `<!-- SYNTHESIS-BELOW -->` marker:
-
-| Layer | Producer | Overwrite Rule |
-|---|---|---|
-| **Envelope** (above marker) | sungen CLI | Regenerated each `sungen figma` run — deterministic |
-| **Narrative** (below marker) | This mode (LLM) | Replaced on re-synthesis — everything from marker to EOF |
-
-The envelope contains: YAML frontmatter, Frame metadata, Screenshots. The narrative is synthesized by YOU from the cached raw Figma node JSON.
-
-## Inputs You Read
-
-The scaffolder persists a raw (unfiltered) Figma node tree to:
-```
-.sungen/figma-cache/<fileKey>/<versionId>/<nodeId>-raw.json
-```
-Read this file + the envelope frontmatter of `requirements/spec_figma.md` + any PNGs under `requirements/ui/`. You MUST NOT call the Figma REST API directly — the PAT is not available to you.
-
-## Synthesis Task
-
-Append 7 narrative sections below `<!-- SYNTHESIS-BELOW -->`. Each is inferred from the raw node tree (names, types, `characters`, layout bounds, auto-layout direction, componentProperties):
-
-### 1. Purpose
-One paragraph. What screen is this? Primary user goal? Infer from frame name + top-level text + dominant CTA.
-
-### 2. ASCII Layout
-Rough spatial sketch using box characters. Reflect top-bottom / left-right ordering from absoluteBoundingBox. Keep under ~20 lines:
-```
-┌──────────────────────────────────────┐
-│ [Logo]                     [Sign In] │
-├──────────────────────────────────────┤
-│  Welcome back                        │
-│  ┌────────────────────────────────┐  │
-│  │ email@example.com              │  │
-│  └────────────────────────────────┘  │
-│  [ Continue ]                        │
-└──────────────────────────────────────┘
-```
-
-### 3. Regions
-Bulleted list of major layout regions (header, sidebar, main, footer, modal…) with a one-line purpose each. Use auto-layout frames as region hints.
-
-### 4. Actions
-Every interactive element the user can trigger (button, link, icon-button, menu-item, toggle…):
-```
-- **<Action name>** — <what it does> (source: <node name>)
-```
-
-### 5. Form Fields
-Every input. Include label, type (text/email/password/select/checkbox/radio/textarea/date), required hint if inferable, placeholder:
-```
-| Label | Type | Required | Placeholder |
-|---|---|---|---|
-```
-Omit (write `_none_`) if no inputs exist.
-
-### 6. Data Columns
-If the screen shows a table/list/card grid — enumerate the columns/fields per row. Otherwise `_none_`.
-
-### 7. Navigation
-Outgoing links, tab bars, breadcrumbs, back buttons — anything that moves to another screen. Include explicit nav components and implicit CTAs that navigate.
-
-## Synthesis Workflow
-
-1. Read `requirements/spec_figma.md` — note `file_key`, `node_id`, `figma_version_id` from frontmatter
-2. Read `.sungen/figma-cache/<file_key>/<figma_version_id>/<safe_node_id>-raw.json` (colons in node_id become underscores)
-3. Traverse the tree. Collect names, types, `characters`, `componentProperties`, `absoluteBoundingBox`
-4. Produce the 7 sections above
-5. **Locate the insertion point** in `spec_figma.md`:
-   - **If `<!-- SYNTHESIS-BELOW -->` is present** → replace everything from the marker (inclusive) to EOF with: the marker line, a blank line, then the 7 sections.
-   - **If the marker is NOT present** (older file or hand-edited) → locate the last non-empty line of the envelope (usually the end of `## Screenshots`), append a blank line, then the marker, another blank line, then the 7 sections. Do NOT delete any envelope content.
-   - **If the file is missing entirely** → advise the user to re-run `sungen add --screen <screen> --figma <url> --refresh` to regenerate the envelope first. Do not fabricate one.
-6. Preserve the envelope (frontmatter + Frame + Screenshots) byte-for-byte. Never touch content above the marker.
-
-## Re-synthesis
-
-- If the envelope's `figma_version_id` changed → envelope is fresh; re-run synthesis
-- If only the narrative is stale → truncate from marker to EOF and regenerate
-- Never edit content ABOVE the marker — that is the scaffolder's territory
-
-## Selector Heuristics (for downstream `run-test`)
-
-During `run-test` Phase 0, provisional selectors can be seeded from the raw JSON:
-
-| Figma Signal | Provisional YAML Entry |
-|---|---|
-| Node name ends `Button`, has text | `role: button` + `name: "<text>"` |
-| Node name ends `Input`/`Field` | `placeholder: "<placeholder text>"` |
-| Node name ends `Link`, has text | `role: link` + `name: "<text>"` |
-| componentProperties has `data-testid` | `testid: <value>` |
-| Plain text leaf (outside interactive) | `text: "<content>"` |
-| Node name ends `Icon` | `role: img` + `name: "<accessible name>"` |
-
-Every provisional entry MUST carry:
-```
-# @needs-live-verify source=figma node_id=<id>
-```
-Provisional selectors feed `selectors.yaml` as candidates. `run-test` Phase 0 verifies them against the live page and overwrites incorrect entries.
-
-## Security
-
-- Never include the PAT in `spec_figma.md`, selectors, test data, or any committed file
-- Never log or echo the PAT in terminal output
-- Read only from `.sungen/figma-cache/` and screen directories — never from `.env`

package/src/orchestrator/templates/ai-instructions/claude-skill-capture-mode-live.md

@@ -1,60 +0,0 @@
-# Capture mode: live
-
-Navigate a running application, take **one accessibility snapshot** and **one screenshot**, and save them as visual context for test generation. Use when the app is live (dev, staging, or production with read-only access) and you want tests grounded in the actual rendered UI. Handles auth gracefully: if the page redirects to login, ask the user to sign in manually rather than injecting cookies.
-
-## Prerequisites
-
-- Playwright MCP connected.
-- Dev/staging server reachable (or a public URL).
-- `playwright.config.ts` exists at the project root (for `baseURL` fallback).
-
-## Steps
-
-### 1. Resolve target URL
-
-1. `Live URL` field in `requirements/spec.md` (Overview section)
-2. `baseURL` from `playwright.config.ts` + `URL Path` from `spec.md`
-3. Neither → `AskUserQuestion`: *"Paste the full URL for the page to scan"*
-
-### 2. Navigate
-
-`browser_navigate` to the resolved URL.
-
-### 3. Handle auth redirect
-
-If the page redirects to a login route (URL contains `/login`, `/signin`, `/auth`, or content indicates a login screen):
-1. Tell the user which login URL they landed on.
-2. `AskUserQuestion`:
-   - **I'll log in manually** — wait for confirmation, then re-navigate to the target URL
-   - **Skip live scan** — switch to mode `local`
-   - **Cancel**
-3. **Never** inject cookies or localStorage via `browser_evaluate` / `browser_run_code`. Auth belongs to the user.
-
-### 4. Snapshot
-
-Take **ONE** `browser_snapshot`. This accessibility tree is the primary AI context — roles, names, text, structure that tc-generation uses to identify sections and fields.
-
-### 5. Screenshot (recommended)
-
-Take **ONE** `browser_take_screenshot` with `fullPage: true`. Save to `requirements/ui/live-<timestamp>.png`, where `<timestamp>` is `YYYYMMDD-HHMM` local time (e.g. `live-20260421-1430.png`).
-
-### 6a. Verify unauthenticated redirect target (flow capture only)
-
-When capturing for a **flow** with security scenarios (e.g. "unauthenticated user cannot access X"):
-1. Open a **fresh incognito/unauthenticated** context (no storage state).
-2. `browser_navigate` to the protected route.
-3. Record the **actual redirect URL** — do NOT assume `/login`; it may be `/register`, `/`, etc.
-4. Report the redirect target: *"Unauthenticated access to `/dashboard` redirects to `/register`"*.
-5. The caller must use the **actual redirect URL** in Gherkin assertions, never an assumed one.
-
-Skip if the flow has no security scenarios or the user says to skip.
-
-### 6. Detect discrepancies vs spec
-
-If `spec.md` exists, cross-check the snapshot against spec sections: fields in spec but not in snapshot → *missing in UI*; elements in snapshot but not in spec → *missing in spec*. Report findings but **do not** auto-edit `spec.md`.
-
-### 7. Report back
-
-> Captured live page `<URL>`: Snapshot N interactive elements · Screenshot `requirements/ui/live-<timestamp>.png` · Discrepancies vs spec: <count or "none">
-
-Hand back to the calling command. Scans **exactly one** page per invocation.

package/src/orchestrator/templates/ai-instructions/claude-skill-capture-mode-local.md

@@ -1,38 +0,0 @@
-# Capture mode: local
-
-Use **pre-existing images** in `requirements/ui/` as visual context. No network, no MCP, no live site — works for any design tool (Figma export, Sketch, Penpot, Zeplin, hand-drawn, staging screenshots). This is the **baseline fallback**: if the live domain is down and Figma MCP isn't configured, this always works as long as the user drops images in the folder.
-
-## Steps
-
-### 1. List available images
-
-Glob `requirements/ui/*.{png,jpg,jpeg,webp,gif}` and report count + filenames. Filter out metadata files (e.g. `figma-meta.md` written by mode figma-mcp) — those are read by `tc-generation` separately, not treated as images here.
-
-### 2. Handle empty folder
-
-If no images found:
-1. Tell the user the folder is empty, with the full path so they can open it in Finder.
-2. `AskUserQuestion`:
-   - **I'll drop images now** — wait for confirmation, then re-glob
-   - **Switch to Figma** — switch to mode `figma-mcp`
-   - **Switch to live page scan** — switch to mode `live`
-   - **Cancel** — abort create-test
-3. If "drop images now", wait for confirmation (e.g. "done") then re-run step 1.
-
-### 3. Read images for context
-
-Use the `Read` tool on each image — Claude Code reads PNG/JPG/WebP directly as visual context. For large sets (>10 images), ask which are primary and which are states/variants to avoid loading too much at once.
-
-### 4. Summarize
-
-> Loaded N image(s) from `requirements/ui/`:
-> - `<filename-1>` — <one-line description of what's visible>
-> - `<filename-2>` — <one-line description>
-
-Hand back to the calling command.
-
-## File naming hints for users
-
-Nudge users toward consistent filenames (don't enforce):
-- `<section>-default.png` / `-error.png` / `-loading.png` / `-empty.png` — section states
-- `full-page.png` / `viewport.png` — whole screen (auto-generated by `sungen add --capture`)

package/src/orchestrator/templates/ai-instructions/claude-skill-capture.md

@@ -1,35 +0,0 @@
----
-name: sungen-capture
-description: 'Acquire visual/design context for test generation from one of four sources (modes): figma-mcp, figma-pat, live, local. Auto-loaded by create-test/add-screen when a visual source is needed, or when --figma flag / spec_figma.md is present. Router skill — read only the mode file you need.'
-user-invocable: false
----
-
-## Purpose
-
-Bring **visual + design context** into test generation so `sungen-tc-generation` can author Gherkin + test-data grounded in the real UI. This is a **router**: pick exactly **one mode** for the run, then read only that mode's file. Do **not** read all four.
-
-This skill never generates Gherkin or `selectors.yaml` — it only acquires context and reports back to the calling command.
-
-## Pick the mode
-
-| Mode | Read | Use when | Needs |
-|---|---|---|---|
-| **figma-mcp** | `mode-figma-mcp.md` | Pre-launch / Figma is source of truth, **Figma Dev Mode MCP** connected | Figma MCP + frame URL |
-| **figma-pat** | `mode-figma-pat.md` | `--figma` flag was used, or `requirements/spec_figma.md` exists (synthesize narrative from cached raw node JSON) | `sungen figma auth` PAT |
-| **live** | `mode-live.md` | App is running (dev/staging/prod read-only) and you want the actual rendered UI | Playwright MCP + reachable URL |
-| **local** | `mode-local.md` | Images already dropped in `requirements/ui/` (any design tool, screenshots, mockups) — baseline fallback, no network | nothing |
-
-### How the mode is chosen (when the caller didn't specify)
-
-1. `requirements/spec_figma.md` exists → **figma-pat** (PAT flow already ran during `add-screen`).
-2. `requirements/ui/` has images → **local**.
-3. Neither → ask the user which source (figma-mcp / live / local), then load that one mode file.
-
-Modes are **mutually exclusive per run**, but the user can run `create-test` again with a different mode to layer context. All modes write to `requirements/ui/` and report back.
-
-## What this skill (any mode) does NOT do
-
-- Does not generate Gherkin — that's `sungen-tc-generation`.
-- Does not write `selectors.yaml` — that's `/sungen:run-test`.
-- Does not inject auth/cookies — the user logs in manually (see `live`).
-- Does not crawl or generate images.

package/src/orchestrator/templates/ai-instructions/claude-skill-dashboard.md

@@ -1,121 +0,0 @@
----
-name: sungen-dashboard
-description: 'Build a single-file HTML dashboard summarising test cases & Playwright results. Auto-loaded by /sungen:dashboard.'
-user-invocable: false
----
-
-## Purpose
-
-Generate `qa/dashboard/index.html` — a single-file, share-ready test report covering all (or selected) screens and flows. The HTML embeds the snapshot data inline, so it can be emailed, Slacked, or committed and opened by anyone via `file://` without any server.
-
-**This skill delegates all heavy work to the `sungen dashboard` CLI.** The CLI is the source of truth for parsing logic — do NOT re-parse files in AI. Your role is only to:
-
-1. Invoke the CLI.
-2. Show its output verbatim.
-3. Help the user decide next actions.
-
----
-
-## Architecture
-
-```
-User → /sungen:dashboard [screen...]
-       │
-       ▼
-  sungen dashboard CLI  (deterministic — no AI tokens)
-  ├─ Discovery: qa/screens/* + qa/flows/*
-  ├─ Reuse delivery parsers (.feature, .spec.ts, test-data.yaml, results.json)
-  ├─ Build DashboardSnapshot JSON
-  ├─ Write qa/dashboard/history/<runId>.json (max 20 retained, oldest pruned)
-  ├─ Inject payload into pre-built HTML template
-  └─ Write qa/dashboard/index.html (~1MB, fully self-contained)
-```
-
-Source modules: `src/dashboard/*.ts` + `src/exporters/json-exporter.ts`.
-UI source: `dashboard/` (built once, ships in npm package as `dist/dashboard/templates/index.html`).
-
----
-
-## Required sources (CLI tolerates missing files)
-
-| # | Source | Path | Required? |
-|---|--------|------|-----------|
-| 1 | Feature file | `qa/screens/<name>/features/<name>.feature` (or `qa/flows/...`) | Yes — screens without a feature are skipped |
-| 2 | Test data | `qa/screens/<name>/test-data/<name>.yaml` | Optional — `{{vars}}` fall back to literal |
-| 3 | Compiled spec | `specs/generated/<name>/<name>.spec.ts` | Optional — flagged as "Not compiled" if missing |
-| 4 | Test results | `specs/generated/<name>/<name>-test-result.json` (or `test-results/results.json`) | Optional — TCs show as "Pending" if missing |
-
-Unlike `sungen delivery`, the dashboard CLI is **forgiving** — it always renders whatever data is available. Pre-flight is implicit, not blocking.
-
----
-
-## Output structure
-
-```
-qa/dashboard/
-├── index.html                      # share-ready single-file report
-└── history/
-    ├── 2026-04-26T...Z.json        # past snapshots, oldest → newest
-    ├── 2026-04-27T...Z.json
-    └── …                           # max 20, older pruned automatically
-```
-
-Both should be committed to git so collaborators see the same trend lines.
-
----
-
-## Dashboard views
-
-| View | What it shows |
-|------|---------------|
-| **Overview** | Stat cards (total/passed/failed/pending), pass-rate donut, priority bar chart, trend mini-chart, per-screen progress bars |
-| **Suites** | Tree: screen → scenarios; filter by search/status/priority; click → detail modal with steps, expected, error, trace |
-| **Trends** | Pass-rate line chart + stacked status bars across all retained runs (requires ≥2 runs) |
-| **Compare** | Pick base/head run; per-screen Δ table; lists of newly passing/failing/added/removed/changed tests |
-| **Export** | Browser-side CSV / XLSX download. One-button generation, no server. Same column layout as `sungen delivery` |
-
-Trends + Compare are disabled in the sidebar until at least 2 runs exist in history.
-
----
-
-## CLI command reference
-
-```bash
-# All screens + flows
-sungen dashboard
-
-# Specific targets
-sungen dashboard kudos awards flow/checkout
-
-# Skip history persistence (one-off / CI ephemeral)
-sungen dashboard --no-history
-
-# Cap retained history (default: 20)
-sungen dashboard --max-history 50
-
-# Auto-open in default browser
-sungen dashboard --open
-```
-
----
-
-## Skill responsibilities (when invoked from /sungen:dashboard)
-
-1. **Run the CLI** with whatever arguments came from `$ARGUMENTS`.
-2. **Show the CLI output verbatim** — do not summarize, paraphrase, or omit warnings.
-3. **Offer next-step options via `AskUserQuestion`** based on what just happened:
-   - On success → open dashboard, share file, run more tests, build for another screen, done.
-   - On error → diagnose from the error message; common causes are missing `qa/` directories or no targets.
-4. **Do NOT** parse `.feature`, `.spec.ts`, or results files yourself — that is the CLI's job.
-5. **Do NOT** touch files under `qa/dashboard/` directly — only the CLI writes there.
-
----
-
-## Sharing the dashboard
-
-The HTML is self-contained:
-- No CDN or external font — system font stack only.
-- All JS, CSS, charts, and the SheetJS library are inlined.
-- The snapshot payload sits in `<script id="__SUNGEN_DASHBOARD__" type="application/json">…</script>`.
-
-Acceptable sharing: email, Slack upload, S3 bucket, committed in git. The recipient opens it directly, no install required. ~1MB on disk, ~300KB gzipped over the wire.

package/src/orchestrator/templates/ai-instructions/claude-skill-delivery.md

@@ -1,141 +0,0 @@
----
-name: sungen-delivery
-description: 'Export Gherkin scenarios + Playwright results → CSV test case deliverable. Auto-loaded by delivery command.'
-user-invocable: false
----
-
-## Purpose
-
-Export test cases from Sungen screens and flows to a standardized CSV file (format BM-2-901-13) for QA delivery.
-
-**This skill delegates all heavy work to the `sungen delivery` CLI.** The CLI is the single source of truth for parsing logic — do NOT re-parse files in AI. Your role is only to:
-
-1. Invoke the CLI
-2. Show its output verbatim
-3. Help the user react to pre-flight failures
-
----
-
-## Architecture
-
-```
-User → /sungen:delivery [name...]
-       │
-       ▼
-  sungen delivery CLI  (deterministic — no AI tokens)
-  ├─ Scope detection (no-arg = all screens + flows)
-  ├─ Auto-detect: qa/flows/<name>/ → flow, qa/screens/<name>/ → screen
-  ├─ Pre-flight source checks per target
-  ├─ Parse .feature (metadata)
-  ├─ Parse .spec.ts (resolved Playwright code — source of truth)
-  ├─ Parse test-data.yaml (resolve {{vars}})
-  ├─ Parse test-results/results.json (match test titles)
-  ├─ Merge sources + generate CSV rows
-  └─ Write qa/deliverables/<name>-testcases.csv
-```
-
-Source modules: `src/exporters/*.ts`
-
----
-
-## Required sources (CLI pre-flight checks these)
-
-| # | Source | Screen path | Flow path | Created by |
-|---|--------|-------------|-----------|------------|
-| 1 | Feature file | `qa/screens/<name>/features/<name>.feature` | `qa/flows/<name>/features/<name>.feature` | `add-screen`/`add-flow` + `create-test` |
-| 2 | Test data | `qa/screens/<name>/test-data/<name>.yaml` | `qa/flows/<name>/test-data/<name>.yaml` | `create-test` |
-| 3 | Selectors | `qa/screens/<name>/selectors/<name>.yaml` | `qa/flows/<name>/selectors/<name>.yaml` | `run-test` |
-| 4 | Compiled spec | `specs/generated/<name>/<name>.spec.ts` | `specs/generated/flows/<name>/<name>.spec.ts` | `sungen generate` |
-| 5 | Test results | `specs/generated/<name>/<name>-test-result.json` or `test-results/results.json` | `specs/generated/flows/<name>/<name>-test-result.json` or global fallback | `run-test` |
-
-**Sources 1-4 are blocking** — CLI aborts if any is missing.
-**Source 5 is optional** — CSV is still generated but Test Result/Date/Executor/Env columns are empty (all tests show as Pending).
-
-The CLI reads the **per-target result file first** (co-located with `.spec.ts`), then falls back to the global `test-results/results.json`. Per-target is preferred because the global file gets OVERWRITTEN each time Playwright runs, losing results from earlier targets.
-
----
-
-## Column mapping (handled by CLI)
-
-| CSV Column | Source |
-|------------|--------|
-| TC ID | Generated, namespaced per screen/flow: `<SCREEN_UPPER>-<CAT>-<NNN>` (e.g. `VP-SEC-001` on screen `login` → `LOGIN-SEC-001`). The namespace makes it globally unique — the stable key the dashboard tracks each test case by. |
-| Category 1 | Scenario name with VP prefix stripped |
-| Category 2 | VP group: `VP-SEC`→Accessing, `VP-UI`→GUI, `VP-VAL`/`VP-LOGIC`→Function |
-| Category 3 | Feature name (first line of `.feature`) |
-| Category 4 | Screen name |
-| Pre-condition | Auth tag → "Logged in as X" / "Not authenticated" + Given steps (natural language) |
-| Test Data | `{{vars}}` from scenario resolved via test-data.yaml → `key: value; key2: value2` |
-| Steps | `.spec.ts` code comments for interactions (numbered) |
-| Expected results | `.spec.ts` `expect(...)` comments (numbered) |
-| Priority | Tag: `@high`/`@normal`/`@low` (default: Normal) |
-| Testcase type | `@manual` → Manual, else Auto. Not compiled → "Not compiled" |
-| Test Result | results.json status: passed→Passed, failed/timedOut→Failed, skipped→N/A, else Pending |
-| Executed Date | results.json startTime formatted as `dd/mm/yyyy` |
-| Test Executor | `git config user.name` |
-| Test Environment | `playwright.config.ts` baseURL + project name |
-| Note | Error message + trace path (for failed tests) |
-
----
-
-## XLSX sheets — Auto / Manual split
-
-The `.xlsx` is split into two sheets so QA manages the sets separately:
-- **`Auto`** — automatable test cases (`Auto` + `Not compiled`).
-- **`Manual`** — `@manual` test cases (always present, header-only when there are none).
-
-Multi-locale (no `SUNGEN_ENV`): one **`<LOCALE> Auto`** sheet per locale + a single shared **`Manual`** sheet (manual TCs are locale-invariant). The **CSV stays one file with every row** — the `Testcase type` column distinguishes Auto vs Manual.
-
----
-
-## API delivery — extra worksheet
-
-For **api-kind units** (`qa/api/<area>/`), the `.xlsx` gains a third worksheet **`API detail`** (appended after Auto/Manual). The main BM-2-901-13 Testcases layout is unchanged. The CSV is unchanged (16-column, no extra sheet).
-
-### Required sources (API detail sheet only)
-
-| Source | Path | Created by |
-|--------|------|------------|
-| Endpoint catalog | `qa/api/<area>/api/apis.yaml` | `sungen add --api` or `sungen api import` |
-| Scenario annotations | `qa/api/<area>/features/<feature>.feature` | `create-test` |
-
-### API detail column mapping
-
-| Column | Source |
-|--------|--------|
-| Endpoint | `path` from `apis.yaml` catalog entry |
-| Method | `method` from catalog entry (uppercased) |
-| Auth / Datasource | catalog `datasource` + any `@auth:<role>` tag from scenarios calling this endpoint |
-| Request shape | catalog `body` + `params` fields composed as `body: {…}; params: [a, b]` |
-| Expected-status matrix | `@cases:<dataset>` label for data-driven scenarios; catalog `expect.status` as fallback |
-| Flow steps | Ordered `@api:<name>` call chain from multi-call scenarios (e.g. `register → count_users`) |
-| Concurrency invariant | `@concurrent:<N>` + `@query:<oracle>` from concurrent scenarios (e.g. `ok_count=2; @query user_count`) |
-
-**Sources are catalog + annotations only** — Field Metadata (FM) is not required for this sheet.
-
----
-
-## Excluded from CSV
-
-- `@steps:<name>` **base** scenarios — these are setup-only, inlined into `@extend:...` scenarios at compile time
-- Default scaffold `Sample scenario for <screen>` — not a real test
-
----
-
-## CLI command reference
-
-```bash
-# Export all screens and flows
-sungen delivery
-
-# Export specific targets (auto-detects screen vs flow)
-sungen delivery kudos awards nomination-flow
-
-# Skip pre-flight (CI only)
-sungen delivery --skip-preflight
-
-# Skip targets with blocking misses
-sungen delivery --continue-on-missing
-```
-
-Output: `qa/deliverables/<name>-testcases.csv` (UTF-8 with BOM)