@@ -285,13 +285,17 @@ CLAWSWEEPER_MAX_REPAIRS_PER_HEAD=1
|
285 | 285 | |
286 | 286 | ## Security Boundary |
287 | 287 | |
288 | | -Do not stage security-sensitive work for ClawSweeper Repair. Route vulnerability |
289 | | -reports, CVE/GHSA/advisory work, leaked secrets/tokens/keys, plaintext secret |
290 | | -storage, SSRF, XSS, CSRF, RCE, auth bypass, privilege escalation, and sensitive |
291 | | -data exposure to central OpenClaw security handling. |
292 | | - |
293 | | -For adopted automerge jobs, trust deterministic ClawSweeper security markers, |
294 | | -labels, and job frontmatter; do not infer security handling from vague prose. |
| 288 | +Do not stage unapproved security-sensitive work for ClawSweeper Repair. Route |
| 289 | +vulnerability reports, CVE/GHSA/advisory work, leaked secrets/tokens/keys, |
| 290 | +plaintext secret storage, SSRF, XSS, CSRF, RCE, auth bypass, privilege |
| 291 | +escalation, and sensitive data exposure to central OpenClaw security handling. |
| 292 | + |
| 293 | +For PRs explicitly opted into `clawsweeper:autofix` or |
| 294 | +`clawsweeper:automerge`, security-sensitive review findings may dispatch |
| 295 | +bounded repair, but merge remains blocked until a later exact-head review is |
| 296 | +clean and the normal merge gates pass. Trust deterministic ClawSweeper security |
| 297 | +markers, labels, and job frontmatter; do not infer security handling from vague |
| 298 | +prose. |
295 | 299 | |
296 | 300 | ## Monitoring |
297 | 301 | |
|
