feat: add exact credential help contexts

docs/CONTEXTUAL_HELP_CONTRACT.md

@@ -52,6 +52,8 @@ than adding custom `F1` listeners:
 - translated label keys provide deterministic field identities for ordinary
   `FormField`, `ToggleSwitch`, search, date/time, email, button, dialog, and card
   controls.
+- `TableActionGroup` action definitions carry the same identities so focused
+  row actions can resolve consequence-specific help.
 
 Module routes, public routes, settings sections, and administration sections
 may also declare `helpContextId` and `helpTopicId`. Each module must keep a

docs/LOCALIZATION_AND_HELP_QUALITY.md

@@ -42,6 +42,12 @@ Shared controls may set `helpModuleId` when their documentation owner differs
 from the containing page; the retention editor uses this to resolve Policy help
 from both administration and Campaign surfaces.
 
+The shared reusable-credential manager keeps Access as its documentation owner
+and publishes exact contexts for credential kind, secret replacement/removal,
+module and server restrictions, lower-scope visibility, activation, save, and
+irreversible deletion. This ensures F1 explains secret custody and the effect on
+dependent connections from system, tenant, group, user, and personal surfaces.
+
 The generated `help_review_candidates` list is therefore a content-depth queue,
 not a list of controls on which F1 cannot work. It should prioritize: