[Copilot]

DSC resource detection could suppress diagnostics for executable commands and scan sibling statements for ordinary commands. It also misclassified assignments, scriptblock expressions, and pipeline elements as resource declarations.

• Constrain resource detection: Defer body lookup until a configuration ancestor is found. Require a standalone command pipeline and a matching resource header for following-line bodies.
• Preserve executable diagnostics: Treat assignment and expression contexts as boundaries; only accept command-expression blocks when they match a resource body.
• Add regressions: Cover assigned commands and scriptblocks, parenthesized expressions, following-line property blocks, and piped commands.

Configuration Example {
    Package App {
        Name = 'Example'
    }

    $result = Verb Argument {}
    Verb Argument {} | Out-Null
}

The resource declaration remains ignored; the executable commands retain their Get-Verb diagnostics.

[Copilot]

🟢 Approval recommended

No active review issues were identified in the AvoidAlias DSC resource-detection changes.

No open issues 🎉

What changed in this PR

This PR tightens DSC resource detection in the AvoidAlias rule so executable commands retain diagnostics while resource declarations remain excluded.

Changes:

• Require a configuration ancestor and a standalone command pipeline before recognizing resource declarations.
• Treat assignment and parenthesized-expression contexts as boundaries, and validate following-line resource bodies against their headers.
• Add regression coverage for assignments, scriptblocks, expressions, following-line property blocks, and pipelines.

File	Description
Tests/​Rules/​AvoidUsingAlias.tests.ps1	Adds regression tests ensuring executable commands retain alias and implicit-command diagnostics.
Rules/​AvoidAlias.cs	Restricts DSC resource detection and validates following-line body associations.

_{Review effort: Balanced}