🩹 [Patch]: Framework-generated code coverage no longer penalizes module authors (#310)

Framework-generated boilerplate — type accelerator registration and
`OnRemove` cleanup — is now tested and covered by updated action
versions referenced in this workflow. The obsolete `$IsWindows` PS 5.1
shim is no longer injected into built modules. Coverage from the
framework test step and the module test step is already aggregated by
Get-CodeCoverage, so module authors' coverage percentages now reflect
only the code they wrote.

- Fixes #309

## Changed: Build-PSModule updated to v4.0.14

Built modules no longer include the `$IsWindows = $true` Desktop edition
shim or its PSScriptAnalyzer suppression attributes. PSModule targets
PowerShell LTS (7.6+), where `$IsWindows` is a built-in automatic
variable.

See
[PSModule/Build-PSModule#132](PSModule/Build-PSModule#132)
for details.

## Changed: Test-PSModule updated to v3.0.10

The framework module tests now validate that every public class and enum
is registered as a type accelerator after import, and that the
`OnRemove` hook cleans them up when the module is removed. These tests
produce coverage artifacts that are aggregated with module author test
coverage, so framework-generated boilerplate no longer counts against
the module author's coverage target.

See
[PSModule/Test-PSModule#113](PSModule/Test-PSModule#113)
for details.

## Changed: README documents the framework testing design

The README now explains:
- Why framework-generated code is tested by the framework itself
- How coverage from both the framework test step and the module test
step is aggregated
- That module authors do not need to test framework-generated code
themselves

## Technical Details

- `.github/workflows/Build-Module.yml`: Updated Build-PSModule from
v4.0.13 to v4.0.14 (`345728124d201f371a8b0f1aacb98f89000a06dc`)
- `.github/workflows/Test-Module.yml`: Updated Test-PSModule from v3.0.8
to v3.0.10 (`8c3337136dc7cf320da39eeb50e776d04bc9ac73`)
- `.github/workflows/Test-SourceCode.yml`: Updated Test-PSModule from
v3.0.8 to v3.0.10
- `README.md`: Added "Code coverage for framework-generated code"
paragraph under the Framework test section; added coverage aggregation
details under the Get code coverage section; removed reference to the
`$IsWindows` shim
- No workflow structure changes — code coverage was already enabled in
Test-Module.yml and Get-PesterCodeCoverage already aggregates all
`*-CodeCoverage` artifacts

Author: MariusStorhaug

.github/workflows/Build-Module.yml

@@ -30,7 +30,7 @@ jobs:
           fetch-depth: 0
 
       - name: Build module
-        uses: PSModule/Build-PSModule@7a3ae1be38587e8051833d85ffa53c348de3cd0d # v4.0.13
+        uses: PSModule/Build-PSModule@345728124d201f371a8b0f1aacb98f89000a06dc # v4.0.14
         with:
           Name: ${{ fromJson(inputs.Settings).Name }}
           ArtifactName: ${{ inputs.ArtifactName }}

.github/workflows/Test-Module.yml

@@ -63,7 +63,7 @@ jobs:
           path: ${{ fromJson(inputs.Settings).WorkingDirectory }}/outputs/module
 
       - name: Test-Module
-        uses: PSModule/Test-PSModule@d4d6d1d2ac1d243ca82c9c199371533e8d2220ef # v3.0.8
+        uses: PSModule/Test-PSModule@8c3337136dc7cf320da39eeb50e776d04bc9ac73 # v3.0.10
         with:
           Name: ${{ fromJson(inputs.Settings).Name }}
           Debug: ${{ fromJson(inputs.Settings).Debug }}

.github/workflows/Test-SourceCode.yml

@@ -27,7 +27,7 @@ jobs:
           fetch-depth: 0
 
       - name: Test-SourceCode
-        uses: PSModule/Test-PSModule@d4d6d1d2ac1d243ca82c9c199371533e8d2220ef # v3.0.8
+        uses: PSModule/Test-PSModule@8c3337136dc7cf320da39eeb50e776d04bc9ac73 # v3.0.10
         with:
           Debug: ${{ fromJson(inputs.Settings).Debug }}
           Prerelease: ${{ fromJson(inputs.Settings).Prerelease }}

README.md

@@ -163,6 +163,14 @@ The [PSModule - SourceCode tests](./scripts/tests/SourceCode/PSModule/PSModule.T
   - [PSModule framework settings for style and standards for modules](https://github.com/PSModule/Test-PSModule?tab=readme-ov-file#module-tests)
   - [PSScriptAnalyzer rules](https://github.com/PSModule/Invoke-ScriptAnalyzer)
 - This produces a JSON-based report that is used by [Get-PesterTestResults](#get-test-results) evaluate the results of the tests.
+- **Code coverage for framework-generated code**: This step collects code coverage for framework-generated
+  boilerplate. During the [build step](#build-module), [Build-PSModule](https://github.com/PSModule/Build-PSModule)
+  injects boilerplate code into the compiled `.psm1` file — including type accelerator registration for public classes
+  and enums, and the `OnRemove` cleanup hook. The framework tests in
+  [Test-PSModule](https://github.com/PSModule/Test-PSModule) exercise these code paths and produce coverage artifacts
+  that are aggregated with coverage from [Test-ModuleLocal](#test-module) in the
+  [Get code coverage](#get-code-coverage) step. This keeps framework-generated lines from counting against the module
+  author's coverage report.
 
 ### Test module
 
@@ -299,6 +307,9 @@ The [PSModule - Module tests](./scripts/tests/Module/PSModule/PSModule.Tests.ps1
 
 [workflow](./.github/workflows/Get-CodeCoverage.yml)
 - Gathers the code coverage from the previous steps and creates a summary of the results.
+- Aggregates coverage from the [Framework test](#framework-test) step (framework-generated boilerplate) and the
+  [Test module](#test-module) step (module author code). A command executed in either step counts as covered, so
+  framework-generated lines do not count against the module author's coverage target.
 - If the code coverage is below the target, the workflow will fail here.
 
 ### Publish module