The weekly freshness check could not fail, and the .nvmrc §4 asks for

[oblomov-dev]

1. release-freshness.yml has never been able to report anything

run: node scripts/check-version.mjs | tee version.txt

GitHub runs a run: step as bash -e {0} — errexit, but not pipefail. A
pipeline reports its last command's status, and tee succeeds whenever it can
write the file. So the step passed however stale the site was, and the
if: failure() step below it — the one that opens the stale-release issue —
never ran.

A weekly check that reports nothing and looks green doing it is the failure mode
this organisation names as the worst it can produce.

Measured rather than reasoned:

$ bash -e -c 'node failing.mjs | tee version.txt'; echo $?
0          # Actions reads this as PASSED

$ bash -e -c 'set +e; node failing.mjs | tee version.txt; S=${PIPESTATUS[0]}; set -e; exit $S'; echo $?
1          # correctly red

abap2UI5/linter's upstream-sync.yml already handles the identical
node … | tee shape with PIPESTATUS, so this copies an in-house pattern
rather than inventing one.

2. A green run claimed more than it had established

check-version.mjs ended with `the documentation names the release that exists

• OK` — even when the release API had been unreachable, two lines under its own
  report that this was UNVERIFIED. The three places had been compared against
  each other and against nothing else.

It now says which of the two it actually checked. Still exit 0 when the API is
down: an outage is not a documentation defect, and the same reasoning
shared-file-gate.mjs writes down ("must not claim to have verified something
they did not") applies to the wording as much as to the verdict.

Both branches exercised — the unreachable one with fetch stubbed out.

3. The .nvmrc CONVENTIONS §4 asks for

§4 is one sentence: "engines.node is >=22 and .nvmrc says 22." The first
half was here; the second was missing — in seven of the nine repositories,
only abap2UI5 and linter had it. §4 is the one section
conventions-gate.mjs does not touch at all, which is how it drifted. The file
records what is already true: CI here already runs Node 22 and engines.node
already says >=22. abap2UI5#2679 adds the gate that keeps it that way.

Checks

npm run check — 33 tests, the VitePress build and all seven gates, green.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.