@qijenchen/design-system 0.1.0-beta.13 → 0.1.0-beta.131

package/ds-canonical/references/repository-hygiene.md

@@ -0,0 +1,106 @@
+# Repository hygiene canonical
+
+Repository hygiene is part of a full/deep audit. It is separate from
+`/knowledge-prune`:knowledge-prune owns governance knowledge only, while this check owns the
+repository's complete folder/file topology.
+
+## Required inventory
+
+For every repository in scope, enumerate the Git worktree with
+`git ls-files --cached --others --exclude-standard`. Classify by declared home instead of judging
+files from names alone:
+
+1. active source/authority;
+2. generated provider or release projection;
+3. fixture/baseline;
+4. archive/evidence;
+5. future-reserved asset with a policy declaration that names all four required fields: owner,
+   concrete purpose, activation condition, and review/expiry lifecycle;
+6. transient junk.
+
+Only class 6 is automatically removable. Classes 2-5 are not redundancy. A zero-reference grep
+is evidence, not deletion authority:dynamic entrypoints, package exports, workflow paths,
+fixtures, templates, compatibility projections, and explicitly future-planned consumers must be
+checked first.
+
+"Future use" by itself is not a classification. A class-5 exemption exists only when
+`repository-hygiene-policy.json` binds the exact path prefix to:
+
+1. an existing repository-relative canonical owner;
+2. a concrete retained purpose (not "maybe useful", `TBD`, or a generic parking area);
+3. a concrete activation condition that names the evidence/authority which would turn the asset
+   into active work; and
+4. a machine-checkable `review-by` or `expire-on` date plus the fail-closed lapse action
+   `reclassify-or-remove`.
+
+Missing any field means the asset cannot use the future-reserved exemption and must be classified
+by its current role. Passing the four-field contract is necessary, not permission to keep unrelated
+temporary/editor junk. On the lifecycle date the invariant fails until the declaration is reviewed,
+renewed with evidence, activated, or removed.
+
+## Mechanical core
+
+`packages/design-system/ds-canonical/references/repository-hygiene-policy.json` is the topology
+and exception SSOT. `node scripts/repository-hygiene-invariant.mjs --profile=authority --check`
+enforces:
+
+- every top-level home has a declared purpose;
+- temporary/editor/OS artifacts are not repository content;
+- every tracked symlink and target is declared;
+- exact-content duplicates outside generated/fixture/baseline/archive homes are rejected unless
+  a narrow path-set exception has a reason.
+- every future-reserved prefix satisfies the four-field contract, has a present canonical owner,
+  and has not crossed its review/expiry date.
+
+Exceptions must be path-bound and explain the retained role. Blanket filename or directory
+exceptions are forbidden. Future-reserved declarations are narrow classification exemptions, not
+an alternate archive or backlog; an undeclared or incomplete "future use" claim fails closed.
+
+## Judgment layer
+
+After the mechanical gate, inspect ambiguous files and homes against package exports, npm scripts,
+workflow references, story globs, test discovery, ownership manifests, and `rg` references. Prefer
+moving a valid file into its owning home over deleting it. Remove only high-confidence junk;
+preserve future-use material only when the four-field declaration is complete and current.
+
+Ignored local caches/builds (`node_modules`, `dist`, `storybook-static`, reference media) are not
+Git repository content. Report their size separately when local disk hygiene is in scope, but do
+not make a portable deep-audit receipt depend on machine-specific ignored state. OS junk such as
+`.DS_Store` may be removed locally with a recoverable operation.
+
+### Local worktree lifecycle
+
+A full/deep audit also enumerates `git worktree list --porcelain` for every observed repository.
+This is machine-local hygiene, not a portable source gate. Classify each linked worktree before
+cleanup:
+
+- preserve the current worktree, every dirty worktree, and every branch whose remote work is open
+  or unmerged;
+- a clean worktree whose exact commit is already merged may be moved out recoverably, after which
+  `git worktree prune` may remove only the now-missing registration;
+- preserve untracked release/debug artifacts together with the recoverable worktree move unless
+  their owning retention policy independently proves them disposable;
+- never delete a branch merely to make the worktree list shorter.
+
+Report active and reclaimed worktrees separately. Missing GitHub/network readback makes merge
+status **unobserved** and therefore preserves the worktree.
+
+Git-local audit/review state below `<absolute-git-dir>/governance-runtime/evidence/` is also outside
+the Git inventory, but a full/deep audit must classify it under
+[runtime evidence retention canonical](runtime-evidence-retention.md). Preserve current active,
+live-referenced, genuine-review, and unexpired-receipt closure; reclaim only complete unreferenced
+blocked/failed/stale runs. Never use repository duplicate rules to delete part of an evidence CAS.
+
+Run the same classification for every locally available registered repository. A repository that
+is unavailable in the current runtime is **unobserved**, never PASS; its repo-local audit/release
+gate remains the authority.
+
+## World-class benchmark(M8/M22;2026-08-04 backfill — canonical 制定時漏做,本節補齊)
+
+| System | Convention(verbatim/paraphrase) | Source | Status |
+|---|---|---|---|
+| Turborepo | `apps/` for applications and services、`packages/` for libraries and tooling;「Turborepo does not support nested packages like `apps/**` or `packages/**`」(flat nesting only);每 package 自帶 `package.json` 成獨立小專案;「If you ever find yourself writing `../` to get from one package to another, you likely have an opportunity to re-think your approach」 | github.com/vercel/turborepo `apps/docs/content/docs/crafting-your-repository/structuring-a-repository.mdx` | VERIFIED(raw 實取) |
+| Carbon | monorepo(Yarn workspaces + Lerna);元件住 `packages/react/src/components` 每元件一資料夾、樣式住 `packages/styles/scss/components`;快取產物不入 repo(「You do not need to commit any `.yarn/cache` tarballs」,non-committed cache strategy) | github.com/carbon-design-system/carbon `docs/developer-handbook.md` | VERIFIED(raw 實取) |
+| Nx | 「common convention … separating applications from packages(shared libraries)」;`libs/`/`packages/` 皆可,分組依 scope(所屬 app 或 app 內區塊);structure 可自訂但「good to have a plan in place」 | nx.dev/docs/concepts/decisions/folder-structure | search-only confidence(nx.dev 不在網域白名單,依官方頁搜尋摘要;maintainer 於 nrwl/nx discussion #16184 未表態單一命名) |
+
+**對照結論**:本 repo 的 R1-R4 + future-reserved 契約與三家一致或更嚴——`apps/`+`packages/` 頂層分家(Turborepo/Nx 同構)、每 package 自為 project(Turborepo 同構)、生成/快取產物不入 tracked tree 或以 generated 家分類(Carbon non-committed cache 同構,本 repo 更進一步:generated 家有 drift check)。三家皆**無**「未來保留檔案」的機械契約——本 repo 的四欄位 future-reserved 契約(owner/用途/啟用條件/複審期限,逾期 fail-closed)為超出業界基線的自有強化,屬 justified 差異而非 drift。

package/ds-canonical/references/runtime-evidence-retention.md

@@ -0,0 +1,88 @@
+# Runtime evidence retention canonical
+
+This policy owns the lifecycle of mutable audit, rollout, and review evidence below
+`<absolute-git-dir>/governance-runtime/evidence/`. That evidence supports current operations; it is
+not product authority, a permanent archive, or a reason to keep every attempted run forever.
+
+## Scope and unit of retention
+
+Resolve the evidence root from the repository's absolute Git directory. Each linked worktree may
+have a different root and must be observed independently. Missing worktree-local evidence is
+**unobserved**, not PASS, and portable audit/release claims must not depend on ignored local state.
+
+The atomic retention unit is a complete run directory. A portable review bundle includes its exact
+artifact topology and content-addressed store (CAS); never delete individual leaves, blobs, task
+descriptors, or other bundle members. Partial CAS pruning creates corrupt evidence rather than
+useful space savings.
+
+## Preserve roots
+
+Preserve a complete run when any one of these conditions holds:
+
+1. the current active-run pointer validates against the current frozen target;
+2. a live staged-rollout, release, readback, in-flight journal, or other operational record directly
+   references the run or one of its receipts;
+3. the run contains a genuine cross-provider review archive;
+4. the run contains an unexpired pass/closure receipt, together with every artifact required to
+   validate that receipt.
+
+A pointer that no longer validates against the current target is stale, not an active preserve
+root. Repair or clear that pointer before classifying its former target.
+
+## Autonomous whole-run reclamation
+
+After enumerating preserve roots and direct references, the agent may reclaim the following
+complete run directories without user approval:
+
+- unreferenced `REVIEW-BLOCKED` runs with no selected peer and no genuine review;
+- unreferenced failed or abandoned runs;
+- stale-target runs with no genuine review and no unexpired receipt;
+- superseded incomplete runs that are not referenced by a live operation.
+
+Cleanup should be recoverable when the runtime permits it. Re-run pointer/reference validation
+after cleanup. Do not add a bespoke approval gate, signing step, receipt ceremony, or general GC
+framework: this is lifecycle-based engineering maintenance under standing authorization.
+
+## Lazy portable-review materialization
+
+`REVIEW-BLOCKED`, peer-null, and review-waived outcomes retain only their compact selection,
+blocked, or waiver evidence. They must not materialize a full portable review bundle.
+
+A full bundle may be built only after a peer capability selection and dispatch schedule are frozen,
+immediately before the existing dispatch/archive path needs it. Repeated attempts for the same
+frozen target should reuse existing valid immutable evidence rather than create parallel copies.
+
+## Typed unobserved deterministic coverage
+
+The credential-gated published-live-deploy dimension may be recorded as `UNOBSERVED` only when
+both accepted credential references, `NETLIFY_LIVE_BASIC_AUTH` and `NETLIFY_PREVIEW_PASSWORD`, are
+absent or empty. The canonical recorder is:
+
+```text
+node scripts/run-deterministic-deep-audit.mjs --record-unobserved=NETLIFY_LIVE_CREDENTIAL_REFERENCE_ABSENT --dims=83
+```
+
+The closed receipt records the exact reason and empty observed-reference set. It contains no
+deployment command observations or sandbox receipt and never claims PASS. If either reference is
+present but unusable, execution must fail closed rather than reclassify it as absent.
+
+A valid typed `UNOBSERVED` receipt closes enumeration coverage only. It adds a trust downgrade,
+keeps compliance blocked and `promotionEligible=false`, and remains visible in verifier output.
+The verifier's default exit gate requires promotion eligibility. An explicitly authorized
+single-provider or self-attested audit may use `--require coverage`, which exits successfully only
+when every expected evidence artifact validates and `coverageStatus=complete`; it does not suppress
+findings or upgrade compliance/release authority.
+
+## Deep-audit and prune procedure
+
+A full/deep audit and knowledge-prune D10 must:
+
+1. report bytes by evidence class and run;
+2. validate the active pointer against the current target;
+3. enumerate direct references from rollout, release, readback, journals, and receipts;
+4. classify every observed run as preserved or whole-run reclaimable with its reason;
+5. autonomously perform high-confidence recoverable cleanup, then verify the remaining roots.
+
+Repository hygiene reports this ignored runtime separately from Git worktree topology. Git-tracked
+fixtures, baselines, release provenance, and archives continue to follow their owning policies and
+must not be mistaken for reclaimable runtime evidence.

package/ds-canonical/references/scenario-definition.md

@@ -0,0 +1,146 @@
+# Scenario Definition — Monorepo 2-Scenario Architecture(SSOT)
+
+> **2026-05-29 ship**:本 file 為 Scenario A / Scenario B 定義 + 互動方式 + verify checkpoints 的**唯一 SSOT**。所有 skill / hook / spec / AGENTS.md 文字 reference 此 file,**不重述定義**(per user「無多餘重複 SSOT」directive)。
+
+> **設計起源**:user 2026-05-29 verbatim「實際上會有兩種場景,一種是直接 fork ds repo 用的一種是 fork template repo 用的使用者,兩種情境都要確保完整沒有斷點又能確保 SSOT」+ codex r5 synthesize verdict(8 gap fix)。
+
+## 1. 兩 Scenario 定義
+
+### Scenario A — Direct fork DS repo
+
+**用戶**:DS 共同維護者 / 想看 DS source 一起改 DS + 寫 product 的人
+**入口**:fork `ajenchen/design-system` GitHub repo
+**他拿到**:DS source(`packages/design-system/`)+ canonical 治理(`packages/design-system/ds-canonical/`)+ registry-generated provider adapters + scaffold(`apps/template/`)+ scripts
+**DS 取得方式**:`packages/*` npm workspace link(local resolution)
+**Governance 取得**:共同 authority 直接讀 `packages/design-system/ds-canonical/`；provider registry/materializer 另產生原生 discovery views(例如 Claude 的 `.claude/`)。這些 view 可刪除重建、不是 owner；**不需 `/plugin install`**。
+**E2E 流程**:`fork → npm install → claude → npm run create-app order-dashboard → npm install(workspace re-link)→ npm run storybook → git push`
+**決策邊界**:`check_substantive_edit_approval_preflight.sh` 以 canonical target-bound classifier 區分變更；純工程 bug／refactor／test／governance remediation 依 Standing Authorization AUTO，只有會改變產品／UI／UX SSOT 且存在真實選擇的 edit 才需 exact user decision，未知情況 fail closed。
+
+### Scenario B — Fork published template repo
+
+**用戶**:純做產品 / 不需看 DS source 的人
+**入口**:`ajenchen/ds-product-template` GitHub「Use this template」(該 repo 內容 = mirror artifact,**非 SSOT**,by 自動 mirror workflow auto-generate from DS repo)
+**他拿到**:scaffold + committed `AGENTS.md` 共用指令 + Claude/Codex adapters + Agent Skills generated views；exact DS version 內含同版治理 payload
+**DS 取得方式**:`@qijenchen/design-system` npm registry(exact `X.Y.Z`;升級只走 reviewed PR)
+**Governance 取得**:Day-0 committed provider views + exact npm `ds-canonical/fork` payload。SessionStart 只做 read-only verification，不安裝、不解析 dist-tag、不改 workspace。**不需 plugin**；native hooks 只是回饋加速器，provider-neutral check + CI 是 hard authority。
+**E2E 流程**:`fork → npm run setup:all(依 lock 安裝、驗簽、執行 hooks-off check，並建立受控 peer CLI)→ Claude/Codex/其他已登錄 agent → npm run setup:netlify(唯讀診斷、Dashboard/manual、exit 2 fail-closed) → 人在 Dashboard import GitHub repo → npm run create-app order-dashboard → npm install → npm run storybook → upgrade 透過 branch/PR → git push`
+**禁**:import `@qijenchen/design-system/src/**` 或 `/dist/**`(`lint:imports` 攔)
+
+## 2. SSOT Architecture
+
+```
+ajenchen/design-system (DS repo) ── SSOT ───────────────────────────┐
+├── packages/design-system/       ← DS library source                │
+├── apps/template/                ← Product app seed                 │
+├── scripts/                      ← Shared workflow scripts          │
+│   ├── create-app.mjs            ← copy apps/template → apps/<name> │
+│   ├── setup-netlify-access.mjs                                      │
+│   ├── build-published-template-mirror.mjs ← mirror builder         │
+│   └── (4 other consumer scripts)                                    │
+├── .devcontainer/                ← Codespaces cloud-dev path        │
+├── .storybook/main.ts            ← globs sharedStoryGlobs + apps/** │
+├── packages/design-system/ds-canonical/ ← Governance canonical     │
+├── .claude/ / .agents/ / .codex/ ← Generated provider adapters     │
+├── template/ds-product-template/ ← Consumer-specific scaffold       │
+│   ├── Claude adapter / README   ← Scenario B onboarding docs       │
+│   ├── .storybook/main.ts        ← apps-only glob(no DS internal)  │
+│   ├── package.json              ← consumer workspaces + npm deps   │
+│   └── (.github / .gitignore / .npmrc / netlify.toml / docs / ...)  │
+└── .github/workflows/                                                │
+    └── mirror-to-published-template.yml ← protected merge/release  │
+                                                                      │
+                              ↓ (GitHub App + generated review PR)   │
+                                                                      │
+ajenchen/ds-product-template (published repo) ← Mirror artifact ─────┘
+(Scenario B fork users land here via「Use this template」)
+```
+
+## 3. Mirror Workflow Chain(Scenario B 自動同步)
+
+**Trigger**(雙觸發,2026-06-16 起):
+- `workflow_run: Release completed` = **發版主路徑**(Release 成功 → npm 已有新版本 → mirror 內部 poll 第一輪即過,零等待)
+- protected PR merge 產生的 `main` push + template-affecting paths(scaffold 改動路徑；版本未上 npm 時 graceful skip 不長等)— path 列表以 `.github/workflows/mirror-to-published-template.yml` `paths:` 為準，不在此逐條複寫
+
+**Build**:`scripts/build-published-template-mirror.mjs` 用 ALLOWLIST(non denylist,per codex r5)+ transform:
+- Flatten `template/ds-product-template/*` → mirror root
+- Transform `package.json`:`workspaces=["apps/*"]` + DS/Storybook deps exact `X.Y.Z`
+- Transform `apps/template/package.json`:`@qijenchen/design-system: "*"` → exact `X.Y.Z`
+- 4 integrity scans:DS source residue / secret leak / Storybook glob / package dep
+- `product-template-scaffold.lock.json` 在 provider/fork 生成完成後對 mirror 的每個靜態發布檔案鎖定 path/mode/size/SHA-256，並將唯一發布後生成路徑 `package-lock.json` 連同 pinned npm generator contract 關閉。該 lock 本身是 BOM-bound immutable Release asset；最終 lockfile bytes 再由 mirror receipt 的 full-tree digest 綁定。
+
+**Promotion**:credential-free job 先重驗 immutable BOM → scaffold-lock exact bytes → 最終 full-tree receipt，fresh writer 再對解壓樹與 rsync 後 checkout 重驗。workflow 以短效 GitHub App token clone + checksum overlay **完整 allowlisted tree(含 workflows)**，重生 lockfile後推 dedicated branch、開 PR。published `main` 禁直推；required checks + review 通過才 merge。缺 App credentials 時 fail-closed，禁止退回 long-lived PAT 或靜默保留 stale workflow。
+
+## 4. Test Cases(Claude 19 + codex 18 union → 20 canonical)
+
+### Scenario A(6 cases)
+
+| # | Test | Verify cmd |
+|---|---|---|
+| A1 | Workspace link resolution(apps/template DS dep `*` → packages/design-system local)| `jq '.dependencies' apps/template/package.json` |
+| A2 | DS source edit → canonical classifier：工程 remediation PASS；未具 current-scope exact target + operation-digest decision 的產品／UI／UX SSOT 取捨 BLOCK + 中文訊息 | `bash packages/design-system/ds-canonical/hooks/tests/test_check_substantive_edit_approval_preflight.sh` |
+| A3 | Canonical corpus 可讀且所有 enabled provider adapter 與它一致(無需 /plugin install)| `node scripts/sync-ds-canonical.mjs --check` |
+| A4 | `npm run create-app <name>` → `apps/<name>/` 從 `apps/template/` 複製 + story title patched `Apps/<name>/...` | run + ls + grep |
+| A5 | DS root `npm run storybook` 含 DS internal stories + `apps/**` stories,namespace 不撞 | grep `.storybook/main.ts` stories glob + 跑 storybook |
+| A6 | Workspaces 含 `apps/*` | `jq '.workspaces' package.json` |
+
+### Scenario B(7 cases,via mirror artifact)
+
+| # | Test | Verify cmd |
+|---|---|---|
+| B1 | Mirror artifact npm deps exact `X.Y.Z`(not range/tag/workspace `*`)| `jq '.dependencies' /tmp/mirror/package.json` |
+| B2 | Mirror 0 DS source(`packages/design-system/src/` 不存在)| `! -d /tmp/mirror/packages/design-system` |
+| B3 | Mirror workspaces apps-only | `jq '.workspaces' /tmp/mirror/package.json` |
+| B4 | Mirror `.storybook/main.ts` apps-only glob | grep stories |
+| B5 | Mirror 含 `check-plugin-installed.mjs` + `setup-netlify-access.mjs` + `create-app.mjs` | ls /tmp/mirror/scripts/ |
+| B6 | Day-0 provider parity(免 plugin):AGENTS + Claude/Codex adapters + 全分類 skills 已 committed；SessionStart zero-write；dispatcher/hard gates 行為一致 | `node scripts/test-fork-governance.mjs` + clean-room provider probes |
+| B7 | `npm run create-app` 同 Scenario A | run + ls |
+
+### Mirror integrity(7 cases)
+
+| # | Test | Verify cmd |
+|---|---|---|
+| M1 | Trigger on protected DS PR merge/main event with template-affecting paths(workflow path filter)| workflow log |
+| M2 | DS source residue scan 0 leak(8 paths checked)| build script integrity scan 1 |
+| M3 | Secret leak scan 0 leak(6 paths checked)| build script integrity scan 2 |
+| M4 | Storybook glob apps-only(no `../packages/**`)| build script integrity scan 3 |
+| M5 | package.json workspaces apps-only + DS dep transformed | build script integrity scan 4 |
+| M6 | `apps/template/package.json` DS dep `*` → exact `X.Y.Z` | build script auto transform |
+| M7 | Clone-and-overlay output reproducible；live path 只開 App-authored PR、不直推 main | local double-build diff + workflow run/PR evidence |
+
+## 5. Verify Checkpoints — 後續增刪改 reference 此 SSOT
+
+任何 future edit:
+- 動 `apps/template/` → 影響兩 scenario 的 seed,測 A4 + B7
+- 動 `scripts/{create-app,setup-netlify-access,check-plugin-installed,...}.mjs` → 測 A4 + B5 + mirror integrity scan
+- 動 `.storybook/main.ts`(DS root)→ 測 A5
+- 動 `template/ds-product-template/.storybook/main.ts` → 測 B4 + M4
+- 動 mirror script `build-published-template-mirror.mjs` → 重跑 4 integrity scans + M2-M5
+- 動 mirror workflow `.yml` → workflow_dispatch dry-run
+
+## 6. Cross-references(其他 file 該 pointer 到本 SSOT,不重述定義)
+
+| File | Reference type |
+|---|---|
+| `packages/design-system/ds-canonical/skills/deep-audit-cross-codex/SKILL.md` Phase 0 cwd detection | 已 reference(2-mode based on cwd structure)|
+| `packages/design-system/ds-canonical/skills/design-system-audit/SKILL.md` dim 83 | 該砍重述部分,改 pointer here |
+| DS root `AGENTS.md` task nav row「建產品 / 開新 product app」 | 該 pointer here |
+| provider-specific generated adapter `template/ds-product-template/CLAUDE.md` `# Fork-and-go onboarding` 段 | 該 pointer here for Scenario B specifics |
+| `template/README.md` 命名 SSOT 段 | 該 pointer here for 3-layer naming |
+
+## 7. Anti-pattern(永久 ban)
+
+- ❌ Scenario A 文件叫 user `/plugin install`(repo 已含 canonical corpus + generated native adapters)
+- ❌ Scenario B 文件假設 user 看得到 `packages/design-system/src/`
+- ❌ Mirror 用 denylist `rm -rf packages/design-system/src`(per codex「太 narrow 會漏 governance/log/planning leak」)
+- ❌ Mirror 使用 long-lived PAT、直推 main、或排除 `.github/workflows` 造成 receiver drift
+- ❌ GitHub App credentials 缺失時 silent succeed / fallback PAT(必 fail-closed)
+- ❌ `apps/template/package.json` DS dep `"beta"` 字串(Gap 3,scenario A workspace resolution vs scenario B npm version 行為不同)
+- ❌ DS root `.storybook/main.ts` 漏 `apps/**` glob(Scenario A 看不到自己 product apps)
+- ❌ Mirror `.storybook/main.ts` 含 `../packages/**` glob(Gap 4,published mirror 不該 leak DS trait grid)
+
+## 8. 對齊上游 canonical
+
+- AGENTS.md mindset 全 + canonical `packages/design-system/ds-canonical/rules/meta-patterns.md` 動態 active M-rule inventory + rule-placement Level 1–9 taxonomy + 自主執行 canonical + 命名 SSOT 3-test(per deep-audit-cross-codex SKILL.md「上游 canonical 全繼承」段 2026-05-29)
+- M17 SSOT 鐵律(本 file 就是 example:single canonical home,其他 file pointer)
+- M19 trigger phrase auto-pipeline + M28 solo-work canonical
+- 命名 SSOT 3 層(per `template/README.md`「命名 SSOT」段)

package/ds-canonical/references/spec-rules.md

@@ -1,6 +1,6 @@
 # Spec 規則 — 詳細展開
 
-`.claude/rules/spec-rules.md` 的詳表。主章留核心原則,本檔放 SSOT 判斷 + 邊界案例 scope default + 禁止清單。
+Canonical `packages/design-system/ds-canonical/rules/spec-rules.md` 的詳表。主章留核心原則,本檔放 SSOT 判斷 + 邊界案例 scope default + 禁止清單。
 
 ## SSOT 結構規則
 

package/ds-canonical/references/ssot-consultation.md

@@ -1,6 +1,6 @@
 # SSOT 消費 canonical — 完整對照 + 反例
 
-CLAUDE.md `# SSOT 消費 canonical` 的詳表 + 反例。主章留核心 + pointer,本檔放大對照表 + 禁止清單 + tsx 註解模板。
+AGENTS.md `# SSOT 消費 canonical` 的詳表 + 反例。主章留核心 + pointer,本檔放大對照表 + 禁止清單 + tsx 註解模板。
 
 ## 視覺決策 → 必查清單(完整)
 
@@ -8,7 +8,7 @@ CLAUDE.md `# SSOT 消費 canonical` 的詳表 + 反例。主章留核心 + point
 |------|---------------|
 | **元件選擇**(這該用哪個既有元件?)| `ls packages/design-system/src/components/` + `ls packages/design-system/src/patterns/` + 近親元件 spec |
 | **Token / 值**(padding / gap / height / color)| 對應 `tokens/{name}/spec.md` + `tokens/README.md` |
-| **Padding / spacing**(chrome vs 元件內 vs 精確幾何)| `.claude/rules/ui-development.md`「Padding source 分層規則」+ `tokens/layoutSpace/layoutSpace.spec.md` |
+| **Padding / spacing**(chrome vs 元件內 vs 精確幾何)| `packages/design-system/ds-canonical/references/ui-dev-rules.md`「Padding source 分層規則」+ `tokens/layoutSpace/layoutSpace.spec.md` |
 | **Row / item 結構**(prefix / content / suffix slot)| `patterns/element-anatomy/item-anatomy.spec.md`(Family 1+2 SSOT) |
 | **連續 item list wrapper gap** | `patterns/element-anatomy/item-anatomy.spec.md`「連續 item 貼邊合法性」— 公式:permanent standalone card/pill → 必 gap;permanent flush / transparent → 0 gap。元件專屬 gap 值 + mixed 混合情境決策表查該元件 spec「List wrapper canonical」節 |
 | **視覺容器 breathing**(自建或 override 帶 bg/border/shadow 的 div)| `patterns/element-anatomy/element-anatomy.spec.md`「視覺容器 breathing invariant」— 有視覺邊界容器必有 inner padding。責任在父容器,子元件 w-full responsive 不變 |
@@ -21,7 +21,7 @@ CLAUDE.md `# SSOT 消費 canonical` 的詳表 + 反例。主章留核心 + point
 | **Overlay chrome dismiss / unbounded button**| `patterns/overlay-surface/overlay-surface.spec.md`「Chrome dismiss size canonical v5」 |
 | **Overlay title size**(modal 16 vs non-modal 14)| `patterns/overlay-surface/overlay-surface.spec.md`「Overlay title typography canonical」 |
 | **Form field gap**| `components/Field/field.spec.md` +「layoutSpace 規則 3:跟 block 相鄰 = tight,inline ↔ inline = loose」 |
-| **Icon 選擇 / 尺寸**| `.claude/rules/ui-development.md`「元件 Props 命名」「Icon canonical」+ `ui-dev-rules.md`「Icon size 來源分層規則」 |
+| **Icon 選擇 / 尺寸**| `packages/design-system/ds-canonical/rules/ui-development.md`「元件 Props 命名」「Icon canonical」+ `ui-dev-rules.md`「Icon size 來源分層規則」 |
 | **浮層 header / body / footer**| `patterns/overlay-surface/overlay-surface.spec.md` |
 | **Scrollbar / 滾動**| `components/ScrollArea/scroll-area.spec.md` +「horizontal-overflow pattern」 |
 | **Variant / prop 命名**| 既有元件 `variant=` 值 grep + `# 命名與語言一致性`「命名必過三重 test」 |
@@ -50,7 +50,7 @@ CLAUDE.md `# SSOT 消費 canonical` 的詳表 + 反例。主章留核心 + point
  */
 ```
 
-Hook `check_ssot_consultation.sh`(Write 新 tsx 到 `packages/design-system/src/components/` 或 `src/explorations/`)→ 若檔內無上述註解區 → warn 要求補齊。
+Hook `check_ssot_consultation.sh` retired;**2026-07-07 以 `check_ssot_header_declaration.sh` 精簡復活**(新建 production tsx 必帶「── 消費的 SSOT ──」段,P0 BLOCKER)+ mindset #2 + `check_canonical_propagation.sh`。(2026-07-10 hunt 修 stale 描述)
 
 ## 禁止:隱性自創
 
@@ -60,4 +60,4 @@ Hook `check_ssot_consultation.sh`(Write 新 tsx 到 `packages/design-system/src/
 - 自寫 `<button aria-label="Close"><X /></button>` 作 dismiss(應用 `ItemInlineAction`)
 - 自寫 Row `<div><Icon /><span>label</span><Button /></div>`(應用 `<MenuItem>` + slot)
 - 自訂 Input `variant="custom-name"` 未先 grep 既有 variant 值
-- 在 Toolbar 用 `<input className="bg-transparent border-0 ...">`(應用 `<Input variant="bare">` 若既有;無 → Ambiguity Protocol)
+- 在 Toolbar 用 `<input className="bg-transparent border-0 ...">`(應用 `<Input size="sm" autoWidth>` 標準 default variant;`variant="bare"` 已於 2026-07-09 退役,不再使用)

package/ds-canonical/references/ssot-index.md

@@ -12,29 +12,30 @@
 
 | Interface | Owner spec | Canonical sentence | Drift status | Last divergence event |
 |---|---|---|---|---|
-| **DataTable body cell internal indicator**(display endAction / clear / edit indicator)| `data-table.spec.md:204` + `inline-action.spec.md:157` | 「Body cell internal = Field family endAction(自動繼承)」「Field display 元件已對齊」 | ⚠ **DRIFT**:`data-table.tsx:1074-1191` `getEditIndicator(colType)` parallel system,`:1190` comment 反向說 SSOT 在 DataTable cellEl | 2026-05-08 round 5(`.claude/planning/cell-indicator-ssot-rfc.md` pending decision)|
-| **Field naked variant state ring**(hover / focus / open / error)| `field-wrapper.tsx:140-189` cva compoundVariants(v13.3)+ `field.spec.md:371-415`「focus dominates everything」| 「SSOT 在 field-wrapper.tsx 三 compoundVariant — 改一處全 control + cell + variant 跟動」 | ✅ aligned(2026-05-08 D path canary 違反後 revert)| 2026-05-08 round 4(D path canary 違反 SSOT,已 revert `f0faab9`)|
+| **DataTable body cell internal indicator**(view endAction / clear / edit indicator)| `data-table.spec.md`「Body cell internal」row + `inline-action.spec.md`「DataTable body cell internal」row | 「Body cell internal = Field family endAction(自動繼承)」「Field view 元件已對齊」 | ✅ aligned:2026-05-09 D-path retired — `getEditIndicator(colType)` parallel system 移除,indicator authority 移交 Field naked view `showDisplayEndIcon` opt-in(prop 名保留),cellEl 不再 render parallel indicator(見 data-table.tsx「D-path retired」註解);2026-07-08 A 案:cell-registry 預設不再傳(view 態零恆顯 icon,prop 留 opt-in 逃生門,見 field.spec L6 v16)| 2026-05-08 round 5 → 2026-05-09 resolved |
+| **Field naked variant state ring**(hover / focus / open / error)| `field-wrapper.tsx` cva compoundVariants(v13.3)+ `field.spec.md`「focus dominates」段 | 「SSOT 在 field-wrapper.tsx 三 compoundVariant — 改一處全 control + cell + variant 跟動」 | ✅ aligned(2026-05-08 D path canary 違反後 revert)| 2026-05-08 round 4(D path canary 違反 SSOT,已 revert `f0faab9`)|
 | **Row prefix/suffix slot**(`<ItemPrefix>` / `<ItemSuffix>`)| `patterns/element-anatomy/item-anatomy.spec.md:175+190` | 「row prefix/suffix slot 必走 patterns/element-anatomy L1 primitive」「`h-[1lh] shrink-0 flex items-center` 普世正確」 | ✅ aligned(hook `check_pattern_invariants.sh` C.4 enforce)| — |
-| **Inline action gap**(ItemInlineAction sibling spacing)| `patterns/element-anatomy/inline-action.spec.md:80` | 「inline-action 跟 sibling gap 必 = `gap-2`(8px)」 | ✅ aligned(hook C.2 enforce)| — |
+| **Inline action gap**(ItemInlineAction sibling spacing)| `patterns/element-anatomy/inline-action.spec.md`「多個 inline action 間距」段 | 「inline-action 跟 sibling gap 必 = `gap-2`(8px)」 | ✅ aligned(hook C.2 enforce)| — |
 | **Drag visual**(drop indicator / drag overlay)| `lib/drag-visual.ts`(2026-05-06 v14.5)+ `tree-view.spec.md:265` | 「TreeView 是 DS 內最早 codified 的 drag canonical,DataTable row drag + column reorder 都 inherit via drag-visual.ts SSOT module」 | ✅ aligned | — |
-| **Color tokens**(primitive vs semantic)| `tokens/color/color.spec.md`(架構流派定位)+ `tokens/color/semantic.css` | 「禁 primitive 色名作 utility,用 semantic alias」 | ✅ aligned(hook D.3 enforce)| — |
-| **Layout space**(region/element + 親疏三級)| `tokens/layoutSpace/layoutSpace.spec.md` v6 + `feedback_layout_v6_canonical.md` | 「region/element + bounded/unbounded + 親疏三級」 | ✅ aligned(2026-05-01 flush variant retire)| 2026-05-01 |
+| **Color tokens**(primitive vs semantic)| `tokens/color/color.spec.md`(架構流派定位)+ `tokens/color/semantic.css` | 「禁 primitive 色名作 utility,用 semantic alias」 | ✅ aligned(hook `check_naming_and_abstraction.sh` D.3 enforce)| — |
+| **Layout space**(region/element + 親疏三級)| `tokens/layoutSpace/layoutSpace.spec.md` v6(原 memory `feedback_layout_v6_canonical.md` 已 retire)| 「region/element + bounded/unbounded + 親疏三級」 | ✅ aligned(2026-05-01 flush variant retire)| 2026-05-01 |
 | **DataTable scroll**(3-region synced + cross-OS scrollbar)| `data-table.spec.md:245-251` | 「center body 用 native overflow-x-auto(非 ScrollArea),pinned column 三 region 同步」 | ✅ aligned(v15.13 interim CSS parity for Windows Bug H,deferred ScrollArea full migration)| 2026-04-30 / 2026-05-07 |
-| **Cell display vs edit content position**(picker offset)| `field.spec.md:407` Layout Family 4 + `data-table.spec.md:204` | 「Field control display + edit 共用同 wrapper geometry」 | ⚠ **MISALIGNED**:6 picker display 走裸 span,跟 edit Field wrapper 不同 DOM | 2026-05-07~08 round 1-5(blocked on indicator SSOT decision)|
-| **Field state machine focus dominates**(v13.3)| `field-wrapper.tsx:140-189` + `field.spec.md:371-415` + `check_field_family_invariants.sh` A.3 | 「focus dominates everything;naked 不寫平行 outline ring」 | ✅ aligned;hook A.3 enforce | 2026-05-06 v9-v13.3 5 round refinement |
-| **Solo dev workflow**(1 chat = 1 branch / Netlify gate / squash merge)| `feedback_solo_dev_workflow.md` + CLAUDE.md「Git solo-work canonical」 | 「1 chat = 1 working branch;Netlify preview = user gate;『push / OK』trigger 才 merge main」 | ✅ aligned(M28 + hook `check_solo_workflow.sh`)| 2026-05-08 M28 codify |
+| **Cell view vs edit content position**(picker offset)| `field.spec.md`「Layout Family 4」段 + `data-table.spec.md`「Body cell internal」row | 「Field control view + edit 共用同 wrapper geometry(Model A:view×default = edit 幾何減 chrome,保留 px/py)」 | ✅ aligned:DataTable cell 場景走 Field naked(`showDisplayEndIcon` opt-in);standalone `mode="view"` 走 view×default = edit 幾何減 chrome(2026-07-16 Model A,原 bare-span deferral 已兌現;值內容層 4-mode 共享 renderer,見 select.tsx 檔頭 `@renderer-symmetry-allow`)| 2026-05-07~08 round 1-5 → 2026-07-16 Model A resolved |
+| **Field state machine focus dominates**(v13.3)| `field-wrapper.tsx` cva compoundVariants + `field.spec.md`「focus dominates」段 + `check_field_family_invariants.sh` A.3 | 「focus dominates everything;naked 不寫平行 outline ring」 | ✅ aligned;hook A.3 enforce | 2026-05-06 v9-v13.3 5 round refinement |
+| **Protected solo workflow**(1 task = 1 branch + 1 PR / required CI / standing engineering delegation)| `infra/governance/release-workflow.json` + `feedback_solo_dev_workflow.md` + AGENTS.md「Git solo-work canonical」 | protected main 禁 direct push；PR 建立正常；required CI/conversations resolved 後由 `release:auto` 自主走 `pr-checks → merge → publish → readback → consumer`；preview/canary/attestation 非 blocking | ✅ aligned(M28 + hooks + GitHub ruleset)| 2026-07-20 migration / 2026-08-02 five-step reconciliation |
 | **Wrapper-vs-primitive schema unify**(SelectOption / MenuItemProps 等)| `SelectMenu/select-menu.tsx` SelectMenuOption + `Combobox/combobox.tsx` extends + `PeoplePicker/people-picker.tsx` extends | 「wrapper API schema 必 `extends primitive`,wrapper 內部 mapping 必 forward 全 primitive surface field(M30)」 | ✅ aligned(2026-05-10 Round 1 commit `561945b` Combobox extends + forward 全 field;PeoplePicker 對齊 + hook `check_wrapper_primitive_schema_drift.sh` BLOCKER)| 2026-05-10 M30 codify |
+| **空值顯示符號 + 分流**(empty value display)| `field-context.ts` `useFieldEmptyDisplay()`(分流 hook)+ `field-wrapper.tsx` `EMPTY_DISPLAY = '-'`(半形常數)+ `field-controls.spec.md`「null / undefined 值」段 | 「符號 = 半形 hyphen `-`(U+002D),**非**全形 em dash;`surface==='table-cell' && isEditable ? '' : '-'`;可編輯 form edit 走 native placeholder。全 Field family 空值渲染必經 hook,consumer 禁直引 `EMPTY_DISPLAY`」 | ✅ aligned(2026-07-08 user 拍板半形;hook `check_field_family_invariants.sh` A.6 BLOCKER — 禁非 owner 直引常數 + 禁 hardcode 全形 em dash;DescriptionList / ProfileCard / FileViewer consumer 同步半形)| 2026-07-08 user directive |
 
 ## How to maintain
 
 - 新 interface 第一次 surface → 加進本 index
 - 新 divergence 發現 → 加 row + 標 ⚠ DRIFT
 - Drift 解決 → 改 ✅ aligned
-- 重大 round 結束 → 跑 audit Dim 38 反 grep verify
+- 重大 round 結束 → 逐 row 反 grep owner spec/code 驗仍一致(`/deep-audit-cross-codex` Phase A 必讀清單已含本檔,見 `phase-a-workflow.md:15`;無專屬 audit dim 機械化)
 
 ## 與 hook 關係
 
-- `check_ds_anchor_preflight.sh`(待 ship)— 偵測編 Field / DataTable / patterns code 時 stderr 提醒「先 grep ssot-index.md」
+- `check_ds_anchor_preflight.sh`(live,P0 BLOCKER exit 2,2026-07-07 升級)— 偵測 production tsx / apps consumer 內 DS primitive wrap 而無 canonical read trace → block;bypass `CLAUDE_BYPASS_DS_ANCHOR=1`(audit-logged)
 - `check_field_family_invariants.sh` A.3 — 機械化 enforce v13.3 SSOT
 - `check_pattern_invariants.sh` C.4 — 機械化 enforce row slot SSOT
 - `check_canonical_propagation.sh` E.2 — 機械化 enforce L3 primitive import

package/ds-canonical/references/story-baseline-registry.json

@@ -1,37 +1,67 @@
 {
   "$schema": "./story-baseline-registry.schema.json",
+  "schemaVersion": 1,
   "_meta": {
-    "purpose": "Anti-drift registry for stories wrap既有 primitive(Sidebar / ChromeHeader / DataTable / Dialog / Sheet / Popover)— machine-readable canonical archetype。Hook `check_story_invariants.sh R8` reads this(not grep spec.md / not憑 Claude judgment)to enforce nearest same-purpose canonical usage(per codex Layer B D4 2026-05-20)。新增 primitive entry 必先寫 baseline + helper list + antiPatterns regex + variantRules。",
-    "owner": ".claude/references/story-baseline-registry.json",
+    "purpose": "Anti-drift registry for stories wrap既有 primitive(Sidebar / ChromeHeader / DataTable / Dialog / Sheet / Popover)— machine-readable canonical archetype。Hook `check_story_invariants.sh R8` reads this(not grep spec.md / not憑 Claude judgment)to enforce nearest same-purpose canonical usage(per codex Layer B D4 2026-05-20)。新增 primitive entry 必先寫 baseline + helper list + antiPatterns regex + buttonCanonical。",
+    "owner": "packages/design-system/ds-canonical/references/story-baseline-registry.json",
     "consumed_by": [
-      ".claude/hooks/check_story_invariants.sh#R8(story_archetype_registry)",
-      ".claude/skills/story-writing/SKILL.md#Phase-0.0(load registry + read baseline + produce diff table)"
+      "packages/design-system/ds-canonical/hooks/check_story_invariants.sh#R8(story_archetype_registry)",
+      "packages/design-system/ds-canonical/skills/story-writing/SKILL.md#Phase-0.0(load registry + read baseline + produce diff table)"
     ],
+    "provider_view_policy": ".claude/.agents/.codex projections are generated discovery adapters only; they are never registry owners or edit targets.",
     "rollout": "ship as warn mode first;確認 zero existing violation → 升 P0 BLOCKER"
   },
   "components": {
     "Sidebar": {
       "baseline": "packages/design-system/src/components/Sidebar/sidebar.stories.tsx#IconCollapse",
-      "requiredHelpers": ["WorkspaceBrand", "MAIN_NAV", "SidebarHeader", "SidebarFooter"],
+      "requiredHelpers": [
+        "WorkspaceBrand",
+        "MAIN_NAV",
+        "SidebarHeader",
+        "SidebarFooter"
+      ],
       "antiPatterns": [
         {
           "id": "sidebar-header-simplified-span",
-          "regex": "<SidebarHeader>\\s*<span",
+          "regex": "<SidebarHeader[^>]*>[[:space:]]*<span",
           "severity": "block",
           "rationale": "SidebarHeader 必 wrap WorkspaceBrand-like ItemAvatar block(per sidebar.stories#IconCollapse baseline);simplified <span> mock = drift"
         },
         {
           "id": "sidebar-menu-button-inline-icon",
-          "regex": "<SidebarMenuButton>[^<]*<[A-Z][a-zA-Z]+\\s+className=\"size-",
+          "regex": "<SidebarMenuButton[^>]*>[^<]*<[A-Z][a-zA-Z]+[[:space:]]+className=\"size-",
           "severity": "block",
           "rationale": "SidebarMenuButton 必用 startIcon prop + tooltip prop;children inline icon = drift"
+        },
+        {
+          "id": "sidebar-header-subtitle-second-line",
+          "regex": "<SidebarHeader[^>]*>[[:space:]]*<div[^>]*flex-col",
+          "severity": "block",
+          "rationale": "SidebarHeader brand 必單行(Fixed-h chrome 不可成長,sidebar.spec.md SidebarHeader 段 2026-06-12 明文)。flex-col 直接子層 = logo name 下加副標的結構簽名 — shadcn TeamSwitcher demo prior 滲漏;plan/org 資訊歸 workspace switcher dropdown row,非常駐 header"
+        },
+        {
+          "id": "sidebar-footer-two-line",
+          "regex": "<SidebarFooter[^>]*>.{0,255}(text-xs|leading-tight)",
+          "severity": "block",
+          "rationale": "SidebarFooter user 區必單行(名字 only;職稱/email 等身份資訊歸帳號選單 DropdownMenuLabel 第二行 text-caption,sidebar.stories.tsx UserFooter canonical;自己的 avatar 不掛 ProfileCard hoverCard——rule owner app-shell.spec.md 帳號入口放置 SSOT)。shadcn nav-user 的「name + email text-xs 兩行」是強 LLM 先驗,且 text-xs 違反 chrome typography canonical(sidebar.spec『chrome 內 text 一律 text-body-lg』);255 字元窗符合 POSIX ERE RE_DUP_MAX 並限制 greediness"
+        },
+        {
+          "id": "sidebar-handbuilt-account-trigger",
+          "regex": "<DropdownMenuTrigger[^>]*>[[:space:]]*<button[^>]*>.{0,160}<Avatar\\b",
+          "severity": "warn",
+          "rationale": "手刻帳號觸發鏈(DropdownMenuTrigger 直包 raw <button> 再包 raw <Avatar>)= 帳號入口 hand-mock 簽名 — 帳號選單必消費 AccountMenu reference(AppShell/_demo-helpers.tsx;app-shell.spec.md「帳號入口放置 SSOT」),且帳號入口只能出現一次(primary-sidebar = SidebarFooter / primary-header = globalHeader 右)。WM F9 錨例(2026-07-30 pre-fix 1a26bd1^):SidebarHeader 右上手刻此鏈與 SidebarFooter user 區並存。雙位置 duplicate 的完整 conjunction 不可單條 ERE 表達(unlessRegex 檔級豁免在錨例實測失效 — 錨例檔同時含 ChromeHeader/isMobile 字面)→ hard P0 BLOCK 由 check_consumer_code_quality.sh 帳號入口 duplicate 段(python block-scope)承擔;本條為 story 層 early-warn。footer canonical(DropdownMenuTrigger > SidebarMenuButton)不直包 raw <button> → 不誤警;stories 全 corpus 實測 0 hit"
         }
       ]
     },
     "DataTable": {
       "baseline": "packages/design-system/src/components/DataTable/data-table.stories.tsx#WithBulkActions",
       "toolbar": {
-        "requiredHelpers": ["Popover", "PopoverTrigger", "PopoverContent", "Input"],
+        "requiredHelpers": [
+          "Popover",
+          "PopoverTrigger",
+          "PopoverContent",
+          "Input"
+        ],
         "filterPanel": "DataTableFilterPanel",
         "sortManager": "DataTableSortManager",
         "buttonCanonical": {
@@ -57,9 +87,17 @@
         },
         {
           "id": "datatable-toolbar-no-popover-wrap",
-          "regex": "startIcon=\\{(Filter|ArrowUpDown)\\}(?![\\s\\S]*?(DataTableFilterPanel|DataTableSortManager))",
+          "regex": "startIcon=\\{(Filter|ArrowUpDown)\\}",
           "severity": "warn",
-          "rationale": "DataTable toolbar filter/sort button 必包在 Popover 內,內含真 DataTableFilterPanel / DataTableSortManager primitive"
+          "rationale": "DataTable toolbar filter/sort button 必包在 Popover 內,內含真 DataTableFilterPanel / DataTableSortManager primitive(2026-07-04 dim 54:原 PCRE lookahead 在 ERE grep exit 2 永不 fire → 改兩段式 regex+unlessRegex)",
+          "unlessRegex": "DataTableFilterPanel|DataTableSortManager"
+        },
+        {
+          "id": "datatable-always-edit-cell",
+          "regex": "cell:[^;]{0,160}<(DS\\.)?(Select|Combobox|PeoplePicker|DatePicker|TimePicker)\\b",
+          "unlessRegex": "onCellCommit|editable|mode=[\"']view",
+          "severity": "block",
+          "rationale": "cell: 直接渲染恆-edit 控件 = view 態渲染 edit chrome,違 data-table.spec.md:373 indicator A 案(view 零恆顯 + hover outline + meta.editable/onCellCommit)。custom cell 元件包裹的同違規 regex 看不進去 → 由 product-ui-audit judgment 兜底(failure-class registry always-edit-cell)。2026-07-16 dim 54:mode display→view 更名後 unlessRegex stale(0 hit)→ 對齊 view"
         }
       ]
     },
@@ -69,9 +107,15 @@
       "antiPatterns": [
         {
           "id": "chromeheader-span-flex-1",
-          "regex": "<ChromeHeader>[\\s\\S]*?<span\\s+className=\"[^\"]*flex-1[^\"]*\">",
+          "regex": "<ChromeHeader[^>]*>.{0,160}<span[[:space:]]+className=\"[^\"]*flex-1[^\"]*\">",
           "severity": "block",
           "rationale": "ChromeHeader title 該用 <h1 className=\"text-body-lg font-medium\"> 緊鄰 SidebarTrigger,不該用 <span flex-1> 撐空間造成 toggle + title 巨大間距"
+        },
+        {
+          "id": "chromeheader-subtitle-second-line",
+          "regex": "<(ChromeHeader|PageHeader)[^>]*>[[:space:]]*<div[^>]*flex-col",
+          "severity": "block",
+          "rationale": "Chrome 家族永遠 single-row(header-canonical.spec.md:47,剛性 --chrome-header-height);title 下加副標/description = LLM 先驗回填(Polaris Page subtitle / Tailwind UI page heading 先驗),頁面說明文字歸 content 區,非 chrome。flex-col 直接子層 = 兩行結構簽名"
         }
       ]
     }