Runde SANDBOX v1.0.106 — the update-validation rig #146

Merged
zai merged 4 commits from pinky-v1106 into main 2026-10-30 01:39:19 +00:00
Member

The update-validation rig (update_sandbox.py +1170): sandbox first, GREEN or nothing — the constitution product side. Rebased onto v1.0.103; gates green (pinky-local).

The update-validation rig (update_sandbox.py +1170): sandbox first, GREEN or nothing — the constitution product side. Rebased onto v1.0.103; gates green (pinky-local).
zai agent added 1 commit 2026-10-29 16:46:01 +00:00
Cherry-pick of oss-oo/pinky-sandbox (v1.0.75, val-sandbox ACCEPT)
onto fresh origin/main (aa906ea), resolved semantically:

- Makefile/install.sh FILES lists: main's newer modules (oauthmint,
  sticky, app_driver, kiss_appserver, claude_door, claude-door-call)
  + update_sandbox.py
- stream.py: both imports, union of CLI commands/flags (update-sandbox
  beside wake-in/unit-watch/ci-watch/idlewatch-park/bg-*)
- fake_app_server.py: docstring + both mode blocks (stream_drop and ok)
- stream_functional_test.py: both appended groups (REGRESSFOLD-era and
  SANDBOX) + unioned final coverage string
- contract_tests.py: DROPPED the branch's obsolete no-arg lambdas
  (group_db/group_resume take ctx on main again); ADDED
  ZDO_ALLOW_TMP_CWD=1 to _stamp_rig_env + the vale probe env — the
  v1.0.75 TMPGUARD mirrors the canary's /tmp scratch cwds mid-probe
  (vale.precheck-fastfail + resume.autoresolve read prompt files from
  the moved-from path; latent for every --probe canary run since
  TMPGUARD, first caught by the update-sandbox rig)
- update_sandbox.py DISPATCHER_FILES: + oauthmint.py, sticky.py,
  kiss_appserver.py, claude_door.py (main's dispatch.py imports; the
  rig dispatcher copy crashed at import without them)

Gates (dedicated worktree ~/.zcode/tmp/oss-singularity/zcode-dispatch/
pinky-int-sandbox): env-stripped make functional EXIT 0 (SANDBOX green
2/2→2/2, RED refused on bundle.same-process-guard, scope clean); all
payload py_compile green. LOCAL only.
zai agent force-pushed pinky-v1106 from bed95cbf67
All checks were successful
Checks / Functional checks (pull_request) Successful in 39m38s
to f509bc2384
Some checks failed
Checks / Functional checks (pull_request) Has been cancelled
2026-10-29 17:28:47 +00:00
Compare
zai agent force-pushed pinky-v1106 from f509bc2384
Some checks failed
Checks / Functional checks (pull_request) Has been cancelled
to ce9626b104
Some checks failed
Checks / Functional checks (pull_request) Has been cancelled
2026-10-29 17:30:00 +00:00
Compare
zai agent force-pushed pinky-v1106 from ce9626b104
Some checks failed
Checks / Functional checks (pull_request) Has been cancelled
to 8fd483621e
Some checks failed
Checks / Functional checks (pull_request) Has been cancelled
2026-10-29 17:30:13 +00:00
Compare
zai agent force-pushed pinky-v1106 from 8fd483621e
Some checks failed
Checks / Functional checks (pull_request) Has been cancelled
to 660b517255
Some checks failed
Checks / Functional checks (pull_request) Has been cancelled
2026-10-29 17:32:43 +00:00
Compare
zai agent added 1 commit 2026-10-29 19:39:38 +00:00
SANDBOX fix: restore idlewatch-park in stream.py command choices
Some checks failed
Checks / Functional checks (pull_request) Failing after 39m41s
e33aca1f66
The post-STEERFELDER rebase dropped 'idlewatch-park' from main()'s
argparse choices while the handler, dispatch branch, and every flag
survived — the CLI died in argparse usage before the WHO refusal
logic, breaking the IDLEWATCH (8) impostor/refusal legs in
stream_functional_test (forge run 1890, Functional checks red on
660b517). One-word restore, no behavior change.
zai agent force-pushed pinky-v1106 from e33aca1f66
Some checks failed
Checks / Functional checks (pull_request) Failing after 39m41s
to 223e156861
Some checks failed
Checks / Functional checks (pull_request) Failing after 37m51s
2026-10-29 21:15:32 +00:00
Compare
zai agent added 1 commit 2026-10-29 22:46:45 +00:00
SANDBOX fix: contract canary exec prologue imports os
Some checks failed
Checks / Functional checks (pull_request) Failing after 40m35s
eb31f5f8af
The RESETSYNC constants (ZDO_NETWORK_REVIVAL_*, os.environ reads) sit
inside the QUOTA_ERROR_CLASS..harvest_quota_death source range that
contract_tests.py's classifier test execs with only 'import re'
prepended — on RESETSYNC main the exec dies with NameError: os, the
rig canary produces no shaped report, and every update-sandbox
validation refuses RED with 'rig boot failure'. The suite's own
classifier leg already prepends import os; the canary now matches.
Uncovered by the rebase of SANDBOX onto RESETSYNC main (forge runs
1893/1896/1897).
zai agent added 1 commit 2026-10-30 00:33:19 +00:00
SANDBOX fix: restore bg-register/bg-close in stream.py command choices
All checks were successful
Checks / Functional checks (pull_request) Successful in 40m56s
1991ff5b5e
Same rebase casualty as idlewatch-park: the BG-REGISTRY suite group's
subcommands vanished from argparse choices while their handlers,
dispatch branches, and flags survived — the legs died in argparse
usage (exit 2 with the choices dump) before any named refusal.
Found via a local podman repro of the CI container (root,
python:3.12-slim-bookworm) instead of guessing at unreachable forge
job logs.
zai agent merged commit b0ed6afae0 into main 2026-10-30 01:39:19 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
OSS-Singularity/zcode-dispatch!146
No description provided.