@markuplint/html-spec 5.0.0-rc.0 → 5.0.0-rc.2

package/ARCHITECTURE.ja.md

@@ -4,7 +4,7 @@
 
 `@markuplint/html-spec` は HTML Living Standard のデータセットプロバイダです。TypeScript ソースコードを含まない純粋なデータパッケージであり、208 個の要素 JSON 仕様ファイル（HTML、SVG、MathML）と 2 個の共通定義ファイルから構成されます。
 
-ビルド時に `@markuplint/spec-generator` が外部ソース（MDN、W3C ARIA 1.1/1.2/1.3、HTML Living Standard、SVG 仕様、MathML 仕様）からデータをフェッチし、手動で管理されたローカル仕様とマージして、統合された `index.json`（48,000 行以上、約 1.4MB）を生成します。手動データは常に外部データより優先され、仕様の正確性を保証します。
+ビルド時に `generator/` のスクリプトが外部ソース（MDN、W3C ARIA 1.1/1.2/1.3、HTML Living Standard、SVG 仕様、MathML 仕様）からデータをフェッチし、手動で管理されたローカル仕様とマージして、統合された `index.json`（48,000 行以上、約 1.4MB）を生成します。手動データは常に外部データより優先され、仕様の正確性を保証します。
 
 ## ディレクトリ構成
 
@@ -18,7 +18,7 @@ src/
 ├── spec-common.attributes.jsonc      # 20 個のグローバル属性カテゴリ定義
 └── spec-common.contents.jsonc        # HTML 10 + SVG 19 + MathML 3 のコンテンツモデルカテゴリ定義
 
-build.mjs                             # @markuplint/spec-generator を呼び出すビルドスクリプト
+build.ts                              # generator/ モジュールを呼び出すビルドスクリプト
 index.json                            # 生成出力（48K 行以上、編集不可）
 index.js                              # CommonJS エントリーポイント
 index.d.ts                            # TypeScript 型宣言
@@ -38,7 +38,7 @@ flowchart TD
 
     subgraph build ["ビルドパイプライン"]
         buildMjs["build.mjs"]
-        specGen["@markuplint/spec-generator\nmain()"]
+        specGen["generator/\nmain()"]
     end
 
     subgraph external ["外部データソース"]
@@ -119,7 +119,7 @@ export = json;
 | -------------- | --------------------------------------- | ------------------------------------------------------------- |
 | ソース仕様     | `src/spec.*.jsonc`（208 ファイル）      | 要素ごとの仕様定義（コンテンツモデル、属性、ARIA マッピング） |
 | 共通定義       | `src/spec-common.*.jsonc`（2 ファイル） | グローバル属性カテゴリとコンテンツモデルマクロの共有定義      |
-| ビルドシステム | `build.mjs`                             | `@markuplint/spec-generator` の `main()` を呼び出すエントリー |
+| ビルドシステム | `build.ts`                              | `generator/` の `main()` を呼び出すエントリー                 |
 | 生成出力       | `index.json`                            | 統合データセット（48K 行以上、直接編集不可）                  |
 | 型宣言         | `index.d.ts`                            | `@markuplint/ml-spec` からの型を再エクスポート                |
 | スキーマ検証   | `test/structure.spec.mjs`               | Ajv ベースの JSON スキーマ検証テスト                          |
@@ -186,19 +186,7 @@ export = json;
 
 ## ビルドパイプライン
 
-ビルドは `build.mjs` を通じて `@markuplint/spec-generator` の `main()` 関数を呼び出します。
-
-```javascript
-import path from 'node:path';
-import { main } from '@markuplint/spec-generator';
-
-await main({
-  outputFilePath: path.resolve(import.meta.dirname, 'index.json'),
-  htmlFilePattern: path.resolve(import.meta.dirname, 'src', 'spec.*.jsonc'),
-  commonAttrsFilePath: path.resolve(import.meta.dirname, 'src', 'spec-common.attributes.jsonc'),
-  commonContentsFilePath: path.resolve(import.meta.dirname, 'src', 'spec-common.contents.jsonc'),
-});
-```
+ビルドは `build.ts` を通じて `generator/` の `main()` 関数を呼び出します。
 
 ビルドプロセスの流れ:
 
@@ -231,18 +219,17 @@ yarn gen:prettier
 
 ## 外部依存パッケージ
 
-| パッケージ                   | 種別 | 用途                                         |
-| ---------------------------- | ---- | -------------------------------------------- |
-| `@markuplint/ml-spec`        | 本番 | 型定義（`Cites`, `ElementSpec`, `SpecDefs`） |
-| `@markuplint/spec-generator` | 開発 | ビルドパイプライン                           |
-| `@markuplint/test-tools`     | 開発 | テストユーティリティ（`glob` 等）            |
+| パッケージ               | 種別 | 用途                                         |
+| ------------------------ | ---- | -------------------------------------------- |
+| `@markuplint/ml-spec`    | 本番 | 型定義（`Cites`, `ElementSpec`, `SpecDefs`） |
+| `@markuplint/test-tools` | 開発 | テストユーティリティ（`glob` 等）            |
 
 ## 他パッケージとの連携
 
 ```mermaid
 flowchart LR
     subgraph upstream ["上流パッケージ"]
-        specGen["@markuplint/spec-generator\n(ビルドパイプライン)"]
+        specGen["generator/\n(ビルドパイプライン)"]
         mlSpecTypes["@markuplint/ml-spec\n(型定義)"]
     end
 
@@ -273,7 +260,7 @@ flowchart LR
 ### 上流
 
 - **`@markuplint/ml-spec`** は `index.d.ts` で使用される型定義（`Cites`, `ElementSpec`, `SpecDefs`）を提供します。
-- **`@markuplint/spec-generator`** はビルド時に外部仕様のフェッチとデータ統合を担当します。
+- **`generator/`** はビルド時に外部仕様のフェッチとデータ統合を担当します。
 
 ### 下流
 
@@ -285,5 +272,5 @@ flowchart LR
 ## ドキュメントマップ
 
 - [要素仕様フォーマット](docs/element-spec-format.ja.md) -- 要素 JSON の構造、フィールド定義、条件分岐パターン
-- [ビルドパイプライン](docs/build-pipeline.ja.md) -- spec-generator の動作、外部データフェッチ、マージ戦略
+- [ビルドパイプライン](docs/build-pipeline.ja.md) -- generator の動作、外部データフェッチ、マージ戦略
 - [メンテナンスガイド](docs/maintenance.ja.md) -- 新規要素の追加、属性更新、外部仕様の変更対応

package/ARCHITECTURE.md

@@ -2,9 +2,9 @@
 
 ## Overview
 
-`@markuplint/html-spec` is the canonical HTML Living Standard dataset provider for markuplint. It is a pure data package with no TypeScript source code. It contains 208 per-element JSON specification files (HTML, SVG, and MathML) and 2 common definition files that are processed by `@markuplint/spec-generator` to produce a single consolidated `index.json` (48K+ lines, 1.4MB).
+`@markuplint/html-spec` is the canonical HTML Living Standard dataset provider for markuplint. It is a pure data package with no TypeScript source code. It contains 208 per-element JSON specification files (HTML, SVG, and MathML) and 2 common definition files that are processed by `generator/` scripts to produce a single consolidated `index.json` (48K+ lines, 1.4MB).
 
-During the build, `@markuplint/spec-generator` fetches live data from MDN, W3C ARIA specifications (1.1, 1.2, 1.3), Graphics ARIA, DPub ARIA, HTML-ARIA mappings, the HTML Living Standard, SVG specifications, and MathML specifications, then merges that external data with the hand-authored JSON files. Manual specifications always take precedence over fetched data, ensuring stable, curated definitions while still benefiting from automated enrichment.
+During the build, `generator/` fetches live data from MDN, W3C ARIA specifications (1.1, 1.2, 1.3), Graphics ARIA, DPub ARIA, HTML-ARIA mappings, the HTML Living Standard, SVG specifications, and MathML specifications, then merges that external data with the hand-authored JSON files. Manual specifications always take precedence over fetched data, ensuring stable, curated definitions while still benefiting from automated enrichment.
 
 ## Directory Structure
 
@@ -18,7 +18,7 @@ src/
 ├── spec-common.attributes.jsonc      # 20 global attribute category definitions
 └── spec-common.contents.jsonc        # 10 HTML + 19 SVG + 3 MathML content model category definitions
 
-build.mjs                             # Build script invoking @markuplint/spec-generator
+build.ts                              # Build script invoking generator/ modules
 index.json                            # Generated output (48K+ lines, DO NOT EDIT)
 index.js                              # CommonJS entry point (re-exports index.json)
 index.d.ts                            # TypeScript type declarations
@@ -38,7 +38,7 @@ flowchart TD
 
     subgraph build ["Build Pipeline"]
         buildScript["build.mjs"]
-        specGen["@markuplint/spec-generator\nmain()"]
+        specGen["generator/\nmain()"]
     end
 
     subgraph external ["External Data Sources"]
@@ -142,18 +142,17 @@ An array of element specifications. Each entry defines a single HTML, SVG, or Ma
 | --------------------- | ------------------------------------------------------------ | ------------------------------------------------------------------------------ |
 | Source Specifications | 208 `src/spec.*.jsonc` files                                 | Per-element definitions: content models, attributes, ARIA mappings             |
 | Common Definitions    | `spec-common.attributes.jsonc`, `spec-common.contents.jsonc` | Shared global attribute categories and content model category macros           |
-| Build System          | `build.mjs`                                                  | Invokes `@markuplint/spec-generator` to merge sources with external data       |
+| Build System          | `build.ts`                                                   | Invokes `generator/` to merge sources with external data                       |
 | Generated Output      | `index.json`                                                 | Single consolidated dataset consumed by downstream packages                    |
 | Type Declarations     | `index.d.ts`                                                 | Re-exports `Cites`, `ElementSpec`, `SpecDefs` from `@markuplint/ml-spec`       |
 | Schema Validation     | `test/structure.spec.mjs`                                    | Ajv-based validation of generated output against `@markuplint/ml-spec` schemas |
 
 ## External Dependencies
 
-| Dependency                   | Type       | Purpose                                                      |
-| ---------------------------- | ---------- | ------------------------------------------------------------ |
-| `@markuplint/ml-spec`        | Production | Type definitions (`Cites`, `ElementSpec`, `SpecDefs`)        |
-| `@markuplint/spec-generator` | Dev        | Build pipeline: merges manual specs with MDN/W3C/WHATWG data |
-| `@markuplint/test-tools`     | Dev        | Test utilities (`glob` for file discovery)                   |
+| Dependency               | Type       | Purpose                                               |
+| ------------------------ | ---------- | ----------------------------------------------------- |
+| `@markuplint/ml-spec`    | Production | Type definitions (`Cites`, `ElementSpec`, `SpecDefs`) |
+| `@markuplint/test-tools` | Dev        | Test utilities (`glob` for file discovery)            |
 
 ## Integration Points
 
@@ -161,7 +160,7 @@ An array of element specifications. Each entry defines a single HTML, SVG, or Ma
 flowchart LR
     subgraph upstream ["Upstream"]
         mlSpec["@markuplint/ml-spec\n(types + schemas)"]
-        specGen["@markuplint/spec-generator\n(build tool)"]
+        specGen["generator/\n(build scripts)"]
     end
 
     subgraph pkg ["@markuplint/html-spec"]
@@ -192,7 +191,7 @@ flowchart LR
 ### Upstream
 
 - **`@markuplint/ml-spec`** provides the TypeScript type definitions (`MLMLSpec`, `ElementSpec`, `SpecDefs`) and JSON schemas used to validate the generated output. The `index.d.ts` re-exports these types.
-- **`@markuplint/spec-generator`** is the build tool invoked by `build.mjs`. It reads the source JSON files, fetches live data from MDN Web Docs, W3C ARIA specifications (versions 1.1, 1.2, 1.3), Graphics ARIA, DPub ARIA, HTML-ARIA mappings, the HTML Living Standard, SVG specifications, and MathML specifications, then merges everything into `index.json`.
+- **`generator/`** is the build module invoked by `build.ts`. It reads the source JSON files, fetches live data from MDN Web Docs, W3C ARIA specifications (versions 1.1, 1.2, 1.3), Graphics ARIA, DPub ARIA, HTML-ARIA mappings, the HTML Living Standard, SVG specifications, and MathML specifications, then merges everything into `index.json`.
 
 ### Downstream
 
@@ -203,5 +202,5 @@ flowchart LR
 ## Documentation Map
 
 - [Element Specification Format](docs/element-spec-format.md) -- Structure and fields of per-element JSON files
-- [Build Pipeline](docs/build-pipeline.md) -- How build.mjs and spec-generator produce index.json
+- [Build Pipeline](docs/build-pipeline.md) -- How build.ts and generator/ produce index.json
 - [Maintenance Guide](docs/maintenance.md) -- Adding elements, updating external sources, troubleshooting

package/CHANGELOG.md

@@ -3,6 +3,43 @@
 All notable changes to this project will be documented in this file.
 See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
 
+# [5.0.0-rc.2](https://github.com/markuplint/markuplint/compare/v5.0.0-rc.1...v5.0.0-rc.2) (2026-04-15)
+
+### Bug Fixes
+
+- **html-spec:** add dir as required attribute for bdo element ([81a6c1f](https://github.com/markuplint/markuplint/commit/81a6c1f40630b3b9a904d380aed47042dfb90972))
+- **html-spec:** change dl content model from oneOrMore to zeroOrMore groups ([e29f6e4](https://github.com/markuplint/markuplint/commit/e29f6e4beb6cee1143d2aa4f53b770d97624dd0a)), closes [#3592](https://github.com/markuplint/markuplint/issues/3592)
+- **html-spec:** change optgroup label type from Any to NoEmptyAny ([c6b0e88](https://github.com/markuplint/markuplint/commit/c6b0e887cbb7576e9139a269c98b8718bcaffb18))
+- **html-spec:** correct permittedRoles for input[type=button/image/reset/submit] ([054e8e2](https://github.com/markuplint/markuplint/commit/054e8e2b1ca9c1b85fa5a0bcd18f72a22669f4a5)), closes [#3588](https://github.com/markuplint/markuplint/issues/3588)
+- **html-spec:** override MDN incorrect experimental flag on audio loading attribute ([09d5898](https://github.com/markuplint/markuplint/commit/09d5898256ef0880bcdce9d8a514fbcae6b4d226))
+- **html-spec:** override MDN incorrect experimental flag on video loading attribute ([52def75](https://github.com/markuplint/markuplint/commit/52def759157d046cacc0660422db188e4d8da753)), closes [#3697](https://github.com/markuplint/markuplint/issues/3697)
+- **html-spec:** remove global attr overrides that drop type definitions ([6ff2f0d](https://github.com/markuplint/markuplint/commit/6ff2f0d2ac8c0410b90af5e9ccb6be126ec96c39))
+- **html-spec:** restore ARIA 1.3 role name extraction ([01b9ce3](https://github.com/markuplint/markuplint/commit/01b9ce350b472e9f37f04238be446c3898e317a8))
+
+- refactor(html-spec)!: migrate spec-generator into html-spec and run via native TypeScript ([8f928cc](https://github.com/markuplint/markuplint/commit/8f928ccf17a959447f477eb4c3d0db13ab2ba730))
+
+### Features
+
+- **html-spec:** add conditional attribute constraints for script element ([9abbf95](https://github.com/markuplint/markuplint/commit/9abbf95c43d8bcedbfa19d0c09223a322967bc3b))
+- **html-spec:** add conditional value types for input element ([#3598](https://github.com/markuplint/markuplint/issues/3598)) ([290be1c](https://github.com/markuplint/markuplint/commit/290be1cde53165f1f6165731bf2ec184b0c46b54))
+- **html-spec:** add forbiddenAncestors for main, header, footer, address ([e51b745](https://github.com/markuplint/markuplint/commit/e51b745c0fd7662946b267b67f94b1bfbf95b89c))
+- **html-spec:** add loading attribute type for audio and video elements ([12a03f7](https://github.com/markuplint/markuplint/commit/12a03f7252bfb8bae2bd427dbb9a553e2038ecb3)), closes [#3542](https://github.com/markuplint/markuplint/issues/3542)
+- **html-spec:** add speculationrules to script type attribute enum ([3568ee6](https://github.com/markuplint/markuplint/commit/3568ee6012b3f30e3f913f346e000519939c1448))
+- **html-spec:** add touch event handler attributes (ontouchstart, etc.) ([9be2b57](https://github.com/markuplint/markuplint/commit/9be2b57ea39ec33c7d3f24bca530a40b6e4d7708))
+- **html-spec:** add uniqueAttrs for track default attribute ([ccafb65](https://github.com/markuplint/markuplint/commit/ccafb65fbda86e42f509566eb95798cfac271c11))
+- **html-spec:** split link[as] enum by rel condition ([#3189](https://github.com/markuplint/markuplint/issues/3189)) ([6aa1fe8](https://github.com/markuplint/markuplint/commit/6aa1fe896223a3b7437e38a3c2b5092edefcd240))
+- **html-spec:** use #nonEmptyText for title and option elements ([ede5d4c](https://github.com/markuplint/markuplint/commit/ede5d4c87c72b7e2e95f17799f3632eb9108feef))
+- **types:** add SRIHash type for integrity attribute validation ([7672999](https://github.com/markuplint/markuplint/commit/7672999a17f7d96dc286aabfcea5cc0861b73be5))
+
+### BREAKING CHANGES
+
+- @markuplint/spec-generator package is removed.
+  Its functionality is now internal to @markuplint/html-spec.
+
+# [5.0.0-rc.1](https://github.com/markuplint/markuplint/compare/v5.0.0-rc.0...v5.0.0-rc.1) (2026-03-27)
+
+**Note:** Version bump only for package @markuplint/html-spec
+
 # [5.0.0-rc.0](https://github.com/markuplint/markuplint/compare/v5.0.0-alpha.3...v5.0.0-rc.0) (2026-03-12)
 
 ### Features

package/README.md

@@ -41,7 +41,7 @@ Core packages (Application Layer)
 
 ### Build System
 
-- **`build.mjs`** - Generation script that invokes `@markuplint/spec-generator`
+- **`build.ts`** - Generation script that invokes `generator/` modules
 - Fetches live data from MDN, W3C ARIA specs, Graphics ARIA, DPub ARIA, HTML-ARIA mappings, HTML Living Standard, SVG specs, and MathML specs
 
 ## Relationship to @markuplint/ml-spec
@@ -79,7 +79,7 @@ For detailed documentation, see:
 
 - [Architecture](ARCHITECTURE.md) -- Package structure, data flow, and integration points
 - [Element Specification Format](docs/element-spec-format.md) -- JSON spec file reference, content models, ARIA integration
-- [Build Pipeline](docs/build-pipeline.md) -- Build process, external data sources, spec-generator modules
+- [Build Pipeline](docs/build-pipeline.md) -- Build process, external data sources, generator modules
 - [Maintenance Guide](docs/maintenance.md) -- Common recipes, testing, troubleshooting
 
 ## License

package/SKILL.md

@@ -46,7 +46,7 @@ and review what has changed.
 yarn up:gen
 ```
 
-This runs `@markuplint/spec-generator`, which scrapes live MDN data and merges it with
+This runs the generator scripts in `generator/`, which scrape live MDN data and merge it with
 the manual spec files in `src/`. The result is written to `index.json`.
 
 ### Step 2: Review the diff
@@ -191,9 +191,9 @@ Mark an element as obsolete. Follow recipe #8 in `docs/maintenance.md`.
 
 There are two approaches:
 
-- **Via spec-generator's hardcoded list** (preferred for standard obsolete elements):
+- **Via generator's hardcoded list** (preferred for standard obsolete elements):
   Add the element name to the `obsoleteList` array in
-  `packages/@markuplint/spec-generator/src/html-elements.ts`
+  `packages/@markuplint/html-spec/generator/html-elements.ts`
 - **Via manual spec file**: Set `"obsolete": true` in the element's
   `src/spec.<element>.jsonc`
 

package/docs/build-pipeline.ja.md

@@ -4,7 +4,7 @@
 
 ## 概要
 
-`@markuplint/html-spec` は `@markuplint/spec-generator` を使用して、単一の統合 `index.json` ファイルを生成します。ビルドプロセス:
+`@markuplint/html-spec` は `generator/` のスクリプトを使用して、単一の統合 `index.json` ファイルを生成します。ビルドプロセス:
 
 1. `src/` から 208 個の要素 JSON 仕様ファイル（HTML、SVG、MathML）と 2 個の共通定義ファイルを読み込む
 2. MDN Web Docs、W3C ARIA 仕様、HTML Living Standard から外部データをフェッチ
@@ -24,8 +24,8 @@ flowchart TD
     end
 
     subgraph build ["ビルド"]
-        buildScript["build.mjs"]
-        specGen["@markuplint/spec-generator"]
+        buildScript["build.ts"]
+        specGen["generator/"]
     end
 
     subgraph external ["外部データソース"]
@@ -54,30 +54,11 @@ flowchart TD
 
 ## ビルドエントリポイント
 
-`build.mjs` が `@markuplint/spec-generator` の `main()` を呼び出します。
-
-```javascript
-import path from 'node:path';
-import { main } from '@markuplint/spec-generator';
-
-await main({
-  outputFilePath: path.resolve(import.meta.dirname, 'index.json'),
-  htmlFilePattern: path.resolve(import.meta.dirname, 'src', 'spec.*.jsonc'),
-  commonAttrsFilePath: path.resolve(import.meta.dirname, 'src', 'spec-common.attributes.jsonc'),
-  commonContentsFilePath: path.resolve(import.meta.dirname, 'src', 'spec-common.contents.jsonc'),
-});
-```
-
-| オプション               | 説明                                       |
-| ------------------------ | ------------------------------------------ |
-| `outputFilePath`         | `index.json` の出力先パス                  |
-| `htmlFilePattern`        | 要素仕様ファイルにマッチする glob パターン |
-| `commonAttrsFilePath`    | グローバル属性定義ファイルのパス           |
-| `commonContentsFilePath` | コンテンツモデルマクロ定義ファイルのパス   |
+`build.ts` が `generator/` の `main()` を呼び出します。
 
 ## 外部データソース
 
-spec-generator はビルド時に以下の外部ソースからデータをフェッチします。
+generator はビルド時に以下の外部ソースからデータをフェッチします。
 
 | ソース                                    | 提供データ                                                   |
 | ----------------------------------------- | ------------------------------------------------------------ |
@@ -90,7 +71,7 @@ spec-generator はビルド時に以下の外部ソースからデータをフ
 | Graphics ARIA                             | グラフィックス固有 ARIA ロール                               |
 | HTML-ARIA（`w3.org/TR/html-aria/`）       | HTML 属性から ARIA プロパティへのマッピング                  |
 
-spec-generator の内部アーキテクチャ（スクレイピング、キャッシュ、モジュール構成）の詳細は `@markuplint/spec-generator` 自身のドキュメントを参照してください。
+generator の内部アーキテクチャ（スクレイピング、キャッシュ、モジュール構成）の詳細は `generator/` ディレクトリを参照してください。
 
 ## データ優先順位ルール
 

package/docs/build-pipeline.md

@@ -4,7 +4,7 @@ This document describes how `index.json` is generated from the source files and
 
 ## Overview
 
-The `@markuplint/html-spec` package uses `@markuplint/spec-generator` to produce a single consolidated `index.json` file. The build process:
+The `@markuplint/html-spec` package uses `generator/` scripts to produce a single consolidated `index.json` file. The build process:
 
 1. Reads 208 per-element JSON spec files (HTML, SVG, MathML) and 2 common definition files from `src/`
 2. Fetches external data from MDN Web Docs, W3C ARIA specifications, and the HTML Living Standard
@@ -24,8 +24,8 @@ flowchart TD
     end
 
     subgraph build ["Build"]
-        buildScript["build.mjs"]
-        specGen["@markuplint/spec-generator"]
+        buildScript["build.ts"]
+        specGen["generator/"]
     end
 
     subgraph external ["External Data Sources"]
@@ -54,30 +54,11 @@ flowchart TD
 
 ## Build Entry Point
 
-The build is triggered via `build.mjs`:
-
-```javascript
-import path from 'node:path';
-import { main } from '@markuplint/spec-generator';
-
-await main({
-  outputFilePath: path.resolve(import.meta.dirname, 'index.json'),
-  htmlFilePattern: path.resolve(import.meta.dirname, 'src', 'spec.*.jsonc'),
-  commonAttrsFilePath: path.resolve(import.meta.dirname, 'src', 'spec-common.attributes.jsonc'),
-  commonContentsFilePath: path.resolve(import.meta.dirname, 'src', 'spec-common.contents.jsonc'),
-});
-```
-
-| Option                   | Description                                      |
-| ------------------------ | ------------------------------------------------ |
-| `outputFilePath`         | Absolute path where `index.json` will be written |
-| `htmlFilePattern`        | Glob pattern matching per-element spec files     |
-| `commonAttrsFilePath`    | Path to global attribute definitions             |
-| `commonContentsFilePath` | Path to content model macro definitions          |
+The build is triggered via `build.ts`, which calls the `main()` function from `generator/index.ts`.
 
 ## External Data Sources
 
-The spec-generator fetches live data from the following sources during the build:
+The generator fetches live data from the following sources during the build:
 
 | Source                                   | Data Provided                                                                     |
 | ---------------------------------------- | --------------------------------------------------------------------------------- |
@@ -90,7 +71,7 @@ The spec-generator fetches live data from the following sources during the build
 | Graphics ARIA                            | Graphics-specific ARIA roles                                                      |
 | HTML-ARIA (`w3.org/TR/html-aria/`)       | HTML attribute to ARIA property mappings                                          |
 
-For details on the spec-generator's internal architecture (scraping, caching, module structure), see `@markuplint/spec-generator`'s own documentation.
+For details on the generator's internal architecture (scraping, caching, module structure), see the `generator/` directory.
 
 ## Data Precedence Rules
 

package/docs/maintenance.ja.md

@@ -59,6 +59,57 @@
 4. `yarn workspace @markuplint/html-spec run gen` を実行
 5. `index.json` で属性が正しいメタデータとともに表示されることを確認
 
+### 2b. 条件付き値型（`ConditionalAttributeType[]`）の使用
+
+属性の期待する値型が（属性の存在可否ではなく）**別の属性の値に依存する**場合、`type` フィールドに単一の `AttributeType` ではなく `ConditionalAttributeType[]` を使用します。
+
+これは属性レベルの `condition` フィールド（レシピ2）とは異なります。`condition` は**属性自体が有効かどうか**を制御しますが、条件付き値型は**どの値が有効か**を要素の状態に応じて制御します。
+
+**例** -- `input[value]` の型は `type` 属性に依存:
+
+```jsonc
+"value": {
+    "type": [
+        { "condition": "[type='color' i]", "type": "SimpleColor" },
+        { "condition": "[type='url' i]", "type": "URL" },
+        { "condition": "[type='email' i]", "type": "Email" },
+        { "condition": ["[type='number' i]", "[type='range' i]"], "type": { "type": "float" } },
+        { "condition": "[type='date' i]", "type": "DateString" }
+    ]
+}
+```
+
+**ランタイムの動作:**
+
+1. `@markuplint/rules` の `isValidAttr()` が `ConditionalAttributeType[]` を検出
+2. 各エントリの `condition`（CSSセレクタまたはセレクタの配列）を要素に対してマッチ
+3. 最初にマッチしたエントリの `type` でバリデーションを実行
+4. どの条件にもマッチしない場合は `Any`（制約なし）にフォールバック
+
+**使用タイミング:** HTML仕様が「属性 Y が Z のとき、値は X でなければならない」と規定している場合 — 例: `type=color` のとき `<input value>` は valid simple color でなければならない。
+
+**例2** -- `link[as]` の有効な値は `rel` に依存:
+
+```jsonc
+"as": {
+    "type": [
+        {
+            "condition": "[rel~='preload' i]",
+            "type": { "enum": ["fetch", "font", "image", "script", "style", "track"] }
+        },
+        {
+            "condition": "[rel~='modulepreload' i]",
+            "type": { "enum": ["audioworklet", "json", "paintworklet", "script", "serviceworker", "sharedworker", "style", "worker"] }
+        }
+    ],
+    "condition": ["[rel~='preload' i]", "[rel~='modulepreload' i]"]
+}
+```
+
+注: 属性レベルの `condition` は `as` 属性自体が有効かどうか（`rel=preload` または `rel=modulepreload` の場合のみ）を制御し、型レベルの `ConditionalAttributeType[]` は各 `rel` 値に対してどの enum 値が有効かを制御します。
+
+**参照:** `@markuplint/ml-spec` ドキュメント（`docs/type-definitions.md`）の `ConditionalAttributeType` セクション。
+
 ### 3. SVG要素の追加
 
 1. `src/spec.svg_<localname>.jsonc` を作成（例: `src/spec.svg_circle.jsonc`）
@@ -216,7 +267,7 @@ description の表現変更などの表面的な変更は、更新された `ind
 
 要素を非推奨にする方法は2つある:
 
-- **ハードコードリスト経由**: `packages/@markuplint/spec-generator/src/html-elements.ts` の `obsoleteList` 配列に要素名を追加
+- **ハードコードリスト経由**: `packages/@markuplint/html-spec/generator/html-elements.ts` の `obsoleteList` 配列に要素名を追加
 - **手動仕様経由**: 要素の仕様ファイルに `"obsolete": true` を設定
 
 非推奨要素には自動的に以下が設定される:
@@ -285,12 +336,11 @@ yarn workspace @markuplint/html-spec run test
 
 ### 開発依存
 
-- **`@markuplint/spec-generator`**: ビルドツール。外部データのスクレイピングとマージを担当
 - **`@markuplint/test-tools`**: テストユーティリティ。`glob` 関数などを提供
 
 ### 依存関係更新時の注意
 
-1. `@markuplint/spec-generator` 更新後は必ず再生成を実行
+1. `generator/` 更新後は必ず再生成を実行
 2. `index.json` の差分を注意深くレビュー（外部データソースの変更により予期しない差分が出る場合がある）
 3. テストを実行してスキーマ検証が通ることを確認
 4. `@markuplint/ml-spec` のスキーマが変更された場合、ソースJSONファイルの更新が必要になることがある

package/docs/maintenance.md

@@ -15,14 +15,14 @@ This is a practical operations and maintenance guide for contributors working on
 
 The generation process (`gen`) performs two steps in sequence via `npm-run-all`:
 
-1. **`gen:build`** -- Executes `build.mjs`, which calls the `main()` function from
-   `@markuplint/spec-generator`. This reads all `src/spec.*.jsonc` files, merges them
+1. **`gen:build`** -- Executes `build.ts`, which calls the `main()` function from
+   `generator/`. This reads all `src/spec.*.jsonc` files, merges them
    with scraped MDN data and the common attribute/content files, appends obsolete
    element stubs, and writes the consolidated output to `index.json`.
 2. **`gen:prettier`** -- Runs Prettier on `index.json` to ensure consistent formatting
    across regenerations.
 
-The build is network-dependent because `@markuplint/spec-generator` fetches live data
+The build is network-dependent because `generator/` fetches live data
 from MDN for each element (descriptions, compatibility flags, attribute metadata).
 Expect the build to take several minutes on a clean run.
 
@@ -77,6 +77,57 @@ will cause the element to be silently excluded from the build output.
 4. Run `yarn workspace @markuplint/html-spec run gen`
 5. Check `index.json` to confirm the attribute appears with correct metadata
 
+### 2b. Using Conditional Value Types (`ConditionalAttributeType[]`)
+
+When an attribute's expected value type depends on **another attribute's value** (not just its existence), use `ConditionalAttributeType[]` as the `type` field instead of a single `AttributeType`.
+
+This is different from the attribute-level `condition` field (Recipe 2), which controls **whether the attribute is valid at all**. Conditional value types control **what values are valid** depending on element state.
+
+**Example** -- `input[value]` type depends on the `type` attribute:
+
+```jsonc
+"value": {
+    "type": [
+        { "condition": "[type='color' i]", "type": "SimpleColor" },
+        { "condition": "[type='url' i]", "type": "URL" },
+        { "condition": "[type='email' i]", "type": "Email" },
+        { "condition": ["[type='number' i]", "[type='range' i]"], "type": { "type": "float" } },
+        { "condition": "[type='date' i]", "type": "DateString" }
+    ]
+}
+```
+
+**How it works at runtime:**
+
+1. `isValidAttr()` in `@markuplint/rules` detects `ConditionalAttributeType[]`
+2. Each entry's `condition` (a CSS selector or array of selectors) is matched against the element
+3. The first matching entry's `type` is used for validation
+4. If no condition matches, the value falls back to `Any` (no constraint)
+
+**When to use:** When the HTML spec says "the value must be X when attribute Y is Z" — e.g., `<input value>` must be a valid simple color when `type=color`.
+
+**Example 2** -- `link[as]` valid values depend on `rel`:
+
+```jsonc
+"as": {
+    "type": [
+        {
+            "condition": "[rel~='preload' i]",
+            "type": { "enum": ["fetch", "font", "image", "script", "style", "track"] }
+        },
+        {
+            "condition": "[rel~='modulepreload' i]",
+            "type": { "enum": ["audioworklet", "json", "paintworklet", "script", "serviceworker", "sharedworker", "style", "worker"] }
+        }
+    ],
+    "condition": ["[rel~='preload' i]", "[rel~='modulepreload' i]"]
+}
+```
+
+Note: The attribute-level `condition` controls whether the `as` attribute is valid at all (only with `rel=preload` or `rel=modulepreload`), while the type-level `ConditionalAttributeType[]` controls which enum values are valid for each `rel` value.
+
+**See also:** `ConditionalAttributeType` in `@markuplint/ml-spec` docs (`docs/type-definitions.md`).
+
 ### 3. Adding an SVG Element
 
 1. Create `src/spec.svg_<localname>.jsonc` (e.g., `src/spec.svg_circle.jsonc`)
@@ -275,7 +326,7 @@ what has changed in web standards and ensuring the spec data remains accurate.
 
 Elements can be marked obsolete in two ways:
 
-- **Via the hardcoded list**: Add the element name to the `obsoleteList` array in `packages/@markuplint/spec-generator/src/html-elements.ts`
+- **Via the hardcoded list**: Add the element name to the `obsoleteList` array in `packages/@markuplint/html-spec/generator/html-elements.ts`
 - **Via manual spec**: Set `"obsolete": true` in the element's spec file
 
 Obsolete elements automatically get:
@@ -358,15 +409,11 @@ grep -A5 '"accept"' index.json
 
 ### Dev Dependencies
 
-- **`@markuplint/spec-generator`**: The build tool. Updates may change:
-  - How MDN pages are scraped (if MDN layout changes)
-  - Which ARIA spec versions are fetched
-  - The output format of `index.json`
 - **`@markuplint/test-tools`**: Test utilities. Updates are generally safe.
 
 ### When Updating Dependencies
 
-1. Always regenerate after updating `@markuplint/spec-generator`: `yarn workspace @markuplint/html-spec run gen`
+1. Always regenerate after updating `generator/`: `yarn up:gen`
 2. Review `index.json` diff carefully for unexpected changes
 3. Run tests to ensure schema validation passes
 
@@ -380,7 +427,7 @@ grep -A5 '"accept"' index.json
 
 - Check network connectivity
 - Failed fetches are cached as empty strings; the build will continue but affected elements will have missing metadata
-- If MDN page structure changed, `@markuplint/spec-generator` scraping selectors may need updating
+- If MDN page structure changed, `generator/` scraping selectors may need updating
 
 ### Schema Validation Error