phasegate 0.83.0 → 0.91.0

package/CHANGELOG.md

@@ -7,6 +7,150 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.91.0] - 2026-04-23
+
+### Fixed
+
+- **ISSUE-023: `StoryId` validator pattern が `HF\d+-\d{2}` を拒否する** — `HF2-XX` 形式（Phase 2 拡張 Epic）を正式サポート。
+  - `scripts/harness/traceability-model/domain/value-objects/story-id.ts`: `STORY_ID_PATTERN` を `/^H(?<epicNumber>F\d+|\d{2})-(?<storyNumber>\d{2})$/` に拡張。エラーメッセージも更新。
+  - `scripts/harness/traceability-model/domain/services/metadata-validator.ts:16`: `STORY_ID_PATTERN` を `/^H(?:F\d+|[0-9]{2})-[0-9]{2}$/` に同期。
+  - `scripts/harness/traceability-model/infrastructure/parsers/story-catalog-parser.ts`: `STORY_ID_LINE_PATTERN` と前後行コンテキスト形式の内部パターンを同期。`user_stories.md` から `HF2-XX` を StoryCatalog に収集可能に。
+  - `StoryId.getEpicNumber()` は `HF2-04` に対して `'F2'` を返す（従来の 2 桁数字は不変）。外部 API shape は維持。
+- **ISSUE-010 完全 CLOSE（副次効果）** — `validate-metadata` FAIL: 103 → **0 件**。`docs/product/construction/` 配下の全 105 設計文書が PASS。Wave 1 (v0.87.0) / Wave 2 (v0.88.0) / Wave 3 (v0.89.0) / fuse-hooks-engine 削除 (v0.90.0) / 本リリースで完結。
+
+### Tests
+
+- `scripts/harness/__tests__/unit/traceability-model/story-id.test.ts` に HF prefix ケース 3 件追加（3308 → 3311）:
+  - `HF2-04` を正常に parse できること
+  - `HF10-99` のような複数桁 F-prefix も受理すること
+  - `HF2-04` の `getEpicNumber()` が `'F2'` を返すこと
+
+### Lint / Metadata state
+
+- L1 violations: **0 件維持**（scanned 1289 files, no violations）
+- `validate-metadata` FAIL: 7 → **0 件** 🎉
+- 3311 件テスト全 green
+
+## [0.90.0] - 2026-04-23
+
+### Removed
+
+- **fuse-hooks-engine Unit の完全削除** — Unit 定義（`docs/product/units/fuse_hooks_engine_unit.md`）・設計文書（`docs/product/construction/fuse-hooks-engine/` 7 件）・inception プラン（`docs/inception/fuse-hooks-engine/` 配下 8 件）を削除。
+  - `scripts/harness/` 配下に実装コードは一切存在せず、他 Unit からの import / 参照もなかった（Future Phase / v1 スコープ外として設計段階で凍結されていた Unit）。
+  - `docs/product/user_stories.md` から HF1-01 〜 HF1-05 の 5 ストーリーセクションと `H-F1` Epic 行を削除。v1 合計を 54 維持、全体（Future 含む）を 62 → 57 に更新。
+  - `docs/product/units/integration_contract.md` の依存図・Wave 実行計画・Validator ID Registry / CLI Command Registry の `fuse-hooks-engine` 参照を削除。L0 拡張ポイント（6.1 / 6.3）は「OS-level enforcement」の抽象概念として残置。
+  - `docs/product/units/agent_integration_unit.md` Stop Hook Adapter 行の `fuse-hooks-engine（Future: FUSE完了ゲートの参照実装）` 参照を `—` に変更。
+  - `docs/product/construction/agent-integration/unit_test_design.md` UT-WTS-I021 のサンプルパスを `fuse-hooks-engine/HF1-06` → `some-unit/HF1-06` に変更（WORK_ITEM_ID_PATTERN 後方互換テストは維持）。
+
+### Fixed
+
+- **ISSUE-010 Wave 3 完全解消（fuse-hooks-engine 削除の副次効果）** — `validate-metadata` FAIL: 14 → **7**（fuse-hooks-engine 7 ファイル消失）。残 7 は `phase2-extensions` の `HF2-XX` 形式 StoryId で、validator `STORY_ID_PATTERN = /^H[0-9]{2}-[0-9]{2}$/` の拡張が別 issue 対象。
+
+### Lint / Metadata state
+
+- L1 violations: **0 件維持**（scanned 1289 files, no violations）
+- `validate-metadata` FAIL: 14 → **7**（-7）
+- 既存 3308 件テスト全 green（regression なし）
+
+## [0.89.0] - 2026-04-23
+
+### Fixed
+
+- **ISSUE-010 Wave 3（partial）** — 11 Unit × 7 設計文書 = 75 件に `@story-id` standalone 注釈を補填し PASS 化。
+  - `agent-integration` / `biome-ast-engine` / `ci-governance` / `harness-api` / `harness-error` / `nyquist-validation` / `phase-dependency-model` / `quick-mode` / `regression-suite` / `skill-quality` / `validator-system` の各 Unit の 7 ファイル（`coverage_report.md` / `domain_model.md` / `it_test_design.md` / `it_test_logic.md` / `logical_design.md` / `unit_test_design.md` / `unit_test_logic.md`）に H01-H15 系 StoryId を付与。
+  - 残 14 件（`fuse-hooks-engine` 7 + `phase2-extensions` 7）は `HF1-XX` / `HF2-XX` 形式の StoryId を必要とするが、`metadata-validator.STORY_ID_PATTERN = /^H[0-9]{2}-[0-9]{2}$/` が `HF` prefix 非対応のため PASS 化不可能。validator パターン拡張は別 issue 対象（ISSUE-019）として切り出し、本 Wave 3 は partial 完了。
+
+### Lint / Metadata state
+
+- L1 violations: **0 件維持**
+- `validate-metadata` FAIL: 89 → **14**（-75: 11 Unit × 7 ファイル解消）
+- 残 14 件は HF-prefix validator 制約による既知の限界（新規回帰ではない）
+- 既存 3308 件テスト全 green（regression なし）
+
+## [0.88.0] - 2026-04-23
+
+### Fixed
+
+- **ISSUE-010 Wave 2** — `adr-foundation` / `config-foundation` Unit の設計文書 11 件に `@story-id` 注釈を standalone 形式で補填。
+  - adr-foundation 6 件（`coverage_report.md` / `domain_model.md` / `it_test_design.md` / `it_test_logic.md` / `unit_test_design.md` / `unit_test_logic.md`）に `@story-id H05-01 / H05-02 / H05-03` を追加。
+  - config-foundation 5 件（`coverage_report.md` / `domain_model.md` / `it_test_logic.md` / `unit_test_design.md` / `unit_test_logic.md`）に `@story-id H04-01 / H04-02 / H04-03` を追加。
+  - これにより両 Unit とも全 7 ファイル PASS 達成。
+
+### Lint / Metadata state
+
+- L1 violations: **0 件維持**
+- `validate-metadata` FAIL: 100 → **89**（adr-foundation 6 件 + config-foundation 5 件解消）
+- 既存 3308 件テスト全 green（regression なし）
+
+## [0.87.0] - 2026-04-23
+
+### Fixed
+
+- **ISSUE-010 Wave 1 + ISSUE-006 formal CLOSE** — traceability-model Unit の `@story-id` 注釈補填と ISSUE-006 機能的完遂の CLOSE 化。
+  - ISSUE-010 Wave 1: `docs/product/construction/traceability-model/` 残 3 件（`coverage_report.md` / `domain_model.md` / `unit_test_logic.md`）に `@story-id H03-01 / H03-02 / H03-03` を standalone 注釈として補填。`validate-metadata` の FAIL 件数 103 → 100（traceability-model Unit は 0 件到達）。
+  - ISSUE-006 CLOSE: Story A（v0.63.0 / `fullModeRequiredWhen` 設定駆動化）/ Story B（v0.64.0 / pre-tool-use hook 統合）/ P2-3（v0.45.0 / `docs/guide/quick-vs-full-mode.md`）すべて着地済のため formal CLOSE。外部PJ再レビュー（welcome-but-not-blocking）のみ残。
+
+### Lint / Metadata state
+
+- L1 violations: **0 件維持**（v0.86.0 時点で完全解消済、本版で変更なし）
+- `validate-metadata` FAIL: 103 → **100**（traceability-model 3 件解消）
+- 既存 3308 件テスト全 green（regression なし）
+
+## [0.86.0] - 2026-04-23
+
+### Changed
+
+- **ISSUE-019 / ADR-014** — LayerBoundary の解釈を **Robert C. Martin 版 Clean Architecture** に切り替え、`presentation → domain` 直接依存を許容。
+  - 変更: `ALLOWED_DEPENDENCIES.presentation` に `'domain'` を追加（`scripts/harness/biome-ast-engine/domain/value-objects/layer-name.ts:15-20`）。
+  - 背景: 従来の厳格 DDD Layered 解釈では presenter / formatter / CLI handler が domain VO / type / policy を read-only で参照するだけで L1-003 違反となっていたが、これは CA では一般的実装。read-only で DIP の本質を侵さない限り許容する。
+  - 禁止は継続: `presentation → infrastructure`、`domain → 他層`、`application → presentation` 等の逆方向依存。
+  - 緩和策の opt-in 提供は ISSUE-014（アーキ config 化）で対応予定。厳格派は `preset: "strict-ddd"` で現行挙動を維持可能とする。
+  - 新規 ADR: `docs/ADR/ADR-014-presentation-domain-dependency.md`。
+  - 新規 test: `layer-boundary.test.ts` に presentation→domain allowed、presentation→infrastructure disallowed の 2 ケース追加。
+
+### Lint state
+
+- total: 8 → **0**（L1-003 presentation→domain 8 件解消、他 rule 増減無し）
+- 既存 3308 件テスト全 green（新規 2 ケース込み）
+
+## [0.85.0] - 2026-04-23
+
+### Fixed
+
+- **ISSUE-022** — Unit barrel (`**/index.ts`) が `no-layer-violation` で誤検知される問題を解消。
+  - 問題: ISSUE-017（v0.83.0）の `extractImports` 修正で `export ... from` 再帰走査が有効化された結果、`quick-mode/index.ts` の barrel 再エクスポート 7 件が `L1-003` で新規露出していた。Unit barrel は `main.ts` / `composition-root.ts` / `presentation/*-hook.ts` と同じ composition root / entry point の性質を持つが、`no-layer-violation.ignorePatterns` に含まれていなかった。
+  - 修正: `scripts/harness/biome-ast-engine/domain/services/rule-definition-registry.ts` の `no-layer-violation.ignorePatterns` に `'**/index.ts'` を追加。`scripts/harness/*/index.ts` の 11 件の Unit barrel が一括で除外される（sub-layer barrel は存在せず副作用リスク無）。
+  - 残 L1-003 8 件は全て `presentation → domain` パターン（ISSUE-019 の philosophical 案件スコープ）。
+
+### Lint state
+
+- total: 15 → **8**（L1-003 barrel 誤検知 7 件解消）
+- 残 L1-003: 8 件（全て ISSUE-019 スコープ: presentation → domain）
+- 既存 3306 件テスト全 green（regression なし）
+
+## [0.84.0] - 2026-04-23
+
+### Removed
+
+- **L1-006 解消** — `adr-foundation` の never-wired な seed 機能を削除。
+  - `scripts/harness/adr-foundation/infrastructure/seeds/initial-adr-definitions.ts` (11 件の seed 定義、docs/ADR/ 13 件の実 ADR と内容不一致で stale だった)
+  - `scripts/harness/adr-foundation/application/usecases/seed-initial-adrs-use-case.ts`
+  - `scripts/harness/adr-foundation/application/dto/seed-adr-definition.ts`
+  - `scripts/harness/__tests__/unit/adr-foundation/seed-initial-adrs-use-case.test.ts` (6 tests)
+  - `application-errors.ts` から未使用になった `SeedAdrDefinitionCountError` / `DuplicateAdrIdApplicationError` を削除
+  - `infrastructure/seeds/` ディレクトリ自体を削除
+  - composition-root に未配線・CLI 未公開だったため外部影響なし。実 ADR は `docs/ADR/` に直接 markdown として管理済み。
+
+### Fixed
+
+- **L1-007 解消** — `agent-integration/domain/ports/error-guidance-query-port.ts` の JSDoc コメント密度超過を修正。WHAT を説明する冗長コメントを削除（型名から自明）。
+
+### Lint state
+
+- total: 17 → **15**（L1-006: 1 → 0, L1-007: 1 → 0）
+- 残 L1-003: 15 件（全て ISSUE-019 スコープ: barrel 再エクスポート 7 件 + presentation→domain 8 件）
+- 既存 3312 件 - 6 件削除 = **3306 件** テスト全 green
+
 ## [0.83.0] - 2026-04-23
 
 ### Fixed

package/docs/ADR/ADR-014-presentation-domain-dependency.md

@@ -0,0 +1,82 @@
+# ADR-014: presentation → domain 直接依存を許容する（Robert C. Martin 版 Clean Architecture 準拠）
+
+## Status
+
+Accepted — 2026-04-23
+
+## Context
+
+ADR-005 で採用した Hexagonal Architecture の派生で、phasegate の L1-003 `no-layer-violation` は当初 **presentation layer は presentation + application にしか依存できない**という厳格 DDD Layered 解釈を採用していた（`scripts/harness/biome-ast-engine/domain/value-objects/layer-name.ts:ALLOWED_DEPENDENCIES`）。
+
+しかしこの解釈では、Clean Architecture 実装として一般的な以下のパターンが全て L1-003 違反として flag される:
+
+- Presenter が Domain VO の値を読み取って表示用文字列に整形する
+- Formatter が Domain Service（policy 系）の判定を呼んで整形する
+- CLI handler が Domain Type（discriminated union 等）を switch して分岐する
+
+ISSUE-019 で監査した時点で 8 件の違反が存在し、いずれも「read-only で VO/type/policy を display/format する」パターンで、Dependency Inversion Principle の本質（domain が外部の詳細に依存しない）は侵していなかった。
+
+### 哲学的立場の整理
+
+| 派 | `presentation → domain` | 出典 |
+|---|---|---|
+| **Robert C. Martin 版 Clean Architecture** | ✅ 許容 | presenter は "Interface Adapters" ring にあり、Entity/VO は Enterprise Business Rules として全 ring から参照可能 |
+| **厳格 DDD Layered** | ❌ 禁止 | presentation は application 経由で DTO を受け取り、domain を直接触らない |
+| **phasegate 旧実装** | ❌ 禁止 | 厳格 DDD 派を採用（実装時の暗黙判断） |
+
+## Decision
+
+`ALLOWED_DEPENDENCIES.presentation` に `'domain'` を追加し、**Robert C. Martin 版 Clean Architecture の解釈を phasegate 標準とする**:
+
+```typescript
+const ALLOWED_DEPENDENCIES = {
+  domain:         ['domain'],
+  application:    ['application', 'domain'],
+  infrastructure: ['infrastructure', 'application', 'domain'],
+  presentation:   ['presentation', 'application', 'domain'],  // domain を追加
+};
+```
+
+### 許容される具体パターン
+
+- presenter/formatter が Domain VO を read-only で取得して表示用文字列に変換
+- CLI handler が Domain Type を参照して分岐
+- formatter が Domain Service の pure method（副作用なし）を呼んで判定
+
+### 依然として禁止されるパターン
+
+- presentation → infrastructure の直接依存（DB/CLI/FS 直叩き）
+- presentation から domain VO の mutation（domain は read-only で扱う）
+- domain → presentation / application / infrastructure の逆方向依存（Dependency Inversion の核）
+
+`infrastructure → domain` と `application → domain` の既存許容は維持。
+
+## Consequences
+
+### ポジティブ
+
+- 既存 8 件の false positive が解消（L1-003 が 8 → 0 件）
+- phasegate を他 PJ に導入したとき、Robert Martin 流 CA を採用している PJ で摩擦が激減
+- `domain VO の直接 read` を presentation で許容する CA 一般的実装が lint を通るようになる
+
+### ネガティブ / トレードオフ
+
+- 厳格 DDD 派（presentation → application → domain を強制したい PJ）では緩すぎる
+  - **緩和策**: ISSUE-014（アーキテクチャスタイル config 化）で `preset: "strict-ddd"` を選択肢として提供予定。厳格派は opt-in できる
+- presenter が domain mutation を行うリスクは残る
+  - **緩和策**: domain VO を immutable（`readonly` + `Object.freeze`）に保つ既存 ADR-009（DDD Tactical Patterns）の規約で抑止
+
+### スコープ外（本 ADR で扱わない）
+
+- application → presentation などの逆方向（Dependency Inversion 違反）の許容は検討対象外
+- domain から他層への依存の許容は検討対象外
+- preset による選択的緩和（`strict-ddd` / `classic-ca` / `custom` 等）は ISSUE-014 の範疇
+
+## 関連
+
+- `scripts/harness/biome-ast-engine/domain/value-objects/layer-name.ts:15-20` — ALLOWED_DEPENDENCIES 実体
+- `scripts/harness/biome-ast-engine/domain/value-objects/layer-boundary.ts:31-45` — standardMatrix
+- ADR-005 (Hexagonal Architecture 採用) — 本 ADR はその依存方向規則の一部緩和
+- ADR-009 (DDD Tactical Patterns) — domain immutability 規約で mutation リスクを抑止
+- ISSUE-019 (LayerBoundary 再評価) — 本 ADR で CLOSED
+- ISSUE-014 (architecture style config) — preset 化での opt-in 厳格派提供を予定

package/package.json

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

package/scripts/harness/adr-foundation/application/dto/application-errors.ts

@@ -9,13 +9,6 @@ export class AdrNotFoundApplicationError extends Error {
   }
 }
 
-export class DuplicateAdrIdApplicationError extends Error {
-  constructor(adrRef: string) {
-    super(`ADR ID が重複しています: ${adrRef}`);
-    this.name = 'DuplicateAdrIdApplicationError';
-  }
-}
-
 export class SupersededTargetNotFoundApplicationError extends Error {
   constructor(adrRef: string) {
     super(`superseded_by の参照先ADRが存在しません: ${adrRef}`);
@@ -51,9 +44,3 @@ export class InvalidAdrDateError extends Error {
   }
 }
 
-export class SeedAdrDefinitionCountError extends Error {
-  constructor(actualCount: number) {
-    super(`初期ADR定義は11件である必要があります: ${actualCount}`);
-    this.name = 'SeedAdrDefinitionCountError';
-  }
-}

package/scripts/harness/agent-integration/domain/ports/error-guidance-query-port.ts

@@ -1,20 +1,12 @@
 // @unit agent-integration
 // @layer domain
 
-/**
- * phase-gate 等のエラーに紐づく actionable なガイダンス情報
- * （harness-error Unit の ErrorDefinition.defaultSuggestedSkill 等から供給される）
- */
 export interface ErrorGuidance {
   readonly suggestedSkill: string | null;
   readonly scaffoldCommand: string | null;
   readonly templatePath: string | null;
 }
 
-/**
- * エラーコード → actionable guidance の lookup を行う port
- * 実装は harness-error Unit の ErrorDefinitionRegistry を参照する
- */
 export interface ErrorGuidanceQueryPort {
   getGuidance(errorCode: string): Promise<ErrorGuidance | null>;
 }

package/scripts/harness/biome-ast-engine/domain/services/rule-definition-registry.ts

@@ -135,6 +135,7 @@ export class RuleDefinitionRegistry {
             '**/composition-root.ts',
             '**/main.ts',
             '**/presentation/*-hook.ts',
+            '**/index.ts',
           ]),
         }),
         'レイヤー違反を検出する',

package/scripts/harness/biome-ast-engine/domain/value-objects/layer-name.ts

@@ -16,7 +16,7 @@ const ALLOWED_DEPENDENCIES: Readonly<Record<LayerNameValue, readonly LayerNameVa
   domain: Object.freeze(['domain']),
   application: Object.freeze(['application', 'domain']),
   infrastructure: Object.freeze(['infrastructure', 'application', 'domain']),
-  presentation: Object.freeze(['presentation', 'application']),
+  presentation: Object.freeze(['presentation', 'application', 'domain']),
 };
 
 export class InvalidLayerNameError extends Error {

package/scripts/harness/traceability-model/domain/services/metadata-validator.ts

@@ -13,7 +13,7 @@ import {
 import type { StoryIdLike } from '../value-objects/story-reference.js';
 import type { StoryIdAnnotation } from '../value-objects/story-id-annotation.js';
 
-const STORY_ID_PATTERN = /^H[0-9]{2}-[0-9]{2}$/;
+const STORY_ID_PATTERN = /^H(?:F\d+|[0-9]{2})-[0-9]{2}$/;
 const VALID_LAYER_NAMES = new Set([
   'domain',
   'application',

package/scripts/harness/traceability-model/domain/value-objects/story-id.ts

@@ -2,13 +2,13 @@
  * @layer domain
  * @unit traceability-model
  *
- * HXX-XX形式の正規ストーリーID
+ * HXX-XX形式の正規ストーリーID（Phase 2 拡張 Epic として HF\d+-XX も許容）
  */
-const STORY_ID_PATTERN = /^H(?<epicNumber>[0-9]{2})-(?<storyNumber>[0-9]{2})$/;
+const STORY_ID_PATTERN = /^H(?<epicNumber>F\d+|\d{2})-(?<storyNumber>\d{2})$/;
 
 export class StoryIdFormatError extends Error {
   constructor(value: string) {
-    super(`StoryIdはHXX-XX形式で指定してください: ${value}`);
+    super(`StoryIdはHXX-XX形式（HF\\d+-XX も可）で指定してください: ${value}`);
     this.name = 'StoryIdFormatError';
   }
 }

package/scripts/harness/traceability-model/infrastructure/parsers/story-catalog-parser.ts

@@ -10,7 +10,7 @@ export interface ParsedStoryCatalog {
   readonly aliasMap: ReadonlyMap<string, string>;
 }
 
-const STORY_ID_LINE_PATTERN = /\bH[0-9]{2}-[0-9]{2}\b/g;
+const STORY_ID_LINE_PATTERN = /\bH(?:F\d+|[0-9]{2})-[0-9]{2}\b/g;
 const TABLE_ALIAS_PATTERN =
   /\|\s*(H[0-9]{2}-[0-9]{2})\s*\|.*?\|\s*(US-[0-9]{3})\s*\|/g;
 const INLINE_ALIAS_PATTERN =
@@ -58,7 +58,7 @@ export function parseStoryCatalog(content: string): ParsedStoryCatalog {
 
   // 前後行コンテキスト形式: H03-01 の直後に 旧US: US-001
   for (let i = 0; i < lines.length; i++) {
-    const storyIdMatch = /\b(H[0-9]{2}-[0-9]{2})\b/.exec(lines[i]);
+    const storyIdMatch = /\b(H(?:F\d+|[0-9]{2})-[0-9]{2})\b/.exec(lines[i]);
     if (storyIdMatch) {
       const nextLine = i + 1 < lines.length ? lines[i + 1] : '';
       const legacyMatch = /旧US\s*[:：]\s*(US-[0-9]{3})/.exec(nextLine);

package/scripts/harness/adr-foundation/application/dto/seed-adr-definition.ts

@@ -1,21 +0,0 @@
-/**
- * @layer application
- * @unit adr-foundation
- */
-export interface SeedAdrDefinition {
-  readonly title: string;
-  readonly status: 'Proposed' | 'Accepted' | 'Deprecated' | 'Superseded';
-  readonly date: string;
-  readonly body: {
-    readonly context: string;
-    readonly decision: string;
-    readonly consequences: string;
-    readonly alternatives?: string;
-  };
-  readonly archgate?: {
-    readonly enforcedBy: ReadonlyArray<{
-      readonly validatorId: string;
-      readonly errorCode: string;
-    }>;
-  };
-}

package/scripts/harness/adr-foundation/application/usecases/seed-initial-adrs-use-case.ts

@@ -1,84 +0,0 @@
-/**
- * @layer application
- * @unit adr-foundation
- */
-import { ADR } from '../../domain/aggregates/adr.js';
-import type { AdrDocumentParserPort } from '../../domain/ports/adr-document-parser-port.js';
-import type { AdrRepositoryPort } from '../../domain/ports/adr-repository-port.js';
-import { AdrValidationService } from '../../domain/services/adr-validation-service.js';
-import { AdrId } from '../../domain/value-objects/adr-id.js';
-import {
-  DuplicateAdrIdApplicationError,
-  SeedAdrDefinitionCountError,
-} from '../dto/application-errors.js';
-import type { SeedAdrDefinition } from '../dto/seed-adr-definition.js';
-
-export interface SeedInitialAdrsInput {
-  readonly definitions: SeedAdrDefinition[];
-  readonly overwrite?: boolean;
-}
-
-export interface SeedInitialAdrsOutput {
-  readonly created: readonly string[];
-  readonly skipped: readonly string[];
-}
-
-export class SeedInitialAdrsUseCase {
-  constructor(
-    private readonly adrRepository: AdrRepositoryPort,
-    private readonly documentParser: AdrDocumentParserPort,
-  ) {}
-
-  async execute(input: SeedInitialAdrsInput): Promise<Readonly<SeedInitialAdrsOutput>> {
-    if (input.definitions.length !== 11) {
-      throw new SeedAdrDefinitionCountError(input.definitions.length);
-    }
-
-    const created: string[] = [];
-    const skipped: string[] = [];
-
-    for (const [index, definition] of input.definitions.entries()) {
-      const adrId = AdrId.create(String(index + 1).padStart(3, '0'));
-      const adrRef = adrId.toAdrRef();
-
-      if (created.includes(adrRef) || skipped.includes(adrRef)) {
-        throw new DuplicateAdrIdApplicationError(adrRef);
-      }
-
-      const adr = ADR.create(
-        {
-          adr_id: adrId.value,
-          title: definition.title,
-          status: definition.status,
-          date: definition.date,
-          archgate: definition.archgate
-            ? {
-                adr_id: adrId.value,
-                enforced_by: definition.archgate.enforcedBy.map((entry) => ({
-                  validator_id: entry.validatorId,
-                  error_code: entry.errorCode,
-                })),
-              }
-            : undefined,
-        },
-        definition.body,
-        new AdrValidationService(),
-      );
-
-      const exists = await this.adrRepository.exists(adrId);
-      if (exists && input.overwrite !== true) {
-        skipped.push(adrRef);
-        continue;
-      }
-
-      this.documentParser.serializeDocument(adr);
-      await this.adrRepository.save(adr);
-      created.push(adrRef);
-    }
-
-    return Object.freeze({
-      created: Object.freeze(created),
-      skipped: Object.freeze(skipped),
-    });
-  }
-}

package/scripts/harness/adr-foundation/infrastructure/seeds/initial-adr-definitions.ts

@@ -1,161 +0,0 @@
-/**
- * @layer infrastructure
- * @unit adr-foundation
- */
-import type { SeedAdrDefinition } from '../../application/dto/seed-adr-definition.js';
-
-export const INITIAL_ADR_DEFINITIONS: readonly SeedAdrDefinition[] = [
-  {
-    title: 'Package separation',
-    status: 'Accepted',
-    date: '2026-03-13',
-    body: {
-      context:
-        'The harness codebase has grown beyond a single-package structure. Build times increase and cross-cutting changes create unnecessary coupling.',
-      decision:
-        'Separate the repository into discrete packages aligned with bounded contexts, each with its own build and test lifecycle.',
-      consequences:
-        'Packages can evolve independently. CI must orchestrate multi-package builds. Shared kernel contracts must be explicitly published.',
-    },
-  },
-  {
-    title: 'Full migration from ESLint to Biome',
-    status: 'Accepted',
-    date: '2026-03-13',
-    body: {
-      context:
-        'The project currently uses ESLint for linting. Biome offers faster execution and unified formatting with linting in a single tool.',
-      decision:
-        'Migrate all linting and formatting from ESLint and Prettier to Biome as the sole toolchain.',
-      consequences:
-        'Tooling becomes simpler and faster. Custom ESLint rules must be re-implemented as Biome plugins or GritQL patterns.',
-      alternatives:
-        'Keep dual toolchain with ESLint for rules not yet supported by Biome.',
-    },
-  },
-  {
-    title: 'Quality harness owns K1-K13',
-    status: 'Accepted',
-    date: '2026-03-13',
-    body: {
-      context:
-        'Quality indicators K1 through K13 are defined across multiple documents with no single owner enforcing them.',
-      decision:
-        'The quality harness unit owns the enforcement of all K1-K13 indicators, providing validators and gates for each.',
-      consequences:
-        'A single unit is accountable for quality enforcement. Other units must integrate through the harness contract rather than implementing ad-hoc checks.',
-    },
-  },
-  {
-    title: 'FUSE Hooks Engine is out of v1 scope',
-    status: 'Proposed',
-    date: '2026-03-13',
-    body: {
-      context:
-        'The FUSE Hooks Engine provides extensible event-driven hooks but adds significant complexity to the initial delivery.',
-      decision:
-        'Defer the FUSE Hooks Engine to a post-v1 phase. The v1 harness will use direct invocation patterns.',
-      consequences:
-        'Reduced initial scope and risk. Hook-based extensibility will require a migration path when introduced later.',
-      alternatives:
-        'Include a minimal hooks engine in v1 with limited extensibility.',
-    },
-  },
-  {
-    title: 'HarnessError requires fix_example',
-    status: 'Accepted',
-    date: '2026-03-13',
-    body: {
-      context:
-        'Developers receiving harness errors often lack actionable guidance on how to resolve violations.',
-      decision:
-        'Every HarnessError definition must include a fix_example field demonstrating the corrective action.',
-      consequences:
-        'Error definitions are more verbose but significantly more useful. All existing error definitions must be updated to include examples.',
-    },
-  },
-  {
-    title: 'Strict quick mode eligibility',
-    status: 'Accepted',
-    date: '2026-03-13',
-    body: {
-      context:
-        'Quick mode bypasses expensive validators but must not compromise quality gates for critical changes.',
-      decision:
-        'Define strict eligibility criteria for quick mode based on file change scope and affected layers.',
-      consequences:
-        'Quick mode runs faster for eligible changes. Complex cross-layer changes always run the full validator stack.',
-      alternatives:
-        'Allow developers to manually opt into quick mode regardless of change scope.',
-    },
-  },
-  {
-    title: 'Separate config files',
-    status: 'Accepted',
-    date: '2026-03-13',
-    body: {
-      context:
-        'A single monolithic configuration file makes it difficult to manage unit-specific settings and increases merge conflicts.',
-      decision:
-        'Split configuration into separate files per concern: phasegate.config.json for core settings, with unit-specific overrides.',
-      consequences:
-        'Configuration is modular and easier to maintain. The config loader must implement a merge strategy for layered configs.',
-    },
-  },
-  {
-    title: 'Nyquist integration for truths and artifacts',
-    status: 'Proposed',
-    date: '2026-03-13',
-    body: {
-      context:
-        'Nyquist provides a truth-source registry and artifact tracking system that could centralize harness state management.',
-      decision:
-        'Integrate with Nyquist for truth registration and artifact lifecycle tracking.',
-      consequences:
-        'Harness gains a centralized truth source. A dependency on Nyquist availability is introduced.',
-      alternatives:
-        'Build a standalone truth registry within the harness codebase.',
-    },
-  },
-  {
-    title: 'Artifact-driven state derivation',
-    status: 'Accepted',
-    date: '2026-03-13',
-    body: {
-      context:
-        'Harness state is currently computed on-the-fly, leading to inconsistent results across different invocation points.',
-      decision:
-        'Derive harness state exclusively from persisted artifacts, making state deterministic and reproducible.',
-      consequences:
-        'State becomes auditable and cacheable. All state-changing operations must produce artifacts as their primary output.',
-    },
-  },
-  {
-    title: 'Validator stack detection',
-    status: 'Accepted',
-    date: '2026-03-13',
-    body: {
-      context:
-        'Validators are registered individually, but their execution order and dependencies are not explicitly managed.',
-      decision:
-        'Implement automatic validator stack detection that resolves execution order based on declared dependencies and layer constraints.',
-      consequences:
-        'Validator execution order is deterministic and verifiable. Circular dependencies are detected at registration time.',
-    },
-  },
-  {
-    title: 'Temporary 4-layer definition with return path to 5-layer',
-    status: 'Proposed',
-    date: '2026-03-13',
-    body: {
-      context:
-        'The target architecture defines 5 layers, but the current codebase structure and team familiarity support only 4 layers.',
-      decision:
-        'Adopt a temporary 4-layer definition (domain, application, infrastructure, presentation) with a documented return path to the 5-layer target.',
-      consequences:
-        'Initial implementation is simpler. The migration plan to 5 layers must be maintained and reviewed periodically.',
-      alternatives:
-        'Adopt the full 5-layer structure from the start despite the complexity cost.',
-    },
-  },
-] as const;