Document governed Unity UI systems and tooling

[islee23520]

Summary

• Establish the governed Game UI domain and add Unity-specific leaves for architecture, UI systems, editor/runtime operation, and repository research.
• Document uGUI, UI Toolkit, and NGUI by rendering model, hierarchy and ownership, input and focus, layout, styling and motion, data binding, scrolling and virtualization, lifecycle, and editor/runtime responsibilities.
• Keep the systems explicitly non-equivalent: this change does not claim automatic migration, interchangeable hierarchy semantics, or general performance superiority.
• Add a practical hatayama/unity-cli-loop workflow covering Play Mode, screenshots and element discovery, SimX/SimY coordinate use, uGUI/EventSystem targeting, direct-callback limits, and Restricted versus FullAccess dynamic-code security boundaries.
• Add a timestamped inventory and UI disposition for all 804 public repositories visible in the Unity-Technologies organization snapshot, with repository identifiers, snapshot limitations, and pinned source references.

Why

StyleGallery needed a source-backed Unity Game UI knowledge surface that separates engine-neutral UI analysis from Unity implementation details and makes current, legacy, and tooling boundaries explicit.

Validation

• 22/22 repository validation commands passed at 003ea1200d3031631700082d4685d391ff07c87e.
• 102/102 external source URLs returned HTTP 200.
• The Unity-Technologies snapshot contains exactly 804 repositories; all inventory and ten-class disposition invariants reconcile.
• Generated artifacts remained unchanged and the tracked worktree is clean.
• Independent goal, code-quality, security, evidence, visual, context, and runtime-debug audits all passed at the frozen HEAD.

Scope and limitations

• No live Unity project or player runtime was executed for this documentation change.
• Repository completeness is limited to the timestamped public/default-branch GitHub snapshot; private, deleted, visibility-restricted, or later-created repositories are outside the claim.
• UI Toolkit VisualElement nodes are not described as Transform children, NGUI retains its own UICamera/legacy-input route, and unity-cli-loop semantic UI operation is primarily documented for uGUI/EventSystem surfaces.
• Direct callbacks do not prove raycast, hover, focus, drag, or real player-input behavior.

[changeroa]

ULW triage — changes requested

Reviewed exact external-fork head 003ea1200d3031631700082d4685d391ff07c87e against main base 24ae581e92666a8864d42ffa64f7c34caf3a2156 in isolated worktrees.

What passed: the complete 22-command workflow; generated drift; five-domain/twelve-leaf validation; official domain adversarial harness 50/50; governance/IA/OKF/link/consumer tests; all six central pinned source commits; current GitHub organization totals (804 public, 59 archived, 356 forks, 4 templates); sampled uGUI/UI Toolkit/NGUI/CLI claims and licenses; clean Layout/consumer-reference boundary. The new documents are well-scoped and useful in shape.

Merge blockers:

1. The core 804-repository evidence is missing. game-ui/unity/repository-map.md:18,31-46,90,94-95 claims a stored 804-row classified JSON inventory, ten per-repository dispositions, exceptions, and SHA-256 8291…, but the PR tracks only aggregate prose—no inventory, immutable snapshot, generator/classifier, or durable artifact link. Organization totals can be corroborated; the row identities, class decisions, reasons, exceptions, and hash cannot. Commit the canonical inventory plus deterministic refresh/verification tool, or narrow/remove the exhaustive/hash claims.
2. Restricted dynamic C# is not a safe trust boundary as documented. At the pinned upstream SHA, Restricted allows arbitrary file reads, File.Create + stream writes, and calls into project assemblies. AI-submitted code can therefore expose host credentials through tool output or modify accessible files. Describe it as defense-in-depth, explicitly disclose these capabilities, require trusted/reviewed code for both modes, and require disposable least-privilege VM/container isolation with no host credentials for AI/untrusted code.
3. The new domain validator has structural false-successes. A README Game UI route hidden in an HTML comment, a required section heading hidden in a comment, and blank forbidden source_* keys all return ok:true. Strip comments for structural checks, use key-presence semantics, and add negative fixtures. Also normalize nested Markdown paths to POSIX for Windows.
4. Source-pinned prose can silently drift. Removing CLI attribution/license, changing a pinned body link to mutable main, replacing every uGUI body SHA with zeroes, or setting reviewed_on: never all pass domain and link validation. Likewise, changing inventory totals/hash passes. Model and validate the source/attribution/date/inventory contract instead of only selected frontmatter strings.

Secondary completeness gap: quality/index.md adds no Game UI scenario/PASS condition to its findability QA table despite the new first-class root task route.

Outcome: triage: changes-requested and formal REQUEST_CHANGES; not safe to merge yet.

[changeroa]

Requesting changes after exact-head ULW review. The complete workflow and source pins pass, but merge is blocked by: (1) the claimed 804-row classified inventory/hash not being committed or reproducible; (2) Restricted dynamic C# guidance omitting permitted file reads/stream writes and required OS-level isolation; (3) HTML-comment and blank-forbidden-key false-successes in the domain validator; and (4) unvalidated drift of source-pinned body citations, attribution, dates, and inventory counts/hash. Full evidence is in the accompanying triage comment.