Scope alarm tracking to selected templates and surface endpoint/security state on the dashboard so operators can deploy in large galaxies without drowning clients in irrelevant alarms or guessing what the server is advertising

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

docs/GalaxyRepository.md

@@ -21,7 +21,7 @@ All queries are embedded as `const string` fields in `GalaxyRepositoryService`.
 
 ### Hierarchy query
 
-Returns deployed Galaxy objects with their parent relationships and browse names:
+Returns deployed Galaxy objects with their parent relationships, browse names, and template derivation chains:
 
 - Joins `gobject` to `template_definition` to filter by relevant `category_id` values (1, 3, 4, 10, 11, 13, 17, 24, 26)
 - Uses `contained_name` as the browse name, falling back to `tag_name` when `contained_name` is null or empty
@@ -29,6 +29,7 @@ Returns deployed Galaxy objects with their parent relationships and browse names
 - Marks objects with `category_id = 13` as areas
 - Filters to `is_template = 0` (instances only, not templates)
 - Filters to `deployed_package_id <> 0` (deployed objects only)
+- Returns a `template_chain` column built by a recursive CTE that walks `gobject.derived_from_gobject_id` from each instance through its immediate template and ancestor templates (depth guard `< 10`). Template names are ordered by depth and joined with `|` via `STUFF(... FOR XML PATH(''))`. Example: `TestMachine_001` returns `$TestMachine|$gMachine|$gUserDefined|$UserDefined`. The C# repository reader splits the column on `|`, trims, and populates `GalaxyObjectInfo.TemplateChain`, which is consumed by `AlarmObjectFilter` for template-based alarm filtering. See [Alarm Tracking](AlarmTracking.md#template-based-alarm-object-filter).
 
 ### Attributes query (standard)