gander: pin SSO and tester socket release argument order
This commit is contained in:
1 parent
0ca104accf
commit
84aea3063c
3 files changed
+27
No files matched your search
@@ -102,3 +102,5 @@ changes are planned before the batch. M1-M29 remain prepared and unexecuted.
|
||||
2026-10-21 sage-2063: driver uses only node --check for syntax validity; runtime test failures count as kills, and the r2 driver records GNU timeout process-group TERM/KILL exits so blocked descendants cannot survive. No rerun before next clear.
|
||||
|
||||
2026-10-21 r2 stop 2: base killer invocations 14/0 under 30 seconds each; M23-M27 killed, M28 survived due rebase making its generic mutation target the earlier SSO insertion. No M29 or golden suite run. Every restored hash and Git status clean; leftover process sweep count 0. Slot returned to Sage in gander-0035. Full per-step counts, base/mutant times and kill table in r2/run2/. Awaiting ruling before any fix or rerun; third stop goes to Mos.
|
||||
|
||||
2026-10-21 sage-2072 product test: added the merge-scoped SSO/socket conversion case without --send, asserting pointer argv order, rendered unit argv order, status agreement and no secret-file reads. Removing socket from sso_for_target is its planned RED case (M28b). Focused RED/GREEN remains pending the busy gate: Herb's suite was active at the preflight, so no test started. Runtime code unchanged. Mos mos-1197 owner-subject ruling recorded in queue-252/BUILD-NOTES.md.
|
||||
@@ -25,3 +25,9 @@ Next review is the manifest. No claim of implementation or live enablement.
|
||||
- N5: Extend readProcess's explicit environment allowlist for the Console nonce
|
||||
and subject metadata keys. Test missing/mismatched keys and distinct namespaces;
|
||||
J5 must reach that check. No token or cookie enters that environment or logs.
|
||||
|
||||
Mos ruling mos-1197, relayed by sage-2072 (2026-10-21T19:04:12Z): on dragon-lin,
|
||||
console.sso contains only Jason's sub, so one configured subject is one owner.
|
||||
No second subject is added without Jason. Host .54 is covered by #430. There
|
||||
is no Jason question now. This supersedes N1's proposed amendment question
|
||||
above; N2-N5 remain implementation items for the code round.
|
||||
Reference in new issue
Block a user