qfai 1.7.13 → 1.7.15

package/assets/init/.qfai/contracts/ui/README.md

@@ -3,9 +3,9 @@
 ## Purpose
 
 Define UI surface contracts for prototyping and E2E selection.
-The contract must describe both screen structure and minimum mockable behavior.
+The contract must describe screen structure, action coverage targets, and inspection anchors for full-harness evidence.
 
-> **Note:** UI contracts are **supporting input** that supplements the discussion sidecar artifacts (`discussion-*/uiux/*`), which remain the primary truth for UI/UX definitions. Screen contract YAML files are read **only when present**; after `qfai init`, this directory may contain only this README — that is the normal initial state.
+> **Note:** UI contracts are supporting input that supplements the discussion sidecar artifacts (`discussion-*/uiux/*`), which remain the primary truth for UI/UX definitions. In `packages/qfai` v1.7.15, prototyping execution is `full-harness` only; therefore, running the prototype harness requires both canonical screen contracts and matching `CON-UI-*` YAML contracts.
 
 ## File rules
 
@@ -35,34 +35,33 @@ The contract must describe both screen structure and minimum mockable behavior.
 
 ### `data-qfai` marker convention
 
-- Recommended marker value: `CONTRACT_ID:ELEMENT_ID` (example: `data-qfai="CON-UI-0001:search_input"`).
+- Canonical marker value: `CONTRACT_ID:ELEMENT_ID` (example: `data-qfai="CON-UI-0001:search_input"`).
 - Use `elements[].id` (stable ID) for the marker suffix, not `elements[].label`.
 - Even when label text is not visible in the UI, markers ensure fidelity coverage.
 - autogen generates expected markers from `elements[].id` automatically.
-- Legacy format (`CONTRACT_ID:ELEMENT_LABEL`) is accepted for backward compatibility but new implementations should use the id-based format.
+- The id-based format (`CONTRACT_ID:ELEMENT_ID`) is the canonical format for new and updated contracts.
+- Legacy label-based markers may still exist in older contracts or downstream tooling; when updating those flows, migrate them to the id-based format and verify any selector/evidence wiring that still depends on label-based markers.
 
-## Mockable prototype minimum (L2)
+## Prototype metadata
 
 Add `prototype` at the top level.
 
-- `mode`: `skeleton | interactive` (`interactive` is the recommended default)
-- `mockPaths`: minimum happy-path checks to validate mock behavior
+- `mode`: `interactive`
+- `mockPaths`: negative-only review ledger derived from real browser QA findings
 - `markers`: selector/marker convention for runtime inspection and future automation
 
-### `prototype.mode` and `mockPaths[]` examples
+### `prototype.mode` and `mockPaths[]` example
+
+The `mockPaths[]` entry is a **negative-only review ledger** — only populate it when a Browser QA finding or review outcome has identified a failure/gap in the mockable path. Do **not** populate it with expected success flows; those belong in `screens[].actions[]` (contracts) and the discussion sidecar.
 
 ```yaml
 prototype:
   mode: interactive
   mockPaths:
-    - id: mp_create_to_list
-      flow: create -> list reflects
-```
-
-```yaml
-prototype:
-  mode: skeleton
-  mockPaths: []
+    - id: mp_create_to_list_mobile_reflow
+      finding_ref: "BQ-2026-04-18-014"
+      failure_condition: "Mobile viewport: created row not reflected in list within 2s (browser QA: stale cache)."
+      status: open
 ```
 
 ## Screen contract rules
@@ -82,7 +81,7 @@ prototype:
 ### L2 `actions[]` minimum set
 
 - For each interactive primary route, define at least one action that changes UI state (`navigate`, `submit`, `toggle`, ...).
-- Tie at least one action to a `prototype.mockPaths[]` flow so reviewers can trace mockable behavior.
+- Tie at least one action to observed browser QA findings so reviewers can trace action coverage.
 - Keep `effect` concrete and testable (`navigates to /orders`, `shows success toast`, ...).
 
 ## Template (YAML)
@@ -91,9 +90,10 @@ prototype:
 # QFAI-CONTRACT-ID: CON-UI-0001
 prototype:
   mode: interactive
-  mockPaths:
-    - id: mp_create_to_list
-      flow: create -> list reflects
+  # mockPaths is a negative-only ledger: leave it empty when there are no
+  # open Browser QA findings against this contract's mockable paths. Only
+  # add entries that cite a finding or review outcome.
+  mockPaths: []
   markers:
     - id: mk_order_form
       selector: "[data-qfai='order-form']"
@@ -148,11 +148,9 @@ screens:
 
 ### Q3. "Can I treat this as a static screen?"
 
-- Use static/skeleton handling only when the screen has no meaningful interactive behavior yet.
-- Configuration options:
-  - Temporary L1: `uiFidelity.mode: skeleton` with `screens: []`
-  - L2 target: keep `mode: interactive`, but define actionable routes with minimum `actions[]` and `mockPaths[]`
-- Move back to `interactive` before ATDD to avoid hidden behavior drift.
+- No. `packages/qfai` v1.7.15 prototyping is `full-harness` only.
+- `uiFidelity.mode: skeleton` is not a valid prototyping execution target.
+- Define actionable routes and `actions[]`, then collect real render and Browser QA evidence.
 
 ## Checklist
 
@@ -160,4 +158,4 @@ screens:
 - [ ] `elements[].id` follows stable naming policy and change policy is respected.
 - [ ] `elements[].label` matches runtime-visible inspection text or documented marker mapping.
 - [ ] `elements` and `actions` include the minimum fields above.
-- [ ] `prototype.mode/mockPaths/markers` are defined for L2 mockable flow.
+- [ ] `prototype.mode` is `interactive` and `mockPaths` is treated as a negative-only issue ledger.

package/assets/init/.qfai/discussion/README.md

@@ -2,7 +2,7 @@
 
 ## Purpose
 
-`discussion/` stores the unified discussion pack that merges interview outputs (discuss) and requirement intake (require). Discussion packs use 15 required markdown files plus required prototyping.yaml.
+`discussion/` stores the unified discussion pack that merges interview outputs (discuss) and requirement intake (require). Discussion packs use 15 required markdown files. When the latest pack is `ui_bearing: true`, it must also include `prototyping.yaml`; when `ui_bearing: false`, `prototyping.yaml` is not required.
 
 This directory does not directly update `specs/`; it prepares decisions, requirements, open questions, and rationale as inputs for `/qfai-sdd`.
 
@@ -29,7 +29,7 @@ discussion/
     ├── 13_Deferred.md
     ├── 14_Review-Request.md
     ├── 99_delta.md
-    └── prototyping.yaml
+    └── prototyping.yaml  # required only when ui_bearing: true
 ```
 
 ## File responsibilities
@@ -37,7 +37,7 @@ discussion/
 - `01_Context.md` – Background, purpose, stakeholders, assumptions, and issues.
 - `02_Inception-Deck.md` – Inception Deck (10 questions) for ambiguity removal and alignment.
 - `03_Story-Workshop.md` – Story workshop with user stories, user flows, and Mermaid diagrams.
-- `04_Sources.md` – Input sources (primary info, evidence, links) with `SRC-XXXX` IDs.
+- `04_Sources.md` – Source registry, trend scan, competitive reference registry, and traceability. This is the canonical location for trend translation, competitive analysis, and source-to-requirement traceability (`SRC-XXXX` IDs).
 - `05_Scope.md` – Scope, out-of-scope, constraints, and success criteria.
 - `06_REQ.md` – Functional requirements list (`REQ-0001` format).
 - `07_NFR.md` – Non-functional requirements list (`NFR-0001` format).
@@ -50,6 +50,19 @@ discussion/
 - `14_Review-Request.md` – Review request for review artifact generation.
 - `99_delta.md` – Change history (adopted, rejected, drift, recurrence prevention).
 
+## UI/UX canonical family
+
+For UI-bearing packs, the canonical design-evaluation source-of-truth is:
+
+- `04_Sources.md` for trend translation and competitive reference registry
+- `uiux/20_design_eval_invariant.md`
+- `uiux/21_design_eval_trend_derived.md`
+- `uiux/22_design_eval_product_specific.md`
+- `uiux/23_design_eval_aggregate.md`
+- `uiux/40_screen_contracts.md`
+
+`05_Scope.md` is not a trend source-of-truth for L2 scoring, and fallback scans such as `uiux/*trend*` or `uiux/*competitive*` must not replace these canonical files.
+
 ## OQ Register rules
 
 `11_OQ-Register.md` must include these mandatory columns:
@@ -103,48 +116,38 @@ discussion/
 - Use timestamp directory naming for new outputs: `discussion-YYYYMMDDhhmmssSSS`.
 - `14_Review-Request.md` must reference routing SSOT: `.qfai/assistant/steering/agent-routing.yml` and `.qfai/assistant/steering/review-profiles.yml`.
 
-## prototyping.yaml (Required Recommendation Artifact)
+## prototyping.yaml (Classification-aware Recommendation Artifact)
 
-Each discussion pack **must** include a `prototyping.yaml` file that recommends the prototyping mode for the project. This is a required side artifact of the 15-file discussion pack plus required prototyping.yaml completion contract.
+Each UI-bearing discussion pack (`ui_bearing: true`) **must** include a `prototyping.yaml` file that recommends the prototyping mode for the project. Non-UI discussion packs (`ui_bearing: false`) do not require `prototyping.yaml`.
 
-### Canonical namespaced schema (recommended)
+### Canonical namespaced schema (required)
 
 ```yaml
 prototyping:
-  recommended_mode: standard
-  rationale: UI validation is recommended but full-harness is not justified by default.
+  recommended_mode: full-harness
+  rationale: UI validation requires the full-harness runtime loop in packages/qfai.
   allowed_modes:
-    - low-cost
-    - standard
     - full-harness
-  surface: web-ui
-```
-
-### Legacy top-level schema (deprecated — read-only backward compatibility)
-
-The following top-level form is accepted by the parser for backward compatibility but produces a deprecation warning (`QFAI-PROT-231`). New artifacts MUST NOT emit this form; use the namespaced canonical schema above.
-
-```yaml
-recommended_mode: standard
-rationale: ...
-allowed_modes:
-  - low-cost
-  - standard
-surface: web-ui
+  surface: web
 ```
 
-If both forms are present in the same file, the namespaced form takes precedence and a conflict warning (`QFAI-PROT-232`) is emitted.
-
 ### Field reference
 
 All 4 fields are **required**. An artifact missing any field will fail validation.
 
-| Field              | Required | Description                                                  |
-| ------------------ | -------- | ------------------------------------------------------------ |
-| `recommended_mode` | yes      | `low-cost`, `standard`, or `full-harness`                    |
-| `rationale`        | yes      | Non-empty string explaining the recommendation               |
-| `allowed_modes`    | yes      | Unique array of valid modes; must include `recommended_mode` |
-| `surface`          | yes      | `web-ui`, `mobile-ui`, `desktop-ui`, `mixed`, or `non-ui`    |
+| Field              | Required | Description                                    |
+| ------------------ | -------- | ---------------------------------------------- |
+| `recommended_mode` | yes      | `full-harness`                                 |
+| `rationale`        | yes      | Non-empty string explaining the recommendation |
+| `allowed_modes`    | yes      | Unique array; must contain only `full-harness` |
+| `surface`          | yes      | `web`, `mobile`, `desktop`, or `mixed`         |
+
+### Validation rules
+
+- Only the canonical namespaced schema under the `prototyping:` key is accepted. Top-level recommendation keys (`recommended_mode`, `rationale`, `allowed_modes`, `surface` at root level) are not supported and will cause validation failure.
+- Coexistence of top-level recommendation keys with the namespaced `prototyping:` block is invalid.
+- `recommended_mode` must be included in `allowed_modes`. In packages/qfai, this means `recommended_mode` must be `full-harness` and `allowed_modes` must only contain `full-harness`.
+- An artifact that does not conform to the canonical namespaced schema is invalid and will be rejected by both validation and execution/CLI. No fallback to explicit mode or default mode is performed for invalid artifacts.
 
 ## Suggested naming
 

package/assets/init/.qfai/evidence/README.md

@@ -2,194 +2,78 @@
 
 ## Purpose
 
-Evidence files record what was actually executed, observed, skipped, or deferred.
+Evidence files record what was actually executed and observed.
+`packages/qfai` v1.7.15 treats prototyping as `full-harness` only and UI-only.
 
-## Prototyping stage required artifacts
+## Prototyping artifacts
 
-`/qfai-prototyping` uses these canonical files:
+Canonical files:
 
 - `.qfai/evidence/prototyping.md`
 - `.qfai/evidence/prototyping.json`
-- `.qfai/evidence/render.json` (when render evidence is emitted)
-- `.qfai/evidence/browser-qa.json` (when browser QA is emitted)
+- `.qfai/evidence/render.json`
+- `.qfai/evidence/browser-qa.json`
+- `.qfai/evidence/fullHarness.exit.json`
+- `.qfai/evidence/fullHarness.handoff.json`
+- `.qfai/evidence/fullHarness.fakeUiDetection.json`
 
-## prototyping.json minimum schema
+## Execution contract
 
-Always required:
-
-- `specs[]`
-- `meta.generatedAt`
-- `meta.toolVersion`
-- `meta.commands[]`
-- `mode.effective`
-- `mode.source`
-- `mode.rationale`
-
-Optional:
-
-- `surface`
-- `mode.requested`
-- `mode.discussionRecommendation`
-- `runtimeGate`
-- `uiFidelity`
-- `renderEvidence`
-- `browserQa`
-- `fullHarness`
+Supported prototyping surfaces are `web`, `mobile`, `desktop`, and `mixed`.
+`cli`, API-only, backend-only, and `ui_bearing: false` classifications are not prototyping execution targets.
 
 ## Obligation matrix
 
-| surface / mode            | specs    | runtimeGate | uiFidelity                    | render evidence | browser QA | fullHarness |
-| ------------------------- | -------- | ----------- | ----------------------------- | --------------- | ---------- | ----------- |
-| non-ui / low-cost         | required | optional    | n/a                           | n/a             | n/a        | absent      |
-| non-ui / standard         | required | optional    | n/a                           | n/a             | n/a        | absent      |
-| non-ui / full-harness     | required | optional    | n/a                           | n/a             | n/a        | required    |
-| ui-bearing / low-cost     | required | optional    | optional (`skeleton` allowed) | optional        | optional   | absent      |
-| ui-bearing / standard     | required | optional    | required                      | optional        | optional   | absent      |
-| ui-bearing / full-harness | required | required    | required                      | required        | required   | required    |
-
-Interpretation:
-
-- `required`: schema and completeness are enforced
-- `optional`: if present, schema must be valid
-- `n/a`: absent is normal success
-
-## non-ui canonical semantics
-
-For `surface: non-ui`, the following are normal success when absent:
-
-- `uiFidelity`
-- render evidence bundle
-- browser QA bundle
-- `runtimeGate.ui`
-
-Contradictory UI-only payloads on `non-ui` are validation errors.
-
-## uiFidelity notes
-
-- `uiFidelity` is the canonical UI evidence block.
-- `mode: interactive` is the default when a working UI flow is exercised.
-- `mode: skeleton` is allowed for low-cost UI proof where structure exists but wiring is intentionally partial.
-- Keep `"version": "0.1"` in the `uiFidelity` payload until the schema version changes.
-
-## fullHarness minimum completeness
-
-When `mode.effective = "full-harness"`:
-
-- `fullHarness.enabled = true`
-- `fullHarness.available`
-- `fullHarness.runId`
-- `fullHarness.iterationCount >= 1`
-- `fullHarness.bestIteration >= 1`
-- `fullHarness.terminationReason`
-- `fullHarness.reviewerSignoff`
-- `fullHarness.scoringTrace.length >= 1`
-
-## Render evidence bundle conventions
-
-Canonical path: `.qfai/evidence/render.json`
-
-```json
-{
-  "renderEvidence": {
-    "status": "captured",
-    "requested": true,
-    "viewports": ["desktop", "mobile"],
-    "outputPath": ".qfai/evidence/render.json"
-  },
-  "screens": [
-    {
-      "route": "/orders",
-      "viewport": "desktop",
-      "status": "captured",
-      "width": 1440,
-      "height": 900,
-      "imagePath": ".qfai/evidence/render/orders.desktop.png",
-      "htmlPath": ".qfai/evidence/render/orders.desktop.html"
-    },
-    {
-      "route": "/orders",
-      "viewport": "mobile",
-      "status": "skipped",
-      "skippedReason": "path-only review for non-blocking mobile check"
-    }
-  ]
-}
-```
-
-Rules:
-
-- `status`: `captured | skipped | failed`
-- `captured`: `imagePath` and `htmlPath` required (QFAI-PROT-252)
-- `skipped`: `skippedReason` required (QFAI-PROT-252)
-- `failed`: `error` required (QFAI-PROT-252)
-- external bundle is the source of truth
-- in-band `uiFidelity.screens[].renders[]` is summary/projection only
-- render evidence must remain `path-only`; `data:` URIs, `base64,` payloads, and inline HTML are invalid (QFAI-PROT-251)
-- extremely long single-line payloads (>500 chars) are treated as inline payload violations
-- top-level `renderEvidence.status` and individual `screens[].status` must not contradict (QFAI-PROT-253)
-
-## browser-qa.json canonical contract
-
-```json
-{
-  "browserQa": {
-    "executed": true,
-    "status": "completed",
-    "mode": "full-harness",
-    "summary": {
-      "smoke": { "passed": 3, "failed": 0 },
-      "interaction": { "passed": 4, "failed": 1 }
-    }
-  },
-  "findings": [
-    {
-      "category": "interaction",
-      "severity": "error",
-      "route": "/orders",
-      "message": "Save button submits duplicate request"
-    }
-  ]
-}
-```
-
-Rules:
-
-- required only for `ui-bearing / full-harness` (QFAI-PROT-263)
-- optional for `ui-bearing / low-cost|standard`
-- n/a for `non-ui`
-- `executed=true` requires `status=completed`; `executed=false` permits `status=skipped|failed` only
-- `status=completed` without `summary` or `findings` produces a warning (QFAI-PROT-262)
-- `browserQa.mode` must match `prototyping.json.mode.effective` (QFAI-PROT-261)
-- `summary.*.passed/failed` must be non-negative integers
-- each finding requires `category`, `severity`, and `message`
-
-## Example prototyping.json
-
-```json
-{
-  "surface": "web-ui",
-  "specs": [
-    {
-      "specId": "spec-0001",
-      "declared": { "uiRoutes": 1, "apiEndpoints": 1, "dbObjects": 1 },
-      "checked": { "uiOk": 1, "apiNon404": 1, "dbPresent": 1 },
-      "missing": { "uiRoutes": [], "apiEndpoints": [], "dbObjects": [] }
-    }
-  ],
-  "mode": {
-    "effective": "standard",
-    "source": "default",
-    "rationale": "No explicit request or discussion recommendation was provided."
-  },
-  "meta": {
-    "generatedAt": "2026-04-04T00:00:00.000Z",
-    "toolVersion": "<current-tool-version>",
-    "commands": ["qfai validate --fail-on error"]
-  },
-  "uiFidelity": {
-    "version": "0.1",
-    "mode": "interactive",
-    "screens": []
-  }
-}
-```
+| surface / mode         | specs    | runtimeGate | uiFidelity | render evidence | browser QA | fullHarness |
+| ---------------------- | -------- | ----------- | ---------- | --------------- | ---------- | ----------- |
+| web / full-harness     | required | required    | required   | required        | required   | required    |
+| mobile / full-harness  | required | required    | required   | required        | required   | required    |
+| desktop / full-harness | required | required    | required   | required        | required   | required    |
+| mixed / full-harness   | required | required    | required   | required        | required   | required    |
+
+`low-cost` and `standard` are unsupported in `packages/qfai` v1.7.15.
+
+## Truthfulness rules
+
+- `mode.effective` must be `full-harness`.
+- `uiFidelity.mode` must be `interactive`.
+- Canonical screen contracts in `discussion-*/uiux/40_screen_contracts.md` are mandatory.
+- Browser QA is mandatory per screen.
+- Calibration is resolved from `fullHarness.calibrationRef.packPath`; scalar caller overrides are invalid.
+- `runtimeGate.evidenceRefs` must contain concrete render/browser QA/spec refs only.
+- `specCoverage` refs must use concrete declared refs plus concrete observed refs. Self-reference and synthetic strings are invalid.
+- `mockPaths` is a negative-only ledger. Allowed values are `fail|finding` only.
+
+## fullHarness semantics
+
+Required fields:
+
+- `enabled = true`
+- `runId`
+- `calibrationRef.configPath`
+- `calibrationRef.packPath`
+- `calibrationRef.packVersion`
+- `iterationCount`
+- `bestIteration`
+- `status`
+- `reviewerSignoff`
+- `reviewerLogs`
+- `iterations`
+- `scoringTrace`
+- `limitations`
+
+Review semantics:
+
+- `finalDecision = accepted` -> `reviewerSignoff.status = approved`
+- `finalDecision = rejected` -> `reviewerSignoff.status = rejected`
+- `finalDecision = abandoned` -> `reviewerSignoff.status = abandoned`
+- `reviewerLogs[last].verdict` must align with the final decision and termination semantics.
+
+## Prohibited patterns
+
+- `low-cost` or `standard` prototyping metadata
+- `cli` prototyping execution
+- self-reference such as `prototyping.json#/runtimeGate`
+- synthetic refs such as `specs: ...`
+- synthetic `mockPaths.status="pass"`
+- hardcoded calibration pack version

package/assets/init/.qfai/evidence/calibration.yaml

@@ -0,0 +1,26 @@
+# QFAI default calibration pack.
+#
+# The full-harness loader (`packages/qfai/src/core/calibration/loader.ts`)
+# requires a calibration pack at the path declared in
+# `qfai.config.yaml > prototyping.calibration.packPath`. This file ships as
+# the zero-configuration default so `qfai init` projects can run full-harness
+# without a manual setup step. Edit the values below to tune iteration limits
+# and score thresholds for your team's review cadence.
+
+version: "1.0.0-default"
+
+thresholds:
+  accept: 0.8
+  refine: 0.5
+
+maxIterations: 5
+plateauDelta: 0.02
+plateauLookback: 3
+
+examples:
+  - input: "Example UI surface with clear primary call-to-action and WCAG AA contrast."
+    expectedScore: 0.9
+    rationale: "High-quality example: explicit primary action, accessible contrast, no layout clutter."
+  - input: "Placeholder layout with lorem-ipsum copy and no primary action."
+    expectedScore: 0.3
+    rationale: "Low-quality example: placeholder content and absent decision path."

package/assets/init/.qfai/review/README.md

@@ -19,7 +19,6 @@ Routing SSOT:
 
 ```text
 .qfai/review/
-├── README.md
 └── review-YYYYMMDDhhmmssSSS/
     ├── review_request.md
     ├── R01_<reviewer>.md
@@ -27,15 +26,59 @@ Routing SSOT:
     └── summary.json
 ```
 
-## summary.json (minimum schema)
+Git ignore management: `review-*/` packs are ignored via the QFAI managed
+block in the **repo-root `.gitignore`** (added/updated by `qfai init`).
+`.qfai/review/` itself does **not** contain a nested `.gitignore`; the
+single managed block in the repo root is the SSOT.
+
+## summary.json (minimum schema; prefer v2.0 for new packs)
+
+> **Accepted schema versions:** the active validator
+> (`packages/qfai/src/core/validators/reviewArtifacts.ts`) accepts
+> `version: "1.0"` and `version: "2.0"` as `ALLOWED_VERSIONS`. Both
+> versions share the top-level envelope (`version`, `created_at`,
+> `target: { kind, path }`, `overall_status`) but carry reviewer entries
+> under different keys:
+>
+> - **v1.0** uses a `roster` array of reviewer entries.
+> - **v2.0** uses a `reviewers` array plus required `routing_profile`
+>   (string) and optional `conditional_reviewers` array. v2.0 is the
+>   canonical choice for new packs.
+>
+> Reviewer entry fields validated in both versions:
+> `{ reviewer: string, status: "PASS" | "FAIL" | "NA", feedback_count?: integer }`.
+> No future-only keys are required. If `summary.json` drifts from this
+> schema, `QFAI-REVIEW-007` fires with the failing field list.
+>
+> **Verdict vocabulary:** `summary.json` uses `PASS|FAIL` historically (the
+> validator above enforces that set). The in-flight reviewer response
+> template in `shared-skill-delegation-baseline.md` uses
+> `Result: PASS | REVISE` — this is the same concept viewed from two
+> angles (reviewer-side verdict vs. serialised summary). A reviewer
+> `REVISE` maps to `status: "FAIL"` in summary.json until the validator
+> schema is broadened in a future release.
+
+### v1.0 example
+
+```json
+{
+  "version": "1.0",
+  "created_at": "2026-02-18T12:34:56+09:00",
+  "target": { "kind": "spec|discussion", "path": "..." },
+  "roster": [{ "reviewer": "name-or-id", "status": "PASS|FAIL|NA", "feedback_count": 0 }],
+  "overall_status": "PASS|FAIL"
+}
+```
+
+### v2.0 example (preferred)
 
 ```json
 {
   "version": "2.0",
   "created_at": "2026-02-18T12:34:56+09:00",
-  "target": { "kind": "spec|require|discussion", "path": "..." },
+  "target": { "kind": "spec|discussion", "path": "..." },
   "routing_profile": "default",
-  "reviewers": [{ "reviewer": "name-or-id", "status": "PASS|FAIL", "feedback_count": 0 }],
+  "reviewers": [{ "reviewer": "name-or-id", "status": "PASS|FAIL|NA", "feedback_count": 0 }],
   "conditional_reviewers": [],
   "overall_status": "PASS|FAIL"
 }
@@ -44,7 +87,9 @@ Routing SSOT:
 Rules:
 
 - Execute only the reviewers routed for the current skill/phase.
-- If any reviewer returns `FAIL`, return/fix and rerun only failed reviewers and reviewers **affected by the changed scope**.
+- If any reviewer returns `FAIL` (equivalent to `REVISE` in the in-flight
+  reviewer response template; see the vocabulary note above), return/fix
+  and rerun only failed reviewers and reviewers **affected by the changed scope**.
   - "changed scope" is defined as the set of file paths affected by the latest fix and the scope tags (component, domain, layer, etc.) associated with those files.
   - An "affected reviewer" is any reviewer matching either of the following:
     - Its assigned scope (path prefix or scope tag) in `.qfai/assistant/steering/agent-routing.yml` or `review-profiles.yml` intersects the changed scope.
@@ -54,11 +99,11 @@ Rules:
     2. Resolve the corresponding scope tags, components, and domains via `agent-routing.yml` / `review-profiles.yml` to enumerate the changed scope.
     3. For each reviewer, check whether its assigned scope intersects the changed scope or whether its routing definition was modified; mark matching reviewers as "affected".
     4. Rerun only "previously FAIL reviewers" + "affected reviewers"; carry forward previous results for all others.
-- Validation evidence for each review pack must archive the latest
-  `.qfai/report/validate.log` and ATDD traceability report
-  (`.qfai/report/atdd-traceability/summary.{json,md}`) by copying them from
-  `.qfai/report` into the corresponding `review-*/evidence/` directory
-  (since `.qfai/report` may be git-ignored).
+- Both `.qfai/report` and `.qfai/review/review-*/` are git-ignored by default
+  (managed by `qfai init`). Review packs are therefore local-only unless a
+  project opts in by adding explicit negation rules to its `.gitignore` (e.g.
+  `!.qfai/review/review-<timestamp>/`) or by archiving packs to an external
+  store before cleanup.
 - Reviewers must confirm no unresolved ATDD hard gates (`QFAI-ATDD-101/102/103/111/112/113/121/122`).
 
 ## Prototyping review quick checklist
@@ -73,5 +118,5 @@ Diagnosis flow:
 
 1. Read validator `code/rule/refs` and capture `contract_id` + `route`.
 2. Check required `elements[].label` and `actions[]` in the contract.
-3. Verify `uiFidelity.screens[]` coverage and `mockPaths.status=pass`.
+3. Verify `uiFidelity.screens[]` coverage and that `mockPaths` contains only negative findings (`fail|finding`).
 4. Confirm UI renders labels or has stable `data-qfai` markers before resolving the review thread.

package/assets/init/.qfai/specs/README.md

@@ -72,9 +72,9 @@ Each `spec-XXXX/` must satisfy:
 
 Each `spec-XXXX/tdd/test-list.md` is the execution ledger for the TDD micro-cycle.
 
-- **8 required columns**: TDD-ID, TC-Refs, Layer, Test file, Selector, Status, DR-ID, Evidence
+- **8 required columns** (in `tdd/test-list.md`): TDD-ID, TC-Refs, Layer, Test file, Selector, Status, DR-ID, Evidence
 - **Coverage** is measured as unit/component TC references from `06_Test-Cases.md` appearing in TC-Refs
-- **Level column fallback**: when `06_Test-Cases.md` has no `Level` column, all TCs are treated as coverage targets (equivalent to all being unit/component)
+- **Test-case classification fallback** (for `06_Test-Cases.md`, which uses its own classification column — typically named `Level`): when that file has no test-case classification column, every TC is treated as a coverage target (equivalent to all being unit/component). This fallback does **not** apply to the `tdd/test-list.md` `Layer` column, which remains required.
 - **Status=exception** rows must have a non-empty DR-ID (Decision Record reference)
 - **Status in {green, refactor, done}** rows must have an existing Test file (resolved relative to project root)
 - **TDD-ID** must match `TDD-NNNN` format and be unique within the spec (case-insensitive)

package/assets/init/root/qfai.config.yaml

@@ -21,9 +21,14 @@ validation:
     testFileGlobs:
       - tests/**/*.test.ts
       - tests/**/*.spec.ts
+      - packages/*/tests/**/*.test.ts
+      - packages/*/tests/**/*.spec.ts
       - src/**/*.test.ts
       - src/**/*.spec.ts
+      - packages/*/src/**/*.test.ts
+      - packages/*/src/**/*.spec.ts
       - features/**/*.feature
+      - packages/*/features/**/*.feature
     testFileExcludeGlobs: []
     scNoTestSeverity: error
     orphanContractsPolicy: error
@@ -33,12 +38,6 @@ output:
 prototyping:
   calibration:
     packPath: .qfai/evidence/calibration.yaml
-    thresholds:
-      accept: 0.8
-      refine: 0.5
-    maxIterations: 15
-    plateauDelta: 0.02
-    plateauLookback: 3
   execution:
     targetUrl: null
     browserProvider: playwright