Document remaining Node 20 workflow backlog

Author: a-a-k

README.md

@@ -109,7 +109,7 @@ The compatibility files in `compat/` are the source of truth for stack-level ass
 
 ## Backlog
 
-The GitHub issue backlog was checked on `2026-03-22`. The only open repository issue is [#20](https://github.com/MB3R-Lab/mb3r-stack/issues/20), tracking migration away from deprecated Node.js 20 GitHub Actions runtimes. This branch updates the workflows to `actions/checkout@v6`, `actions/setup-python@v6`, and `azure/setup-helm@v4.3.1`; once CI on `main` is green, that issue can be closed.
+The GitHub issue backlog was checked on `2026-03-22`. The only open repository issue is [#20](https://github.com/MB3R-Lab/mb3r-stack/issues/20), tracking migration away from deprecated Node.js 20 GitHub Actions runtimes. `actions/checkout` and `actions/setup-python` were moved to Node 24-ready lines, but GitHub `ci` run `23407592947` still reports the Node.js 20 deprecation annotation for `azure/setup-helm@v4.3.1`, so the issue remains open pending a Helm setup replacement in the GitHub workflows.
 
 ## License
 

docs/backlog.md

@@ -14,6 +14,7 @@ At the time of this snapshot there is one open issue:
 
 ## Current status
 
-- The workflow updates in this branch move the repository to `actions/checkout@v6`, `actions/setup-python@v6`, and `azure/setup-helm@v4.3.1`.
-- That change is intended to satisfy the acceptance criteria of issue `#20`.
-- Close the issue after `ci` and `release` on `main` confirm the Node.js 20 deprecation warning is no longer emitted.
+- The repository has already moved `actions/checkout` to `v6` and `actions/setup-python` to `v6`.
+- `azure/setup-helm@v4.3.1` still emits the GitHub Node.js 20 deprecation annotation.
+- `ci` run `23407592947` for commit `ce14aef6dd2ee99571a7ef4d6a211f9cf9173aba` succeeded functionally but did not satisfy the backlog acceptance criteria for issue `#20`.
+- Issue `#20` remains open until `.github/workflows/ci.yml` and `.github/workflows/release.yml` stop using a Node 20-based Helm setup action or otherwise run without the annotation.

release/v0.3.0.md

@@ -7,7 +7,7 @@ Minor bundle release that realigns the integration layer with the current upstre
 - upgrades the bundle pins to Bering `v0.3.1` and Sheaft `v0.2.1`
 - records strict stack compatibility for the published Bering `io.mb3r.bering.model` and `io.mb3r.bering.snapshot` schema lines at both `1.0.0` and `1.1.0`
 - keeps the stack-level adapter envelopes stable at `v1alpha1` while refreshing chart defaults, examples, and CI adapters to the new upstream images
-- updates GitHub Actions workflows to `actions/checkout@v6`, `actions/setup-python@v6`, and `azure/setup-helm@v4.3.1` to address the Node.js 20 deprecation backlog item
+- updates GitHub Actions workflows to `actions/checkout@v6`, `actions/setup-python@v6`, and `azure/setup-helm@v4.3.1` as a partial step on the Node.js 20 deprecation backlog item
 - hardens local acceptance and live-smoke helpers to use dynamic localhost ports so verification is resilient on busy developer machines
 - does not change formal maturity: the bundle remains `candidate`
 
@@ -25,4 +25,6 @@ Minor bundle release that realigns the integration layer with the current upstre
 
 ### Backlog on 2026-03-22
 
-- GitHub issue [#20](https://github.com/MB3R-Lab/mb3r-stack/issues/20) is the only open repository issue and is addressed by the workflow action upgrades in this release branch; close it after post-merge CI confirms the warning is gone
+- GitHub issue [#20](https://github.com/MB3R-Lab/mb3r-stack/issues/20) is the only open repository issue
+- `actions/checkout@v6` and `actions/setup-python@v6` are in place, but GitHub `ci` run `23407592947` still reports the Node.js 20 deprecation annotation for `azure/setup-helm@v4.3.1`
+- the issue therefore remains open until Helm setup in the GitHub workflows is replaced with a Node 24-safe path