Repository navigation
v0.3.23 — REQ-017/030 fixes + semantic-audit SRS corrections
·
264 commits
to develop
since this release
Immutable
release. Only release title and notes can be modified.
v0.3.23
- fix REQ-017: the guest/WinRM password file written during Windows LabVIEW VM provisioning was never shredded/removed anywhere in the workflow (only an unrelated PAT file was) -- added a
shred(withrm -ffallback) cleanup line to every step inprovision-windows-labview-vm.ymlthat writes it - fix REQ-030:
add-project.yml's upsert only replaced the first matching entry by project name, so a pre-existing duplicate entry would survive a re-registration instead of collapsing to one -- now filters out every matching entry before appending the fresh one - correct REQ-013, REQ-018/REQ-019 (narrowed "LabVIEW/VIPM" to "LabVIEW" -- VIPM activation on the Ubuntu-LabVIEW family is genuinely automated and deliberately so, now its own REQ-032), and REQ-025 wiki SRS/RTM/Architecture-Packet wording to match the real code they cite -- all found by this session's multi-model semantic audit (
#52) cross-checking the SRS against the real ISO/IEC/IEEE 29148:2018 clause text and the real repo source, not just the heuristicrepo-standards-reviewpattern-match score - fix a second instance of the same self-referential DoD false-positive bug class:
CHANGELOG.md's own v0.3.22 entry (describing the first fix) quoted the exact literal CI-context string the DoD rule detects, re-triggering a false DoDPASS-- rephrased the same way, without reproducing the matched string - re-certify the compliance stamp against
repo-standards-review@v0.2.23(adds the canonical multi-model semantic-audit mode used to find the REQ findings above): all 5 required gates stillPASS, High confidence (99-100%); DoD correctly back to its realFAIL (not required)/60% state once the self-referential false positive above was fixed