qfai 1.8.7 → 1.8.8

package/README.md

@@ -18,10 +18,9 @@ The agent reads the repository, produces the required artifacts, and iterates un
 ## Release status
 
 - Release posture: runtime truthfulness is enforced.
-- Prototyping is UI-only; v2.0 (spec-0017) runs a single-thread evolution loop
-  driven by `qfai prototyping iterate --cycle <n>`, with deterministic stop
-  conditions (exit codes 0/64/65/2). The v1.x mode tier and full-harness
-  machinery are removed.
+- Prototyping is UI-only and runs a single-thread evolution loop driven by
+  `qfai prototyping iterate --cycle <n>`, with deterministic stop conditions
+  (exit codes 0 continue / 64 convergence / 65 max-iterations / 2 input error).
 - Runtime observation is observed-only (no synthetic 200 / API / DB prototyping coverage).
 - Per-iter evidence is `screenshot.png` + `index.html` per declared screen plus a single `review.json` (4-axis ordinal, prose critique, anti-slop detection, pivot directive).
 - Calibration SSOT is the calibration pack referenced by `calibrationRef.packPath`.
@@ -62,15 +61,15 @@ npx qfai report
     primary spec, UI contracts, design contract readiness, active agent-wrapper
     integrations, shipped role-input readiness, Playwright CLI launcher
     resolution/probing, and target URL reachability.
-    Note: prototyping evidence (`.qfai/evidence/prototyping/prototyping.json` v3.0) is produced by the AI workflow
-    (`/qfai-prototyping` v2.0, see spec-0017), not by a general-purpose end-user CLI flow.
+    Note: prototyping evidence (`.qfai/evidence/prototyping/prototyping.json`) is produced by the AI workflow
+    (`/qfai-prototyping`), not by a general-purpose end-user CLI flow.
     Use `npx qfai prototyping preflight --target-url <url>` for a focused
     prototyping preflight before the skill starts; it surfaces blocking
     `QFAI-DCON-*` design-contract issues alongside runtime assumptions and resolves a runnable Playwright CLI launcher.
-    Use `npx qfai prototyping iterate --cycle <n> --target-url <url>` to drive each cycle of the v2.0 single-thread
+    Use `npx qfai prototyping iterate --cycle <n> --target-url <url>` to drive each cycle of the single-thread
     evolution loop. Exit codes: 0 (continue), 64 (convergence), 65 (max-iterations), 2 (input error).
     Traceability refs inside prototyping evidence must use repo-root-relative concrete artifact refs
-    (for example `.qfai/specs/spec-0017/01_Spec.md#L3` or `.qfai/evidence/prototyping/iter-03/home.png`).
+    (for example `.qfai/specs/spec-0001/01_Spec.md#L3` or `.qfai/evidence/prototyping/iter-03/home.png`).
     Absolute paths are invalid. The same strict ref grammar is enforced for top-level and leaf evidence-bearing fields, including
     `runtimeGate.evidenceRefs`, `runtimeGate.ui[].declaredRef`, `runtimeGate.ui[].renderEvidenceRefs[]`,
     `runtimeGate.ui[].browserQaEvidenceRefs[]`, `specs[].coverageRefs[].declaredRef`, `specs[].coverageRefs[].observedRefs[]`,
@@ -121,12 +120,22 @@ QFAI includes a small set of custom skills (stored under `.qfai/assistant/skills
 - **qfai-discussion**: Run a unified structured discussion that produces and maintains the latest discussion pack
   as 15 required markdown files under `.qfai/discussion/discussion-<ts>/`.
   UI-bearing discussion packs may include `prototyping.yaml` as an optional recommendation artifact; non-ui discussion packs typically omit it.
-- **qfai-sdd**: Unified SDD entrypoint with discussion-pack preflight guard (missing/incomplete/blocking OQ causes stop + next action guidance).
-- **qfai-prototyping** (v2.0, spec-0017): Single-thread design evolution loop. One prototype iterated
-  through up to 15 cycles of generate -> capture -> review with a 4-axis ordinal rubric, anti-slop
-  detection, prose critique, and explicit pivot permission. Stops deterministically when all four
-  axes hit `exceptional` (exit 64) or the iteration budget is exhausted (exit 65). The v1.x funnel,
-  mode tier, polish/branch cycles, and 100/100 completion gate are removed.
+- **qfai-sdd**: Unified SDD entrypoint with discussion-pack preflight guard
+  (missing/incomplete/blocking OQ causes stop + next action guidance).
+  After preflight, the skill runs a mandatory **Stage 1 Triage** that classifies
+  every incoming requirement into one of 8 first-class operations
+  (CREATE / UPDATE:APPEND / UPDATE:MODIFY / UPDATE:REMOVE / DELETE / SPLIT /
+  MERGE / SUPERSEDE) with an **append-first** bias: existing active specs
+  absorb the change unless there is zero subject-token overlap.
+  CREATE / DELETE / SPLIT / MERGE / SUPERSEDE / UPDATE:REMOVE require explicit
+  `AskUserQuestion` approval, and CREATE rows must register a new `CAP-NNNN`
+  in `.qfai/specs/_policies/03_Capabilities.md` before the row is accepted
+  (`QFAI-TRIAGE-006`). Every `01_Spec.md` declares a lifecycle
+  `Status: active | superseded | deprecated | removed` (`QFAI-STATUS-001..006`).
+- **qfai-prototyping**: Single-thread design evolution loop. One prototype iterated through up to
+  15 cycles of generate -> capture -> review with a 4-axis ordinal rubric, anti-slop detection,
+  prose critique, and explicit pivot permission. Stops deterministically when all four axes hit
+  `exceptional` (exit 64) or the iteration budget is exhausted (exit 65).
 - **qfai-atdd**: Implement acceptance tests driven by specs/scenarios.
 - **qfai-implement**: Unified TDD micro-cycle (Red/Green/Refactor) one test at a time using `test-list.md` as the execution ledger, including ledger status updates and exception closure.
 - **qfai-verify**: Run full-scan local quality gates (`validate --fail-on error`, `report`, repo gates) and produce reviewer-approved evidence under `.qfai/evidence/`.
@@ -283,6 +292,16 @@ Release gate behavior:
   - A: Include all required sections (`Change Summary`, `Rationale`, `Candidates Considered`, `Adopted`, `Rejected`, `Impact`, `Follow-ups`) and include both `DO NOT` and `Temptation` in `Rejected`.
 - Q: release_candidate validation fails due open questions.
   - A: Keep specs definition-only, use `.qfai/report/run-*` as execution logs, and convert open OQ to `resolved` or `deferred` with evidence.
+- Q: `qfai validate` reports `QFAI-STATUS-001` ("Status bullet が見つかりません") on every spec.
+  - A: Each `01_Spec.md` must declare `- Status: active | superseded | deprecated | removed` (introduced in 1.8.8).
+    Add `Status: active` for currently-authoritative specs; superseded specs need a `- Superseded-by: spec-NNNN` companion bullet,
+    and deprecated/removed specs need `- Deprecated-at: YYYY-MM-DD`. The previous `QFAI-STATUS-001` (status-leak guard) was renamed to `QFAI-STATUSLEAK-001` to free the namespace.
+- Q: `/qfai-sdd` is asking for `AskUserQuestion` approval that earlier versions never asked for.
+  - A: Stage 1 Triage classifies each requirement into one of 8 first-class operations and gates approval-required ops
+    (CREATE / DELETE / SPLIT / MERGE / SUPERSEDE / UPDATE:REMOVE) on explicit user confirmation. Append-first means UPDATE:APPEND on an existing active spec is the default;
+    CREATE additionally requires a new `CAP-NNNN` row in `.qfai/specs/_policies/03_Capabilities.md` before the row is accepted (`QFAI-TRIAGE-006`).
+- Q: `delta.md` validation reports `QFAI-TRIAGE-001` ("Change Summary はあるが Triage がありません") as a warning.
+  - A: 1.8.8 introduced a `## Triage` section requirement. Existing operational deltas without it currently fail soft (warning); future minor versions will promote this to an error after operational backfill.
 
 ## Continuous integration
 

package/assets/init/.qfai/assistant/skills/qfai-discussion/SKILL.md

@@ -68,12 +68,11 @@ For UI-bearing targets, follow `references/design-dna-intake.md` while authoring
 
 - `30_exploration_brief.md` must define product intent, brand signals, and differentiation targets.
 - `31_reference_pool.md` must define exploration references with adopted points, rejected points, and copy risk — framed as **deviate-from** inputs (not imitate-this) for downstream `/qfai-prototyping` reviewer.
-- `32_design_anti_goals.md` must contain explicit anti-goals; this also feeds the global anti-slop pattern list consulted by the v2.0 reviewer.
+- `32_design_anti_goals.md` must contain explicit anti-goals; this also feeds the global anti-slop pattern list consulted by the prototyping reviewer.
 - `50_review_input_bundle.md` must document review inputs for downstream skills.
 
-v1.x sidecars `33_exploration_rubric.md` and `34_evaluator_calibration.md`
-are removed in spec-0017 P4 (axes are global constants in
-`core/prototyping/iteration.ts#OrdinalScore`, ordinal 4-step scale).
+Evaluation axes are global constants (4-step ordinal: weak / acceptable /
+strong / exceptional) and are not authored as discussion sidecars.
 
 ## Completion Contract (Shared)
 

package/assets/init/.qfai/assistant/skills/qfai-discussion/references/design-dna-intake.md

@@ -25,6 +25,5 @@ Use this reference only for UI-bearing discussion packs.
 - Put all reference decisions in `31_reference_pool.md` (deviate-from input, not imitate).
 - Put prohibited visual directions in `32_design_anti_goals.md` (also feeds reviewer anti-slop).
 
-v1.x sidecars `33_exploration_rubric.md` and `34_evaluator_calibration.md`
-are removed in spec-0017 P4. Evaluation axes are now global constants in
-`core/prototyping/iteration.ts#OrdinalScore`.
+Evaluation axes are global constants (4-step ordinal: weak / acceptable /
+strong / exceptional) and are not authored as discussion sidecars.

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

@@ -50,13 +50,13 @@ Discussion is exploration-first and must not choose a single visual winner or fi
 
 ## `prototyping.yaml`
 
-When `prototyping.yaml` is present, use the v2.0 single-thread schema:
+When `prototyping.yaml` is present, use the single-thread schema:
 
 ```yaml
 prototyping:
   surface: web # web | mobile | desktop | mixed
 ```
 
-The v1.x `recommended_mode` / `allowed_modes` / `mode_expectations` fields
-were removed in spec-0017 P3 (the single-thread evolution loop fixes
-iteration count globally to 15).
+Mode-tier fields (`recommended_mode` / `allowed_modes` / `mode_expectations`)
+are not supported. The single-thread evolution loop fixes iteration count
+globally to 15.

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

@@ -1,7 +1,6 @@
 prototyping:
-  # v2.0 single-thread evolution loop (spec-0017): mode/maxCycles concepts
-  # are removed; iteration count is fixed at 15 globally in
-  # `core/prototyping/iteration.ts#MAX_ITERATIONS`.
+  # Single-thread evolution loop. Iteration count is fixed at 15 globally
+  # (no per-mode override).
   # Replace `web` with one of the prototyping-supported surfaces if needed:
   #   web | mobile | desktop | mixed
   # (discussion classification also allows `cli` and `non-ui`, but those are

package/assets/init/.qfai/assistant/skills/qfai-implement/SKILL.md

@@ -76,20 +76,17 @@ Execute the TDD micro-cycle for each pending item in `test-list.md`, transitioni
 
 - Review rendered output, screenshot evidence, or HTML output before closing any UI-affecting item.
 - Read spec + contract inputs first whenever implementation touches UI or critique-driven behavior.
-- Read order (v2.0, spec-0017 P11): `01_Spec.md` → `03_Acceptance-Criteria.md` → `05_Examples.md` →
+- Read order: `01_Spec.md` → `03_Acceptance-Criteria.md` → `05_Examples.md` →
   `.qfai/contracts/design/exploration-brief.yaml` →
   `.qfai/contracts/design/reference-pool.yaml` → `.qfai/contracts/design/brand-design.yaml` →
   `.qfai/contracts/design/design-system.yaml` (extracted from final iter) →
   `.qfai/contracts/design/prototype-handoff.yaml` → `.qfai/contracts/ui/*.yaml` →
   canonical prototype evidence under `.qfai/evidence/prototyping/iter-NN/<screen>.{png,html}` →
   `.qfai/prototypes/final/index.html`.
-- The v1.x evaluation-rubric / evaluator-calibration / selected-direction contracts and
-  `prototypes/winner/index.html` were removed in spec-0017 P4/P8.
-- Do not read discussion-pack UI/UX sidecars, fallback mocks, or legacy design aliases.
+- Do not read discussion-pack UI/UX sidecars or fallback mocks.
 - Prototype HTML is analysis input, not production source. Reimplement with project-native
   patterns while preserving the visual identity captured in `prototype-handoff.yaml`
-  `implementationNotes` (free-form prose); the v1.x mustPreserve / mayAdapt / mustNotCopy
-  three-category split is removed.
+  `implementationNotes` (free-form prose).
 - UI-affecting items require product-surface-reviewer prototype parity review before `done`.
 - If code intent and rendered output diverge, treat the rendered/HTML result as the blocking review input and reconcile before DONE.
 
@@ -299,7 +296,7 @@ Completion MUST NOT be declared when any of the following are true:
 - Items with `todo`, `red`, `green`, or `refactor` status still exist (for spec-level completion)
 - Parallel slices were used but integration verify has not been run post-merge
 - Checkpoint boundary was reached but verification was not executed
-- `it.todo(...)` / `test.todo(...)` / `describe.todo(...)` stubs remain in any file covered by `validation.traceability.testFileGlobs` (`QFAI-TEST-001`, spec-0012). Implement the body or delete the stub — an opt-out via `validation.testStrategy.forbidTestTodoStubs: false` is permitted only with an accompanying waiver DR-ID.
+- `it.todo(...)` / `test.todo(...)` / `describe.todo(...)` stubs remain in any file covered by `validation.traceability.testFileGlobs` (`QFAI-TEST-001`). Implement the body or delete the stub — an opt-out via `validation.testStrategy.forbidTestTodoStubs: false` is permitted only with an accompanying waiver DR-ID.
 
 ## Evidence (MANDATORY)
 
@@ -347,7 +344,7 @@ Each TDD item MUST have fresh evidence containing at minimum:
 - [ ] No backward transitions occurred.
 - [ ] Exception items have DR-IDs recorded.
 - [ ] All tests pass.
-- [ ] `qfai validate --profile tdd --fail-on error` passes with zero `QFAI-TEST-001` findings (no `it.todo` / `test.todo` / `describe.todo` stubs remain; spec-0012).
+- [ ] `qfai validate --profile tdd --fail-on error` passes with zero `QFAI-TEST-001` findings (no `it.todo` / `test.todo` / `describe.todo` stubs remain).
 
 ## Completion Checklist (MUST)
 

package/assets/init/.qfai/assistant/skills/qfai-prototyping/references/handoff.md

@@ -25,7 +25,6 @@ LLM assistance is allowed for naming (primary / surface / accent etc.).
 ### `.qfai/contracts/design/prototype-handoff.yaml`
 
 ```yaml
-schemaVersion: "2.0"
 finalIterIndex: <number>
 finalArtifact: ".qfai/prototypes/final/index.html"
 extractedDesignSystem: ".qfai/contracts/design/design-system.yaml"
@@ -34,8 +33,8 @@ implementationNotes: |
   what makes this artifact distinct from generic AI defaults.
 ```
 
-The v1.x preserve / adapt / copy three-category split is removed. The artifact itself is the SSOT.
+The artifact itself is the SSOT (no preserve / adapt / copy split).
 
 ## Cert
 
-Run `qfai prototyping certify` to produce `.qfai/evidence/prototyping/completion-certificate.json` (`schemaVersion: "2.0"`). Use `certify --check` to verify digests.
+Run `qfai prototyping certify` to produce `.qfai/evidence/prototyping/completion-certificate.json`. Use `certify --check` to verify digests.

package/assets/init/.qfai/assistant/skills/qfai-prototyping/references/reviewer-prompt.md

@@ -14,7 +14,6 @@ This file is injected into the product-surface-reviewer sub-agent on each cycle.
 
 ```json
 {
-  "schemaVersion": "3.0",
   "iterIndex": <NN>,
   "reviewerId": "product-surface-reviewer",
   "scores": {

package/assets/init/.qfai/assistant/skills/qfai-prototyping/templates/contracts/prototype-handoff.sample.yaml

@@ -1,8 +1,7 @@
-# prototype-handoff.yaml v2.0 (spec-0017).
+# prototype-handoff.yaml.
 # Produced by /qfai-prototyping post-loop. Consumed by /qfai-implement.
-# v1.x preserve/adapt/copy three-category split is removed: the final
-# artifact itself is the SSOT, not this handoff yaml.
-schemaVersion: "2.0"
+# The final artifact itself is the SSOT; this handoff yaml is a thin
+# pointer plus implementation notes.
 finalIterIndex: 8
 finalArtifact: ".qfai/prototypes/final/index.html"
 extractedDesignSystem: ".qfai/contracts/design/design-system.yaml"