Release v0.6.12 (to main)

CHANGELOG.md

@@ -7,6 +7,28 @@ The format is based on Keep a Changelog, and this project adheres to Semantic Ve
 
 ## [Unreleased]
 
+## [v0.6.12] - 2026-04-01
+
+### Fixed
+
+- Reworked Windows preflight and Docker runtime-manager process capture so
+  large `docker manifest inspect` payloads no longer deadlock the bounded
+  timeout path, preserving truthful Windows NI preflight and runtime
+  determinism outcomes instead of hanging the release-proof surface.
+
+### Added
+
+- Regression coverage in `tests/Invoke-DockerRuntimeManager.Tests.ps1` and
+  `tests/Test-WindowsNI2026q1HostPreflight.Tests.ps1` proving large manifest
+  output still completes cleanly through the shared timeout helper.
+
+### Changed
+
+- Built the `v0.6.12` release line on top of the published `v0.6.11` stable
+  baseline, preserving the Windows NI proof authority and VI-history
+  native-path repair while adding the preflight deadlock fix required for a
+  clean release rail.
+
 ## [v0.6.11] - 2026-04-01
 
 ### Fixed

Directory.Build.props

@@ -7,9 +7,9 @@
     <GenerateDocumentationFile>false</GenerateDocumentationFile>
     <Deterministic>true</Deterministic>
     <ContinuousIntegrationBuild>true</ContinuousIntegrationBuild>
-    <Version>0.6.11</Version>
-    <AssemblyVersion>0.6.11.0</AssemblyVersion>
-    <FileVersion>0.6.11.0</FileVersion>
+    <Version>0.6.12</Version>
+    <AssemblyVersion>0.6.12.0</AssemblyVersion>
+    <FileVersion>0.6.12.0</FileVersion>
     <InformationalVersion>$(Version)+local</InformationalVersion>
     <CompareViSharedSource Condition="'$(CompareViSharedSource)' == ''">package-first</CompareViSharedSource>
     <CompareViSharedFallbackSource Condition="'$(CompareViSharedFallbackSource)' == ''">project</CompareViSharedFallbackSource>

Invoke-PesterTests.ps1

@@ -567,6 +567,9 @@ $ErrorActionPreference = 'Stop'
 if (-not (Get-Variable -Name includeIntegrationBool -Scope Script -ErrorAction SilentlyContinue)) {
   $script:includeIntegrationBool = $false
 }
+$script:stuckGuardEnabled = $false
+$script:hbPath = $null
+$script:partialLogPath = $null
 $script:executionPackResolved = 'full'
 $script:executionPackReason = 'default'
 $script:executionPackBaseIncludePatterns = @()
@@ -1204,11 +1207,6 @@ Write-Host "  Script Root: $root"
 Write-Host "  Tests Directory: $testsDir"; if ($limitToSingle) { Write-Host "  Single Test File: $singleTestFile" }
 Write-Host "  Results Directory: $resultsDir"
 Write-Host ""
-$script:dispatcherEventsPath = Join-Path $resultsDir 'dispatcher-events.ndjson'
-Write-DispatcherEventLine -Level info -Phase 'lifecycle' -Message 'Dispatcher session initialized.' -Data @{
-  testsDir   = $testsDir
-  resultsDir = $resultsDir
-}
 
 # Validate tests directory exists
 if (-not (Test-Path -LiteralPath $testsDir -PathType Container)) {
@@ -1306,6 +1304,27 @@ function _Build-Snapshot {
   return $index
 }
 
+# Artifact tracking pre-snapshot (optional). Capture before any dispatcher-owned
+# result files are written so isolated runs report those files as created rather
+# than modified.
+$script:artifactTrail = $null
+$script:executionFinalizeContextPath = $null
+$preIndex = $null
+$artifactRoots = @()
+if ($TrackArtifacts) {
+  if (-not $ArtifactGlobs -or $ArtifactGlobs.Count -eq 0) {
+    $ArtifactGlobs = @('tests/results','results','tmp-agg/results','scratch-schema-test/results')
+  }
+  $artifactRoots = _Resolve-ArtifactRoots -Roots $ArtifactGlobs -Base $root
+  try { $preIndex = _Build-Snapshot -Roots $artifactRoots -Base $root } catch { $preIndex = @{} }
+}
+
+$script:dispatcherEventsPath = Join-Path $resultsDir 'dispatcher-events.ndjson'
+Write-DispatcherEventLine -Level info -Phase 'lifecycle' -Message 'Dispatcher session initialized.' -Data @{
+  testsDir   = $testsDir
+  resultsDir = $resultsDir
+}
+
 # Hard gate: never start tests while LabVIEW.exe is running
 $labviewOpen = @(_Find-ProcsByPattern -Patterns @('LabVIEW') )
 if ($labviewOpen.Count -gt 0) {
@@ -1765,19 +1784,6 @@ if ($CleanLabVIEW) {
   _Report-Procs -Names @('LabVIEW')
 }
 
-# Artifact tracking pre-snapshot (optional)
-$script:artifactTrail = $null
-$script:executionFinalizeContextPath = $null
-$preIndex = $null
-$artifactRoots = @()
-if ($TrackArtifacts) {
-  if (-not $ArtifactGlobs -or $ArtifactGlobs.Count -eq 0) {
-    $ArtifactGlobs = @('tests/results','results','tmp-agg/results','scratch-schema-test/results')
-  }
-  $artifactRoots = _Resolve-ArtifactRoots -Roots $ArtifactGlobs -Base $root
-  try { $preIndex = _Build-Snapshot -Roots $artifactRoots -Base $root } catch { $preIndex = @{} }
-}
-
 # Count test files (respect single file mode)
 if ($limitToSingle) {
   $testFiles = @([IO.FileInfo]::new($singleTestFile))

docs/archive/releases/RELEASE_NOTES_v0.6.12.md

@@ -0,0 +1,38 @@
+# Release Notes v0.6.12
+
+`v0.6.12` is a maintenance release that carries the published `v0.6.11` stable
+line forward and fixes the Windows preflight process-capture deadlock exposed
+when Docker returns large manifest output.
+
+## Highlights
+
+- The released backend no longer deadlocks while collecting large Docker
+  manifest payloads during Windows preflight and runtime-manager checks.
+- A shared timeout helper now owns bounded process execution and concurrent
+  stdout/stderr draining for the Windows preflight seam.
+- The stable release keeps the `v0.6.11` Windows NI proof authority and
+  VI-history native-path repair instead of regressing to an older integration
+  surface.
+
+## Included maintenance slice
+
+- `#2091` fix: Windows preflight process capture deadlock
+- carry forward the published `v0.6.11` release-line policy and proof surfaces
+
+## Validation highlights
+
+- Focused Pester coverage proves large-manifest replay no longer blocks either
+  `tools/Invoke-DockerRuntimeManager.ps1` or
+  `tools/Test-WindowsNI2026q1HostPreflight.ps1`.
+- The release branch is prepared from the published `v0.6.11` line and merged
+  with the post-`#2091` `develop` tip, preserving the already-published stable
+  fixes while adding the Windows preflight deadlock repair.
+- Release helper docs, changelog, and version surfaces align on `0.6.12`.
+
+## Consumer impact
+
+- Stable consumers should move from `@v0.6.11` to `@v0.6.12` to pick up the
+  Windows preflight/runtime-manager deadlock repair.
+- `comparevi-history` should repin `comparevi-backend-ref.txt` to `v0.6.12`
+  before rerunning the clone-backed `ni/labview-icon-editor` proof on the
+  released backend.

docs/release/PR_NOTES.md

@@ -1,37 +1,41 @@
 <!-- markdownlint-disable-next-line MD041 -->
-# Release v0.6.11 - PR Notes Helper
+# Release v0.6.12 - PR Notes Helper
 
-Reference sheet for the `v0.6.11` maintenance release. This cut carries the
-`v0.6.10` stable line forward and adds the VI-history native-path repair proven
-on the Windows NI Docker-backed proof surface.
+Reference sheet for the `v0.6.12` maintenance release. This cut carries the
+published `v0.6.11` stable line forward and adds the Windows preflight
+process-capture deadlock fix proven on the Windows NI Docker-backed proof
+surface.
 
 ## 1. Summary
 
-Release `v0.6.11` focuses on three themes:
+Release `v0.6.12` focuses on three themes:
 
-- **VI-history native-path correctness**: the released backend now resolves
-  Windows NI proof-surface file paths without losing the repository-relative VI
-  target, so hosted and local replay lanes can reach the real history target
-  instead of a synthetic temp-root mismatch.
+- **Deadlock-free Windows preflight capture**: the released backend now drains
+  large Docker manifest output without stalling the bounded timeout path, so
+  Windows NI preflight and runtime-manager checks can report real readiness
+  instead of hanging.
 - **Windows NI proof continuity**: the LabVIEW Docker-backed Windows proof path
-  remains the authoritative hosted execution surface, and `v0.6.11` is cut
-  directly from the `v0.6.10` stable line so the released proof authority is
-  preserved rather than reintroduced from stale `develop`.
+  remains the authoritative hosted execution surface, and `v0.6.12` is cut
+  directly from the published `v0.6.11` stable line so the released proof
+  authority is preserved rather than reintroduced from stale `develop`.
 - **Consumer-ready repin path**: the release packet is aligned for the next
   `comparevi-history` pin bump and the clone-backed `ni/labview-icon-editor`
   history proof rerun on the newly published backend.
 
 ## 2. Maintenance Highlights
 
-- `tools/Compare-VIHistory.ps1`, `tools/Compare-RefsToTemp.ps1`, and
-  `tools/Render-VIHistoryReport.ps1` now preserve the intended VI-history
-  target path across the Windows NI proof surface instead of collapsing to a
-  host-native path that the replay layer cannot certify.
-- `tests/TestFileExistsAtRef.Tests.ps1` and
-  `tests/CompareVI.GitRefs.VI2.Tests.ps1` now cover the backend-side path and
-  git-ref seams that caused the Windows proof regression.
-- Stable release surfaces now pin `0.6.11`, while the helper docs still point
-  consumers at `v0.6.10` until publication completes.
+- `tools/ProcessTimeoutHelper.ps1` now centralizes bounded process execution
+  and concurrent stdout/stderr capture for the Docker-backed Windows proof
+  seam.
+- `tools/Invoke-DockerRuntimeManager.ps1`,
+  `tools/Assert-DockerRuntimeDeterminism.ps1`, and
+  `tools/Test-WindowsNI2026q1HostPreflight.ps1` now share that helper so large
+  manifest responses cannot deadlock the release-proof path.
+- `tests/Invoke-DockerRuntimeManager.Tests.ps1` and
+  `tests/Test-WindowsNI2026q1HostPreflight.Tests.ps1` now prove large manifest
+  output stays non-blocking on the authoritative Windows surface.
+- Stable release surfaces now pin `0.6.12`, while the helper docs still point
+  consumers at `v0.6.11` until publication completes.
 
 ## 3. Validation Snapshot
 
@@ -44,12 +48,12 @@ Release `v0.6.11` focuses on three themes:
 - [ ] Hosted Windows NI Docker proof is green on the release branch.
 - [ ] Local-proof autonomy selector still emits the truthful next proof
       surface instead of looping or hanging.
-- [ ] `node tools/npm/run-script.mjs release:finalize -- 0.6.11` completes from
+- [ ] `node tools/npm/run-script.mjs release:finalize -- 0.6.12` completes from
       a clean helper lane and writes fresh finalize metadata under
       `tests/results/_agent/release/`
-- [ ] Published release `v0.6.11` includes the signed distribution assets,
+- [ ] Published release `v0.6.12` includes the signed distribution assets,
       `SHA256SUMS.txt`, `sbom.spdx.json`, and `provenance.json`
-- [ ] `comparevi-history` repins `comparevi-backend-ref.txt` to `v0.6.11`
+- [ ] `comparevi-history` repins `comparevi-backend-ref.txt` to `v0.6.12`
       before the clone-backed `ni/labview-icon-editor` proof is rerun
 
 ## 4. Reviewer Focus
@@ -58,23 +62,25 @@ Release `v0.6.11` focuses on three themes:
   - `package.json`
   - `Directory.Build.props`
   - `tools/CompareVI.Tools/CompareVI.Tools.psd1`
-- Review the released Windows NI Docker proof and VI-history backend surfaces for correctness:
-  - `.github/workflows/windows-ni-proof-reusable.yml`
-  - `tools/Compare-VIHistory.ps1`
-  - `tools/Compare-RefsToTemp.ps1`
-  - `tools/Render-VIHistoryReport.ps1`
+- Review the released Windows preflight/runtime-manager surfaces for
+  correctness:
+  - `tools/ProcessTimeoutHelper.ps1`
+  - `tools/Invoke-DockerRuntimeManager.ps1`
+  - `tools/Test-WindowsNI2026q1HostPreflight.ps1`
+  - `tests/Invoke-DockerRuntimeManager.Tests.ps1`
+  - `tests/Test-WindowsNI2026q1HostPreflight.Tests.ps1`
 - Review the release helper packet for consistency:
   - `CHANGELOG.md`
   - `docs/release/TAG_PREP_CHECKLIST.md`
-  - `docs/archive/releases/RELEASE_NOTES_v0.6.11.md`
+  - `docs/archive/releases/RELEASE_NOTES_v0.6.12.md`
 
 ## 5. Follow-Up After Stable
 
-1. Re-pin `comparevi-history` from `v0.6.10` to `v0.6.11` and rerun the
+1. Re-pin `comparevi-history` from `v0.6.11` to `v0.6.12` and rerun the
    clone-backed `ni/labview-icon-editor` proof on the released backend.
 2. Confirm the Windows NI proof artifacts and the published benchmark packet
    still agree on the certified backend version after the repin.
 3. Re-evaluate the current emitted history surface against the real developer
    question before treating any mode as decision-ready.
 
---- Updated: 2026-04-01 (prepared for the `v0.6.11` maintenance cut).
+--- Updated: 2026-04-01 (prepared for the `v0.6.12` maintenance cut).

docs/release/README.md

@@ -7,7 +7,9 @@ work.
 ## Contents
 
 - `PR_NOTES.md` - release PR summary helper
-- `RELEASE_EVIDENCE_v0.6.6.md` - latest immutable release and certified-consumer evidence packet retained in-repo while the `v0.6.11` cut supersedes the published `v0.6.10` baseline
+- `RELEASE_EVIDENCE_v0.6.6.md` - latest immutable release and
+  certified-consumer evidence packet retained in-repo while the `v0.6.12` cut
+  supersedes the published `v0.6.11` baseline
 - `TAG_PREP_CHECKLIST.md` - tag preparation checklist
 - `POST_RELEASE_FOLLOWUPS.md` - post-release backlog tracker
 - `ROLLBACK_PLAN.md` - rollback procedure reference

docs/release/TAG_PREP_CHECKLIST.md

@@ -1,14 +1,14 @@
-# v0.6.11 Tag Preparation Checklist
+# v0.6.12 Tag Preparation Checklist
 <!-- markdownlint-disable-next-line MD041 -->
 
-Helper reference for cutting or replaying the `v0.6.11` maintenance release.
+Helper reference for cutting or replaying the `v0.6.12` maintenance release.
 Aligns with the archived release notes
-(`../archive/releases/RELEASE_NOTES_v0.6.11.md`) and the checked-in stable
+(`../archive/releases/RELEASE_NOTES_v0.6.12.md`) and the checked-in stable
 release surfaces.
 
 ## 1. Pre-flight Verification
 
-- [ ] Work from `release/v0.6.11` and ensure it contains the final maintenance
+- [ ] Work from `release/v0.6.12` and ensure it contains the final maintenance
       changes.
 - [ ] CI is green on the release branch (`lint`, `pester / normalize`,
       `smoke-gate`, `Policy Guard (Upstream) / policy-guard`,
@@ -22,26 +22,30 @@ release surfaces.
 ## 2. Version & Metadata Consistency
 
 - [ ] `CHANGELOG.md` contains a finalized
-      `## [v0.6.11] - 2026-04-01` section.
-- [ ] Stable docs reference `v0.6.10` consistently until `v0.6.11` publication
-      completes, and the release helper packet references `v0.6.11`
+      `## [v0.6.12] - 2026-04-01` section.
+- [ ] Stable docs reference `v0.6.11` consistently until `v0.6.12` publication
+      completes, and the release helper packet references `v0.6.12`
       consistently.
 - [ ] `package.json`, `Directory.Build.props`, and
-      `tools/CompareVI.Tools/CompareVI.Tools.psd1` all report `0.6.11`.
+      `tools/CompareVI.Tools/CompareVI.Tools.psd1` all report `0.6.12`.
 - [ ] `docs/action-outputs.md` still matches `action.yml`.
 - [ ] Update `docs/documentation-manifest.json` if release-doc coverage changed.
 
-## 3. Bundle Contract Regression Validation
+## 3. Windows Preflight Regression Validation
 
-- [ ] Focused bundle regression tests pass locally:
+- [ ] Focused Windows preflight/runtime-manager regression tests pass locally:
 
 ```bash
-pwsh -NoLogo -NoProfile -File tools/Test-CompareVIHistoryBundleCertification.ps1 -BundleArchivePath tests/results/_agent/bundle-fix/artifacts/CompareVI.Tools-v0.6.11.zip -ResultsDir tests/results/_agent/bundle-fix/certification -SummaryJsonPath tests/results/_agent/bundle-fix/certification/summary.json
+pwsh -NoLogo -NoProfile -File Invoke-PesterTests.ps1 -TestsPath tests/Invoke-DockerRuntimeManager.Tests.ps1
+pwsh -NoLogo -NoProfile -File Invoke-PesterTests.ps1 -TestsPath tests/Test-WindowsNI2026q1HostPreflight.Tests.ps1
 ```
 
 - [ ] Confirm the released Windows NI / LabVIEW Docker image proof surface is intact:
 
 - [ ] The released surface still includes:
+      `tools/ProcessTimeoutHelper.ps1`
+      `tools/Invoke-DockerRuntimeManager.ps1`
+      and
       `tools/Run-NIWindowsContainerCompare.ps1`
       and
       `tools/Test-WindowsNI2026q1HostPreflight.ps1`
@@ -56,17 +60,17 @@ pwsh -NoLogo -NoProfile -File tools/Test-CompareVIHistoryBundleCertification.ps1
 ## 4. Release Materials Review
 
 - [ ] `PR_NOTES.md`, this checklist, and
-      `../archive/releases/RELEASE_NOTES_v0.6.11.md` are consistent.
-- [ ] `README.md` and `docs/USAGE_GUIDE.md` still treat `v0.6.10` as the
-      previously released stable pin until `v0.6.11` publication completes.
+      `../archive/releases/RELEASE_NOTES_v0.6.12.md` are consistent.
+- [ ] `README.md` and `docs/USAGE_GUIDE.md` still treat `v0.6.11` as the
+      previously released stable pin until `v0.6.12` publication completes.
 
 ## 5. Tag Creation
 
 - [ ] Verify signed-tag readiness before push:
 
 ```pwsh
 node tools/npm/run-script.mjs priority:release:signing:readiness
-node tools/npm/run-script.mjs priority:release:conductor -- --apply --channel stable --version 0.6.11
+node tools/npm/run-script.mjs priority:release:conductor -- --apply --channel stable --version 0.6.12
 ```
 
 - [ ] Confirm `tests/results/_agent/release/release-signing-readiness.json`
@@ -77,35 +81,35 @@ node tools/npm/run-script.mjs priority:release:conductor -- --apply --channel st
 - [ ] Create an annotated stable tag:
 
 ```pwsh
-git tag -a v0.6.11 -m "v0.6.11: repair VI history native paths on Windows proof surfaces"
+git tag -a v0.6.12 -m "v0.6.12: fix Windows preflight process capture deadlock"
 ```
 
 - [ ] Push the tag:
 
 ```pwsh
-git push origin v0.6.11
+git push origin v0.6.12
 ```
 
 ## 6. Validation After Publish
 
-- [ ] Run `node tools/npm/run-script.mjs release:finalize -- 0.6.11` from a
+- [ ] Run `node tools/npm/run-script.mjs release:finalize -- 0.6.12` from a
       clean helper lane to fast-forward `main` and `develop`, then record the
       finalize metadata.
-- [ ] Install the bundle via `@v0.6.11` in a sample workflow and confirm the
+- [ ] Install the bundle via `@v0.6.12` in a sample workflow and confirm the
       released Windows NI and hosted VI-history contracts execute without a
       local source-tree override.
 - [ ] Optional maintainer fast loop: run the local Windows Docker replay lane
       for `vi-history-scenarios-windows` and confirm it still mirrors the
       hosted contract without replacing the hosted proof requirement.
-- [ ] Re-pin `comparevi-history` to `v0.6.11` and confirm the clone-backed
+- [ ] Re-pin `comparevi-history` to `v0.6.12` and confirm the clone-backed
       `ni/labview-icon-editor` proof reaches real comparisons on the released
       backend.
 
 ## 7. Communication
 
-- [ ] Announce the maintenance cut, calling out the promoted Windows NI Docker
-      proof surface and the required `comparevi-history` repin.
-- [ ] Notify consumers that `v0.6.11` supersedes `v0.6.10` as the supported
+- [ ] Announce the maintenance cut, calling out the Windows preflight deadlock
+      fix and the required `comparevi-history` repin.
+- [ ] Notify consumers that `v0.6.12` supersedes `v0.6.11` as the supported
       stable pin.
 
---- Updated: 2026-04-01 (prepared for the `v0.6.11` maintenance cut).
+--- Updated: 2026-04-01 (prepared for the `v0.6.12` maintenance cut).