@qijenchen/design-system 0.1.0-beta.116 → 0.1.0-beta.117

package/AGENTS.md

@@ -1,8 +1,8 @@
 # `@qijenchen/design-system` package scope
 
-This file is a **scoped augmentation**, not a second repository or product-governance SSOT.
+Scoped augmentation only — never a second repository or product-governance SSOT.
 
-- Inside the design-system monorepo, inherit the repository-root `AGENTS.md`; do not restate or override it here. Author governance only in the canonical owners classified by `infra/governance/protected-root-classification.json`, then regenerate the declared build graph.
-- Inside an installed npm package, treat every file under `node_modules/@qijenchen/design-system` as immutable release material. Never patch it in place; fix the upstream DS source, publish an immutable exact version/BOM, and upgrade the consumer through its governed PR flow.
-- Consumer product governance comes from the authenticated `ds-canonical/fork/manifest.json` snapshot materialized into the consumer repository. This package-scoped file is navigation only and must never substitute for that snapshot, its lock, provider adapters, verifier, or protected CI.
-- Rules, hooks, skills, commands, and provider views under this package follow the same owner/output boundary: `ds-canonical/` is the shipped canonical corpus; generated `.claude`, `.codex`, and `.agents` views are rebuildable adapters and are not edit targets.
+- In the monorepo, inherit the root `AGENTS.md`; never restate or override it here. Author governance only in the owners classified by `infra/governance/protected-root-classification.json`, then regenerate the declared build graph.
+- In an installed package, everything under `node_modules/@qijenchen/design-system` is immutable release material: never patch in place; fix upstream, publish an immutable exact version/BOM, upgrade the consumer by governed PR.
+- Consumer governance comes from the authenticated `ds-canonical/fork/manifest.json` snapshot materialized into the consumer repo. This file is navigation only and never substitutes for that snapshot, its lock, adapters, verifier, or protected CI.
+- Same owner/output boundary for rules, hooks, skills, commands, and provider views: `ds-canonical/` is the shipped canonical corpus; generated `.claude`, `.codex`, `.agents` views are rebuildable adapters, not edit targets.

package/dist/patterns/element-anatomy/item-anatomy.js

@@ -1,7 +1,7 @@
 import { jsx, jsxs } from "react/jsx-runtime";
 import * as React from "react";
 import { cva } from "class-variance-authority";
-import { lineClampClass, cn } from "../../lib/utils.js";
+import { cn, lineClampClass } from "../../lib/utils.js";
 import { Avatar } from "../../components/Avatar/avatar.js";
 import { Tooltip, TooltipTrigger, TooltipContent } from "../../components/Tooltip/tooltip.js";
 import { useTruncated } from "../../hooks/use-truncated.js";

package/ds-canonical/fork/AGENTS.md

@@ -1,26 +1,24 @@
 # Product consumer AI governance (provider-neutral)
 
-> **Generated view**: upstream `build-fork-governance.mjs` publishes this role-specific source as
-> `AGENTS.md`. Do not edit the generated copy. Claude loads it through `CLAUDE.md`; Codex and other
-> AGENTS-compatible agents load it directly.
+> **Generated view**: upstream `build-fork-governance.mjs` publishes this source as `AGENTS.md`; never
+> edit the generated copy. Claude loads it via `CLAUDE.md`, Codex and other agents load it directly.
 
 ## Authority and trust boundary
 
-- This repository builds a product with exact versions of `@qijenchen/design-system` and
-  `@qijenchen/storybook-config`; it does not author or publish those packages.
-- Merge enforcement comes from protected `main` requiring exactly one `Verify consumer` check. That
-  check runs the locked install, typecheck, import lint, and build against the exact candidate head.
-- Native Claude/Codex hooks are fast feedback only; hookless operation is judged by the same
-  hooks-off checker. Generated hook commands scrub inherited startup injection before repository
-  launchers, and the running provider host stays an external trust boundary, so hooks never
-  replace protected CI.
-- Run `npm run setup:all` in every fresh local checkout and hosted setup/cache-refresh lifecycle. It
-  installs the committed lock, verifies signatures, and runs the exact checker; SessionStart only verifies.
+- This repository builds a product against exact versions of `@qijenchen/design-system` and
+  `@qijenchen/storybook-config`; it never authors or publishes them.
+- Merge enforcement is protected `main` requiring exactly one `Verify consumer` check, which runs the
+  locked install, typecheck, import lint, and build against the exact candidate head.
+- Native Claude/Codex hooks are fast feedback only; hookless operation is judged by the same hooks-off
+  checker. Hook commands scrub inherited startup injection before repository launchers, and the provider
+  host stays an external trust boundary — hooks never replace protected CI.
+- Run `npm run setup:all` in every fresh local checkout and hosted setup/cache-refresh lifecycle: it
+  installs the committed lock, verifies signatures, and runs the exact checker. SessionStart only verifies.
 - `governance/lock.json`, managed provider adapters, and managed skills are generated upstream.
-  Product-specific, provider-neutral policy belongs in `governance/overlay.md`; read it when present.
-  It may add stricter product rules but must never replace or weaken upstream controls.
+  Product-specific, provider-neutral policy belongs in `governance/overlay.md` (read it when present);
+  it may add stricter product rules but never replaces or weakens upstream controls.
 - Never install a mutable tag or semver range for internal packages. Upgrades are reviewed pull
-  requests that pin an exact version and include the regenerated lock/adapters.
+  requests pinning an exact version with the regenerated lock/adapters.
 <!-- canonical-decision-authority:start -->
 **Decision／Engineering Authority**:user 只拍板產品／UI／UX SSOT 真取捨及可感知／產品語意變更（behavior/interaction/IA/visual/token/layout/content/a11y/canonical rules）；核准 = user 在對話中對 exact target + choice 說可（**「我說可以就是可以，就是授權」— user 2026-08-04 verbatim**；最新一則 user 訊息的明確 blanket 授權即核准當下 pending 的 exact 提案）。operation digest 為可選佐證——有引且相符可加強、有引但不符 fail-closed、未引不阻擋（強制引 digest 屬已拆除的 per-PR 簽章同族儀式，835b519e 先例）。引用/條件/舊 scope/跨 target 無效。其餘工程/external writes 皆 Standing Authorization AUTO，含已核准 UI／UX 實作/機械 generation/sync 與 source→commit/PR/merge→canonical `infra/governance/release-workflow.json` 的 `pr-checks → merge → publish → readback → consumer`；依 frozen scope、SSOT、required checks、security、least privilege、rollback/readback 收斂，不逐 milestone 重問。Deep Audit 必須在單一 branch／PR 完成 remediation 與 local/CI candidate validation，禁止把 immutable publish 當 iteration/test loop，每次 audit 最多一次 final release；只有另有 evidence ref 綁定 incident ID、failure class、published version 的 post-publish blocker 或 security incident 才可額外 release。Certification、rollout、staged rollout、preview/canary 與 independent review 是明確要求時的附加 assurance，不得進入標準 five-step release blocking graph；peer 不可用只阻擋明確要求的 independent-review claim。
 
@@ -31,30 +29,24 @@
 
 ## Six working principles
 
-1. **World-class, no shortcuts**: visual and interaction decisions must be defensible against at
-   least three relevant systems such as Polaris, Material, Atlassian, Ant, Carbon, or Apple HIG.
+1. **World-class, no shortcuts**: visual and interaction decisions must be defensible against at least
+   three relevant systems (Polaris, Material, Atlassian, Ant, Carbon, Apple HIG).
 2. **Consume before inventing**: search the installed public API, nearest component spec, token, and
    pattern before adding a value, wrapper, variant, or layout primitive.
-3. **Change all affected surfaces**: product code, tests/stories, and product documentation move
-   together. A DS defect is reported upstream with a minimal reproduction; never patch `node_modules`.
-4. **Use real product scenarios**: examples must represent recognizable business work, not Option
-   A/B/C placeholders or minimal mocks that conceal composition problems.
+3. **Change all affected surfaces**: product code, tests/stories, and docs move together. A DS defect is
+   reported upstream with a minimal reproduction; never patch `node_modules`.
+4. **Use real product scenarios**: examples show recognizable business work, not Option A/B/C
+   placeholders or minimal mocks that conceal composition problems.
 5. **Ask only for a genuine product decision**: first search current product usage and the nearest
-   shipped DS spec. Stop only when the remaining choice changes product UX or canonical meaning.
-6. **Fix the invariant, not one symptom**: search for sibling occurrences, add a regression proof,
-   and route reusable DS/template defects to their canonical upstream owner.
+   shipped DS spec; stop only when the remaining choice changes product UX or canonical meaning.
+6. **Fix the invariant, not one symptom**: search sibling occurrences, add a regression proof, and route
+   reusable DS/template defects to their canonical upstream owner.
 
 ## Before changing product UI
 
-Record the canonical inputs you inspected:
-
-- public component/pattern exports from `@qijenchen/design-system`;
-- the nearest shipped `*.spec.md` under
-  `node_modules/@qijenchen/design-system/src/`;
-- relevant token docs under
-  `node_modules/@qijenchen/design-system/src/tokens/`;
-- a nearest shipped story or a real product precedent;
-- any product-specific exception and its concrete rationale.
+Record the canonical inputs you inspected: public component/pattern exports; the nearest shipped
+`*.spec.md` and token docs under `node_modules/@qijenchen/design-system/src/`; a nearest shipped story
+or real product precedent; and any product-specific exception with its concrete rationale.
 
 Only import public package exports. Deep imports, copied DS source, raw primitive reimplementations,
 magic visual values, and undocumented escape markers are governance failures.
@@ -75,14 +67,10 @@ allowed only when the shipped spec makes it intentional and the exception is nar
 
 ## Verification contract
 
-For every change, run the checks that exist in this product and report their real outcome. The
-minimum repository-wide contract is:
-
-1. `npm run governance:check` (exact installed, hooks-off authority);
-2. `npm run typecheck`;
-3. `npm run build`;
-4. product lint/test/a11y scripts when present;
-5. browser or Storybook visual verification for user-visible changes.
+Run every check this product has and report its real outcome. The minimum repository-wide contract is
+`npm run governance:check` (exact installed, hooks-off authority), `npm run typecheck`, `npm run build`,
+product lint/test/a11y scripts when present, and browser or Storybook visual verification for
+user-visible changes.
 
 Never replace a check with `true`, an empty script, a notice-only waiver, or an unverified claim.
 Missing required tooling is a failure, not a pass. Evidence must bind the checked source snapshot.
@@ -93,35 +81,30 @@ Missing required tooling is a failure, not a pass. Evidence must bind the checke
 - Native events enter one immutable hook corpus; unsupported events use the exact checker/protected-CI
   fallback and are never presented as native parity.
 - Future providers read `AGENTS.md` and use the same checks; adapters cannot redefine semantics.
-- When an independent-review deliverable is explicitly requested, it requires a distinct certified
-  peer and immutable read-only evidence or reports that claim `REVIEW-BLOCKED`. Peer availability never
-  blocks ordinary engineering or the standard five-step release. Product review cannot authorize
-  DS/template/release changes; route reusable defects upstream.
+- An explicitly requested independent-review deliverable needs a distinct certified peer and immutable
+  read-only evidence, or the report claims `REVIEW-BLOCKED`. Peer availability never blocks ordinary
+  engineering or the standard five-step release. Product review cannot authorize DS/template/release
+  changes; route reusable defects upstream.
 
 ## Git and release flow
 
 - The upstream design-system authority owns the machine-readable release SSOT at
-  `infra/governance/release-workflow.json`: `pr-checks → merge → publish → readback → consumer`.
-  Every engineering step is AUTO; only an unresolved product/UI/UX SSOT choice is ASK. Login,
-  MFA, OAuth, or a missing credential reference pauses only the affected action, then execution resumes AUTO.
+  `infra/governance/release-workflow.json`: `pr-checks → merge → publish → readback → consumer`. Every
+  engineering step is AUTO; only an unresolved product/UI/UX SSOT choice is ASK. Login, MFA, OAuth, or a
+  missing credential reference pauses only the affected action, then execution resumes AUTO.
 - One task uses one working branch and one PR into protected `main`; never direct-push `main`.
-- The required `Verify consumer` check, conversations, and protected-main exact readback must be clear.
-  Then merge and verify under Standing Authorization—no self-approval or chat trigger. Preview, a11y,
+- The required `Verify consumer` check, conversations, and protected-main exact readback must be clear;
+  then merge and verify under Standing Authorization — no self-approval or chat trigger. Preview, a11y,
   visual, canary, and independent-peer evidence are scheduled or optional unless the user explicitly
-  requests them or an unresolved product/UI/UX SSOT choice requires a decision; they never block the
-  standard release by default.
+  requests them, and never block the standard release by default.
 - Product repos never publish the DS; exact-version upgrade PRs merge after `Verify consumer` passes.
 
 ## Pilot and upstream feedback
 
-This product may serve as a canary for the DS/product template. When a failure is reusable:
-
-1. preserve a minimal product reproduction and evidence;
-2. classify the owner as product, DS, template, governance corpus, or deployment infrastructure;
-3. fix the canonical owner first;
-4. release an immutable upstream version;
-5. upgrade this product by exact-version PR and rerun the required `Verify consumer` check;
-6. remove any temporary product workaround after the upstream fix lands.
+This product may serve as a canary for the DS/product template. When a failure is reusable: preserve a
+minimal reproduction and evidence; classify the owner as product, DS, template, governance corpus, or
+deployment infrastructure; fix the canonical owner first; release an immutable upstream version;
+upgrade by exact-version PR and rerun `Verify consumer`; then remove any temporary workaround.
 
 WM is a pilot consumer, not an alternative governance authority. Its local checks may add product
 coverage but may not replace or weaken the shipped lock/checker/provider surfaces.

package/ds-canonical/fork/common/instruction.md

@@ -1,26 +1,24 @@
 # Product consumer AI governance (provider-neutral)
 
-> **Generated view**: upstream `build-fork-governance.mjs` publishes this role-specific source as
-> `AGENTS.md`. Do not edit the generated copy. Claude loads it through `CLAUDE.md`; Codex and other
-> AGENTS-compatible agents load it directly.
+> **Generated view**: upstream `build-fork-governance.mjs` publishes this source as `AGENTS.md`; never
+> edit the generated copy. Claude loads it via `CLAUDE.md`, Codex and other agents load it directly.
 
 ## Authority and trust boundary
 
-- This repository builds a product with exact versions of `@qijenchen/design-system` and
-  `@qijenchen/storybook-config`; it does not author or publish those packages.
-- Merge enforcement comes from protected `main` requiring exactly one `Verify consumer` check. That
-  check runs the locked install, typecheck, import lint, and build against the exact candidate head.
-- Native Claude/Codex hooks are fast feedback only; hookless operation is judged by the same
-  hooks-off checker. Generated hook commands scrub inherited startup injection before repository
-  launchers, and the running provider host stays an external trust boundary, so hooks never
-  replace protected CI.
-- Run `npm run setup:all` in every fresh local checkout and hosted setup/cache-refresh lifecycle. It
-  installs the committed lock, verifies signatures, and runs the exact checker; SessionStart only verifies.
+- This repository builds a product against exact versions of `@qijenchen/design-system` and
+  `@qijenchen/storybook-config`; it never authors or publishes them.
+- Merge enforcement is protected `main` requiring exactly one `Verify consumer` check, which runs the
+  locked install, typecheck, import lint, and build against the exact candidate head.
+- Native Claude/Codex hooks are fast feedback only; hookless operation is judged by the same hooks-off
+  checker. Hook commands scrub inherited startup injection before repository launchers, and the provider
+  host stays an external trust boundary — hooks never replace protected CI.
+- Run `npm run setup:all` in every fresh local checkout and hosted setup/cache-refresh lifecycle: it
+  installs the committed lock, verifies signatures, and runs the exact checker. SessionStart only verifies.
 - `governance/lock.json`, managed provider adapters, and managed skills are generated upstream.
-  Product-specific, provider-neutral policy belongs in `governance/overlay.md`; read it when present.
-  It may add stricter product rules but must never replace or weaken upstream controls.
+  Product-specific, provider-neutral policy belongs in `governance/overlay.md` (read it when present);
+  it may add stricter product rules but never replaces or weakens upstream controls.
 - Never install a mutable tag or semver range for internal packages. Upgrades are reviewed pull
-  requests that pin an exact version and include the regenerated lock/adapters.
+  requests pinning an exact version with the regenerated lock/adapters.
 <!-- canonical-decision-authority:start -->
 **Decision／Engineering Authority**:user 只拍板產品／UI／UX SSOT 真取捨及可感知／產品語意變更（behavior/interaction/IA/visual/token/layout/content/a11y/canonical rules）；核准 = user 在對話中對 exact target + choice 說可（**「我說可以就是可以，就是授權」— user 2026-08-04 verbatim**；最新一則 user 訊息的明確 blanket 授權即核准當下 pending 的 exact 提案）。operation digest 為可選佐證——有引且相符可加強、有引但不符 fail-closed、未引不阻擋（強制引 digest 屬已拆除的 per-PR 簽章同族儀式，835b519e 先例）。引用/條件/舊 scope/跨 target 無效。其餘工程/external writes 皆 Standing Authorization AUTO，含已核准 UI／UX 實作/機械 generation/sync 與 source→commit/PR/merge→canonical `infra/governance/release-workflow.json` 的 `pr-checks → merge → publish → readback → consumer`；依 frozen scope、SSOT、required checks、security、least privilege、rollback/readback 收斂，不逐 milestone 重問。Deep Audit 必須在單一 branch／PR 完成 remediation 與 local/CI candidate validation，禁止把 immutable publish 當 iteration/test loop，每次 audit 最多一次 final release；只有另有 evidence ref 綁定 incident ID、failure class、published version 的 post-publish blocker 或 security incident 才可額外 release。Certification、rollout、staged rollout、preview/canary 與 independent review 是明確要求時的附加 assurance，不得進入標準 five-step release blocking graph；peer 不可用只阻擋明確要求的 independent-review claim。
 
@@ -31,30 +29,24 @@
 
 ## Six working principles
 
-1. **World-class, no shortcuts**: visual and interaction decisions must be defensible against at
-   least three relevant systems such as Polaris, Material, Atlassian, Ant, Carbon, or Apple HIG.
+1. **World-class, no shortcuts**: visual and interaction decisions must be defensible against at least
+   three relevant systems (Polaris, Material, Atlassian, Ant, Carbon, Apple HIG).
 2. **Consume before inventing**: search the installed public API, nearest component spec, token, and
    pattern before adding a value, wrapper, variant, or layout primitive.
-3. **Change all affected surfaces**: product code, tests/stories, and product documentation move
-   together. A DS defect is reported upstream with a minimal reproduction; never patch `node_modules`.
-4. **Use real product scenarios**: examples must represent recognizable business work, not Option
-   A/B/C placeholders or minimal mocks that conceal composition problems.
+3. **Change all affected surfaces**: product code, tests/stories, and docs move together. A DS defect is
+   reported upstream with a minimal reproduction; never patch `node_modules`.
+4. **Use real product scenarios**: examples show recognizable business work, not Option A/B/C
+   placeholders or minimal mocks that conceal composition problems.
 5. **Ask only for a genuine product decision**: first search current product usage and the nearest
-   shipped DS spec. Stop only when the remaining choice changes product UX or canonical meaning.
-6. **Fix the invariant, not one symptom**: search for sibling occurrences, add a regression proof,
-   and route reusable DS/template defects to their canonical upstream owner.
+   shipped DS spec; stop only when the remaining choice changes product UX or canonical meaning.
+6. **Fix the invariant, not one symptom**: search sibling occurrences, add a regression proof, and route
+   reusable DS/template defects to their canonical upstream owner.
 
 ## Before changing product UI
 
-Record the canonical inputs you inspected:
-
-- public component/pattern exports from `@qijenchen/design-system`;
-- the nearest shipped `*.spec.md` under
-  `node_modules/@qijenchen/design-system/src/`;
-- relevant token docs under
-  `node_modules/@qijenchen/design-system/src/tokens/`;
-- a nearest shipped story or a real product precedent;
-- any product-specific exception and its concrete rationale.
+Record the canonical inputs you inspected: public component/pattern exports; the nearest shipped
+`*.spec.md` and token docs under `node_modules/@qijenchen/design-system/src/`; a nearest shipped story
+or real product precedent; and any product-specific exception with its concrete rationale.
 
 Only import public package exports. Deep imports, copied DS source, raw primitive reimplementations,
 magic visual values, and undocumented escape markers are governance failures.
@@ -75,14 +67,10 @@ allowed only when the shipped spec makes it intentional and the exception is nar
 
 ## Verification contract
 
-For every change, run the checks that exist in this product and report their real outcome. The
-minimum repository-wide contract is:
-
-1. `npm run governance:check` (exact installed, hooks-off authority);
-2. `npm run typecheck`;
-3. `npm run build`;
-4. product lint/test/a11y scripts when present;
-5. browser or Storybook visual verification for user-visible changes.
+Run every check this product has and report its real outcome. The minimum repository-wide contract is
+`npm run governance:check` (exact installed, hooks-off authority), `npm run typecheck`, `npm run build`,
+product lint/test/a11y scripts when present, and browser or Storybook visual verification for
+user-visible changes.
 
 Never replace a check with `true`, an empty script, a notice-only waiver, or an unverified claim.
 Missing required tooling is a failure, not a pass. Evidence must bind the checked source snapshot.
@@ -93,35 +81,30 @@ Missing required tooling is a failure, not a pass. Evidence must bind the checke
 - Native events enter one immutable hook corpus; unsupported events use the exact checker/protected-CI
   fallback and are never presented as native parity.
 - Future providers read `AGENTS.md` and use the same checks; adapters cannot redefine semantics.
-- When an independent-review deliverable is explicitly requested, it requires a distinct certified
-  peer and immutable read-only evidence or reports that claim `REVIEW-BLOCKED`. Peer availability never
-  blocks ordinary engineering or the standard five-step release. Product review cannot authorize
-  DS/template/release changes; route reusable defects upstream.
+- An explicitly requested independent-review deliverable needs a distinct certified peer and immutable
+  read-only evidence, or the report claims `REVIEW-BLOCKED`. Peer availability never blocks ordinary
+  engineering or the standard five-step release. Product review cannot authorize DS/template/release
+  changes; route reusable defects upstream.
 
 ## Git and release flow
 
 - The upstream design-system authority owns the machine-readable release SSOT at
-  `infra/governance/release-workflow.json`: `pr-checks → merge → publish → readback → consumer`.
-  Every engineering step is AUTO; only an unresolved product/UI/UX SSOT choice is ASK. Login,
-  MFA, OAuth, or a missing credential reference pauses only the affected action, then execution resumes AUTO.
+  `infra/governance/release-workflow.json`: `pr-checks → merge → publish → readback → consumer`. Every
+  engineering step is AUTO; only an unresolved product/UI/UX SSOT choice is ASK. Login, MFA, OAuth, or a
+  missing credential reference pauses only the affected action, then execution resumes AUTO.
 - One task uses one working branch and one PR into protected `main`; never direct-push `main`.
-- The required `Verify consumer` check, conversations, and protected-main exact readback must be clear.
-  Then merge and verify under Standing Authorization—no self-approval or chat trigger. Preview, a11y,
+- The required `Verify consumer` check, conversations, and protected-main exact readback must be clear;
+  then merge and verify under Standing Authorization — no self-approval or chat trigger. Preview, a11y,
   visual, canary, and independent-peer evidence are scheduled or optional unless the user explicitly
-  requests them or an unresolved product/UI/UX SSOT choice requires a decision; they never block the
-  standard release by default.
+  requests them, and never block the standard release by default.
 - Product repos never publish the DS; exact-version upgrade PRs merge after `Verify consumer` passes.
 
 ## Pilot and upstream feedback
 
-This product may serve as a canary for the DS/product template. When a failure is reusable:
-
-1. preserve a minimal product reproduction and evidence;
-2. classify the owner as product, DS, template, governance corpus, or deployment infrastructure;
-3. fix the canonical owner first;
-4. release an immutable upstream version;
-5. upgrade this product by exact-version PR and rerun the required `Verify consumer` check;
-6. remove any temporary product workaround after the upstream fix lands.
+This product may serve as a canary for the DS/product template. When a failure is reusable: preserve a
+minimal reproduction and evidence; classify the owner as product, DS, template, governance corpus, or
+deployment infrastructure; fix the canonical owner first; release an immutable upstream version;
+upgrade by exact-version PR and rerun `Verify consumer`; then remove any temporary workaround.
 
 WM is a pilot consumer, not an alternative governance authority. Its local checks may add product
 coverage but may not replace or weaken the shipped lock/checker/provider surfaces.

package/ds-canonical/fork/consumer/lock.json

@@ -3,8 +3,8 @@
   "schemaVersion": 1,
   "role": "template-consumer",
   "release": {
-    "designSystem": "0.1.0-beta.116",
-    "storybookConfig": "0.1.0-beta.116"
+    "designSystem": "0.1.0-beta.117",
+    "storybookConfig": "0.1.0-beta.117"
   },
   "upgradeTrust": {
     "schemaVersion": 1,
@@ -42,13 +42,13 @@
     "implementationSha256": "98b74118fb5b410b77ad2994aa9105fa7609c7353822f8c5213cce54d94f0af4"
   },
   "payload": {
-    "forkCorpusLockSha256": "a0212eb86af934f840c70eb858f0eded52f4f78e35e256b05ee47d056f051371",
+    "forkCorpusLockSha256": "92a7a449773f392fb29ef81c5709e240acd72c96b30343d656fdb63b01af730a",
     "discoveryPolicySha256": "fba289aeeb5a3f11139b9589f7ab08b5e8c8799c7bdf8f0ea57ebfeb8e7c9da6",
     "providerMaterializersSha256": "732e85b01a12e7dd19469e26e4427f0e0cfe5117a78fc9f69c2f0f89702f463a",
-    "providerLifecycleSha256": "070e10807ce68a14f8bb01bf9ccfb6737bd77208f94178c220f1e7785230d5c7",
+    "providerLifecycleSha256": "9a9f921c2dc064d4cf3d0dd0b7fc45e3e322d373ff5c29222bde9e25f33a7223",
     "providerInventorySha256": "00adf1c4f6b3367055a9cc3fdfe658660771b4c9931f696e12761a95076ad92c",
     "executionRuntimeSha256": "d9377cc45308731f287d7b1711b7c38fc4e02ff8f84729bcbbf01bb52d136904",
-    "commonInstructionSha256": "6b9aa8747d9ddc9bd9a78de88a0c3d65f5b100ea917c4dd69be4d889b8299438",
+    "commonInstructionSha256": "a72c51a412d6cdb3961d691744013c8362e826626a330cecf4a296a6f4d93a5c",
     "providerArtifactDigests": {
       "claude": {
         "instructionSha256": "f56a44c730506258cc7e2581dbdd31bfd1e6d13d60dc8a8ee8bcc398228453fb",
@@ -57,7 +57,7 @@
         "treeDigests": {}
       },
       "codex": {
-        "instructionSha256": "6b9aa8747d9ddc9bd9a78de88a0c3d65f5b100ea917c4dd69be4d889b8299438",
+        "instructionSha256": "a72c51a412d6cdb3961d691744013c8362e826626a330cecf4a296a6f4d93a5c",
         "hookSha256": "de8b8a9739dc9736cfe28004cbbc462dae525485202c871af9265d4dd8049740",
         "skillsSha256": "6411ba088fd09f048caca23083e5ef5367887632dd3c604b11f6a1cab5060466",
         "treeDigests": {}
@@ -109,7 +109,7 @@
       "scripts/lib/closed-tool-execution.mjs": "eacd0cd92c5bff03e40ff4e82c02fae9bf2e6f543f157eef3d41c3ed8b7d3cb6",
       "scripts/lib/consumer-control-plane-policy.mjs": "ea8b11ddc5c964ea742ccba5e6a3bc2f215db5d165afe2cca96192812287750c",
       "scripts/lib/exact-workspace-dependencies.mjs": "3c9453e5228d7eaf1bfef3350585746e1aff1475411cb7cf8696bf9acdb048cf",
-      "scripts/lib/governance-dependency-bootstrap.mjs": "79b84cd0a7a8f262d1445503528e1251bb510517efb56550aad659c53c6b3cec",
+      "scripts/lib/governance-dependency-bootstrap.mjs": "8b37cf68731810ad665e02b7ac4a2a5a4ad55b01c6d9e0cbb37f33f3b00118f3",
       "scripts/lib/provider-lifecycle.mjs": "9aabb2c98efc454b8555308a34830e6590b034b10a63f76f788fbd4cf37ce7e7",
       "scripts/lib/verified-exact-npm-runtime.mjs": "811ed3390a4ff6b4e818a5ce8b5c0ce34e10f48fb443b6177d6e4c8e14fa9670",
       "scripts/lib/workspace-post-create.mjs": "f3ddc6db740d5c4d48b1c6e16c55222325e4d1c16fe6644a455e7b7e5bea0a0d",

package/ds-canonical/fork/consumer/managed-files/46f10bc55cdfdf834d0749eebff42ea0bb8576f361b36d2b6ba1851354c50150.blob

@@ -217,7 +217,13 @@ export function runClosedBootstrapStep(command, args, {
     cwd: root,
     env: environment,
     shell: false,
-    stdio: 'inherit',
+    // npm progress lines are diagnostics, not program output. Callers such as
+    // `sync-all.mjs --json` promise a machine-readable stdout, and an inherited fd 1 would
+    // interleave npm chatter with that report (2026-08-06: a consumer upgrade applied
+    // cleanly yet its workflow died on `jq: Invalid numeric literal` because `npm warn` and
+    // `added 4 packages` landed in the report file). Route child stdout to this process's
+    // stderr so the logs stay visible while stdout stays a closed machine channel.
+    stdio: ['inherit', 2, 'inherit'],
     timeout: timeoutMs,
     windowsHide: true,
   })

package/ds-canonical/fork/governance.lock

@@ -7,7 +7,7 @@
     {
       "schemaVersion": 1,
       "file": "AGENTS.md",
-      "sha256": "6b9aa8747d9ddc9bd9a78de88a0c3d65f5b100ea917c4dd69be4d889b8299438",
+      "sha256": "a72c51a412d6cdb3961d691744013c8362e826626a330cecf4a296a6f4d93a5c",
       "source": "common instruction compatibility alias",
       "classification": null,
       "destination": null
@@ -271,7 +271,7 @@
     {
       "schemaVersion": 1,
       "file": "common/instruction.md",
-      "sha256": "6b9aa8747d9ddc9bd9a78de88a0c3d65f5b100ea917c4dd69be4d889b8299438",
+      "sha256": "a72c51a412d6cdb3961d691744013c8362e826626a330cecf4a296a6f4d93a5c",
       "source": "scripts/fork-role-sources/AGENTS.product.md + AGENTS.md#canonical-decision-authority",
       "classification": null,
       "destination": null
@@ -359,7 +359,7 @@
     {
       "schemaVersion": 1,
       "file": "consumer/managed-files/46f10bc55cdfdf834d0749eebff42ea0bb8576f361b36d2b6ba1851354c50150.blob",
-      "sha256": "79b84cd0a7a8f262d1445503528e1251bb510517efb56550aad659c53c6b3cec",
+      "sha256": "8b37cf68731810ad665e02b7ac4a2a5a4ad55b01c6d9e0cbb37f33f3b00118f3",
       "source": "scripts/lib/governance-dependency-bootstrap.mjs",
       "classification": null,
       "destination": "scripts/lib/governance-dependency-bootstrap.mjs"
@@ -919,7 +919,7 @@
     {
       "schemaVersion": 1,
       "file": "manifest.json",
-      "sha256": "5befcb9f70e70b550e8eeb902f65177cc161db2824ebaf36e137579991cbf586",
+      "sha256": "8927ec4334bdd1cbc4c7bc7d41b1153b83db245070e328c2433867270aa7c5ec",
       "source": null,
       "classification": null,
       "destination": null

package/ds-canonical/fork/manifest.json

@@ -104,20 +104,20 @@
   },
   "providerLifecycle": {
     "schemaVersion": 4,
-    "releaseVersion": "0.1.0-beta.116",
+    "releaseVersion": "0.1.0-beta.117",
     "immutableHead": {
       "providerInventorySha256": "86e9d0668cb54ad1bf05c36e78b4aa80417d5f468c929dd3ddcf69c1afbf32e4",
-      "releaseVersion": "0.1.0-beta.115",
-      "snapshotSha256": "25bf1bb5c751623812af2c5b35b8c47bac9a93a718aa2b9222a6b3294296446d"
+      "releaseVersion": "0.1.0-beta.116",
+      "snapshotSha256": "f022897462d32b7e633c5f9d8e58ee9efe41e641ae42ab52668c4e3f360e2f9d"
     },
-    "ledgerSha256": "08466811258527c6bdbcd042a06dbdd3eca6715111711e3e6d46b5ffd86c81a4",
-    "previousSnapshotSha256": "25bf1bb5c751623812af2c5b35b8c47bac9a93a718aa2b9222a6b3294296446d",
-    "currentSnapshotSha256": "f022897462d32b7e633c5f9d8e58ee9efe41e641ae42ab52668c4e3f360e2f9d",
+    "ledgerSha256": "a3d9e38cc1ed799f058ae771d35d951004158ac2874eba0fddb52b509de33dda",
+    "previousSnapshotSha256": "f022897462d32b7e633c5f9d8e58ee9efe41e641ae42ab52668c4e3f360e2f9d",
+    "currentSnapshotSha256": "e03b95342944512f9c084c0ac5fe5fba4b688924758ce725f16504eaec8af5a4",
     "currentProviderInventorySha256": "86e9d0668cb54ad1bf05c36e78b4aa80417d5f468c929dd3ddcf69c1afbf32e4",
     "retiredProviders": [],
     "currentSnapshot": {
-      "releaseVersion": "0.1.0-beta.116",
-      "previousSnapshotSha256": "25bf1bb5c751623812af2c5b35b8c47bac9a93a718aa2b9222a6b3294296446d",
+      "releaseVersion": "0.1.0-beta.117",
+      "previousSnapshotSha256": "f022897462d32b7e633c5f9d8e58ee9efe41e641ae42ab52668c4e3f360e2f9d",
       "providers": [
         {
           "id": "claude",
@@ -193,8 +193,8 @@
       "retiredProviders": []
     },
     "immutableHeadSnapshot": {
-      "releaseVersion": "0.1.0-beta.115",
-      "previousSnapshotSha256": "31cffe8b7659879bf2e04c6a624d6720d12330e50ba5c351bca4ca82699c79c4",
+      "releaseVersion": "0.1.0-beta.116",
+      "previousSnapshotSha256": "25bf1bb5c751623812af2c5b35b8c47bac9a93a718aa2b9222a6b3294296446d",
       "providers": [
         {
           "id": "claude",

package/package.json

@@ -4,7 +4,7 @@
     "type": "git",
     "url": "git+https://github.com/ajenchen/design-system.git"
   },
-  "version": "0.1.0-beta.116",
+  "version": "0.1.0-beta.117",
   "private": false,
   "description": "World-class design system — components, patterns, tokens, hooks (single source of truth for team distribution).",
   "type": "module",

package/src/components/AppShell/app-shell.principles.stories.tsx

@@ -26,7 +26,7 @@ export const UsageGuidance: Story = {
           </li>
           <li>
             • 需要右側詳情面板(議題詳情 / inspector / 成員資料)跟 main 並存——如 Linear 點選議題後右側展開詳情。開合行為見{' '}
-            <LinkTo kind="Design System/Components/AppShell/設計規格" name="右側面板開合行為(兩種模式)"><span className="text-primary hover:text-primary-hover font-medium cursor-pointer">設計規格 → 右側面板開合行為</span></LinkTo>
+            <LinkTo kind="Design System/Components/AppShell/設計規格" name="狀態行為"><span className="text-primary hover:text-primary-hover font-medium cursor-pointer">設計規格 → 狀態行為(右側面板開合)</span></LinkTo>
           </li>
         </ul>
       </section>