stylegallery 0.1.3 → 0.1.6

package/game-ui/unity/org-wiki.md

@@ -0,0 +1,146 @@
+---
+type: Domain Guide
+title: Unity Organization Compressed Wiki
+description: Independent cluster index over a tracked snapshot of 804 public Unity-Technologies repositories for bounded Game UI source discovery.
+domain: game-ui
+lifecycle: experimental
+platform: Unity-Technologies public GitHub organization
+platform_version: public repository snapshot captured 2026-07-14T12:59:16Z
+reviewed_on: 2026-07-15
+---
+
+# Unity Organization Compressed Wiki
+
+Primary role: bounded organization-wide source discovery for Unity Game UI research.
+
+> **Independent research — not affiliated with or endorsed by Unity Technologies. Snapshot evidence, not a support-status catalog.**
+
+This locally authored index compresses **804** public repositories into one tracked data inventory and 20 exclusive primary clusters. It is not produced, sponsored, endorsed, or maintained by Unity Technologies. Organization placement does not establish authorship of forked, mirrored, vendored, or third-party content. Each repository retains its own license and terms.
+
+The machine-readable source is [`data/unity-technologies-public-repositories.json`](data/unity-technologies-public-repositories.json). It records one row per captured public repository, including stable identity, repository URL, raw fork/archive/template state, default branch and observed HEAD when resolved, snapshot time, license metadata, UI relevance, and one exclusive `primary_cluster`.
+
+The source snapshot was captured at `2026-07-14T12:59:16Z`. The pre-projection inventory SHA-256 was `8291b471251053a8921651eb7c791d13a4794984b73670a51cdb1116deb49657`; the tracked JSON SHA-256 is `b1438e6e8d438bab3eff2ff02f5a10e9374fdfb89b0581ffb936a42920fa2e05`. It records 59 archived repositories, 356 forks, and 4 templates.
+
+## Repository Boundary
+
+The inventory covers the public Unity-Technologies organization snapshot and no other owner. NGUI and other third-party sources remain outside its counts. Public organization metadata is discovery evidence; it is not an affiliation, authorship, quality, or support claim.
+
+## Reusable Method
+
+1. Start with [Unity UI Systems](ui-systems.md) for a current system-choice decision.
+2. Use the [Unity Repository Map](repository-map.md) to find UI authority, examples, adjacent evidence, and historical material.
+3. Use this page when a UI question depends on a broader engine subject such as rendering, input, ECS, networking, XR, platform integration, services, or tooling.
+4. Open the tracked inventory for individual repository URLs and captured metadata.
+5. Before turning a repository observation into guidance, resolve and pin the exact Unity/package version and source revision.
+
+The evidence order is: versioned Unity manuals and package changelogs; SHA-pinned implementation source; current version-bounded examples; dated announcements; historical demos; then community anecdotes. Stars, recent pushes, and organization placement are discovery signals, not authority or support status.
+
+## Exclusive Cluster Index
+
+First match wins. Fork and archive gates precede subjects; UI authority precedes adjacent technical subjects; technical subjects precede generic samples; the residual is an explicit covered value.
+
+| Primary cluster | Repositories | Game UI use boundary |
+| --- | ---: | --- |
+| `meta-forks-mirrors` | 356 | Discovery only. GitHub `fork: true` does not establish first-party authority. |
+| `meta-archived-historical` | 32 | Archaeology and migration context, not current guidance. |
+| `game-ui-primary` | 9 | Explicit UI sources/examples; refine lifecycle and version before use. |
+| `graphics-rendering` | 38 | Rendering constraints, shaders, pipelines, VFX, materials, and display behavior. |
+| `ecs-dots` | 22 | Data-oriented runtime architecture that can constrain UI state flow. |
+| `networking` | 21 | Multiplayer state, transport, lobby, relay, matchmaking, and server flows. |
+| `xr-ar` | 25 | Spatial interaction, device input, world-space presentation, and XR constraints. |
+| `ml-ai` | 23 | ML, inference, perception, and synthetic-data context; no UI defaults. |
+| `robotics` | 6 | Simulation and operator-interface observations only. |
+| `2d` | 7 | Sprite, tilemap, 2D package, and pixel-oriented implementation context. |
+| `animation` | 10 | Timeline, rigging, Cinemachine, and animation-system dependencies. |
+| `audio` | 3 | Audio/DSP and spatial-audio state dependencies. |
+| `physics` | 1 | Physics-system context only. |
+| `editor-tooling` | 29 | Authoring, profiling, build, package, recorder, and asset-tooling surfaces. |
+| `ci-infra` | 2 | Build and test infrastructure; not product UI evidence. |
+| `language-runtime` | 3 | Runtime, compilation, scripting, and serialization dependencies. |
+| `services-cloud` | 3 | Authentication, economy, analytics, leaderboard, and remote-service states. |
+| `platform-mobile` | 9 | Native integration, safe areas, packaging, device constraints, and platform input. |
+| `samples-templates` | 30 | Observation-only examples without a stronger subject assignment. |
+| `other-mixed-or-insufficient-metadata` | 175 | Covered residual; no speculative subject claim. |
+| **Total** | **804** | Exactly one primary cluster per tracked row. |
+
+`localization-text` remains a reserved search facet with zero primary rows in this snapshot. A zero primary count does not prove absence; use UI relevance and repository-specific inspection.
+
+## UI Authority Route
+
+The current source triangle is deliberately split:
+
+- [`uGUI`](https://github.com/Unity-Technologies/uGUI) owns the GameObject/Canvas UI package source and current TextMesh Pro source. Use the package version in the target project and a matching SHA.
+- [`UnityCsReference`](https://github.com/Unity-Technologies/UnityCsReference) contains the broad UI Toolkit reference implementation within engine C# reference source; it is not a package mirror.
+- [`InputSystem`](https://github.com/Unity-Technologies/InputSystem) owns UI-input integration such as action maps and `InputSystemUIInputModule`, not rendering or layout.
+
+Open UnityCsReference as a Unity-engine C# study and reference textbook surface when tracing module architecture, ownership boundaries, and version-pinned implementation paths. It is valuable for readers who already know C# and want to study how Unity's managed engine layer is organized; it is not a learn-C#-from-zero or general-purpose C# curriculum. Read a branch or SHA matched to the target Unity version line, and treat the repository as reference source rather than a package mirror or the complete engine: native/C++ implementation remains outside this corpus.
+
+Current scoped examples include [`BagelGame`](https://github.com/Unity-Technologies/BagelGame), [`ui-toolkit-manual-code-examples`](https://github.com/Unity-Technologies/ui-toolkit-manual-code-examples), and [`a11y-public-sample`](https://github.com/Unity-Technologies/a11y-public-sample). Preserve each example's recorded Unity/package baseline.
+
+Historical UIElements/UI Toolkit conference and runtime demos remain historical even if unarchived or recently pushed. [`com.unity.uiwidgets`](https://github.com/Unity-Technologies/com.unity.uiwidgets) is a separate archived framework, not UI Toolkit.
+
+NGUI is third-party [`tasharen/ngui`](https://github.com/tasharen/ngui). It is outside the Unity-Technologies 804-repository inventory and appears only as a separately pinned migration comparison in [Unity UI Systems](ui-systems.md).
+
+## Opinionated Guidance
+
+- Use `game-ui-primary` only as a candidate route; open the repository-map lifecycle disposition before citing it.
+- Prefer a matching release or Unity-version SHA over a mutable default-branch HEAD for implementation claims.
+- Keep engine-subject clusters as dependency context. They do not supply visual defaults or universal Game UI rules.
+- Treat stars, recent pushes, and repository names as discovery signals only.
+
+## Platform-Specific Guidance
+
+- Match uGUI and UnityCsReference source to the target Unity editor/package line.
+- Match Input System evidence to the project's installed package version and UI module configuration.
+- Revalidate XR, mobile, safe-area, HDR, and native-integration examples on the target device and render pipeline.
+- Preserve each sample's recorded Unity version even when its repository is unarchived or recently pushed.
+
+## Residual And Provenance Policy
+
+The 175-row residual means the bounded metadata classifier selected no earlier cluster. It does not mean irrelevant, empty, undocumented, or free of UI evidence. Curated overrides must be versioned and must recompute the full partition; do not edit cluster counts by hand.
+
+Raw `fork`, `archived`, and `is_template` values remain in the inventory. GitHub's fork flag is not a complete authorship model: non-fork repositories can still describe themselves as mirrors, forks, or vendored sources. Treat provenance as unresolved until repository evidence establishes it.
+
+## Completeness And Refresh Limits
+
+- The snapshot excludes private, deleted, transferred, and non-default-branch-only material.
+- Five stored tree scans were truncated and two zero-size repositories returned tree-fetch errors; absence claims do not rely on those trees.
+- Some repository HEADs, versions, licenses, lifecycle statements, and replacement paths remain unresolved.
+- X/Twitter evidence was unavailable during the research session. No post, handle, date, URL, or quotation is inferred from that absence.
+- The taxonomy is metadata-first. The residual protects against false precision; it is not editorial completion for 175 individual repositories.
+
+Refresh by rebuilding the complete public inventory, preserving stable identities and raw lifecycle fields, rerunning the exclusive classifier, validating all 804 assignments, reviewing changed authority records, and updating the snapshot identity. Never hand-edit one count without recomputing the whole partition.
+
+## Unsupported Absolutes
+
+- “In the Unity-Technologies organization” does not mean Unity authored every file.
+- “Unarchived” or “recently pushed” does not mean current or supported.
+- “No UI signal” does not prove a repository contains no interface code.
+- The 175-row residual does not mean the repositories are irrelevant or unclassifiable with deeper evidence.
+- This snapshot does not establish the contents of private, deleted, transferred, or non-default branches.
+
+## Verification Contract
+
+Run `node scripts/validate-unity-org-wiki.mjs --json` and `node scripts/test-validate-unity-org-wiki.mjs`. A refreshed publication must retain 804 unique identities for this snapshot, preserve the exclusive cluster sum, keep NGUI external, and update the page, data, snapshot identity, and tests together.
+
+## Source, License, And Attribution
+
+- Inventory basis: public GitHub repository metadata and captured default-branch inspection at `2026-07-14T12:59:16Z`.
+- Inventory identity before tracked projection: SHA-256 `8291b471251053a8921651eb7c791d13a4794984b73670a51cdb1116deb49657`; tracked JSON SHA-256 `b1438e6e8d438bab3eff2ff02f5a10e9374fdfb89b0581ffb936a42920fa2e05`; 59 archived repositories, 356 forks, and 4 templates.
+- Repository licenses and reuse terms differ. Follow each repository's recorded and current license before copying code or assets.
+- Reuse form: locally authored taxonomy, discovery index, and metadata projection; no Unity logos, trade dress, or first-person organizational voice.
+
+## Review Trigger
+
+Revisit this experimental page when the public snapshot is refreshed, a current UI authority source changes ownership or lifecycle, high-value unresolved HEAD/version fields are pinned, curated residual overrides are accepted, or verified social evidence materially changes the source-ranking discussion.
+
+Implementation handoff: Unity public-repository inventory and compressed discovery index.
+
+Consumer reference: `not_applicable`
+
+Consumer reference reason: This implementation adds repository provenance and discovery evidence, not consumer-specific visual or component guidance.
+
+## IA Navigation
+
+Parent: [Game UI](../index.md).
+Next: [Platform Guides](../../platform-guides/index.md).

package/game-ui/unity/repository-map.md

@@ -0,0 +1,102 @@
+---
+type: Domain Guide
+title: Unity Repository Map
+description: Public default-branch snapshot map for locating Unity UI system sources, examples, adjacent references, and historical material.
+domain: game-ui
+lifecycle: experimental
+platform: Unity-Technologies public GitHub organization
+platform_version: public and default-branch snapshot captured 2026-07-14T12:59:16Z
+reviewed_on: 2026-07-14
+---
+
+# Unity Repository Map
+
+Primary role: Unity public-source discovery and authority map.
+
+## Repository Boundary
+
+This locally authored map classifies the Unity-Technologies public organization snapshot captured at `2026-07-14T12:59:16Z`. GitHub organization metadata and fully paginated public-repository enumeration both returned 804 repositories. The pre-projection capture had SHA-256 `8291b471251053a8921651eb7c791d13a4794984b73670a51cdb1116deb49657`; the tracked classified [`data/unity-technologies-public-repositories.json`](data/unity-technologies-public-repositories.json) has SHA-256 `b1438e6e8d438bab3eff2ff02f5a10e9374fdfb89b0581ffb936a42920fa2e05` and records 59 archived repositories, 356 forks, and 4 templates.
+
+The map is a discovery index. A repository's presence, name, archive flag, or push date does not make it a current UI-system source.
+
+## Reusable Method
+
+1. Enumerate every public repository through REST pagination and retain stable repository identity and snapshot time.
+2. Record archive, fork, template, default branch, default-branch HEAD, README location, and tree-scan status.
+3. Scan default-branch paths for UXML, USS, UI Toolkit/UIElements, uGUI/Canvas/EventSystem, IMGUI, HUD/menu, accessibility, localization, text, and input signals.
+4. Counter-search descriptions and code paths so name-hidden candidates remain discoverable.
+5. Assign every repository one relevance class and a disposition reason.
+6. Deep-read only the authority subset, then pin each guidance claim to an exact revision and lifecycle context.
+
+## Snapshot Classification
+
+| UI relevance class | Repositories | Use |
+| --- | ---: | --- |
+| `primary-ui-source` | 8 | Unity UI system or explicit UI/example repository; refine lifecycle before use. |
+| `ui-adjacent-reference` | 5 | Input, reference source, safe-area, calibration, or vector-graphics evidence that constrains a UI review. |
+| `runtime-ui-observation` | 23 | Runtime UXML/USS or game/product UI implementation whose repository purpose is broader than UI. |
+| `legacy-ui-observation` | 72 | Multiple uGUI, HUD, menu, or Canvas observations in repositories owned for another purpose. |
+| `editor-or-incidental-uitoolkit` | 21 | UI Toolkit appears in editor tooling, inspectors, tests, or incidental help surfaces. |
+| `code-only-or-incidental-ui-signal` | 93 | Sparse or ambiguous UI-like paths do not justify reference status. |
+| `historical-ui-source` | 1 | Archived UIWidgets source retained as a separate historical framework. |
+| `excluded-misleading-name` | 1 | A UI-like repository name does not match a general UI source after inspection. |
+| `excluded-fork-or-vendor-ui` | 90 | Forked, mirrored, or vendored UI content is not automatically Unity-authored evidence. |
+| `no-ui-signal` | 490 | No UI signal was located in metadata, topics, default-branch path scan, or counter-search. |
+
+Total: 804 repositories.
+
+## Authority And Lifecycle Disposition
+
+| Disposition | Pinned examples | How to use them |
+| --- | --- | --- |
+| Current primary system/reference | uGUI's Unity 6000.3 [`Graphic.cs`](https://github.com/Unity-Technologies/uGUI/blob/9edb4420267b6652090ece4c28c38bd98746a68e/com.unity.ugui/Runtime/UGUI/UI/Core/Graphic.cs), UnityCsReference 6000.3.19f1 [`Panel.cs`](https://github.com/Unity-Technologies/UnityCsReference/blob/79f16640303119112ca5caed4d71c607d0dff6fb/Modules/UIElements/Core/Panel.cs), and InputSystem [`InputSystemUIInputModule.cs`](https://github.com/Unity-Technologies/InputSystem/blob/8a57d62081cf3546b46444e17223e0121a3568b2/Packages/com.unity.inputsystem/InputSystem/Runtime/Plugins/UI/InputSystemUIInputModule.cs) | Use version-pinned component and integration architecture. UnityCsReference remains reference source rather than a package mirror. |
+| Current explicit examples | [BagelGame README](https://github.com/Unity-Technologies/BagelGame/blob/5d0348bfa013f3c76299dd582c90a7549f66abce/README.md), [UI Toolkit manual code examples README](https://github.com/Unity-Technologies/ui-toolkit-manual-code-examples/blob/7ed6e7af9fc8a8f83facea818f47928d2e03a30f/README.md), and [accessibility sample README](https://github.com/Unity-Technologies/a11y-public-sample/blob/ec14cfcb8c10bafab83ea02cd17759d77b225fae/README.md) | BagelGame is a Unity 6.3 full-game UI Toolkit example; the manual repository contains documentation snippets; the accessibility sample is a Unity 2023.3 uGUI example. Keep each example's version and purpose attached. |
+| Adjacent and current observation examples | [EntityComponentSystemSamples README](https://github.com/Unity-Technologies/EntityComponentSystemSamples/blob/6786a741ee1f118ed14cecfa02beae8e926937b0/README.md), [XR Interaction Toolkit Examples README](https://github.com/Unity-Technologies/XR-Interaction-Toolkit-Examples/blob/881f7e197c7b0958621ebd1a05f249bbe254d36f/README.md), and [Unity Industry Viewer Template README](https://github.com/Unity-Technologies/unity-industry-viewer-template/blob/5d50da18f68b14c4dc15bcf3d535878cc2254497/README.md) | Use as implementation observations for their own product, ECS, XR, or industry-template context. They do not own the general UI-system contract. |
+| Historical UI examples | [UIElementsExamples README](https://github.com/Unity-Technologies/UIElementsExamples/blob/e940d1c9dddfe99fd500c9f34f4801856ad37f18/README.md), [Unite Copenhagen 2019 demo README](https://github.com/Unity-Technologies/UIElementsUniteCPH2019RuntimeDemo/blob/fa4f2c70cf2d6127ab624cc11a2742260ca6ff20/README.md), [Unite LA turret demo README](https://github.com/Unity-Technologies/UIElementsUniteLATurretDemo/blob/1fce133fe3a3473d418066d8005c64340e9985d5/README.md), and [Unity Royale runtime demo README](https://github.com/Unity-Technologies/UIToolkitUnityRoyaleRuntimeDemo/blob/9b5006d2580101b4d08d59d03d7dadc697d75311/README.md) | Retain for UIElements/UI Toolkit technique lineage and their recorded Unity-era context. Unarchived status or a recent push does not revise their baseline. |
+| Separate or excluded | Archived [UIWidgets README](https://github.com/Unity-Technologies/com.unity.uiwidgets/blob/0310984e947881eca6c2657f1a2fcaaa19329c22/README.md), [SimpleUIDemo README](https://github.com/Unity-Technologies/SimpleUIDemo/blob/c33907f1ffa0f8a30b46f958d3cf45e5da08b01c/README.md), and the 90 `excluded-fork-or-vendor-ui` rows | UIWidgets is a separate archived framework whose README points development elsewhere. SimpleUIDemo is a Project Tiny sample rather than a general UI reference. Fork and vendor content requires an independent provenance decision. |
+
+## Completeness Limits
+
+- The snapshot covers the public organization and each repository's observable default branch at capture time. It cannot observe private, deleted, transferred, or non-default-branch-only material.
+- `gen-playerid-stats` and `repotest123` returned tree-fetch errors; both reported repository size zero, leaving no default-branch content to inspect.
+- Recursive trees were truncated for Graphics, google-dawn, llvm-project, mono, and runtime. No absence claim relies on those truncated trees.
+- Broad GitHub Code Search has rate and result ceilings. It was used to counter-check candidates, not as the enumeration mechanism.
+- Path and metadata signals identify candidates; they do not prove compilation, rendered behavior, lifecycle correctness, or current support.
+
+## Opinionated Guidance
+
+- Start UI architecture research with the current primary sources, then use explicit examples for concrete version-scoped implementation evidence.
+- Keep product samples, historical demos, separate frameworks, forks, mirrors, and incidental UI in distinct evidence lanes.
+- Record repository owner, fork state, archive state, default-branch HEAD, README lifecycle statement, Unity/package version, authority class, and replacement path when one is named.
+- Rebuild the inventory instead of editing counts by hand when the organization snapshot changes.
+
+## Platform-Specific Guidance
+
+- Use the Unity 6000.3 branch and package context when applying the uGUI source linked here.
+- Use the UnityCsReference 6000.3.19f1 SHA for this page's UI Toolkit architecture boundary, not the newer default-branch head captured by the inventory.
+- Use InputSystem only for the input and UI integration behavior visible at its pinned SHA.
+- Preserve each sample's recorded Unity version and purpose in any downstream Game UI reference record.
+
+## Unsupported Absolutes
+
+- An unarchived repository is not proof of current guidance.
+- A recent `pushed_at` value is not proof that a sample's Unity baseline changed.
+- Repository ownership does not prove that every vendored or forked file is Unity-authored.
+- A matching path or term does not prove that the repository is a UI-system source.
+- This snapshot does not establish private or deleted repository history.
+
+## Verification Contract
+
+Before citing a repository, resolve the exact default-branch or release SHA, read its lifecycle statement and version files, inspect the relevant source path, and assign one of the dispositions above. For a refreshed map, repeat public pagination, verify unique ids and full names, recompute archive/fork/template totals and all ten class totals, record tree exceptions, and publish the new inventory hash and capture timestamp together.
+
+## Source, License, And Attribution
+
+- Inventory basis: public GitHub organization metadata, fully paginated public repository metadata, default-branch tree scans, and targeted counter-search captured on `2026-07-14T12:59:16Z`.
+- Inventory identity: 804 classified rows; pre-projection SHA-256 `8291b471251053a8921651eb7c791d13a4794984b73670a51cdb1116deb49657`; tracked JSON SHA-256 `b1438e6e8d438bab3eff2ff02f5a10e9374fdfb89b0581ffb936a42920fa2e05`; 59 archived repositories, 356 forks, and 4 templates.
+- Repository licenses and reuse terms differ. Follow the pinned repository's own license before copying code or assets.
+- Reuse form: locally authored discovery and authority map; repository metadata and links are evidence references, not imported implementation guidance.
+
+## IA Navigation
+
+Parent: [Game UI](../index.md).
+Next: [Unity Organization Compressed Wiki](org-wiki.md).

package/game-ui/unity/ui-systems.md

@@ -0,0 +1,85 @@
+---
+type: Domain Guide
+title: Unity UI Systems
+description: Source-pinned comparison of uGUI, UI Toolkit, and NGUI ownership and responsibilities for Game UI review.
+domain: game-ui
+lifecycle: experimental
+platform: Unity uGUI, UI Toolkit, and NGUI
+platform_version: Unity 6000.3 source boundary for uGUI and UI Toolkit; NGUI pinned repository snapshot
+reviewed_on: 2026-07-14
+---
+
+# Unity UI Systems
+
+Primary role: Unity UI stack comparison guide.
+
+## Repository Boundary
+
+This locally authored comparison helps a Game UI reviewer identify which hierarchy, input, layout, and lifecycle evidence belongs to uGUI, UI Toolkit, or NGUI. It compares ownership and responsibilities at pinned sources; it does not prescribe one stack, treat the APIs as interchangeable, or project historical examples onto current Unity releases.
+
+## Version Boundary
+
+- uGUI observations use the Unity 6000.3 branch at `9edb4420267b6652090ece4c28c38bd98746a68e`.
+- UI Toolkit observations use UnityCsReference `6000.3.19f1` at `79f16640303119112ca5caed4d71c607d0dff6fb`. UnityCsReference is reference source, not a package mirror.
+- NGUI observations use `tasharen/ngui@9bbc56f11e0e25b89fd55b9b9bc67ddf1f182fe2`. The repository describes a third-party system originating in 2011; treat this pinned snapshot separately from Unity-owned stacks and older NGUI distributions.
+
+## Reusable Method
+
+1. Record the Unity, package, and repository revisions used by the project.
+2. Identify the tree owner: Canvas and GameObjects, Panel and VisualElements, or UIRoot/UIPanel and GameObjects.
+3. Trace input and focus through the active stack-specific route.
+4. Inspect layout, styling, motion, binding, and scrolling as separate responsibilities.
+5. Record serialized assets, runtime-created state, and editor-only tooling.
+6. Label every example as current system source, current example, adjacent observation, or historical material.
+
+## System Comparison
+
+| Axis | uGUI at the pinned Unity 6000.3 source | UI Toolkit at the pinned Unity 6000.3 reference source | NGUI at the pinned repository snapshot |
+| --- | --- | --- | --- |
+| Rendering | A `Graphic` registers with a Canvas, rebuilds geometry or material state, and sends mesh data through the Canvas rendering path. See [`Graphic.cs`](https://github.com/Unity-Technologies/uGUI/blob/9edb4420267b6652090ece4c28c38bd98746a68e/com.unity.ugui/Runtime/UGUI/UI/Core/Graphic.cs#L547-L716). | A Panel owns a VisualElement tree, while repaint processing consumes visual changes and renders the root tree. See [`Panel.cs`](https://github.com/Unity-Technologies/UnityCsReference/blob/79f16640303119112ca5caed4d71c607d0dff6fb/Modules/UIElements/Core/Panel.cs#L1238-L1259) and [`UIRRepaintUpdater.cs`](https://github.com/Unity-Technologies/UnityCsReference/blob/79f16640303119112ca5caed4d71c607d0dff6fb/Modules/UIElements/Core/Renderer/UIRRepaintUpdater.cs#L25-L148). | `UIRoot`, `UIPanel`, `UIWidget`, and `UIDrawCall` divide scaling, clipping, geometry, and draw-call work. See [`UIRoot.cs`](https://github.com/tasharen/ngui/blob/9bbc56f11e0e25b89fd55b9b9bc67ddf1f182fe2/Assets/NGUI/Scripts/UI/UIRoot.cs), [`UIPanel.cs`](https://github.com/tasharen/ngui/blob/9bbc56f11e0e25b89fd55b9b9bc67ddf1f182fe2/Assets/NGUI/Scripts/UI/UIPanel.cs), and [`UIDrawCall.cs`](https://github.com/tasharen/ngui/blob/9bbc56f11e0e25b89fd55b9b9bc67ddf1f182fe2/Assets/NGUI/Scripts/Internal/UIDrawCall.cs). |
+| Hierarchy and ownership | GameObjects, `RectTransform`, Canvas, and component registration form the inspected hierarchy. Canvas membership is runtime state, not merely folder or prefab placement. | A `UIDocument` attaches a `VisualTreeAsset`-derived VisualElement tree to Panel Settings. VisualElement descendants are not Transform children. See [`UIDocument.cs`](https://github.com/Unity-Technologies/UnityCsReference/blob/79f16640303119112ca5caed4d71c607d0dff6fb/Modules/UIElements/Core/GameObjects/UIDocument.cs#L509-L539). | The Unity GameObject hierarchy carries `UIRoot`, `UIPanel`, `UIWidget`, control components, atlases, and fonts. Inspect component ownership as well as Transform nesting. See [`UIWidget.cs`](https://github.com/tasharen/ngui/blob/9bbc56f11e0e25b89fd55b9b9bc67ddf1f182fe2/Assets/NGUI/Scripts/Internal/UIWidget.cs). |
+| Input and focus | `EventSystem` selects and runs an active `BaseInputModule`; New Input System projects can use `InputSystemUIInputModule`. See [`EventSystem.cs`](https://github.com/Unity-Technologies/uGUI/blob/9edb4420267b6652090ece4c28c38bd98746a68e/com.unity.ugui/Runtime/UGUI/EventSystem/EventSystem.cs#L158-L177) and [`InputSystemUIInputModule.cs`](https://github.com/Unity-Technologies/InputSystem/blob/8a57d62081cf3546b46444e17223e0121a3568b2/Packages/com.unity.inputsystem/InputSystem/Runtime/Plugins/UI/InputSystemUIInputModule.cs). | Focus and event dispatch are Panel-owned. The pinned `DefaultEventSystem` chooses the InputForUI provider path or a legacy path according to its context. See [`DefaultEventSystem.cs`](https://github.com/Unity-Technologies/UnityCsReference/blob/79f16640303119112ca5caed4d71c607d0dff6fb/Modules/UIElements/Core/GameObjects/DefaultEventSystem.cs#L67-L82). | `UICamera` performs its own 3D/2D raycasts and message dispatch. Its default delegates read legacy `UnityEngine.Input`; do not document an EventSystem or New Input System route unless the project supplies one. See [`UICamera.cs`](https://github.com/tasharen/ngui/blob/9bbc56f11e0e25b89fd55b9b9bc67ddf1f182fe2/Assets/NGUI/Scripts/UI/UICamera.cs#L13-L43). |
+| Layout | `LayoutRebuilder`, layout groups, fitters, anchors, and RectTransform calculations operate across component passes. See [`LayoutRebuilder.cs`](https://github.com/Unity-Technologies/uGUI/blob/9edb4420267b6652090ece4c28c38bd98746a68e/com.unity.ugui/Runtime/UGUI/UI/Core/Layout/LayoutRebuilder.cs#L60-L89). | Flex-style layout nodes are calculated for the visual tree, with bounded validation passes. See [`VisualTreeLayoutUpdater.cs`](https://github.com/Unity-Technologies/UnityCsReference/blob/79f16640303119112ca5caed4d71c607d0dff6fb/Modules/UIElements/Core/VisualTreeLayoutUpdater.cs#L105-L201). | Anchoring, stretching, grid, table, and wrapping responsibilities are separate components. See [`UIAnchor.cs`](https://github.com/tasharen/ngui/blob/9bbc56f11e0e25b89fd55b9b9bc67ddf1f182fe2/Assets/NGUI/Scripts/UI/UIAnchor.cs), [`UIStretch.cs`](https://github.com/tasharen/ngui/blob/9bbc56f11e0e25b89fd55b9b9bc67ddf1f182fe2/Assets/NGUI/Scripts/UI/UIStretch.cs), [`UIGrid.cs`](https://github.com/tasharen/ngui/blob/9bbc56f11e0e25b89fd55b9b9bc67ddf1f182fe2/Assets/NGUI/Scripts/Interaction/UIGrid.cs), and [`UITable.cs`](https://github.com/tasharen/ngui/blob/9bbc56f11e0e25b89fd55b9b9bc67ddf1f182fe2/Assets/NGUI/Scripts/Interaction/UITable.cs). |
+| Styling and motion | `Selectable` supports color, sprite, and Animator transition modes; projects may add Animator, Timeline, tween, or script-owned motion. See [`Selectable.cs`](https://github.com/Unity-Technologies/uGUI/blob/9edb4420267b6652090ece4c28c38bd98746a68e/com.unity.ugui/Runtime/UGUI/UI/Core/Selectable.cs#L655-L708). | USS style resolution and typed transition-property changes are processed by the style updater. See [`VisualTreeStyleUpdater.cs`](https://github.com/Unity-Technologies/UnityCsReference/blob/79f16640303119112ca5caed4d71c607d0dff6fb/Modules/UIElements/Core/VisualTreeStyleUpdater.cs#L68-L170). | Widget colors, sprites, fonts, `UITweener` subclasses, springs, `UIPlayTween`, and `UIPlayAnimation` provide stack-local presentation and motion mechanisms. See [`UITweener.cs`](https://github.com/tasharen/ngui/blob/9bbc56f11e0e25b89fd55b9b9bc67ddf1f182fe2/Assets/NGUI/Scripts/Tweening/UITweener.cs#L10-L38). |
+| Binding | Serialized component references, scripts, `UnityEvent`, and project-owned presenters connect UI components to project code. The pinned runtime source exposes `Button.onClick`, but this review did not locate a general collection/data-binding family. See [`Button.cs`](https://github.com/Unity-Technologies/uGUI/blob/9edb4420267b6652090ece4c28c38bd98746a68e/com.unity.ugui/Runtime/UGUI/UI/Core/Button.cs#L15-L70). | `dataSource`, `dataSourcePath`, `SetBinding`, and Panel binding management form an explicit data-binding surface. See [`VisualElementDataBinding.cs`](https://github.com/Unity-Technologies/UnityCsReference/blob/79f16640303119112ca5caed4d71c607d0dff6fb/Modules/UIElements/Core/VisualElementDataBinding.cs#L185-L290). | `EventDelegate`, localization, `PropertyBinding`, and project scripts support callbacks, localization, and property synchronization. Record the concrete component and callback path. See [`EventDelegate.cs`](https://github.com/tasharen/ngui/blob/9bbc56f11e0e25b89fd55b9b9bc67ddf1f182fe2/Assets/NGUI/Scripts/Internal/EventDelegate.cs). |
+| Scrolling and virtualization | `ScrollRect` owns wheel, drag, bounds, velocity, and anchored-position behavior. The pinned runtime review did not locate a built-in collection-virtualization family. See [`ScrollRect.cs`](https://github.com/Unity-Technologies/uGUI/blob/9edb4420267b6652090ece4c28c38bd98746a68e/com.unity.ugui/Runtime/UGUI/UI/Core/ScrollRect.cs#L647-L680). | `ScrollView` provides scrolling, while collection controls own virtualization controllers. See [`BaseVerticalCollectionView.cs`](https://github.com/Unity-Technologies/UnityCsReference/blob/79f16640303119112ca5caed4d71c607d0dff6fb/Modules/UIElements/Core/Controls/BaseVerticalCollectionView.cs#L560-L574). | `UIScrollView`, scroll bars, `UIWrapContent`, and centering components divide scrolling and repeated-content behavior. See [`UIScrollView.cs`](https://github.com/tasharen/ngui/blob/9bbc56f11e0e25b89fd55b9b9bc67ddf1f182fe2/Assets/NGUI/Scripts/Interaction/UIScrollView.cs) and [`UIWrapContent.cs`](https://github.com/tasharen/ngui/blob/9bbc56f11e0e25b89fd55b9b9bc67ddf1f182fe2/Assets/NGUI/Scripts/Interaction/UIWrapContent.cs). |
+| Lifecycle and serialization | MonoBehaviour callbacks register and unregister Graphics and layout state; scenes and prefabs serialize component fields and events. Inspect runtime-created objects and domain reload behavior separately. | `UIDocument`, Panel Settings, UXML/`VisualTreeAsset`, USS, and runtime Panel attachment create a distinct serialized-asset and runtime-tree lifecycle. | MonoBehaviours, prefabs, atlases, fonts, and serialized delegates carry state. Inspect runtime-created widgets, atlas/font ownership, and callback teardown directly. |
+| Editor and runtime | Runtime and Editor assemblies are separate; editor menu code can create Canvas controls. See [`MenuOptions.cs`](https://github.com/Unity-Technologies/uGUI/blob/9edb4420267b6652090ece4c28c38bd98746a68e/com.unity.ugui/Editor/UGUI/UI/MenuOptions.cs#L205-L282). | Runtime Panels and editor-root contexts are separate. See [`RuntimePanel.cs`](https://github.com/Unity-Technologies/UnityCsReference/blob/79f16640303119112ca5caed4d71c607d0dff6fb/Modules/UIElements/Core/GameObjects/RuntimePanel.cs#L27-L48). | Runtime scripts, editor tools, and inspectors coexist. See [`UICreateNewUIWizard.cs`](https://github.com/tasharen/ngui/blob/9bbc56f11e0e25b89fd55b9b9bc67ddf1f182fe2/Assets/NGUI/Scripts/Editor/UICreateNewUIWizard.cs) and [`UIPanelInspector.cs`](https://github.com/tasharen/ngui/blob/9bbc56f11e0e25b89fd55b9b9bc67ddf1f182fe2/Assets/NGUI/Scripts/Editor/UIPanelInspector.cs). |
+| Current and historical boundary | The pinned 6000.3 branch is the evidence boundary for this page; record the project's exact package revision before applying it. | The pinned 6000.3 reference source is the evidence boundary. UIElements conference demos and 2019–2020 runtime samples are historical technique records, not current-version contracts. | NGUI is third-party. Record the exact repository or asset-distribution revision and license context instead of using the name alone as a version marker. |
+
+## Opinionated Guidance
+
+- Start a review by naming the tree owner and input owner; those two facts reduce cross-stack ambiguity.
+- Capture both serialized assets and the runtime tree because project folders or Scene hierarchy alone can omit runtime ownership.
+- Treat mixed-stack projects as explicit integrations. Record render order, camera or Panel ownership, input routing, focus transfer, and teardown at each bridge.
+- Prefer version-pinned system source for architecture claims and use samples only for the narrower behavior they actually demonstrate.
+
+## Platform-Specific Guidance
+
+- For uGUI, record Canvas mode, scaler, sorting, raycaster, EventSystem, input module, selected object, and ScrollRect structure.
+- For UI Toolkit, record Panel Settings, UIDocument, UXML and USS assets, runtime `rootVisualElement`, focus order, data source, and collection controller.
+- For NGUI, record UIRoot scaling, UIPanel clipping and depth, atlas/font assets, UICamera event type and delegates, tweener ownership, and scroll components.
+- For every stack, distinguish editor-only tooling from runtime code and current sources from historical examples.
+
+## Unsupported Absolutes
+
+- Do not infer input routing from visual similarity or a shared GameObject parent.
+- Do not infer a VisualElement tree from the Transform hierarchy.
+- Do not infer current behavior from an unarchived repository or a recent push date alone.
+- Do not infer rendered behavior, focus behavior, or lifecycle correctness from serialized files alone.
+
+## Verification Contract
+
+Record exact revisions, open the relevant Scene or document, and capture the serialized owner, runtime tree, active input path, initial and returned focus, layout changes, scrolling behavior, dynamic content reuse, and teardown. Exercise pointer, keyboard, gamepad, or touch modes actually declared by the project. Recheck historical examples against their own Unity version instead of using them as a current baseline.
+
+## Source, License, And Attribution
+
+- uGUI source: [Unity-Technologies/uGUI at `9edb4420267b6652090ece4c28c38bd98746a68e`](https://github.com/Unity-Technologies/uGUI/blob/9edb4420267b6652090ece4c28c38bd98746a68e/com.unity.ugui/LICENSE.md)
+- UI Toolkit reference source: [Unity-Technologies/UnityCsReference at `79f16640303119112ca5caed4d71c607d0dff6fb`](https://github.com/Unity-Technologies/UnityCsReference/blob/79f16640303119112ca5caed4d71c607d0dff6fb/LICENSE.md)
+- NGUI source: [tasharen/ngui at `9bbc56f11e0e25b89fd55b9b9bc67ddf1f182fe2`](https://github.com/tasharen/ngui/blob/9bbc56f11e0e25b89fd55b9b9bc67ddf1f182fe2/README.md) and its pinned [license](https://github.com/tasharen/ngui/blob/9bbc56f11e0e25b89fd55b9b9bc67ddf1f182fe2/License.txt)
+- Reuse form: locally authored comparison of source-observable ownership and responsibilities; no upstream prose or implementation sample is reproduced.
+
+## IA Navigation
+
+Parent: [Game UI](../index.md).
+Next: [Unity CLI Loop](cli-loop.md).

package/game-ui/verification-workflow.md

@@ -0,0 +1,100 @@
+---
+type: Domain Guide
+title: Game UI Verification Workflow
+description: Convert a screen recipe into repeatable input, state, hierarchy, and teardown evidence.
+domain: game-ui
+lifecycle: experimental
+provenance_kind: local
+---
+
+# Game UI Verification Workflow
+
+Primary role: game-interface acceptance and evidence procedure.
+
+## Repository Boundary
+
+This workflow verifies a declared game-interface contract on a named runtime. It does not authenticate third-party captures or convert a hypothetical recipe into a real gallery reference. Shared [Quality Gates](../quality/index.md) determine what a claim's evidence can support.
+
+## Reusable Method
+
+1. Select a [Screen Recipe](screen-recipes.md), build/version, scene, starting data, and supported inputs.
+2. Record the active hierarchy's lifetime, input, sorting, focus, and teardown owners.
+3. Reset to known state before each scenario. Name any non-resettable external dependency.
+4. Execute actions in order, including an exception or interruption.
+5. Compare expected and actual state, selection, input recipient, and surviving objects.
+6. Save artifacts with source/build identity; classify pass, fail, not-run, or not-applicable with a reason.
+
+## Minimum Scenario Matrix
+
+| Dimension | Scenario | Inspect |
+| --- | --- | --- |
+| Entry | Open by each supported input | Correct screen and initial focus/selection |
+| Navigation | Visit first, middle, last, and unavailable actions | Predictable order, visible target, no unreachable required action |
+| Modality | Open overlay above a screen, then another interruption | Exactly the intended input recipient; world input policy |
+| Cancellation | Back/Cancel during entry, request, and exit | One-layer dismissal; no click-through or stale blocker |
+| Content | Empty, long localized text, unbroken identifiers, many rows | Readable critical information and reachable actions |
+| Surface | Target aspect ratios, safe areas, scaled UI, constrained window | No obscured controls or accidental scroll ownership |
+| Data | Delay, fail, supersede, and complete requests out of order | Current identities and truthful operation status |
+| Device | Switch/disconnect a claimed input device | Updated prompts and a viable recovery action |
+| Lifetime | Reopen repeatedly and change scene/session | No duplicate handlers, surviving blockers, or stale view updates |
+
+This is a selection matrix. A title that supports no touch input records touch as not applicable; it does not claim a touch pass.
+
+## Worked Scenario: Inventory With Confirmation
+
+Precondition: local fictional test data has two items, A and B. The inventory is open with A selected; no real commerce operation is involved.
+
+| Step | Action | Expected observation |
+| --- | --- | --- |
+| 1 | Navigate to B and open its action dialog | B remains selected beneath the dialog; focus enters the dialog |
+| 2 | Press Cancel once | Only the dialog closes; focus/selection returns to B |
+| 3 | Reopen and trigger a delayed operation | Dialog exposes pending state and the declared duplicate-input behavior |
+| 4 | Close/change the screen, then resolve the operation | Data owner reconciles the result; destroyed views do not update |
+| 5 | Reopen inventory | Confirmed data appears; selection follows the documented restore policy |
+
+Actual result: `not_run`. This procedure is a test design, not engine execution evidence.
+
+A separate [web inventory adaptation](../examples/domain-interactions/README.md) exercises nested dismissal, delayed equipment responses after view closure, selection restoration, and reward reveal. Its [local browser results](../examples/domain-interactions/verification.md) are browser evidence only. The native-engine scenario above remains `not_run`.
+
+## Evidence Record Template
+
+```yaml
+scenario: inventory-dialog-return
+build_revision: # immutable source/build identity
+runtime: # engine, UI stack, packages, OS, device
+surface: # resolution, aspect ratio, safe area, UI scale, locale
+input: # exercised mode and device
+precondition: # scene, data, selection, connectivity
+actions: # ordered, reproducible steps
+expected: # visible state plus hierarchy/input assertions
+actual: not_run
+artifacts: # capture, recording, hierarchy trace, operation log
+limitations: # missing channels, device scope, mocked dependencies
+consumer_reference: not_applicable
+consumer_reference_reason: This blank procedure selects no consumer-owned reference record.
+```
+
+## Opinionated Guidance
+
+Capture hierarchy and input evidence together when a screenshot could hide the failure. A visually dismissed overlay with an active blocker is a failed dismissal, regardless of its appearance.
+
+## Platform-Specific Guidance
+
+For Unity use the source-pinned [CLI Loop](unity/cli-loop.md) and its UI-stack-specific capabilities. If a runner cannot inspect focus or controller routing, mark those checks not-run and collect them on the real engine surface.
+
+## Unsupported Absolutes
+
+A successful editor inspection does not prove player-build behavior. Mocked operation responses do not prove a live service works. Device and accessibility coverage must be named explicitly.
+
+## Verification Contract
+
+A completed record binds actions and actual outcomes to a build and runtime, includes exceptional-state evidence, and lists missing coverage. Failed required cases need remediation and rerun. A real gallery entry must also satisfy the [Reference Record](reference-record.md). Review when input routing, engine version, hierarchy ownership, or the recipe changes.
+
+## Source, License, And Attribution
+
+Locally authored test procedure and fictional inventory scenario. No real game reference, asset license, or runtime result is implied.
+
+## IA Navigation
+
+Parent: [Game UI](index.md).
+Next: [Game UI Reference Record](reference-record.md).

package/guides/vocabulary.md

@@ -15,7 +15,7 @@ Primary role: vocabulary and scannability contract.
 - Canonical: `domain`
   - Concept: top-level knowledge ownership
   - Definition: A governed StyleGallery decision surface with a named scope, exclusions, lifecycle, source-of-truth, validator, and review owner.
-  - Use for: Layout, Motion, Design Engineering, Game UI, Platform Guides, root routing, and `domain` frontmatter on governed leaves.
+  - Use for: Layout, Motion, Design Engineering, Game UI, Platform Guides, Design Terminology, root routing, and `domain` frontmatter on governed leaves.
 - Canonical: `category`
   - Concept: domain-local browse placement
   - Definition: A canonical grouping inside one domain; it cannot change the owning domain or its evidence boundary.

package/index.md

@@ -4,7 +4,7 @@ okf_version: "0.1"
 
 # StyleGallery
 
-StyleGallery is an OKF-style knowledge bundle organized into governed interface-knowledge domains. Existing Layout paths remain canonical while Motion, Design Engineering, Game UI, and Platform Guides own separate product and reference boundaries.
+StyleGallery is an OKF-style knowledge bundle organized into governed interface-knowledge domains. Existing Layout paths remain canonical while Motion, Design Engineering, Game UI, Platform Guides, and Design Terminology own separate product and reference boundaries.
 
 Primary role: OKF bundle map.
 
@@ -16,6 +16,7 @@ Primary role: OKF bundle map.
 - [Design Engineering](design-engineering/index.md) - Product-layer interface-craft decisions and verification questions.
 - [Game UI](game-ui/index.md) - Game-interface classification, hierarchy, reference records, and named engine implementation guides.
 - [Platform Guides](platform-guides/index.md) - Bounded comparative references for named platforms.
+- [Design Terminology](design-terminology/index.md) - Source-kind and concept-family classification, typed term relations, and cross-system conflict cases for named vocabulary sources.
 - [Consumer reference](consumer-reference/index.md) - Shared non-domain receiver contract for declared repository-local JSON records or reasoned non-applicability.
 - [Agent-Native StyleGallery](consumer-reference/agent-native/README.md) - Machine-facing identity, retrieval, operation, CLI, read-only MCP, task projection, and governed-learning contracts.
 - [Consumer migration readiness](design-engineering/consumer-migration-readiness.md) - Experimental Design Engineering method for consumer-owned conformance, runtime proof, and source-bound page evidence.
@@ -34,3 +35,11 @@ Primary role: OKF bundle map.
 - [Quality gates](quality/index.md) - Principle-backed gates for admissible layout and design evidence claims.
 - [Consumer migration evidence gate](quality/gates/consumer-migration-evidence.md) - Blocking contract for declared migration evidence.
 - [Update log](log.md) - Bundle update history.
+
+## Applied Workflows
+
+- [Motion Decision Tree](motion/decision-tree.md) - Choose a behavior from the user task.
+- [Design Engineering Decision Tree](design-engineering/decision-tree.md) - Route the uncertain product decision.
+- [Game UI Decision Tree](game-ui/decision-tree.md) - Choose by player task and ownership.
+- [Platform Adaptation Workflow](platform-guides/adaptation-workflow.md) - Record native facts, target decisions, and fallbacks.
+- [Design Term Comparison Workflow](design-terminology/comparison-workflow.md) - Resolve a source-specific question and produce a scoped handoff.

package/log.md

@@ -1,7 +1,50 @@
 # StyleGallery Log
 
+## 2026-09-09
+
+- Added a full-page fixed-viewport scene-navigation example with chapter hashes/history, wheel-burst gating, keyboard and art-surface swipe navigation, native copy overflow, immediate reduced-motion transitions, and a complete reading escape.
+- Extended Motion, Design Engineering, Platform Guides, and the Homepage composition route for this distinct navigation model. Kept visual values and controllers in the example layer.
+- Preserved one device shell across Flow's scroll-controlled scenes and linked the new page through the Scroll Story Lab. Historical verification remains bound to its original source; follow-up checks have separate records.
+- Prepared npm 0.1.6 with the cumulative governed-document updates. Runnable examples remain repository-only and are not added to the material admission or npm file inventory.
+
+- Added scroll-story contracts to Motion, a product media handoff to Design Engineering, and browser target cases to Platform Guides. Linked the existing Homepage recipe without adding a new Layout pattern or changing domain lifecycle.
+- Replaced the Flow transfer scene with three reversible scroll-controlled chapters and added a second product example, native CSS scrubbing, bounded image decoding, static reading, and deterministic/runtime checks in the Scroll Story Lab.
+
+- Added an independent Toss-inspired homepage study that composes the existing Homepage recipe and Layout patterns inside a standalone product layer.
+- Added original generated hero and travel imagery, responsive navigation, keyboard-operated asset tabs, section progress, reduced-motion behavior, and explicit horizontal service-rail ownership.
+- Recorded real Chrome verification at desktop, tablet, and mobile viewport sizes with retained desktop and mobile screenshots. No reusable Layout CSS or consumer-reference profile values were changed.
+
+Implementation handoff: `consumer_reference: not_applicable`.
+
+Consumer reference: not_applicable
+Consumer reference reason: This standalone visual study selects no consumer-reference profile or record.
+
+## 2026-09-08
+
+- Prepared npm release `stylegallery@0.1.5` with the complete six-domain, 147-document Material v2 corpus and the README compatibility repair.
+- Added fourteen local guides across the five non-Layout domains: task selection, motion briefs and recipes, component contracts and worked examples, game screen recipes and verification, Apple/Android/Windows adaptation, and terminology comparison.
+- Connected the guides through domain hubs and root routes, declared their membership/provenance, and included them in the closed 147-document material index and npm package. Layout retains its existing 46 patterns and spatial boundaries.
+- Replaced unsupported aggregate term records with directly sourced records; corrected representation direction and the confusion between composition and set containment. The Markdown validator now checks dates, source locators, labels, scoped direction, temporal relations, inverse consistency, and containment cycles with negative fixtures.
+- Examples remain expected behavior rather than claimed runtime evidence. Domain leaves remain `experimental`; no lifecycle promotion or consumer adoption is claimed.
+
+- Follow-up runtime work added the [Interaction Lab](examples/domain-interactions/README.md), a standalone web adaptation with explicit mock responses. Its [verification notes](examples/domain-interactions/verification.md) bind actual browser observations to local source hashes and separate desktop execution from simulated viewport sizes, untested mobile devices, and untested native engines. Fixed the lab's modal Tab boundary after observing focus escape in the real browser.
+- Fixed the v1 compatibility suite's stale README digest. Commit `d8bdf0bd5b5aec2fbc38e322a9ac7a1d31fd1332` had added material-v2 guidance and corrected the domain count without updating the test. The exact reviewed documentation digest is now checked separately; all 21 original core/source pins and six CLI output goldens remain unchanged. `npm run test:agent-native` passes.
+- Integrated the current domain lifecycle policy from `main`: reader tasks and adoption counts do not authorize or block domain promotion. Refreshed active workflow/document seals and source-generated protocol inventories for the added validation and documentation; preserved job bytes, lifecycle decisions, external caller status, deadlines, and immutable archive bindings.
+
+Implementation handoff: `consumer_reference: consumer-reference/agent-native/registry.json`.
+
+Consumer reference: declared
+Consumer reference record: consumer-reference/agent-native/registry.json
+
+Terminology reliance: `figma.variable`, `figma.mode`, `figma.collection`, `figma.component`, `dtcg.token`, `dtcg.group`, `dtcg.token.draft2`, `css.custom-property`, `carbon.component`, `carbon.pattern`, and `stylegallery.pattern`. Relation types used in the records: `partial_overlap`, `implementation_representation`, `not_comparable`, `same_label_different_meaning`, and `near_equivalent`. Their named Figma, DTCG, CSSWG, Carbon, and local Layout sources were rechecked on 2026-09-08; this is an author review, not independent semantic approval. Direct locators and comparison boundaries are in [Term Cases](design-terminology/conflict-cases.md).
+
 ## 2026-08-18
 
+- Added Design Terminology as the sixth governed domain: source-kind and concept-family classification separated as distinct axes, a typed term relation model, freshness-bounded source vocabularies, and cross-system conflict cases with three representative scenarios.
+- Added the Design Terminology domain scope decision record comparing four placement alternatives and defining the domain's independent decision surface.
+- Recorded six-domain scope in the domain manifest, root routes, quality scope, controlled vocabulary domain list, and governance rows; recorded sealed-cardinality duplication as accepted technical debt in the scope decision.
+- Admitted the new domain pages and scope decision into material v2 and regenerated the material registry without modifying the git index.
+
 - Added the StyleGallery homepage example planned from a clean npm installation and verified across desktop, tablet, and mobile Chrome CDP viewports.
 - Added pinned Pretext text-layout measurement as an npm-installed verification dependency while keeping browser Canvas execution outside the Node CLI and MCP surfaces.
 - Added deterministic hero-heading line-count, DOM overflow, accessibility, console, request, and screenshot checks.