docs(skills): tighten validated guidance

docs/architecture/iptvnator-ui-guidelines.md

@@ -116,6 +116,14 @@ Do not copy the full detail-view stylesheet into feature libraries. Add shared
 layout changes to the mixin, and keep provider-specific differences explicit in
 the wrapper file that includes it.
 
+## Electron Drag Regions
+
+Every interactive descendant of a drag region—including buttons, links,
+inputs, overlays, and resize handles—requires `app-region: no-drag`. The shared
+directive-generated `.resize-handle` does not set this centrally yet. Until
+that debt is fixed, consumers in drag regions must cover the handle themselves
+and must not assume it already opts out.
+
 ## Channel List Item
 
 The shared row should be reused instead of rebuilding channel markup per view.

docs/architecture/stalker-portal.md

@@ -268,11 +268,12 @@ list:
 Stalker has multiple real-world data shapes. The current implementation supports all three:
 
 Within Stalker portal data access and feature code,
-`isStalkerSeriesFlag()` is the sole interpretation of `is_series`. The
-dependency-neutral activity normalizer in `libs/shared/interfaces` preserves
-the same closed set for dashboard records: boolean `true`, numeric `1`, or
-string `'1'`. Unsupported values do not by themselves classify a VOD item as a
-series.
+`isStalkerSeriesFlag()` is the canonical predicate for `is_series`.
+`normalizeStalkerSeriesFlag()` delegates to it and produces the normalized
+positive marker `true` or `undefined`. The activity normalizer in
+`libs/shared/interfaces` keeps its dependency-neutral equivalent for dashboard
+records. Both accept the same closed set: boolean `true`, numeric `1`, or string
+`'1'`. Unsupported values do not by themselves classify a VOD item as a series.
 
 1. Regular Series (`/series`):