Record runtime-validated candidate workflow results

Author: ealdent

docs/modernization-handoff.md

@@ -127,6 +127,7 @@ Delivered:
 - release failure alert workflow (`.github/workflows/release-failure-alert.yml`)
 - maintainer release runbook (`docs/release-runbook.md`)
 - manual precompiled candidate workflow now validated on both lanes (`precompiled-candidate-evaluation.yml` run `22556129503`)
+- manual precompiled candidate workflow now validated with runtime checks on both lanes (`precompiled-candidate-evaluation.yml` run `22556206925`)
 - Windows candidate portability hardening across native + Rust build paths:
   - C portability fixes (`cokus` macros, `time_t`, `_mkdir`)
   - Rust toolchain alignment to GNU target for RubyInstaller (`x64-mingw-ucrt`)
@@ -200,7 +201,7 @@ Priority 1:
 Priority 2:
 
 - evaluate additional precompiled targets (Windows and/or musl Linux) using `docs/precompiled-target-evaluation.md`
-- latest candidate workflow signal: both Windows and musl candidate lanes are green in run `22556129503`; remaining promotion work is packaged-gem runtime coverage + release dry-run matrix validation
+- latest candidate workflow signal: both Windows and musl candidate lanes are green with runtime checks in run `22556206925`; remaining promotion work is release dry-run matrix validation before making new targets release-blocking
 
 Priority 3:
 

docs/precompiled-target-evaluation.md

@@ -15,7 +15,7 @@ Reference implementation constraints:
 
 ## Candidate: Windows (`x64-mingw-ucrt`)
 
-Status: candidate workflow green; not yet onboarded as release-blocking.
+Status: candidate workflow green (including runtime checks); not yet onboarded as release-blocking.
 
 Feasibility notes:
 
@@ -27,15 +27,15 @@ Feasibility notes:
   - [run 22555550326](https://github.com/ealdent/lda-ruby/actions/runs/22555550326): progressed further, failed on `utils.c` `mkdir(name, mode)` mismatch (Windows `_mkdir` required).
   - [run 22556009214](https://github.com/ealdent/lda-ruby/actions/runs/22556009214): Rust bindgen/toolchain parsing fixed; build then failed on Windows DLL name staging expectation.
   - [run 22556129503](https://github.com/ealdent/lda-ruby/actions/runs/22556129503): Windows candidate build + artifact upload succeeded after GNU toolchain alignment, bindgen header/sysroot setup, and dual DLL name staging support.
+  - [run 22556206925](https://github.com/ealdent/lda-ruby/actions/runs/22556206925): Windows candidate remained green with packaged-gem runtime smoke checks enabled.
 
 Required validation to promote:
 
-1. Add Windows-specific packaged-gem runtime checks (install + load + backend smoke).
-2. Run one release dry-run with a Windows target in the release matrix before making it release-blocking.
+1. Run one release dry-run with a Windows target in the release matrix before making it release-blocking.
 
 ## Candidate: musl Linux (`x86_64-linux-musl`)
 
-Status: candidate workflow green; not yet onboarded as release-blocking.
+Status: candidate workflow green (including runtime checks); not yet onboarded as release-blocking.
 
 Feasibility notes:
 
@@ -49,15 +49,14 @@ Feasibility notes:
   - [run 22555475302](https://github.com/ealdent/lda-ruby/actions/runs/22555475302): built `x86_64-linux-musl` successfully but artifact upload path was misconfigured.
   - [run 22555550326](https://github.com/ealdent/lda-ruby/actions/runs/22555550326): musl candidate built and uploaded artifacts successfully with corrected glob path (`pkg/lda-ruby-*-linux-musl.gem*`).
   - [run 22556129503](https://github.com/ealdent/lda-ruby/actions/runs/22556129503): musl candidate build + artifact upload remained green alongside the fixed Windows lane.
+  - [run 22556206925](https://github.com/ealdent/lda-ruby/actions/runs/22556206925): musl candidate remained green with packaged-gem runtime smoke checks enabled.
 
 Required validation to promote:
 
-1. Verify packaged gem metadata/platform and runtime smoke checks on musl (install + load + backend smoke).
-2. Add the lane to release dry-run matrix before making musl release-blocking.
+1. Add the lane to release dry-run matrix before making musl release-blocking.
 
 ## Recommendation
 
 Promote both candidates in staged order:
-1. Add Windows + musl packaged-gem runtime checks.
-2. Run a release dry-run with both candidate targets included.
-3. Make each target release-blocking only after dry-run and runtime parity are stable.
+1. Run a release dry-run with both candidate targets included.
+2. Make each target release-blocking only after dry-run stability is confirmed.