[Yuchao Yan (msyyc)]

Summary

Clarify Windows publication command safety for the LintDiff queue and review loop.

• Separate read-only identity checks from short rooted staging, commit, push, and publication steps.
• Validate multi-line PowerShell publication syntax before executing it.
• Use native Git exit codes, not stdout truthiness, for outputless commands.
• Inspect the actual refreshed diagnostic-snapshot set instead of a guessed file count.

Evidence

The LroExtension workflow in #5639 completed its required review-fix validation but stopped before staging because a large PowerShell publication wrapper had a missing closing parenthesis. Earlier outputless Git wrappers and a guessed five-snapshot guard also obstructed valid work; the actual nine changed snapshots were independently verified as diagnostic-message replacements.

The primary review loop is stopped. This independent PR changes only skill documentation and does not resume that workflow, alter rule code, or grant an additional correction attempt. Parser rejection still counts as a command failure under the existing finite recovery policy, despite zero native mutation attempts.

Validation

Formatted only the two changed Markdown files with the existing Prettier 3.9.5 installation and identical repository configuration. Checked the complete diff, relative documentation links, staged scope, and git diff --check.

No dependency installation, submodule initialization, package build, corpus rerun, CI retry, or additional Copilot review loop is required for this documentation-only PR.