#736 Remove automatic tag creation for UUID/localname tags Issue created by zhuoyuan-liu The admin UI performance was significantly degraded when loading large environments (10k+ nodes). Recent profiling showed that the main bottleneck was initializing Select2 with a very large tag list. We partially addressed the issue by deferring Select2 initialization in the nodes table. However, a deeper root cause remains: the system eagerly auto-creates tags for every node's UUID and localname (and other attributes). These tags provide little organizational value because: • UUID is already a unique identifier and linkable elsewhere. • Localname/hostname is already displayed in the table and searchable. • The explosion in automatically generated tags drastically increases the volume of tag records and payload size sent to the browser. • Operators typically expect tags to represent meaningful cohorts (environment, platform, region, team, function), not raw unique identifiers. Proposed Change: Modify auto-tagging so that only meaningful cohort-level tags are auto-created (e.g. environment name, platform) and stop creating per-node UUID and localname tags. Acceptance Criteria: • New nodes no longer generate UUID or localname tags. • Existing UUID/localname tags can be removed via documented cleanup process. • UI tag selector shows a significantly reduced tag list after cleanup (manual verification). • No regression in environment/platform tagging (if retained). jmpsec/osctrl