@miller-tech/uap 1.190.1 → 1.190.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/package.json +1 -1
- package/src/policies/enforcers/__pycache__/_common.cpython-312.pyc +0 -0
- package/src/policies/enforcers/enforcement_self_protect.py +14 -0
- package/templates/hooks/__pycache__/deliver_autoroute.cpython-312.pyc +0 -0
- package/tools/agents/scripts/__pycache__/toolcall_path_normalizer.cpython-312.pyc +0 -0
package/package.json
CHANGED
|
Binary file
|
|
@@ -121,6 +121,20 @@ DESTRUCTIVE_VERBS = (
|
|
|
121
121
|
PROTECTED_EXEMPT = (
|
|
122
122
|
".uap/interaction/evidence",
|
|
123
123
|
"policies/waivers",
|
|
124
|
+
# The STOP file is a SIGNAL, not state. It lives under deliver-runs/ and so
|
|
125
|
+
# inherited that directory's protection, which made it un-removable — and a
|
|
126
|
+
# stop request you cannot withdraw is a trap: an unconsumed STOP ends the
|
|
127
|
+
# NEXT run at its first turn boundary, wasting a launch, with no way to
|
|
128
|
+
# clear it by hand.
|
|
129
|
+
#
|
|
130
|
+
# Seen live on 2026-08-10: an agent created one at 20:46:38 and its own
|
|
131
|
+
# `rm -f .uap/deliver-runs/STOP` three seconds later was refused. It cleared
|
|
132
|
+
# only because a run happened to start and consume it. That was luck.
|
|
133
|
+
#
|
|
134
|
+
# Removing it destroys nothing: the checkpoints are the run DIRECTORIES,
|
|
135
|
+
# which stay protected, and writing the file is already allowed — a remedy
|
|
136
|
+
# you can request but not withdraw is half a remedy.
|
|
137
|
+
".uap/deliver-runs/stop",
|
|
124
138
|
)
|
|
125
139
|
|
|
126
140
|
# Deliberately NARROW inside .uap/: that directory is mostly runtime state the
|
|
Binary file
|