dev to main

.github/workflows/vale-autofix.yml

@@ -10,12 +10,43 @@ on:
       - '!docs/**/CLAUDE.md'
       - '!docs/**/SKILL.md'
       - '!docs/kb/**'
+      - 'scripts/**'
+      - 'package.json'
 
 concurrency:
   group: vale-autofix-${{ github.event.pull_request.number }}
 
 jobs:
+  test-scripts:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+    steps:
+      - name: Checkout
+        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        with:
+          ref: ${{ github.event.pull_request.head.sha }}
+          fetch-depth: 0
+
+      - name: Check if scripts changed
+        id: scripts-changed
+        run: |
+          CHANGED=$(git diff --name-only origin/dev...HEAD -- scripts/ package.json)
+          if [ -z "$CHANGED" ]; then
+            echo "changed=false" >> "$GITHUB_OUTPUT"
+          else
+            echo "changed=true" >> "$GITHUB_OUTPUT"
+          fi
+
+      - name: Test anchor/slugify scripts
+        if: steps.scripts-changed.outputs.changed == 'true'
+        run: npm run test:scripts
+
   vale-autofix:
+    needs: test-scripts
+    if: >-
+      github.event.pull_request.head.repo.fork == false &&
+      github.actor != 'dependabot[bot]'
     runs-on: ubuntu-latest
     permissions:
       contents: write
@@ -60,11 +91,9 @@ jobs:
       - name: Get changed markdown files
         id: changed-files
         if: steps.bot-check.outputs.skip != 'true'
-        env:
-          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
         run: |
-          PR_NUMBER=${{ github.event.pull_request.number }}
-          CHANGED_MD_FILES=$(gh pr diff "$PR_NUMBER" --name-only | grep -E '^docs/.*\.md$' | grep -v '/CLAUDE\.md$' | grep -v '/SKILL\.md$' | grep -v '^docs/kb/' || true)
+          DIFF_OUTPUT=$(git diff --name-only origin/dev...HEAD -- docs/)
+          CHANGED_MD_FILES=$(printf '%s\n' "$DIFF_OUTPUT" | grep -E '^docs/.*\.md$' | grep -v '/CLAUDE\.md$' | grep -v '/SKILL\.md$' | grep -v '^docs/kb/' || true)
           if [ -z "$CHANGED_MD_FILES" ]; then
             echo "No docs markdown files changed"
             echo "count=0" >> "$GITHUB_OUTPUT"
@@ -167,9 +196,9 @@ jobs:
             2. Apply a fix that resolves the Vale rule while preserving the author's meaning
             3. If you are NOT confident in a fix (ambiguous context, multiple valid interpretations, fix would change meaning) SKIP it
 
-            Note: if your fixes change any heading text, do not update anchor links — the workflow repairs all anchor links automatically after all fixes are complete.
+            Never edit heading text (a line starting with `#` through `######`, outside any fenced code block). Other files link to headings by anchor, and a heading rename breaks those links. If a violation is on a heading line, SKIP it with reason "heading text — not modified to avoid breaking anchor links".
 
-            If a fix adds or changes a link with a `#anchor`, the anchor must match a real Markdown heading (a line starting with `#` through `######`) OUTSIDE any fenced code block. Text that merely looks like a heading inside a ``` code block (for example, sample CLI/installer output) is never a valid anchor target, even if it matches the wording you're looking for. Before finishing, run exactly `bash scripts/check-anchors.sh <file>` (that literal invocation, one file per call, no chaining with other commands) on every file where you added or changed a link anchor. The script also reports broken link targets, not just anchors — only act on a finding for an anchor your own edit introduced: find the correct heading and fix it, or SKIP the violation if no correct target exists. Anchors broken because you renamed a heading are repaired automatically by a later step — leave those alone.
+            If a fix adds or changes a link with a `#anchor`, the anchor must match a real Markdown heading OUTSIDE any fenced code block. Text that merely looks like a heading inside a ``` code block (for example, sample CLI/installer output) is never a valid anchor target, even if it matches the wording you're looking for. Before finishing, run exactly `bash scripts/check-anchors.sh <file>` (that literal invocation, one file per call, no chaining with other commands) on every file where you added or changed a link anchor. The script also reports broken link targets, not just anchors — only act on a finding for an anchor your own edit introduced: find the correct heading and fix it, or SKIP the violation if no correct target exists.
 
             After fixing, write a JSON summary to /tmp/phase2-summary.json with this structure:
             ```json
@@ -212,9 +241,9 @@ jobs:
 
             Step 4: Fix each violation in-place, preserving the author's meaning. If you are NOT confident in a fix (ambiguous context, multiple valid interpretations, fix would change meaning), SKIP it.
 
-            Note: if your fixes change any heading text, do not update anchor links — the workflow repairs all anchor links automatically after all fixes are complete.
+            Never edit heading text (a line starting with `#` through `######`, outside any fenced code block). Other files link to headings by anchor, and a heading rename breaks those links. If a violation is on a heading line, SKIP it with reason "heading text — not modified to avoid breaking anchor links".
 
-            If a fix adds or changes a link with a `#anchor` (for example, resolving a "positional-references" violation into an explicit link), the anchor must match a real Markdown heading (a line starting with `#` through `######`) OUTSIDE any fenced code block. Text that merely looks like a heading inside a ``` code block (for example, sample CLI/installer output) is never a valid anchor target. Before finishing, run exactly `bash scripts/check-anchors.sh <file>` (that literal invocation, one file per call, no chaining with other commands) on every file where you added or changed a link anchor. The script also reports broken link targets, not just anchors — only act on a finding for an anchor your own edit introduced: find the correct heading and fix it, or SKIP the violation if no correct target exists. Anchors broken because you renamed a heading are repaired automatically by a later step — leave those alone.
+            If a fix adds or changes a link with a `#anchor` (for example, resolving a "positional-references" violation into an explicit link), the anchor must match a real Markdown heading OUTSIDE any fenced code block. Text that merely looks like a heading inside a ``` code block (for example, sample CLI/installer output) is never a valid anchor target. Before finishing, run exactly `bash scripts/check-anchors.sh <file>` (that literal invocation, one file per call, no chaining with other commands) on every file where you added or changed a link anchor. The script also reports broken link targets, not just anchors — only act on a finding for an anchor your own edit introduced: find the correct heading and fix it, or SKIP the violation if no correct target exists.
 
             Step 5: Write a JSON summary to /tmp/dale-summary.json with this structure:
             ```json
@@ -234,11 +263,6 @@ jobs:
             IMPORTANT: Do NOT run any git commands — the workflow handles staging, committing, and pushing. Do not post any PR comments.
           claude_args: '--allowedTools "Bash(git:*),Bash(bash scripts/check-anchors.sh:*),Bash(./scripts/check-anchors.sh:*),Bash(scripts/check-anchors.sh:*),Read,Write,Edit,Glob,Grep"'
 
-      - name: Fix heading anchors
-        if: steps.bot-check.outputs.skip != 'true' && steps.changed-files.outputs.count > 0
-        run: |
-          bash scripts/vale-autofix.sh --anchors-only origin/dev /tmp/changed-files.txt
-
       - name: Check anchor links
         id: anchor-check
         if: steps.bot-check.outputs.skip != 'true' && steps.changed-files.outputs.count > 0
@@ -260,7 +284,9 @@ jobs:
       - name: Commit all fixes
         if: steps.bot-check.outputs.skip != 'true' && steps.changed-files.outputs.count > 0
         run: |
-          git add -A docs/
+          while IFS= read -r file; do
+            [ -f "$file" ] && git add -- "$file"
+          done < /tmp/changed-files.txt
           if git diff --cached --quiet; then
             echo "No changes to commit"
           else

docs/accessanalyzer/11.6/admin/action/activedirectory/operations/computerdetails.md

@@ -12,14 +12,14 @@ Use the Computers Details page to select computer attributes to change.
 
 Highlight the attribute to edit:
 
-- Insert field – Use the drop-down list to select a field (column) from the source table. Then click
+- Insert field – Use the dropdown list to select a field (column) from the source table. Then click
   the blue arrow to insert the item into the Value box. The executed action replaces the AD Object
   property with the specified value from the source table.
 - Add Attribute – Adds a custom attribute to the Computer Details attribute list
 - Remove Attribute – Removes a selected attribute Computer Details attribute list
 - Edit Attribute – Click this icon to change the name of the selected custom attribute
-- Import Attribute – Opens the Import Custom Attributes Import Wizard where one or more custom
-  attributes can be imported. See the
+- Import Attribute – Opens the Import Custom Attributes Import Wizard, where you can import one or
+  more custom attributes. See the
   [Custom Attribute Import Wizard](#custom-attribute-import-wizard) topic for additional
   information.
 - Value – This field contains selections from the Insert field. If the Manager attribute is
@@ -30,16 +30,15 @@ Highlight the attribute to edit:
 
 ## Custom Attribute Import Wizard
 
-The Custom Attributes Import Wizard is used to import a list of custom attributes. Follow the steps
-to use the Custom Attributes Import Wizard.
+Use the Custom Attributes Import Wizard to import a list of custom attributes.
 
 **Step 1 –** On the Computer Details page of the Active Directory Action Module Wizard, click
 **Import**. The Custom Attribute Import Wizard opens.
 
 ![Custom Attributes Import Wizard Credentials page](/images/accessanalyzer/11.6/admin/action/activedirectory/operations/credentials.webp)
 
 **Step 2 –** On the Credentials page, identify a domain either by entering one manually or selecting
-one from the **Domain Name** drop-down menu which displays a list of domains trusted by the one in
+one from the **Domain Name** dropdown menu which displays a list of domains trusted by the one in
 which the Enterprise Auditor Console server resides. Then set the credentials for reading the
 attributes list from the domain:
 
@@ -52,11 +51,11 @@ attributes list from the domain:
 ![Custom Attributes Import Wizard Attributes page](/images/accessanalyzer/11.6/admin/action/activedirectory/operations/attributescomputer.webp)
 
 **Step 4 –** The wizard populates available attributes from the domain specified on the Attributes
-page. Expand the desired object class and select the checkboxes for the custom attributes to be
+page. Expand the object class you want and select the checkboxes for the custom attributes to be
 imported. Then click **Next**.
 
 ![Custom Attributes Import Wizard Completion page](/images/accessanalyzer/11.6/admin/action/activedirectory/operations/completionpage.webp)
 
 **Step 5 –** On the Completion page, click **Finish**.
 
-The selected attributes have been added to the attribute list on the Computer Details page.
+The wizard adds the selected attributes to the attribute list on the Computer Details page.

docs/accessanalyzer/11.6/admin/action/activedirectory/operations/creategroups.md

@@ -12,12 +12,12 @@ Use the Create Groups page to configure the action to create groups on the selec
 
 Use the following options to configure the action:
 
-- Insert field – Use the drop-down list to select a field (column) from the source table. Then,
+- Insert field – Use the dropdown list to select a field (column) from the source table. Then,
   click the blue arrow to insert the item into the OU, Group name, or Group name (pre Windows 2000)
   boxes.
 - OU – The organizational unit that contains the group
 
-    - Create target OU location if it does not already exist – Select this checkbox to create the
+    - Create target OU location if it doesn't already exist – Select this checkbox to create the
       target OU
 
 - Group Name – The name of the group that being created. This field is required.
@@ -27,10 +27,10 @@ Use the following options to configure the action:
     - Universal
     - Global
     - DomainLocal
-    - SqlField – Enter a value from the drop-down list
+    - SqlField – Enter a value from the dropdown list
 
 - Group type – The type of group being created. Select from the following:
 
     - Security
     - Distribution
-    - SqlField – Enter a value from the drop-down list
+    - SqlField – Enter a value from the dropdown list

docs/accessanalyzer/11.6/admin/action/activedirectory/operations/createusers.md

@@ -12,11 +12,11 @@ Use the Create Users page to create users on the selected target.
 
 Use the following options to configure the action:
 
-- Insert field – Use the drop-down list to select a field (column) from the source table. Then,
+- Insert field – Use the dropdown list to select a field (column) from the source table. Then,
   click the blue arrow to insert the item into the selected box.
 - OU – The organizational unit in which to create the user
 
-    - Create target OU location if it does not already exist - Select this checkbox to create the
+    - Create target OU location if it doesn't already exist - Select this checkbox to create the
       target OU.
 
 - First Name – The first name of the user being created
@@ -31,6 +31,6 @@ Optionally, select from the following checkboxes:
 
 - User must change password at next logon – Require the user to change the password at the next
   logon
-- User cannot change password
+- User can't change password
 - Password never expires
 - Account is disabled

docs/accessanalyzer/11.6/admin/action/activedirectory/operations/disableenablecomputers.md

@@ -11,7 +11,7 @@ options on target computers.
 
 ![Active Directory Action Module Wizard Disable/Enable Computers page](/images/accessanalyzer/11.6/admin/action/activedirectory/operations/disableenablecomputers.webp)
 
-Select the radio button for the desired option:
+Select the radio button for the option you want:
 
 - Enable – Enables users' operation options
 - Disable – Disables users' operation options

docs/accessanalyzer/11.6/admin/action/activedirectory/operations/disableenableusers.md

@@ -10,7 +10,7 @@ Use the Disable/Enable Users page to enable or disable target users.
 
 ![Active Directory Action Module Wizard Disable/Enable Users page](/images/accessanalyzer/11.6/admin/action/activedirectory/operations/disableenableusers.webp)
 
-Select the radio button for the desired option:
+Select the radio button for the option you want:
 
 - Disable – Select this radio button to disable users' operation options
 - Enable – Select this radio button to enable users' operation options

docs/accessanalyzer/11.6/admin/action/activedirectory/operations/groupdetails.md

@@ -18,13 +18,13 @@ The options at the bottom of the page vary based on the highlighted attribute.
 :::
 
 
-- Insert field – Use the drop-down list to select a field (column) from the source table. Then,
+- Insert field – Use the dropdown list to select a field (column) from the source table. Then,
   click the blue arrow to insert the item into the Value box.
 - Add Attribute – Adds a custom attribute to the Computer Details attribute list
 - Remove Attribute – Removes a selected attribute from the action
 - Edit Attribute – Click this icon to change the name of the selected custom attribute
-- Import Attribute – Opens the Import Custom Attributes Import Wizard where current attributes for
-  an object is viewed and can be imported for editing. See the
+- Import Attribute – Opens the Import Custom Attributes Import Wizard, where you can view an
+  object's current attributes and import them for editing. See the
   [Custom Attribute Import Wizard](#custom-attribute-import-wizard) topic for additional
   information.
 - Value/Name – This field derives its name from selections made on the page. It can contain
@@ -36,16 +36,15 @@ the action.
 
 ## Custom Attribute Import Wizard
 
-The Custom Attributes Import Wizard is used to import a list of custom attributes. Follow the steps
-to use the Custom Attributes Import Wizard.
+Use the Custom Attributes Import Wizard to import a list of custom attributes.
 
 **Step 1 –** On the Group Details page of the Active Directory Action Module Wizard, click
 **Import**. The Custom Attribute Import Wizard opens.
 
 ![Custom Attributes Import Wizard Credentials page](/images/accessanalyzer/11.6/admin/action/activedirectory/operations/credentials.webp)
 
 **Step 2 –** On the Credentials page, identify a domain either by entering one manually or selecting
-one from the **Domain Name** drop-down menu which displays a list of domains trusted by the one in
+one from the **Domain Name** dropdown menu which displays a list of domains trusted by the one in
 which the Enterprise Auditor Console server resides. Then set the credentials for reading the
 attributes list from the domain:
 
@@ -58,11 +57,11 @@ attributes list from the domain:
 ![Custom Attributes Import Wizard Attributes page](/images/accessanalyzer/11.6/admin/action/activedirectory/operations/attributesgroup.webp)
 
 **Step 4 –** The wizard populates available attributes from the domain specified on the Attributes
-page. Expand the desired object class and select the checkboxes for the custom attributes to be
+page. Expand the object class you want and select the checkboxes for the custom attributes to be
 imported. Then click **Next**.
 
 ![Custom Attributes Import Wizard Completion page](/images/accessanalyzer/11.6/admin/action/activedirectory/operations/completionpage.webp)
 
-**Step 5 –** On the Completion page, click **Finish**. On the Completion page, click **Finish**.
+**Step 5 –** On the Completion page, click **Finish**.
 
-The selected attributes have been added to the attribute list on the Group Details page.
+The wizard adds the selected attributes to the attribute list on the Group Details page.

docs/accessanalyzer/11.6/admin/action/activedirectory/operations/groupmembership.md

@@ -13,7 +13,7 @@ be used to specify if the object will be added or removed.
 
 Use the following options to configure the action:
 
-- Insert field – Use the drop-down list to select a field (column) from the source table. Then,
+- Insert field – Use the dropdown list to select a field (column) from the source table. Then,
   click the blue arrow to insert the item into the selected box.
 - Select one of the following:
 
@@ -22,18 +22,18 @@ Use the following options to configure the action:
 
 - OU – The organizational unit that contains the group. This field is required.
 
-    - Create target OU location if it does not already exist – Select this checkbox to create the
+    - Create target OU location if it doesn't already exist – Select this checkbox to create the
       target OU.
 
 - Group (CN, not a pre-Windows 2000 name) – The group to create. This field is required.
 
-    - Create target Group if it does not already exist
+    - Create target Group if it doesn't already exist
 
 - Select one of the following:
 
     - Add members
     - Remove members
-    - Add/Remove members – Enables the ChangeType Column drop down list
+    - Add/Remove members – Enables the ChangeType Column dropdown list
 
 - ChangeType Column – The value to use from the source table to specify if the object is added or
   removed. The contents of the ChangeType column should be a 0 for Add or a 1 for Remove.

docs/accessanalyzer/11.6/admin/action/activedirectory/operations/moveobjects.md

@@ -13,8 +13,8 @@ Use the Move Objects page to specify the OU in which to move objects.
 Use the following options to configure the action:
 
 - Insert Field – Contains available values from populated from the source table
-- OU – Use the drop-down list to select a field (column) from the source table. Then, click the blue
+- OU – Use the dropdown list to select a field (column) from the source table. Then, click the blue
   arrow to insert the item into the OU box.
 
-    - Create target OU location if it does not already exist – Select this checkbox to create the
+    - Create target OU location if it doesn't already exist – Select this checkbox to create the
       target OU