docs: apply reviewed wiki editorial corrections
docs: document SetSystemwideThreatLevel privilege for system-wide activation
docs: apply validated SDK wiki corrections
docs: improve SDK documentation accuracy and clarity
docs: apply SDK audit corrections across Platform, Media, Plugin, and Workspace pages Address factual and API-accuracy issues identified by the SDK documentation audit: corrected obsolete and internal identifiers, removed an internal certificate error name from reader-facing text, fixed inverted and missing default-state notes, narrowed over-broad capability claims, and reworded to observable behavior. Also adds a strongly typed interface-builder example for access control units and clarifies AddMapping upsert semantics.
docs: replace em-dashes per style guide Style rule PUNCT-03 disallows em-dashes. Replace with a colon in platform-sdk-threat-levels.md (introduces an explanatory list) and a period in web-sdk-custom-fields.md (joins two independent clauses).
docs: normalize See also descriptions and remove cross-SDK leakage - Capitalize first letter of See also descriptions per wiki-style-reviewer LIST-01/LIST-06/LINK-09 across 29 pages - Apply canonical descriptions for shared cross-references (0 inconsistencies across 109 cross-references) - Remove Platform -> Web/Workspace/Plugin See also links (audience mismatch: Platform SDK reader does not reach for Web/Workspace/Plugin SDK from a C# integration context) - Remove 2 inline Platform -> Web body cross-references - Add IsNetworkSettingsCombinationValid result examples and PTZ zoom-factor explanation in web-sdk-video.md
docs(platform-sdk): re-alphabetize the threat-levels See also (only that file)
Revert "docs(platform-sdk): canonical alphabetical ordering for See also sections" This reverts commit 2229e4b6f10517da2090372404ab089c89586de8.
docs(platform-sdk): canonical alphabetical ordering for See also sections Reorders See also entries alphabetically by link text on the pages edited this session. Removes editorial bias in which subsystem appears first; the order is now produced by the link title rather than by an implicit framing choice. Also lowercases description text where the prior pattern accidentally had Title Case openings.
docs(platform-sdk): rebalance the threat-levels See also Removes the access-control framing from the See also list. The previous phrasing ("areas reference active threat levels, and threat-level actions are commonly wired against access-control entities") still treated access control as the primary consumer. It is not. Threat- level actions land in alarms, video, access control, and any other subsystem with equal frequency. Reorders the entries so no single subsystem leads, and rewrites the descriptions as neutral targets (alarm triggering, recording boost, door locking) rather than privileging access control.
docs(platform-sdk): split threat levels into a standalone page Threat levels are a cross-cutting system feature, not an access-control concept. ActivationActions can fire any system action: video record- boost, alarm masking, notifications, macros, in addition to door locking. The system/area scoping and the action symmetry make threat levels conceptually closer to alarms and custom fields than to access rules or doors. Moves the threat-level conceptual content out of the access-control hub into a new platform-sdk-threat-levels.md. Keeps the area-side references (Area.ActiveThreatLevel and Area.ThreatLevelMappings) on the doors-and-access-points page where the consumer side already lives, and points the cross-link there at the new standalone page. Drops the ThreatLevel reference from the access-control four-layer model (it was misframing threat levels as access-control policy). Adds the new page to the sidebar in the cross-cutting cluster (next to mobile credentials and alarms) and to the Subsystem guides table on platform-sdk-overview.