Cleanup of SaaS code (#6669)

# Description of Changes
De-AI comments and fix ridiculously indented code

frontend/editor/src/proprietary/components/policies/Policies.stories.tsx

@@ -158,6 +158,6 @@ export const ListSection: Story = {
   ),
 };
 
-// Note: the setup + edit wizard now embeds the Watch Folders automation builder
-// (its Workflow step), which needs the ToolWorkflow context — so the wizard is
+// The setup + edit wizard embeds the Watch Folders automation builder (its
+// Workflow step), which needs the ToolWorkflow context - so the wizard is
 // exercised in-app, not via an isolated story here.

frontend/editor/src/proprietary/components/policies/PolicyToolConfigStep.tsx

@@ -39,8 +39,8 @@ interface PolicyToolConfigStepProps {
   initialOperations: AutomationOperation[];
   /**
    * The preset's default operations. Their params seed any tool whose saved
-   * value is still at the tool's own default — so e.g. a policy saved before the
-   * PII patterns existed inherits them rather than running with an empty list.
+   * value is still at the tool's own default — so e.g. a policy saved with the
+   * PII list at its default inherits the preset patterns rather than running empty.
    */
   presetOperations: AutomationOperation[];
   /** Used to name the built pipeline definition. */

frontend/editor/src/proprietary/components/policies/policyRunStore.ts

@@ -1,5 +1,5 @@
 /**
- * External store for real backend policy runs (Phase B: auto-run on upload).
+ * External store for real backend policy runs (auto-run on upload).
  *
  * The auto-run controller fires a backend run for each enabled policy × each
  * newly-uploaded file and records it here; the detail view's activity feed reads

frontend/editor/src/proprietary/components/policies/policyToolChains.ts

@@ -3,8 +3,6 @@
  * config page shows (one section per tool). Tools can be configured + toggled
  * on/off, but not added or removed. Each id is a frontend tool-registry key (and
  * maps to that tool's backend endpoint via the registry's operationConfig).
- *
- * Only Security is wired today; other categories follow.
  */
 export const POLICY_TOOL_CHAINS: Record<string, string[]> = {
   // Security: redact PII + watermark + sanitize (strips JS). Which are enabled

frontend/editor/src/proprietary/components/policies/usePolicyAutoRun.ts

@@ -1,5 +1,5 @@
 /**
- * Auto-run controller (Phase B): every enabled policy enforces on every uploaded
+ * Auto-run controller: every enabled policy enforces on every uploaded
  * file. Watches the session's files and, for each (active policy × not-yet-run
  * file), fires a real backend run (`POST /api/v1/policies/{id}/run`) and polls it
  * to completion, recording progress in {@link policyRunStore} for the activity