phasegate 0.130.0 → 0.132.0

package/CHANGELOG.md

@@ -7,6 +7,38 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.132.0] - 2026-05-08
+
+### Fixed
+
+- **WI-094 follow-up — `DriftReport` / `ConsistencyReport` / `DeadCodeReport` の `toHarnessError(s)` が `severity: 'error'` を hardcode していたため v0.131.0 の集計セマンティクス修正が L4-001/002/003 で実機に反映されなかった (post-publish dogfood で発見)** — `error catalog` の `defaultSeverity: warning` 宣言と各 report の `toHarnessError(s)` 出力 severity が乖離しており、aggregator が `severity !== 'warning'` で hasNonWarningError と判定して overall FAIL となっていた。
+  - **修正対象**:
+    - `scripts/harness/validator-system/domain/value-objects/drift-report.ts:47` — L4-001 drift error の severity を `'error'` → `'warning'`
+    - `scripts/harness/validator-system/domain/value-objects/consistency-report.ts:49` — L4-002 consistency error の severity を `'error'` → `'warning'`
+    - `scripts/harness/validator-system/domain/value-objects/dead-code-report.ts:46/54` — L4-003 dead-code error の severity を `'error'` → `'warning'` (unused export / unreachable code 双方)
+  - **dogfood 結果 (v0.131.0 の状態)**: `/private/tmp/phasegate-dogfood-wi094` で drift 2 件発生させて `validate --layer L4 --format human` を実行 → `[FAIL] L4-001` / overall FAIL ✗ / exit 1。期待は `[WARN] L4-001` / overall PASS ✓ / exit 0。原因は本 fix で解消。
+  - **後方互換**: `validate.failOnWarning: true` を設定している user の挙動は不変 (warning でも overall FAIL)。`failOnWarning: false` (default for `minimal` / `standard`) の user のみ exit code 0 に変わる。これは ADR-017 で承認済みの BREAKING の意図通りで、v0.131.0 で動かなかった部分が初めて動く形。
+  - **post-publish dogfood**: WI-094 description.md に v0.132.0 dogfood 結果を反映。
+
+## [0.131.0] - 2026-05-08
+
+### Changed (BREAKING for `standard` / `minimal` preset users)
+
+- **WI-094 — warning-severity validator の集計セマンティクスを修正 (ADR-017, GitHub Issue #4 finding #2)** — `error catalog` で `defaultSeverity: warning` と宣言された validator (L4-001 drift / L4-002 consistency / L4-003 dead-code) が fail を返した際、`overallPassed` 判定が severity を見ず常に `failedValidators++` していたバグを修正。warning-only validator fail は `overall PASS / exit 0` を default に変更。
+  - **修正前**: `aggregate-validation-results-usecase.ts:35-42` の `hasFail = !result.passed || (failOnWarning && hasWarnings)` で `failOnWarning` flag が常に dead code 化していた。warning-only fail でも `[FAIL]` 表示・exit 1 となり、reporter (nakataj-mti) は plan-level workaround (false positive 注釈) で凌いでいた。
+  - **修正後**: `hasFail = !result.passed && (isEmptyFail || hasNonWarningError || (failOnWarning && hasWarnings))` で severity を反映。`failOnWarning=true` で旧挙動 (warning も fail) に opt-in 可能。
+  - **新 config フラグ**: `phasegate.config.json` に `validate.failOnWarning: boolean` を追加。default は `false`。preset 別 default: `minimal` / `standard` = `false`、`strict` = `true` (ci-governance preset adapter の precedent と整合)。schema v2 / v3 双方で optional property として追加 — 既存 user の config はそのまま valid。
+  - **新 CLI flag**: `--fail-on-warning` / `--no-fail-on-warning` の tri-state 化。両方未指定の場合は config 値を使用 (CLI > config 優先順位)。
+  - **Formatter 改修**: `human` formatter で `[FAIL]` と `[WARN]` を分離表示。warning-only fail は `[WARN] L4-001` として表示。`agent` / `ci` formatter (JSON) は既存 `severity` field 構造を維持し、後方互換性を確保。
+  - **Migration**: warning-only fail で CI を止めたい既存 user は `phasegate.config.json` に以下を追加:
+    ```json
+    { "validate": { "failOnWarning": true } }
+    ```
+    または CLI で `--fail-on-warning` を指定。`strict` preset 利用者は default で `failOnWarning: true` のため migration 不要。
+  - **回帰テスト**: warning-only / error-only / mixed / failOnWarning=true / 防御的 (passed=false かつ errors=[]) の 5 ケースを `aggregate-validation-results-usecase.test.ts` に追加。`human-validation-result-formatter.test.ts` 新設で `[WARN]` / `[FAIL]` / `[PASS]` / `[SKIP]` の表示を網羅。
+  - **検証 (publish 前)**: `pnpm test` 454 files / 3531 tests pass (baseline +11)。`npx phasegate validate --layer L2` は pre-existing fail のみ (L2-001 artifact 不足、本 WI とは無関係)。
+  - **post-publish dogfood**: WI-094 description.md / `tdd_implementation_plan.md` に dogfood 結果を反映予定。
+
 ## [0.130.0] - 2026-05-08
 
 ### Fixed
@@ -15,7 +47,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   - **phase-dependency-model**: Level 1 product 文書を `{designDocsRoot}/../...` で定義し、`Artifact.resolve()` / `expandRoots()` で POSIX 正規化。`paths.designDocs: "mydocs/product/construction"` の場合、L2 blocker は `mydocs/product/product_overview.md` / `mydocs/product/user_stories.md` を参照する。
   - **traceability-model**: `MarkdownStoryCatalogGateway` / `MarkdownDesignDocumentGateway` / `MarkdownUnitDefinitionGateway` / `TraceabilityChainBuilder` に custom design docs root を注入し、`mydocs/product/user_stories.md` と `mydocs/product/construction/{unit}` を読むよう修正。
   - **後方互換**: config 未指定時は従来通り `docs/product/user_stories.md` / `docs/product/construction/{unit}` を利用。
-  - **検証 (publish 前 local/self-host)**: `pnpm exec tsc --noEmit` pass。対象テスト 4 files / 29 tests pass。`pnpm test` は 453 files / 3520 tests pass。`/private/tmp/phasegate-local-wi093` の symlink なし reporter fixture で `validate --layer L2 --format human` を実行し、L2-001 blocker が `mydocs/product/product_overview.md` を参照することを確認。post-publish dogfood は publish 後に実施予定。
+  - **検証 (publish 前 local/self-host)**: `pnpm exec tsc --noEmit` pass。対象テスト 4 files / 29 tests pass。`pnpm test` は 453 files / 3520 tests pass。`/private/tmp/phasegate-local-wi093` の symlink なし reporter fixture で `validate --layer L2 --format human` を実行し、L2-001 blocker が `mydocs/product/product_overview.md` を参照することを確認。
+  - **post-publish dogfood**: `/private/tmp/phasegate-dogfood-wi093-published` で `npx phasegate@0.130.0` を使い検証済み。custom `paths.designDocs: "mydocs/product/construction"` では L2-001 blocker が `mydocs/product/product_overview.md` を参照し、default `paths.designDocs: "docs/product/construction"` では `docs/product/product_overview.md` を参照。`validate-metadata mydocs/product/construction/sample/domain_model.md` は `mydocs/product/user_stories.md` 由来で PASS。`docs/product` symlink workaround なし。
 
 ## [0.129.0] - 2026-05-08
 

package/docs/ADR/ADR-017-warning-severity-aggregation.md

@@ -0,0 +1,202 @@
+# ADR-017: warning-severity validator の集計セマンティクス
+
+## Status
+
+Accepted — 2026-05-08
+
+## Context
+
+`phasegate validate` の集計ロジック (`aggregate-validation-results-usecase.ts:67`) は `overallPassed = failedValidators === 0` で総合判定するが、この判定は **error severity を考慮していない**。
+
+その結果、`error catalog` 上で `defaultSeverity: warning` と宣言されている validator (L4-001 / L4-002 / L4-003) が fail を報告すると、warning-only にもかかわらず:
+
+- 個別 validator: `[FAIL] L4-001`
+- 総合判定: `FAIL ✗`
+- exit code: 非ゼロ (1)
+
+となる。GitHub Issue [#4](https://github.com/junpei-9898/phasegate/issues/4) (reporter: nakataj-mti, 2026-05-08) で報告され、reporter は plan-level workaround (「validate FAIL を許容、L4-001 false positive と plan に明記」) で凌いでいる。WI-091 finding #2 → WI-094 として起票。
+
+### バグの実体（grep ベース、2026-05-08）
+
+#### 1. 集計ロジックが severity を見ていない
+
+`scripts/harness/validator-system/application/use-cases/aggregate-validation-results-usecase.ts:35-42`:
+
+```ts
+const hasWarnings = result.errors.some((e) => e.severity === 'warning');
+const hasFail = !result.passed || (failOnWarning && hasWarnings);
+
+if (hasFail) {
+  failedValidators++;
+} else {
+  passedValidators++;
+}
+```
+
+`failOnWarning` パラメータは存在するが、`!result.passed` を OR 第一項に置いているため、**warning-only validator が `ValidationResult.fail([warningError])` を返した瞬間に `failOnWarning` の値に関係なく `failedValidators++` が確定する**。`failOnWarning` 経路は実質デッドコード。
+
+#### 2. exit code が overallPassed に直結
+
+`scripts/harness/validator-system/presentation/handlers/report-validation-results-handler.ts:62`:
+
+```ts
+const exitCode = report.overallPassed ? 0 : 1;
+```
+
+`overallPassed` が severity を見ない以上、warning-only fail は必ず exit 1。
+
+#### 3. `--fail-on-warning` CLI flag は通っているが効かない
+
+`scripts/harness/main.ts:997`:
+
+```ts
+const failOnWarning = hasFlag(args, "--fail-on-warning");
+```
+
+CLI からは flag が `RunFullValidationInput.failOnWarning` まで伝搬しているが、(1) のバグにより default 挙動 (warning も fail) と `--fail-on-warning` 指定時の挙動が同一になっている。
+
+#### 4. config からは設定不可
+
+`phasegate.config.json` には `validate.failOnWarning` 相当のキーが存在しない。CLI flag のみ。CI スクリプトを書く側で都度 `--fail-on-warning` を付け外しする必要があり、config single source (ADR-007) の精神に反する。
+
+### 検討した代替案
+
+#### (A) warning-only fail は overall PASS / exit 0 を default にする（**採用**）
+
+集計ロジックを修正し、validator が warning-only fail を返した場合は `failedValidators` にカウントしない。`failOnWarning: true` で従来挙動 (warning も fail) に opt-in。`validate.failOnWarning: boolean` を config schema に追加して持続的設定を可能にする。
+
+#### (B) warning も exit 1 を default に保つ (CI 互換性優先)
+
+既存挙動を維持し、`failOnWarning: false` で warning-only fail を許容できるようにする。default を変えないため移行コストはゼロだが、`defaultSeverity: warning` の宣言と「常に fail として扱う」実装の semantic 乖離は残る。
+
+## Decision
+
+**(A) を採用する。**
+
+### 採用理由
+
+1. **error catalog の宣言と実装を整合させる** — `defaultSeverity: warning` は「警告であって致命ではない」という宣言。実装側が常に fail として扱うのは catalog 宣言と矛盾しており、catalog を信頼できない状態を放置することは品質防御ツールとして自己矛盾
+2. **L4 validator の位置付けと整合** — ADR-001 (4層防御モデル) で L4 は advisory/observability layer として位置付けられており、drift / dead-code / freshness は「気付きを与える」ことが目的。これらが CI を止めるのは過剰
+3. **`failOnWarning: true` で旧挙動に opt-in 可能** — 厳格な CI を維持したい user は config flag または CLI flag で従来通りの挙動を選べる
+4. **config single source (ADR-007) の精神** — CLI flag のみで設定可能だった項目を config に持ち上げることで、CI スクリプトと config の再現可能性を担保
+5. **既存内部パラメータ名 `failOnWarning` と整合** — `AggregateResultsInput.failOnWarning` / `RunFullValidationInput.failOnWarning` / `ci-governance.PresetConfigAdapter.failOnWarning` が既に同名で通っている。schema 名と内部命名を揃えることで threading が単純
+
+### 集計セマンティクス（修正後）
+
+```ts
+const hasNonWarningError = result.errors.some((e) => e.severity !== 'warning');
+const hasWarnings = result.errors.some((e) => e.severity === 'warning');
+
+// passed=false かつ errors=[] の防御的ケースは fail としてカウント（severity 判定不能のため安全側に倒す）
+const isEmptyFail = !result.passed && result.errors.length === 0;
+
+const hasFail =
+  !result.passed &&
+  (isEmptyFail || hasNonWarningError || (failOnWarning && hasWarnings));
+```
+
+| 状態 | `failOnWarning=false` (default) | `failOnWarning=true` |
+|------|---------------------------------|----------------------|
+| `passed=true` (errors=[]) | PASS | PASS |
+| `passed=false` + error-severity 含む | FAIL | FAIL |
+| `passed=false` + warning-only | **PASS (新挙動)** | FAIL (従来挙動) |
+| `passed=false` + errors=[] | FAIL (防御) | FAIL (防御) |
+
+### Config schema 拡張
+
+`phasegate.config.json` に `validate` セクションを新設:
+
+```json
+{
+  "validate": {
+    "failOnWarning": false
+  }
+}
+```
+
+- 型: `boolean`、default: `false`
+- 旧挙動を維持したい user は `true` に設定
+- CLI flag `--fail-on-warning` は config 値を override する（CLI > config の優先順位）
+
+### Formatter での severity 表示
+
+human/agent/ci formatter で `[FAIL]` と `[WARN]` を分離:
+
+- `result.passed === false` かつ errors が **error severity を含む** → `[FAIL]`
+- `result.passed === false` かつ errors が **warning-only** → `[WARN]`
+- `result.passed === true` → `[PASS]`
+- `result.skipped === true` → `[SKIP]`
+
+これにより output から severity が一目で読める。CI 解析スクリプトの後方互換のため、`agent` / `ci` フォーマットでは `severity` フィールドが既に JSON に含まれている (現状)。`[WARN]` 表示は human フォーマットを主対象とする。
+
+### 後方互換戦略
+
+- **default 挙動の変更**: warning-only fail で exit 0 / overall PASS — これは BREAKING CHANGE
+- **opt-in 経路**: `validate.failOnWarning: true` を config に追加するか、`--fail-on-warning` CLI flag で旧挙動を選べる
+- **CHANGELOG**: `BREAKING` 認定で記載。ただし phasegate は `0.x` リリースのため、CLAUDE.md のバージョニングルールに従い minor bump (`0.130.0` → `0.131.0`) で出す（SemVer 上の major bump は phasegate `1.0.0` 到達時にまとめて宣言）
+- **migration ガイド**: 「CI で warning も止めたかった user は `validate.failOnWarning: true` を設定する」を CHANGELOG / configuration.md に明記
+
+## Consequences
+
+### ポジティブ
+
+- error catalog の `defaultSeverity` 宣言と実装挙動が一致し、catalog を信頼できる状態に戻る
+- L4 advisory validator が CI を止めなくなり、drift / dead-code / freshness が日常的に観測しやすい運用形態になる
+- `validate.failOnWarning` で CI 厳格度を config 経由で持続的に設定可能になり、CI スクリプト側の `--fail-on-warning` 散逸が解消
+- formatter の `[WARN]` 表示で fail の severity が UX 上明確になる
+- WI-091 reporter の plan-level workaround（false positive 注釈）が不要になる
+
+### ネガティブ / トレードオフ
+
+- **既存 user CI への BREAKING**: warning-only fail を error 同等に扱っていた user の CI が「PASS / exit 0」に変わる。silent regression 化のリスク
+  - **緩和策**: CHANGELOG で BREAKING 認定 + migration ガイド明記。`validate.failOnWarning: true` で旧挙動に opt-in
+- **回帰テスト負荷**: warning-only / error-only / mixed の 3 ケースを `aggregate-validation-results-usecase` の IT で網羅する必要
+  - **緩和策**: 既存テストヘルパで 3 ケースは小コストで追加可能
+- **config schema v3 拡張**: 新セクション `validate` の追加。schema migration は不要だが、config-foundation の defaults / mapper を更新
+  - **緩和策**: `validate.failOnWarning` のみの新規追加。既存 schema を変えないため migration 不要
+
+### スコープ外（本 ADR で扱わない）
+
+- error severity 自体のカタログ変更 (L4-XXX を warning から error に変える等) — 別 WI
+- `defense preset` (`project.preset: minimal/standard/strict`) ごとの `failOnWarning` default 切り替え — 現状全 preset で `false` default。preset ごとに切り替える必要が出たら別 ADR
+- WI-091 finding #4 (paths threading / WI-093) / #5 (pointers / WI-095) — 別 WI
+- exit code を `0` / `1` 以外 (`2` 等) に拡張 — 本 ADR は warning と error の二値判定のみ
+
+## Migration
+
+1. **集計ロジック改修** (`aggregate-validation-results-usecase.ts:35-42`):
+   - `hasFail` 計算式を「Decision 集計セマンティクス」通りに変更
+   - 既存テスト (`__tests__/integration/validator-system/usecases/aggregate-validation-results-usecase.test.ts`) を新挙動に合わせて更新
+2. **回帰テスト追加**:
+   - warning-only fail で `overallPassed=true` / exit 0 になること
+   - error-severity fail で `overallPassed=false` / exit 1 になること
+   - mixed (warning + error) で `overallPassed=false` / exit 1 になること
+   - `failOnWarning=true` 時に warning-only でも `overallPassed=false` になること
+3. **config schema 拡張**:
+   - `HarnessConfigResolvedDocument` に `validate: { failOnWarning: boolean }` を追加
+   - `config-foundation` の defaults / loader / mapper で新キーをハンドル
+   - `toValidatorSystemConfig` で `validate.failOnWarning` を validator-system module に伝搬
+   - `createValidatorSystemModule` 経由で `RunValidatorsHandler` に渡す
+4. **formatter 改修**:
+   - `human-validation-result-formatter.ts` で warning-only fail を `[WARN]` 表示
+   - `agent-validation-result-formatter.ts` / `ci-validation-result-formatter.ts` も整合 (既存 `severity` field との重複を整理)
+5. **ドキュメント**:
+   - `docs/guide/layer-model.md` に severity policy セクション追加
+   - `docs/guide/configuration.md` に `validate.failOnWarning` 説明と migration ガイド
+6. **CHANGELOG**: BREAKING CHANGE として記載 (GitHub Issue [#4](https://github.com/junpei-9898/phasegate/issues/4) 参照付き)
+7. **dogfood**: drift 検出を意図的に発生させて exit code が `validate.failOnWarning` に従って切り替わることを確認
+
+詳細な実装は WI-094 で進める。
+
+## 関連
+
+- **WI-094** — 本 ADR を駆動する Work Item。GitHub Issue [#4](https://github.com/junpei-9898/phasegate/issues/4) finding #2 に対応
+- **WI-091** — WI-094 の親 Work Item。dogfood で finding #2 を検出
+- **`scripts/harness/validator-system/application/use-cases/aggregate-validation-results-usecase.ts:35-42`** — 集計ロジックの修正対象
+- **`scripts/harness/validator-system/presentation/handlers/report-validation-results-handler.ts:62`** — exit code 算出箇所
+- **`scripts/harness/validator-system/domain/value-objects/error-catalog.ts`** — `defaultSeverity` 宣言の一次情報
+- **`scripts/harness/main.ts:997-1008`** — CLI flag → handler への threading
+- **`scripts/harness/config-foundation/domain/harness-config.ts`** — `HarnessConfigResolvedDocument` 拡張対象
+- **`scripts/harness/config-foundation/application/mappers/validator-system-config-mapper.ts`** — `toValidatorSystemConfig` 拡張対象
+- **ADR-007** — harness-config Single Source of Truth。本 ADR は `failOnWarning` を CLI flag のみから config まで持ち上げて ADR-007 の精神を強化
+- **ADR-001** — 4 層防御モデル。L4 validator の advisory 位置付けが本決定の根拠

package/docs/guide/configuration.md

@@ -405,6 +405,40 @@ Quick Mode with `relaxedGates: ["phase-gate"]` relaxes `storyReflection` as well
 | `format`    | `string` | `"json"`    | Output format for validation reports.                 |
 | `outputDir` | `string` | `"reports"` | Directory where reports are written.                  |
 
+#### `validate` (severity policy, ADR-017 / WI-094)
+
+Controls how warning-severity validator failures are aggregated into the overall result. Introduced in v0.131.0 to fix the dead-code `failOnWarning` parameter (`aggregate-validation-results-usecase.ts:35-42`) where warning-only fails were always counted as overall FAIL.
+
+| Sub-field        | Type      | Default by preset                                                | Description                                                                                                                                                          |
+|------------------|-----------|------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| `failOnWarning`  | `boolean` | `false` (`minimal` / `standard`), `true` (`strict`)              | When `true`, warning-only validator fails (e.g. L4-001 drift, L4-002 consistency, L4-003 dead-code) count as overall FAIL / exit 1. When `false`, they count as PASS / exit 0. |
+
+CLI override: `--fail-on-warning` / `--no-fail-on-warning` (CLI > config). Both unspecified → config value used.
+
+Resulting label in `human` formatter:
+
+| validator state                     | `failOnWarning=false` | `failOnWarning=true` |
+|-------------------------------------|-----------------------|----------------------|
+| `passed=true` (errors=[])           | `[PASS]`              | `[PASS]`             |
+| `passed=false` + `severity: error`  | `[FAIL]` (overall FAIL) | `[FAIL]` (overall FAIL) |
+| `passed=false` + warning-only       | `[WARN]` (overall PASS) | `[WARN]` (overall FAIL) |
+| `passed=false` + errors=[] (defensive) | `[FAIL]` (overall FAIL) | `[FAIL]` (overall FAIL) |
+| `skipped=true`                      | `[SKIP]`              | `[SKIP]`             |
+
+`agent` / `ci` formatter (JSON output) preserves the existing `severity` field on each error and is unchanged structurally — downstream parsers do not need to update.
+
+##### Migration from v0.130.0 and earlier
+
+The fix is BREAKING for `minimal` / `standard` preset users who relied on warning-only fails stopping CI:
+
+```json
+{
+  "validate": { "failOnWarning": true }
+}
+```
+
+`strict` preset already defaults to `failOnWarning: true`, matching ci-governance template adapter precedent — no migration needed.
+
 #### `baseline` (retrofit grandfather)
 
 Introduced in ISSUE-007 Wave 1 (v0.65.0) and wired into the pre-tool-use hook by Wave 2 (v0.66.0). When phasegate is added to an existing repository, the `baseline` block lets you snapshot the current state of the codebase so legacy files do not trip `phase-gate` on first edit. Files in the snapshot are exempted **until they are structurally modified** (sha1 mismatch); new files are subject to `phase-gate` from the start.

package/docs/guide/layer-model.md

@@ -183,6 +183,25 @@ Error codes follow the pattern `L{layer}-{number}`:
 
 ---
 
+## Severity Policy (ADR-017 / WI-094, v0.131.0+)
+
+Each error catalog entry declares a `defaultSeverity` of `error` or `warning`. As of v0.131.0, the aggregator (`aggregate-validation-results-usecase.ts`) honors this declaration when computing `overallPassed` and exit code:
+
+- A validator returning **only `severity: warning` errors** is treated as **overall PASS** (exit 0) by default. The result is labeled `[WARN]` in `human` formatter so the warning is still visible.
+- A validator returning at least one **`severity: error`** counts as **overall FAIL** (exit 1). Mixed warning + error fails are also FAIL because of the error.
+- A validator returning `passed=false` with no errors is treated as FAIL (defensive — severity cannot be assessed).
+
+**Validators with `defaultSeverity: warning`** (advisory by design — fail does not stop CI by default):
+- L4-001 drift-detect
+- L4-002 consistency-check
+- L4-003 dead-code
+
+**Opt-in to strict mode** via `phasegate.config.json` `validate.failOnWarning: true` or CLI `--fail-on-warning` (CLI > config). The `strict` preset defaults to `failOnWarning: true` to match the precedent set by the `ci-governance` preset adapter.
+
+History: prior to v0.131.0, the aggregator's `failOnWarning` flag was effectively dead code (`hasFail = !result.passed || ...` masked it), so every warning-only fail produced exit 1 regardless of severity declaration. See ADR-017 for the rationale.
+
+---
+
 ## Presets and Layer Activation
 
 Presets control which layers are active. Choose based on project maturity and team discipline.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "phasegate",
-  "version": "0.130.0",
+  "version": "0.132.0",
   "packageManager": "pnpm@10.30.1",
   "description": "Phasegate — AI-agnostic quality defense toolkit. Enforces structural integrity between design intent and code.",
   "license": "MIT",

package/scripts/harness/config-foundation/application/mappers/validator-system-config-mapper.ts

@@ -1,7 +1,7 @@
 /**
  * @layer application
  * @unit config-foundation
- * @work-item-id WI-092
+ * @work-item-id WI-092 / WI-094
  */
 import type { HarnessConfigV2 } from '../../domain/harness-config.js';
 
@@ -15,5 +15,8 @@ export function toValidatorSystemConfig(resolvedConfig: HarnessConfigV2 | undefi
       L3: { enabled: resolvedConfig.layers.L3.enabled },
       L4: { enabled: resolvedConfig.layers.L4.enabled },
     },
+    validate: {
+      failOnWarning: resolvedConfig.validate.failOnWarning,
+    },
   };
 }

package/scripts/harness/config-foundation/domain/harness-config.ts

@@ -13,6 +13,7 @@ import { PlanningModeConfig } from './value-objects/planning-mode-config.js';
 import { ProjectConfig } from './value-objects/project-config.js';
 import { QuickModeConfig } from './value-objects/quick-mode-config.js';
 import { ReportingConfig } from './value-objects/reporting-config.js';
+import { ValidateConfig } from './value-objects/validate-config.js';
 import { HarnessesConfig } from './value-objects/harnesses-config.js';
 import type { FeatureNameValue } from './value-objects/feature-name.js';
 import type { FeatureName } from './value-objects/feature-name.js';
@@ -49,6 +50,7 @@ export interface HarnessConfigSourceDocument {
   harnesses: Partial<HarnessConfigResolvedDocument['harnesses']>;
   paths: HarnessConfigResolvedDocument['paths'];
   reporting: HarnessConfigResolvedDocument['reporting'];
+  validate?: HarnessConfigResolvedDocument['validate'];
   architecture?: ArchitectureConfigSource;
 }
 
@@ -108,6 +110,9 @@ export interface HarnessConfigResolvedDocument {
     format: string;
     outputDir: string;
   };
+  validate: {
+    failOnWarning: boolean;
+  };
   architecture?: ArchitectureConfigDocument;
 }
 
@@ -226,6 +231,7 @@ export class HarnessConfig {
   readonly planningMode: PlanningModeConfig;
   readonly paths: PathsConfig;
   readonly reporting: ReportingConfig;
+  readonly validate: ValidateConfig;
   harnesses: HarnessesConfig;
 
   private sourceDocument: HarnessConfigSourceDocument;
@@ -241,6 +247,7 @@ export class HarnessConfig {
     harnesses: HarnessesConfig;
     paths: PathsConfig;
     reporting: ReportingConfig;
+    validate: ValidateConfig;
     sourceDocument: HarnessConfigSourceDocument;
     resolvedDocument: HarnessConfigResolvedDocument;
     pendingEvents: readonly DomainEvent[];
@@ -253,6 +260,7 @@ export class HarnessConfig {
     this.harnesses = props.harnesses;
     this.paths = props.paths;
     this.reporting = props.reporting;
+    this.validate = props.validate;
     this.sourceDocument = deepClone(props.sourceDocument);
     this.resolvedDocument = deepClone(props.resolvedDocument);
     this.pendingEvents = [...props.pendingEvents];
@@ -271,6 +279,7 @@ export class HarnessConfig {
     const harnesses = HarnessesConfig.create(props.resolvedDocument.harnesses);
     const paths = PathsConfig.create(props.resolvedDocument.paths);
     const reporting = ReportingConfig.create(props.resolvedDocument.reporting);
+    const validate = ValidateConfig.create(props.resolvedDocument.validate);
 
     if (
       props.sourceDocument.project.preset !== props.resolvedDocument.project.preset
@@ -289,6 +298,7 @@ export class HarnessConfig {
       harnesses,
       paths,
       reporting,
+      validate,
       sourceDocument: props.sourceDocument,
       resolvedDocument: props.resolvedDocument,
       pendingEvents: props.pendingEvents ?? [],

package/scripts/harness/config-foundation/domain/services/preset-resolution-service.ts

@@ -18,6 +18,7 @@ export interface PresetDefinition {
   harnesses: HarnessConfigResolvedDocument['harnesses'];
   paths: HarnessConfigResolvedDocument['paths'];
   reporting: HarnessConfigResolvedDocument['reporting'];
+  validate: HarnessConfigResolvedDocument['validate'];
 }
 
 export class InvalidPresetDefinitionError extends ConfigFoundationDomainError {
@@ -113,6 +114,7 @@ function assertValidPresetDefinition(
     'harnesses',
     'paths',
     'reporting',
+    'validate',
   ];
 
   for (const key of requiredKeys) {
@@ -177,6 +179,11 @@ export class PresetResolutionService {
         sourceDocument.reporting,
         'reporting',
       ),
+      validate: deepMerge(
+        presetDefinition.validate,
+        sourceDocument.validate,
+        'validate',
+      ),
     };
   }
 

package/scripts/harness/config-foundation/domain/value-objects/validate-config.ts

@@ -0,0 +1,32 @@
+/**
+ * @layer domain
+ * @unit config-foundation
+ *
+ * バリデーション挙動設定を表す値オブジェクト (ADR-017 / WI-094)
+ * failOnWarning=true の場合、warning-only validator fail も overall FAIL として扱う
+ */
+import { ConfigValidationError } from '../errors/config-validation-error.js';
+
+export interface ValidateConfigProps {
+  readonly failOnWarning: boolean;
+}
+
+export class ValidateConfig {
+  readonly failOnWarning: boolean;
+
+  constructor(props: ValidateConfigProps) {
+    if (typeof props.failOnWarning !== 'boolean') {
+      throw new ConfigValidationError('failOnWarning は boolean でなければなりません');
+    }
+
+    this.failOnWarning = props.failOnWarning;
+  }
+
+  static create(raw: ValidateConfigProps): ValidateConfig {
+    return new ValidateConfig(raw);
+  }
+
+  equals(other: ValidateConfig): boolean {
+    return this.failOnWarning === other.failOnWarning;
+  }
+}

package/scripts/harness/config-foundation/infrastructure/presets/minimal.json

@@ -46,5 +46,8 @@
   "reporting": {
     "format": "json",
     "outputDir": "reports"
+  },
+  "validate": {
+    "failOnWarning": false
   }
 }

package/scripts/harness/config-foundation/infrastructure/presets/standard.json

@@ -46,5 +46,8 @@
   "reporting": {
     "format": "json",
     "outputDir": "reports"
+  },
+  "validate": {
+    "failOnWarning": false
   }
 }

package/scripts/harness/config-foundation/infrastructure/presets/strict.json

@@ -46,5 +46,8 @@
   "reporting": {
     "format": "json",
     "outputDir": "reports"
+  },
+  "validate": {
+    "failOnWarning": true
   }
 }

package/scripts/harness/config-foundation/infrastructure/schemas/harness-config-v2.schema.json

@@ -455,6 +455,15 @@
         }
       }
     },
+    "validate": {
+      "type": "object",
+      "additionalProperties": false,
+      "properties": {
+        "failOnWarning": {
+          "type": "boolean"
+        }
+      }
+    },
     "protectedFiles": {
       "type": "object",
       "additionalProperties": false,

package/scripts/harness/config-foundation/infrastructure/schemas/harness-config-v3.schema.json

@@ -455,6 +455,15 @@
         }
       }
     },
+    "validate": {
+      "type": "object",
+      "additionalProperties": false,
+      "properties": {
+        "failOnWarning": {
+          "type": "boolean"
+        }
+      }
+    },
     "protectedFiles": {
       "type": "object",
       "additionalProperties": false,

package/scripts/harness/main.ts

@@ -174,6 +174,20 @@ function hasFlag(args: readonly string[], flag: string): boolean {
   return args.includes(flag);
 }
 
+/**
+ * WI-094 / ADR-017: CLI で boolean フラグを tri-state に解釈する。
+ * - `--<flag>` 指定 → true
+ * - `--no-<flag>` 指定 → false
+ * - 両方未指定 → undefined (config 値にフォールバック)
+ * 両方同時指定された場合は後置を優先する。
+ */
+function parseTriStateFlag(args: readonly string[], positiveFlag: string, negativeFlag: string): boolean | undefined {
+  const positiveIdx = args.lastIndexOf(positiveFlag);
+  const negativeIdx = args.lastIndexOf(negativeFlag);
+  if (positiveIdx === -1 && negativeIdx === -1) return undefined;
+  return positiveIdx > negativeIdx;
+}
+
 function levenshtein(a: string, b: string): number {
   const m = a.length;
   const n = b.length;
@@ -994,7 +1008,8 @@ async function main(): Promise<void> {
         const unit = parseFlag(args, "--unit");
         const phase = parseFlag(args, "--phase");
         const format = parseFlag(args, "--format") as "human" | "agent" | "ci" | undefined;
-        const failOnWarning = hasFlag(args, "--fail-on-warning");
+        // WI-094 / ADR-017: --fail-on-warning / --no-fail-on-warning / 未指定→config値
+        const failOnWarning = parseTriStateFlag(args, "--fail-on-warning", "--no-fail-on-warning");
         const noL4 = hasFlag(args, "--no-l4");
         const targetPaths = parsePositionalArgs(args.slice(1), ["--layer", "--unit", "--phase", "--format"]);
         const result = await mod.handlers.runValidators.execute({

package/scripts/harness/validator-system/application/use-cases/aggregate-validation-results-usecase.ts

@@ -32,8 +32,12 @@ export class AggregateValidationResultsUseCase {
         continue;
       }
 
+      // ADR-017: warning-only validator fail は failOnWarning=false で overall PASS、true で従来挙動 (FAIL)
+      const hasNonWarningError = result.errors.some((e) => e.severity !== 'warning');
       const hasWarnings = result.errors.some((e) => e.severity === 'warning');
-      const hasFail = !result.passed || (failOnWarning && hasWarnings);
+      const isEmptyFail = !result.passed && result.errors.length === 0;
+      const hasFail =
+        !result.passed && (isEmptyFail || hasNonWarningError || (failOnWarning && hasWarnings));
 
       if (hasFail) {
         failedValidators++;

package/scripts/harness/validator-system/composition-root.ts

@@ -50,6 +50,7 @@ const DEFAULT_CONFIG = {
     L3: { enabled: true, validators: ['L3-001', 'L3-002', 'L3-003', 'L3-004'], coverageThreshold: 90, bundleSizeLimit: 512000 },
     L4: { enabled: true, validators: ['L4-001', 'L4-002', 'L4-003'] },
   },
+  validate: { failOnWarning: false },
 };
 
 /** バリデータ定義カタログ（全10件） */
@@ -111,6 +112,8 @@ export interface ValidatorSystemModule {
 export function createValidatorSystemModule(config?: object): ValidatorSystemModule {
   const configData = (config ?? DEFAULT_CONFIG) as typeof DEFAULT_CONFIG;
   const configPort = new HarnessConfigValidatorConfigAdapter(configData);
+  // WI-094 / ADR-017: validate.failOnWarning を handler に伝搬。config 未指定時は false
+  const defaultFailOnWarning = configData.validate?.failOnWarning ?? false;
   const registry = buildDefaultRegistry();
   const executionService = new ValidatorExecutionService({ configPort });
   const contractMapper = new ValidationResultContractMapper();
@@ -215,7 +218,12 @@ export function createValidatorSystemModule(config?: object): ValidatorSystemMod
   });
 
   const handlers = {
-    runValidators: new RunValidatorsHandler({ runFullValidationUseCase, runL0ValidatorsUseCase, runL1ValidatorsUseCase }),
+    runValidators: new RunValidatorsHandler({
+      runFullValidationUseCase,
+      runL0ValidatorsUseCase,
+      runL1ValidatorsUseCase,
+      defaultFailOnWarning,
+    }),
     runQuickMode: new RunQuickModeHandler({ runQuickModeUseCase }),
     reportValidationResults: new ReportValidationResultsHandler(),
   };

package/scripts/harness/validator-system/domain/value-objects/consistency-report.ts

@@ -43,10 +43,11 @@ export class ConsistencyReport {
     return this.mismatchPairs.length;
   }
 
+  // ADR-017 / WI-094: error catalog の defaultSeverity: warning と整合
   toHarnessErrors(): readonly HarnessErrorLike[] {
     return this.mismatchPairs.map((pair) => ({
       code: { value: 'L4-002', toString: () => 'L4-002' },
-      severity: { value: 'error', toString: () => 'error' },
+      severity: { value: 'warning', toString: () => 'warning' },
       message: `レイヤー整合性違反: expected "${pair.expected}" but got "${pair.actual}" at ${pair.location}`,
       suggestion: '設計文書間のレイヤー依存方向を統一してください',
     }));

package/scripts/harness/validator-system/domain/value-objects/dead-code-report.ts

@@ -38,12 +38,13 @@ export class DeadCodeReport {
     return this.unusedExports.length > 0 || this.unreachableCode.length > 0;
   }
 
+  // ADR-017 / WI-094: error catalog の defaultSeverity: warning と整合
   toHarnessErrors(): readonly HarnessErrorLike[] {
     const errors: HarnessErrorLike[] = [];
     for (const exportId of this.unusedExports) {
       errors.push({
         code: { value: 'L4-003', toString: () => 'L4-003' },
-        severity: { value: 'error', toString: () => 'error' },
+        severity: { value: 'warning', toString: () => 'warning' },
         message: `未使用エクスポート: ${exportId}`,
         suggestion: '未使用エクスポートを削除するか、他ファイルからimportしてください',
       });
@@ -51,7 +52,7 @@ export class DeadCodeReport {
     for (const loc of this.unreachableCode) {
       errors.push({
         code: { value: 'L4-003', toString: () => 'L4-003' },
-        severity: { value: 'error', toString: () => 'error' },
+        severity: { value: 'warning', toString: () => 'warning' },
         message: `到達不能コード: ${loc.filePath}:${loc.range.startLine}-${loc.range.endLine}`,
         suggestion: '到達不能なコードブロックを削除してください',
       });

package/scripts/harness/validator-system/domain/value-objects/drift-report.ts

@@ -42,9 +42,10 @@ export class DriftReport {
   }
 
   toHarnessError(): HarnessErrorLike {
+    // ADR-017 / WI-094: error catalog の defaultSeverity: warning と整合
     return {
       code: { value: 'L4-001', toString: () => 'L4-001' },
-      severity: { value: 'error', toString: () => 'error' },
+      severity: { value: 'warning', toString: () => 'warning' },
       message: `乖離検出 [${this.direction}] Unit: ${this.unitName}, Element: ${this.element}`,
       suggestion: this.recommendation,
     };

package/scripts/harness/validator-system/presentation/formatters/human-validation-result-formatter.ts

@@ -15,7 +15,15 @@ export class HumanValidationResultFormatter {
     lines.push('');
 
     for (const result of report.results) {
-      const status = result.skipped ? 'SKIP' : result.passed ? 'PASS' : 'FAIL';
+      // WI-094 / ADR-017: warning-only fail は [WARN]、error severity を含む fail は [FAIL]
+      const hasNonWarningError = result.errors.some((e) => e.severity !== 'warning');
+      const status = result.skipped
+        ? 'SKIP'
+        : result.passed
+          ? 'PASS'
+          : hasNonWarningError || result.errors.length === 0
+            ? 'FAIL'
+            : 'WARN';
       lines.push(`[${status}] ${result.validatorId} (${result.durationMs}ms)`);
       for (const error of result.errors) {
         lines.push(`  ⚠ ${error.message}`);

package/scripts/harness/validator-system/presentation/handlers/run-validators-handler.ts

@@ -27,17 +27,21 @@ export interface RunValidatorsHandlerDeps {
   runFullValidationUseCase: RunFullValidationUseCase;
   runL0ValidatorsUseCase?: RunL0ValidatorsUseCase;
   runL1ValidatorsUseCase?: RunL1ValidatorsUseCase;
+  /** WI-094 / ADR-017: config 由来の failOnWarning デフォルト。args.failOnWarning が undefined の場合に適用 */
+  defaultFailOnWarning?: boolean;
 }
 
 export class RunValidatorsHandler {
   private readonly useCase: RunFullValidationUseCase;
   private readonly l0UseCase: RunL0ValidatorsUseCase | undefined;
   private readonly l1UseCase: RunL1ValidatorsUseCase | undefined;
+  private readonly defaultFailOnWarning: boolean;
 
   constructor(deps: RunValidatorsHandlerDeps) {
     this.useCase = deps.runFullValidationUseCase;
     this.l0UseCase = deps.runL0ValidatorsUseCase;
     this.l1UseCase = deps.runL1ValidatorsUseCase;
+    this.defaultFailOnWarning = deps.defaultFailOnWarning ?? false;
   }
 
   async execute(args: RunValidatorsHandlerArgs): Promise<{ output: string; exitCode: number }> {
@@ -118,12 +122,13 @@ export class RunValidatorsHandler {
       else if (args.layer === 'all') targetLayers = ['L2', 'L3', 'L4'];
       // undefined → フィルタなし（従来挙動）
 
+      const failOnWarning = args.failOnWarning ?? this.defaultFailOnWarning;
       const report = await this.useCase.execute({
         targetPaths: args.targetPaths ?? [],
         unitName: args.unit ?? '',
         currentPhase: args.phase ?? '',
         includeL4: !args.noL4,
-        failOnWarning: args.failOnWarning,
+        failOnWarning,
         targetLayers,
       });