qfai 1.7.9 → 1.7.13

package/assets/init/.qfai/assistant/skills/qfai-discussion/references/rcp_footer.md

@@ -1,7 +1,6 @@
 # RCP Footer (qfai-discussion / SSOT)
 
-この文書は `/qfai-discussion` のレビュー周回（Review Cycle）を「discussion-pack 前提」で固定するための SSOT です。
-他skill向けの共通規約ではありません。
+この文書は `/qfai-discussion` の Review Cycle を discussion-pack 前提で固定する SSOT です。
 
 ---
 
@@ -9,32 +8,21 @@
 
 - Scope: `discussion`
 - Pack: `.qfai/discussion/discussion-<YYYYMMDDhhmmssSSS>/`
-- レビュー対象（必須15ファイル）:
-  - `01_Context.md`
-  - `02_Inception-Deck.md`
-  - `03_Story-Workshop.md`
-  - `04_Sources.md`
-  - `05_Scope.md`
-  - `06_REQ.md`
-  - `07_NFR.md`
-  - `08_Glossary.md`
-  - `09_Constraints.md`
-  - `10_Policy.md`
-  - `11_OQ-Register.md`
-  - `12_OQ-Resolution-Log.md`
-  - `13_Deferred.md`
-  - `14_Review-Request.md`
-  - `99_delta.md`
+- レビュー対象は discussion-pack の必須15ファイル
 
 ---
 
-## Roster Execution Rule（固定）
+## Routing Rule（固定）
 
-- Roster は `.qfai/assistant/steering/review-roster.yml` を読む
-- 各レビューは `PASS` / `FAIL` / `N/A` を返す
-- `N/A` は `na_rule` を満たす理由が必須
-- `FAIL` が1つでも出たら **即修正へ戻る**（後続レビューは回さない）
-- 修正後は **review cycle を新規作成し** roster を先頭から再実行する（スキップ禁止）
+- reviewer の選定は `.qfai/assistant/steering/agent-routing.yml` と `.qfai/assistant/steering/review-profiles.yml` を読む
+- 常設 reviewer:
+  - `completion-reviewer`
+  - `requirements-reviewer`
+- 条件付き reviewer:
+  - `architecture-reviewer` — architecture-affecting decision がある場合
+  - `product-surface-reviewer` — UI-bearing の場合
+- 各レビューは `PASS` / `FAIL` を返す
+- `FAIL` が出たら、失敗 reviewer と修正影響を受ける reviewer のみ再実行する
 
 ---
 
@@ -47,71 +35,15 @@
 
 ## discussion-pack 固有の Gate（必須）
 
-以下は validator が **error** として扱うため、`fixed` 判定前に必ず潰す：
-
-1. 命名（最新pack判定）
-
-- pack は `discussion-YYYYMMDDhhmmssSSS/` のみ許可
-- 不正な `discussion-*` がある場合は latest 判定が壊れるため、退避または削除する
-
-2. Blocking OQ の解消
-
-- `11_OQ-Register.md` の **Disposition が `open` のまま**で、
-  かつ Gate が `discuss|require|sdd` の OQ が残っていないこと
-- `open` を残す場合は、**Gateを外す**か `Disposition: deferred/resolved` に変更する
-
-3. Deferred の整合
-
-- OQ register で `deferred` にした OQ-ID は、`13_Deferred.md` に同じ OQ-ID で必ず記載する
-
-4. Story Workshop の Mermaid（最小要件）
-
-- `03_Story-Workshop.md` に mermaid fenced block を最低1つ含める
-  - `flowchart` または `sequenceDiagram` を推奨
+- `11_OQ-Register.md` に `Disposition: open` かつ blocking gate の OQ を残さない
+- `13_Deferred.md` は deferred OQ と整合している
+- `03_Story-Workshop.md` は Mermaid を最低1つ含む
 
 ---
 
 ## レビュー観点（discussion-pack 特化）
 
 - Context → Inception Deck → Story Workshop の因果が通っているか
-  - 「なぜ作るか」→「誰のためか」→「どんな業務フローか」が矛盾しない
 - `06_REQ.md` と `07_NFR.md` の境界が崩れていないか
-- Glossary/Constraints/Policy が単なる箇条書きでなく、意思決定（後工程の設計/実装）の入力として使える粒度か
-- `99_delta.md` が “更新履歴” ではなく “検討ログ（採用/不採用/基準）” を持っているか
-
----
-
-## 代表的な FAIL と復旧（discussion-pack 特化）
-
-- FAIL: `11_OQ-Register.md` に open+Gate が残る
-  - 復旧: 影響範囲が大きいものは `Disposition: deferred` + `13_Deferred.md` に詳細を移す
-- FAIL: `03_Story-Workshop.md` に図がない
-  - 復旧: 1本でよいので、登場人物（ペルソナ）と主要分岐が分かる flowchart を入れる
-- FAIL: pack 名が不正（latest 判定がブレる）
-  - 復旧: 不正 pack を `discussion-legacy-*` に退避し、最新 pack を timestamp 命名で作り直す
-
----
-
-## 拡張レビュアー
-
-### devils-advocate（11番目）
-
-- 役割: 全否定エージェント — 「現状すべてが間違っている」前提でレビューし、あるべき姿を提示する
-- `can_be_na: false` — N/A は許可されない
-- FAIL 判定時は必ず具体的代替案を提示すること。代替案なしの FAIL は無効とし、再判定を要求する
-- 3 回連続 FAIL → アドバイザリー降格（当該レビューサイクル限定）。降格後はブロッキング力が消失し、フィードバックのみ記録する
-- レビュー記録: `R11_devils-advocate.md`
-
-### pattern-doubler（12番目）
-
-- 役割: パターン倍増エージェント — discussion phase では ID 付き項目が少ないため N/A が基本
-- `can_be_na: true` — discussion phase では Example Seeds の数と観点網羅性を評価対象とする
-- N/A でない場合、追加パターンの根拠提示が必須
-- レビュー記録: `R12_pattern-doubler.md`
-
-### 代表的な FAIL と復旧（拡張レビュアー特化）
-
-- FAIL (devils-advocate): 代替案なしの否定のみ
-  - 復旧: 具体的な「あるべき姿」と移行パスを記述させ、再判定する
-- FAIL (devils-advocate, 3回連続): 無限ループ検知
-  - 復旧: アドバイザリー降格を記録し、devils-advocate のフィードバックを advisory として保存。次フェーズに進行する
+- Glossary / Constraints / Policy が後工程入力として十分か
+- `99_delta.md` に採用/不採用の判断根拠が残っているか

package/assets/init/.qfai/assistant/skills/qfai-discussion/templates/01_Context.md

@@ -1,6 +1,14 @@
 # 01 Context
 
-<!-- UX-INTENT: If UI-bearing, see uiux/10_strategy.md for implementation strategy context -->
+<!-- UX-INTENT: If UI-bearing, see uiux/10_implementation_strategy.md for implementation strategy context -->
+
+## UI-bearing Classification
+
+- ui_bearing: [true|false]
+- primary_surface: [web|mobile|desktop|cli|mixed|non-ui]
+- secondary_surfaces:
+  - [optional]
+- classification_rationale: [Why this classification was chosen]
 
 ## Metadata
 

package/assets/init/.qfai/assistant/skills/qfai-discussion/templates/02_Inception-Deck.md

@@ -43,7 +43,7 @@ flowchart LR
     App --> Data["Data Store"]
 ```
 
-<!-- UX-INTENT: If UI-bearing, reference uiux/30_comparison.md for design option alignment -->
+<!-- UX-INTENT: If UI-bearing, reference uiux/30_option_comparison.md and uiux/31_selected_anchor_screen.md for design option alignment -->
 
 ## 7. What Keeps Us Up at Night (Risks)
 

package/assets/init/.qfai/assistant/skills/qfai-discussion/templates/03_Story-Workshop.md

@@ -45,22 +45,22 @@ flowchart TD
 
 ## Behavior Obligations
 
-<!-- Primary focus for UI-bearing packs. Define behavioral requirements before visual mockups. -->
+<!-- Primary focus for UI-bearing packs. Capture behavioral discovery before screen-level contracts.
+     Screen-level contract SSOT lives in uiux/40_screen_contracts.md. -->
 
 ### State Coverage
 
-| State     | Trigger   | Display   | Transitions   |
-| --------- | --------- | --------- | ------------- |
-| empty     | [trigger] | [display] | [transitions] |
-| loading   | [trigger] | [display] | [transitions] |
-| error     | [trigger] | [display] | [transitions] |
-| populated | [trigger] | [display] | [transitions] |
+| State / Risk    | Discovery Notes                                   | Handoff to Contract                                                           |
+| --------------- | ------------------------------------------------- | ----------------------------------------------------------------------------- |
+| [state or risk] | [what might trigger confusion, delay, or failure] | Reflect the final `required_states` contract in `uiux/40_screen_contracts.md` |
 
 ### Interaction Contracts
 
-| Element   | Action   | Expected Result | Error Handling |
-| --------- | -------- | --------------- | -------------- |
-| [element] | [action] | [result]        | [error case]   |
+| Primary Task     | Key Action         | Priority Hint            | Expected Result | Error Handling |
+| ---------------- | ------------------ | ------------------------ | --------------- | -------------- |
+| [main user goal] | [main interaction] | [primary/high/secondary] | [result]        | [error case]   |
+
+Screen-level contract details are finalized in `uiux/40_screen_contracts.md`. Primary tasks, required states, transitions, and observable outcomes are finalized there; Story Workshop is for discovery and handoff, not final contract fixation.
 
 ### Error Handling
 
@@ -68,11 +68,14 @@ flowchart TD
 - Network failure: [approach]
 - Timeout: [approach]
 
-## Screen Mock — Fallback (HTML+CSS)
+---
+
+## Appendix: Screen Mock — Optional Fallback (HTML+CSS)
 
-- Secondary: required when UI requirements exist, but subordinate to Behavior Obligations above.
-- Visual mock only; do not include JavaScript behavior.
-- This HTML/CSS mock is a fallback visual aid that supplements (not replaces) the behavioral definitions.
+<!-- Optional fallback only — do not use as the primary UI definition artifact.
+     Include only when it materially clarifies the selected direction.
+     Behavior Obligations and sidecar artifacts (uiux/) are the primary UI definitions.
+     The required state SSOT is uiux/40_screen_contracts.md (`default/loading/empty/error`). -->
 
 ```html
 <section class="screen-mock">
@@ -91,49 +94,3 @@ flowchart TD
   border-radius: 12px;
 }
 ```
-
-## Design Direction Summary
-
-<!-- Required for UI-bearing packs. Validated by QFAI-DDP-019..025. -->
-
-### Option Comparison
-
-<!-- List 2+ design options. Each must be a separate entry. (QFAI-DDP-020) -->
-
-- **Option A**: [Name and description]
-- **Option B**: [Name and description]
-
-### Anchor Screen Selection
-
-<!-- Select one of the compared options as the anchor. (QFAI-DDP-021) -->
-
-Selected: [Option X] — [Reason for selection]
-
-### Competitive References
-
-<!-- Summarize competitive references from 04_Sources.md. (QFAI-DDP-022) -->
-
-See 04_Sources.md for full competitive reference registry.
-
-### CTA Hierarchy
-
-<!-- Define CTA hierarchy with at least a primary CTA. (QFAI-DDP-023) -->
-
-- Primary: [CTA label and placement]
-- Secondary: [CTA label and placement]
-
-### State Coverage
-
-<!-- Define all 4 required states. (QFAI-DDP-024) -->
-<!-- SSOT for state details: Behavior Obligations > State Coverage table above. Keep these bullets for validator compliance; fill display-level details or reference the table. -->
-
-- empty: [Empty state display — see Behavior Obligations table for triggers/transitions]
-- loading: [Loading state display — see Behavior Obligations table for triggers/transitions]
-- error: [Error state display — see Behavior Obligations table for triggers/transitions]
-- populated: [Populated state display — see Behavior Obligations table for triggers/transitions]
-
-### Design Anti-goals
-
-<!-- List 1+ design patterns to intentionally avoid. (QFAI-DDP-025) -->
-
-- Anti-goal: [Pattern to avoid and reason]

package/assets/init/.qfai/assistant/skills/qfai-discussion/templates/04_Sources.md

@@ -12,12 +12,79 @@
 - `secondary`: Derived information (summaries, analyses).
 - `external`: Third-party references (specs, RFCs, vendor docs).
 
-## Competitive Reference Registry
+## Trend Scan
+
+### Visual Tone Trends
+
+#### Entry 1
+
+- reference: [Source name or URL]
+- observation: [What visual tone signal was observed]
+- freshness_date: YYYY-MM-DD
+- confidence: [high|medium|low]
+- source_translation: [How the signal translates into this project]
+- local_implication: [What should change locally]
+
+### Layout / Composition Trends
+
+#### Entry 1
+
+- reference: [Source name or URL]
+- observation: [What layout or composition signal was observed]
+- freshness_date: YYYY-MM-DD
+- confidence: [high|medium|low]
+- source_translation: [How the signal translates into this project]
+- local_implication: [What should change locally]
+
+### Density / Hierarchy Trends
+
+#### Entry 1
+
+- reference: [Source name or URL]
+- observation: [What density or hierarchy signal was observed]
+- freshness_date: YYYY-MM-DD
+- confidence: [high|medium|low]
+- source_translation: [How the signal translates into this project]
+- local_implication: [What should change locally]
 
-<!-- Required for UI-bearing packs. Each entry must have all 3 fields populated. (QFAI-DDP-022) -->
+### Interaction / Motion Trends
+
+#### Entry 1
+
+- reference: [Source name or URL]
+- observation: [What interaction or motion signal was observed]
+- freshness_date: YYYY-MM-DD
+- confidence: [high|medium|low]
+- source_translation: [How the signal translates into this project]
+- local_implication: [What should change locally]
+
+### Component Styling Trends
+
+#### Entry 1
+
+- reference: [Source name or URL]
+- observation: [What component styling signal was observed]
+- freshness_date: YYYY-MM-DD
+- confidence: [high|medium|low]
+- source_translation: [How the signal translates into this project]
+- local_implication: [What should change locally]
+
+### Stale / Overused AI Slop Patterns
+
+#### Entry 1
+
+- reference: [Source name or URL]
+- observation: [What stale pattern should be avoided]
+- freshness_date: YYYY-MM-DD
+- confidence: [high|medium|low]
+- source_translation: [Why this stale pattern is relevant to avoid here]
+- local_implication: [What should be explicitly avoided locally]
+
+## Competitive Reference Registry
 
 ### Reference: [Product/Service Name]
 
+- reference: [Product/Service Name or URL]
 - adopted_points: [What was adopted from this reference and why]
 - rejected_points: [What was not adopted and why]
 - local_translation: [How adopted points were adapted for this project]

package/assets/init/.qfai/assistant/skills/qfai-discussion/templates/06_REQ.md

@@ -1,6 +1,6 @@
 # 06 REQ (Functional Requirements)
 
-<!-- UX-INTENT: If UI-bearing, see uiux/40_contracts.md for screen interaction requirements -->
+<!-- UX-INTENT: If UI-bearing, see uiux/40_screen_contracts.md for screen interaction requirements -->
 
 ## Requirements Table
 

package/assets/init/.qfai/assistant/skills/qfai-discussion/templates/07_NFR.md

@@ -1,6 +1,6 @@
 # 07 NFR (Non-Functional Requirements)
 
-<!-- UX-INTENT: If UI-bearing, see uiux/20_eval_axis_usability.md for usability measurement targets -->
+<!-- UX-INTENT: If UI-bearing, see uiux/20_design_eval_invariant.md for usability measurement targets -->
 
 ## Requirements Table
 

package/assets/init/.qfai/assistant/skills/qfai-discussion/templates/09_Constraints.md

@@ -1,6 +1,6 @@
 # 09 Constraints
 
-<!-- UX-INTENT: If UI-bearing, see uiux/22_eval_axis_accessibility.md for accessibility constraints -->
+<!-- UX-INTENT: If UI-bearing, see uiux/20_design_eval_invariant.md for accessibility constraints (invariant layer) -->
 
 ## Technical Constraints
 

package/assets/init/.qfai/assistant/skills/qfai-discussion/templates/10_Policy.md

@@ -1,6 +1,6 @@
 # 10 Policy
 
-<!-- UX-INTENT: If UI-bearing, see uiux/10_strategy.md for design policy alignment -->
+<!-- UX-INTENT: If UI-bearing, see uiux/10_implementation_strategy.md for design policy alignment -->
 
 ## Security Policy
 

package/assets/init/.qfai/assistant/skills/qfai-discussion/templates/11_OQ-Register.md

@@ -1,6 +1,6 @@
 # 11 OQ Register
 
-<!-- UX-INTENT: If UI-bearing, track design direction OQs from uiux/60_critique_loop.md -->
+<!-- UX-INTENT: If UI-bearing, track design direction OQs from uiux/30_option_comparison.md and uiux/31_selected_anchor_screen.md -->
 
 ## OQ Table
 

package/assets/init/.qfai/assistant/skills/qfai-discussion/templates/12_OQ-Resolution-Log.md

@@ -1,6 +1,6 @@
 # 12 OQ Resolution Log
 
-<!-- UX-INTENT: If UI-bearing, log design critique resolutions from uiux/60_critique_loop.md -->
+<!-- UX-INTENT: If UI-bearing, log design critique resolutions from uiux/30_option_comparison.md and uiux/31_selected_anchor_screen.md -->
 
 ## Resolution Timeline
 

package/assets/init/.qfai/assistant/skills/qfai-discussion/templates/13_Deferred.md

@@ -1,6 +1,6 @@
 # 13 Deferred
 
-<!-- UX-INTENT: If UI-bearing, track deferred design decisions from uiux/50_review_bundle.md -->
+<!-- UX-INTENT: If UI-bearing, track deferred design decisions from uiux/50_review_input_bundle.md -->
 
 ## Deferred Items
 

package/assets/init/.qfai/assistant/skills/qfai-discussion/templates/14_Review-Request.md

@@ -35,38 +35,47 @@
   - Acceptance criteria are consistent with flows/state transitions
   - Security/operations risks are reflected in diagrams where relevant
 - Mermaid diagrams use ` ```mermaid ` fences only
-- HTML+CSS screen mock is usable for UI alignment when UI requirements exist
-  - If UI requirements exist and no screen mock is provided, request changes
+- Strategy alignment and chosen_option consistency (when UI-bearing)
+- Taste reflection completeness and clarity (when UI-bearing)
+- Trend scan freshness and source translation quality (when UI-bearing)
+- 3-layer axes evaluation quality and traceability (when UI-bearing)
+- Option comparison integrity (when UI-bearing)
+- Selected anchor screen clarity and direction justification (when UI-bearing)
+- Screen contract sufficiency and strong schema completeness (when UI-bearing)
+- Generic fallback risk — ensure no unreviewed generic/placeholder UI remains (when UI-bearing)
 - OQ register exit condition (open count = 0)
 - Deferred items have full metadata
 
-## Design Direction Decisions
+## Selected Direction Consistency
 
-<!-- Required for UI-bearing packs. Populated from DDS in 03_Story-Workshop.md. -->
+<!-- Required for UI-bearing packs. Verifies sidecar-family alignment. -->
 
-- Anchor screen: [Selected option reference]
-- Rejection rationale: [Why other options were not selected]
-- Adopted competitive references: [Key references adopted from 04_Sources.md]
+- Selected direction: verify `uiux/31_selected_anchor_screen.md` Selected Direction is populated and references a compared option from `uiux/30_option_comparison.md`
+- Strategy alignment: verify `uiux/10_implementation_strategy.md` aligns with the selected direction in `uiux/31_selected_anchor_screen.md`
+- Evaluation traceability: verify selected direction rationale aligns with 3-layer evaluation family (20/21/22/23 + optional 24)
 
 ## Sidecar Artifact Review Scope
 
 <!-- Required for UI-bearing packs. Reviews uiux/ sidecar artifacts. -->
 
 - Verify all 11 uiux/ sidecar files are present (when UI-bearing)
-- Verify uiux/10_strategy.md YAML schema conforms to version `"0.1"`
+- Verify uiux/10_implementation_strategy.md strict canonical schema is complete
 - Verify scoring axes have evaluation criteria and measurement approaches
-- Verify option comparison covers 2+ options against all scoring axes
-- Verify anchor screen selection references a compared option
-- Verify screen contracts define all 4 required states (empty/loading/error/populated)
+- Verify option comparison covers 2+ options against all scoring axes in `uiux/30_option_comparison.md`
+- Verify `uiux/31_selected_anchor_screen.md` Selected Direction references a compared option
+- Verify `uiux/24_design_eval_dynamic_overrides.md` has documented override rules
+- Verify screen contracts use nested strong schema with all 4 required states (default/loading/empty/error) and treat `uiux/40_screen_contracts.md` as the state SSOT
 
 ## Required Reviewers
 
-- Load all reviewers from `.qfai/assistant/steering/review-roster.yml`.
-- Run all reviewers in roster order for every cycle.
-- Allowed verdicts: `PASS`, `FAIL`, `N/A` (`N/A` requires `na_rule` reason).
+- Resolve reviewers from `.qfai/assistant/steering/agent-routing.yml` and `.qfai/assistant/steering/review-profiles.yml`.
+- Always run reviewers listed in `profiles.<routing_profile>.always_required` in `review-profiles.yml`.
+- Add `architecture-reviewer` only when architecture-affecting decisions exist.
+- Add `product-surface-reviewer` only when the pack is UI-bearing.
+- Allowed verdicts: `PASS`, `FAIL`.
 
 ## RCP Rules (Mandatory)
 
 - Any feedback triggers immediate return (`changes_requested`).
-- After fixes, create a new review-pack and restart reviewer sequence from the first reviewer.
-- Set `overall_status: PASS` only when all required reviewers are `PASS` or valid `N/A`, and no unresolved `FAIL` remains.
+- After fixes, rerun only failed reviewers and reviewers whose scope changed because of the fix.
+- Set `overall_status: PASS` only when all routed blocking reviewers are `PASS`, and no unresolved `FAIL` remains.

package/assets/init/.qfai/assistant/skills/qfai-discussion/templates/99_delta.md

@@ -1,6 +1,6 @@
 # 99 Delta
 
-<!-- UX-INTENT: If UI-bearing, record design direction changes from uiux/31_anchor.md -->
+<!-- UX-INTENT: If UI-bearing, record design direction changes from uiux/30_option_comparison.md and uiux/31_selected_anchor_screen.md -->
 
 ## Change History
 

package/assets/init/.qfai/assistant/skills/qfai-discussion/templates/prototyping.yaml

@@ -0,0 +1,9 @@
+prototyping:
+  recommended_mode: standard
+  rationale: >
+    Fill this with a concrete reason tied to evidence obligations.
+  allowed_modes:
+    - low-cost
+    - standard
+    - full-harness
+  surface: web

package/assets/init/.qfai/assistant/skills/qfai-discussion/templates/review/Rxx_reviewer.md

@@ -1,8 +1,8 @@
 # Reviewer Result
 
 - reviewer_id: `Rxx`
-- reviewer_role: `qa-lead`
-- verdict: `PASS` <!-- PASS | FAIL | N/A -->
+- reviewer_role: `<reviewer-name>`
+- verdict: `PASS` <!-- PASS | FAIL -->
 - reviewed_at: `YYYY-MM-DDThh:mm:ssZ`
 
 ## Checked
@@ -13,7 +13,11 @@
 - [ ] Clarity and actionability
 - [ ] Mermaid diagrams are sufficient for decisions (scope/AC/risk consistency)
 - [ ] Mermaid diagrams use ` ```mermaid ` fences only
-- [ ] HTML+CSS screen mock exists when UI requirements are present
+- [ ] Taste interview completeness (when UI-bearing)
+- [ ] Trend freshness and translation quality (when UI-bearing)
+- [ ] 3-layer evaluation quality and traceability (when UI-bearing)
+- [ ] Option comparison integrity and selected direction clarity (when UI-bearing)
+- [ ] Strong screen contract completeness (when UI-bearing)
 - [ ] OQ register exit condition (open count = 0)
 - [ ] Deferred items have full metadata
 
@@ -23,4 +27,4 @@
 
 ## Decision
 
-- PASS / FAIL / N/A
+- PASS / FAIL

package/assets/init/.qfai/assistant/skills/qfai-discussion/templates/review/review_request.md

@@ -22,8 +22,11 @@
   - Acceptance criteria are consistent with flows/state transitions
   - Security/operations risks are reflected in diagrams where relevant
 - Mermaid diagrams use ` ```mermaid ` fences only (no ` ```text ` or language-less fences)
-- HTML+CSS screen mock is usable for UI alignment when UI requirements exist
-  - If UI requirements exist and no screen mock is provided, request changes
+- Taste interview completeness and clarity (when UI-bearing)
+- Trend freshness and source translation quality (when UI-bearing)
+- 3-layer evaluation quality and traceability (when UI-bearing)
+- Option comparison integrity and selected direction clarity (when UI-bearing)
+- Strong screen contract completeness (when UI-bearing)
 - OQ register exit condition (open count = 0)
 - Deferred items have full metadata in `13_Deferred.md`
 - Validate hard gate evidence exists (`.qfai/report/validate.log`).
@@ -31,12 +34,13 @@
 
 ## Required Reviewers
 
-- Load all reviewers from `.qfai/assistant/steering/review-roster.yml`.
-- Run all reviewers in roster order for every cycle.
-- Allowed verdicts: `PASS`, `FAIL`, `N/A` (`N/A` requires `na_rule` reason).
+- Resolve reviewers from `.qfai/assistant/steering/agent-routing.yml` and `.qfai/assistant/steering/review-profiles.yml`.
+- Always run reviewers listed in `profiles.<routing_profile>.always_required` in `review-profiles.yml`.
+- Add conditional reviewers according to `conditional_required` and related routing rules defined in `agent-routing.yml` and `review-profiles.yml` (do not introduce additional ad-hoc conditions in this template).
+- Allowed verdicts: `PASS`, `FAIL`.
 
 ## RCP Rules (Mandatory)
 
 - Any feedback triggers immediate return (`changes_requested`).
-- After fixes, create a new review-pack and restart reviewer sequence from the first reviewer.
-- Set `overall_status: PASS` only when all required reviewers are `PASS` or valid `N/A`, and no unresolved `FAIL` remains.
+- After fixes, rerun only failed reviewers and reviewers whose scope changed because of the fix.
+- Set `overall_status: PASS` only when all routed blocking reviewers are `PASS`, and no unresolved `FAIL` remains.

package/assets/init/.qfai/assistant/skills/qfai-discussion/templates/review/summary.json

@@ -1,61 +1,23 @@
 {
-  "version": "1.0",
+  "version": "2.0",
   "created_at": "YYYY-MM-DDThh:mm:ssZ",
   "target": {
     "kind": "discussion",
     "path": ".qfai/discussion/discussion-YYYYMMDDhhmmssSSS"
   },
-  "roster": [
+  "routing_profile": "requirements-heavy",
+  "reviewers": [
     {
-      "reviewer": "qa-lead",
+      "reviewer": "completion-reviewer",
       "status": "PASS",
       "feedback_count": 0
     },
     {
-      "reviewer": "qa-gatekeeper",
-      "status": "PASS",
-      "feedback_count": 0
-    },
-    {
-      "reviewer": "reviewer",
-      "status": "PASS",
-      "feedback_count": 0
-    },
-    {
-      "reviewer": "code-reviewer",
-      "status": "PASS",
-      "feedback_count": 0
-    },
-    {
-      "reviewer": "architect-reviewer",
-      "status": "PASS",
-      "feedback_count": 0
-    },
-    {
-      "reviewer": "qa-reviewer",
-      "status": "PASS",
-      "feedback_count": 0
-    },
-    {
-      "reviewer": "frontend-reviewer",
-      "status": "PASS",
-      "feedback_count": 0
-    },
-    {
-      "reviewer": "backend-reviewer",
-      "status": "PASS",
-      "feedback_count": 0
-    },
-    {
-      "reviewer": "design-review-lead",
-      "status": "PASS",
-      "feedback_count": 0
-    },
-    {
-      "reviewer": "runtime-gatekeeper",
+      "reviewer": "requirements-reviewer",
       "status": "PASS",
       "feedback_count": 0
     }
   ],
+  "conditional_reviewers": [],
   "overall_status": "PASS"
 }