v0.3.27 — round-3 semantic-audit findings (verification pass)

v0.3.27

• fix a real, residual gap in v0.3.26's own REQ-017 fix: 2 of the 5 trap ... EXIT installations wrote their credential file(s) before installing the trap, so a failure during file creation itself (e.g. the register-runner step's PAT-file creation) could still leave an earlier-written file behind -- moved every trap installation to the very first executable line of its step, before any file is created, since rm -f/shred -u on a not-yet-created file are safe no-ops
• fix REQ-032 (wiki) and docs/vm-provisioning/procedure.md: the previous round claimed VIPM's automated activation is "gated on the operator having already completed LabVIEW's own interactive activation" -- this is false. capture-activation.sh runs VIPM activation unconditionally whenever a VIPM env file is supplied, with no check of LabVIEW's actual activation state; the precondition is a documented operator convention (the phase's usage text), not a runtime-enforced gate. Also corrected the real call chain (activate-vipm.sh is invoked by capture-activation.sh, not directly by complete-activation.sh)
• fix README.md: a second, still-present instance of the "LabVIEW/VIPM activation is human-only" overclaim (line 78, a different passage than the one already fixed) and a reintroduced "every ... required input" overclaim contradicting the same round's own "no built-in default" fix
• fix the wiki Architecture Packet: the Container/Component View tables still described Run-Pipeline.ps1/.sh together as the "Native SBOM pipeline" -- split into two rows, with Run-Pipeline.sh correctly described as the unrelated LabVIEWCLI tool it actually is (README.md/docs/sbom-pipeline/procedure.md were fixed in v0.3.26, the wiki was not)
• fix the wiki Architecture Packet's Deployment View: no longer asserts the Ubuntu package-build/signed-.vip capability is proven, since provision-ubuntu-vm.yml's package-build phase cannot currently succeed (#62, open)
• fix wiki REQ-007: still listed Run-Pipeline.sh as a "native SBOM pipeline script" with Dependency-Track fail-closed behavior it doesn't implement (same class of gap as the Architecture Packet fix above)
• fix docs/vm-provisioning/procedure.md's "no built-in default" wording: disclosed a real gap the previous round's correction didn't go far enough to catch -- batch-provision.sh never overrides guest_hostname/guest_full_name per VM, so every VM it creates in a single batch gets the identical in-guest hostname (vm-builder.local), a real same-hostname collision risk, not just a cosmetic placeholder
• fix docs/sbom-pipeline/procedure.md's ALLOW_PACKAGE_DRIFT default claim: it said =1 was the default; the real code only treats it as true when explicitly set to the literal string "1", so the real default is off
• fix docs/cm/cm-plan.md's unrendered [[Home]] wiki-link syntax (only the wiki itself supports [[...]]; replaced with a real link)
• fix docs/release/release-procedure.md: documented the already-practiced, legitimate no-op exception for the release/vX.Y.Z -> develop merge-back step when develop/main are already content-identical (this is what v0.3.24-v0.3.26 actually did, correctly, but the procedure didn't say so)
• fix the published v0.3.26 GitHub release notes, which were truncated by one bullet relative to the full CHANGELOG.md entry (a copy/paste range error, not a code change -- release notes text is editable, unlike the tag/assets)
• fix docs/information-item-map.md's baseline (bumped to this version)
• all findings from this verification-focused re-run of repo-standards-review@v0.2.23's --mode semantic-audit (same 3-model delegation, explicitly asked to verify whether v0.3.26's fixes actually held up): most of v0.3.26's fixes were confirmed genuinely SOLID this round (REQ-013/017/018/025/030, the Run-Pipeline.sh fix in README/sbom-pipeline docs, the CM Change Control disclosure); the gaps above are what a single-pass fix missed. #62/#63 updated with additional evidence (a REQ-001-violating hardcoded package name in the same broken package-build phase; a missing docs/projectbuddy-consumption.md; REQ-013's dangling "tracked separately" reference, now actually linked)