Docs-Sync #183: av-exclusions staging-path entry says "Installation" only — updater uses it too, and post-merge inconsistency incoming

[Sev7eNup]

Source PR: #183 — "Name the longest part of an update, and stop scanning it twice over" (status: open)

Summary

PR #183 adds a new, detailed entry for %TEMP%\nodepilot-artifact-* to the server A.1 Ordner table in both docs/av-exclusions.md and src/nodepilot-docs-ui/content/deployment/av-exclusions.md (priority: "Empfohlen"). The PR does not touch the pre-existing entry for this path in the "Nur während Installation und Update" section of either file.

Two issues result — one exists today on main, one will appear when the PR merges.

---

Finding 1 — Existing inaccuracy on main (independent of the PR)

Update-NodePilot.ps1 at line 192 on main already calls Expand-NodePilotArtifactToStaging, meaning the updater already places files under %TEMP%\nodepilot-artifact-*. Yet:

• docs/av-exclusions.md line 187 ("Nur während Installation und Update" section): priority says "Pflicht während der Installation" — no mention of updates.
• src/nodepilot-docs-ui/content/deployment/av-exclusions.md line 102 (equivalent section): same wording.

The "der Installation" narrowing is factually incomplete today.

Why not auto-applied: broadening "der Installation" to "Installation und Update" is the accurate factual fix; however, the PR's new A.1 entry simultaneously reclassifies the same path from "Pflicht" to "Empfohlen." Making that priority change unilaterally (from an unmerged PR) is a judgment call outside the auto-apply rules.

---

Finding 2 — Post-merge inconsistency introduced by PR #183

After PR #183 merges, both files will have two entries for the same path with conflicting priorities:

Section	Entry	Priority
A.1 Ordner (new, from PR #183)	%TEMP%\nodepilot-artifact-*	Empfohlen
"Nur während Installation und Update" (existing, unchanged)	%TEMP%\nodepilot-artifact-*	Pflicht während der Installation

A reader consulting the doc post-merge will see contradictory signals for the same exclusion in the same document.

Why not auto-applied: resolving this requires a decision about whether to remove the older "Nur während Installation und Update" entry (consolidating everything into the new A.1 row), update its priority and wording to match, or keep both with a clarifying cross-reference. That is a human call.

---

Affected doc surfaces

• docs/av-exclusions.md — line 187 (existing "Nur während Installation und Update" table row)
• src/nodepilot-docs-ui/content/deployment/av-exclusions.md — line 102 (equivalent row)

Checklist

• docs/av-exclusions.md line 187 — At minimum, broaden "Pflicht während der Installation" to cover the update path too (true on main today regardless of PR Make the setup say what it is doing, extract faster, and stop crushing the prerequisites page #183). Then decide: keep this entry alongside the new A.1 entry from PR Make the setup say what it is doing, extract faster, and stop crushing the prerequisites page #183 (with consistent or clarified priorities), remove it as redundant, or merge the two.
• src/nodepilot-docs-ui/content/deployment/av-exclusions.md line 102 — Same: update wording, then decide on dedup vs. keep.
• After PR Make the setup say what it is doing, extract faster, and stop crushing the prerequisites page #183 merges, verify neither file carries two entries for %TEMP%\nodepilot-artifact-* with contradictory priorities.

---

Automated docs-drift finding from nightly docs-sync run 2026-08-11T03:09 UTC. Needs triage.