AzLocal.UpdateManagement v0.8.6: Step.3 cycle-calendar enrichment + 6 v0.8.5 pipeline regression fixes

[NeilBird]

AzLocal.UpdateManagement v0.8.6

Step.3 cycle-calendar enrichment + six v0.8.5 thin-YAML pipeline regression fixes + 11 new Pester regression-guard tests. Same 55 public exports; no parameter changes on existing cmdlets.

NEW (Step.3 cycle calendar)

• Get-AzLocalApplyUpdatesScheduleCycleCalendar gains two opt-in render-time columns:
  • -CronFiringsByDate ([hashtable], keys = yyyy-MM-dd UTC, values = [string[]] of HH:mm UTC firing times) → centered Ring CRON Start Time (UTC) (Step 6 pipeline) column between Date (UTC) and Day. 0 firings → _(none)_; 1-2 → comma-joined; 3+ → first 2 + " (+N)"; dead day → _(none - dead day)_.
  • -WindowMatchByRingAndDate ([hashtable[string,hashtable]]) → Tag Start Window Match (>=95%) column after Eligible rings. Per-ring line: `Ring`: True/False mat/tot (pct%).
• Export-AzLocalApplyUpdatesScheduleAudit auto-wires both via Read-AzLocalApplyUpdatesYamlCrons + ConvertFrom-AzLocalUpdateWindow. Pure render-time contract preserved; failure mode is non-fatal (degrades to v0.8.5 calendar with Write-Warning).

FIX (v0.8.5 thin-YAML port regressions)

• Step.0 Export-AzLocalAuthValidationReport: @() wrap on unary-comma Invoke-AzResourceGraphQuery collapsed visible-cluster count to 1. Switched to direct assignment + $clusterRows = @($clusterRows) variable-level coerce.
• Step.3 Test-AzLocalApplyUpdatesScheduleCoverage: array-level .MatchingCrons enumeration crashed under strict mode on empty $segmentStatuses. Guarded with Count check.
• Step.4 Get-AzLocalFleetConnectivityStatus: single-cluster RG crashed because if-as-expression silently unwrapped @() to scalar. Now $matchedList → $matched = @($matchedList) at variable level.
• Step.6 Get-AzLocalClusterUpdateReadiness: $cluster.NotFound strict-mode error — three builder paths missing the key, all now set NotFound=$false.
• Step.9 Export-AzLocalFleetHealthStatusReport: @() wrap on both Get-AzLocalFleetHealthFailures and Get-AzLocalFleetHealthOverview collapsed row sets. Switched to direct assignment.
• Step.2 Set-AzLocalClusterUpdateRingTag: Format-Table without | Out-Host leaked formatter wrapper objects into -PassThru pipeline (Total clusters processed = 44 on a 20-row CSV). Added | Out-Host + defence-in-depth ClusterName -is [string] filter in Set-AzLocalClusterUpdateRingTagFromCsv.
• Step.2 UX: per-cluster Message now names changed tags (Tags updated: UpdateExcluded: 'False' -> 'True') instead of always "UpdateRing tag updated successfully". Summary split into 3 collapsible buckets (Tag Updates Applied / Skipped or Failed / No Tag Updates).
• Node.js 20 deprecation: bumped actions/upload-artifact@v4 → @v6 in Step.0_authentication-test.yml (every other Step YAML already on v6).

TESTS (11 new regression-guard It blocks across 7 Describe blocks)

• @() wrap on unary-comma return helpers (Invoke-AzResourceGraphQuery, Get-AzLocalFleetHealth{Failures,Overview}, Read-AzLocalApplyUpdatesYamlCrons).
• Step.3 .MatchingCrons strict-mode crash; Step.4 $matched if/else { @() } branch; Step.6 NotFound key on every $clustersToProcess builder; Step.0 $clusterRows variable-level @() coerce; Step.2 Format-Table | Out-Host.
• GHA Node.js 20 deprecation (artifact action versions across every bundled GHA YAML).
• 12 new cycle-calendar It blocks for backwards compat / both-params header / (+N) suffix / 95% boundary / case-insensitivity / -ClusterRingCounts coexistence.

DRIFT

• 20 bundled Step.{0..9}.yml templates bump GENERATED_AGAINST_MODULE_VERSION 0.8.5 → 0.8.6.
• Pester $expectedVersion bumped to 0.8.6.

Local verification

• Full Pester (excl. Live): 1102 passed / 0 failed / 1 skipped, ~8m45s.
• Step.2 subset after Format-Table fix: 12/12 passed, 5.2s.
• 3 Live-tagged Step.0 / Step.3 / Step.4 integration tests skipped here (env-only nebird@microsoft.com not visible to Azure AD Graph from workstation); CI also excludes the Live tag.