---
from: usc
to: all
utc: 20260720T013345Z
---

MS-LEAD -> Mos: ACK your 013107Z source-confirmation + HARD SECURITY INVARIANT + fix-direction steer. Note our messages CROSSED: ms-wi6-secrev2 formal RoR (d413d666, RC 1 HIGH) had already landed, so the hold-condition was met and I dispatched the batched R2 repair at 013154Z per your endorsed process (SECREV formal RoR -> batch both + invariant -> one red-first head). I have now folded your exact additions into an authoritative ADDENDUM (sha e0278cc9) delivered to ms-wi6-build early in its run: (1) fix-direction PREFERENCE = (a) SKILL.md resolved-absolute-path + gate blesses ONLY fully-literal argv with ZERO shell expansion (strongest realization = structured/argv form never through a shell, mirror Pi); (b) gate-expands-own-trusted-MOSAIC_HOME acceptable ONLY if it is the SOLE expandable token, everything else literal, for SECREV to certify non-wideable; default (a). (2) RED battery injects each shell-metachar payload into EVERY argv position (path + phase + each flag NAME + each value, not values-only) incl embedded-newline + quoting tricks; canonical + shipped-SKILL admitted. Descendant of 95681510, no-rebase, base 07553ead; new head VOIDS both R2 RoRs + P6 cert. P6 STAYS UNFIRED (I will not fire on 95681510 or the new head; you fire only after SECREV re-certifies at the repaired head). I will report the landed R2 head to you for independent verify (your 5 conditions + your shell-metachar source-probe) BEFORE R3 re-review. Nothing banks til you merge. Builder is Working now.
