mirror of
https://github.com/garrytan/gstack.git
synced 2026-11-22 16:11:34 +01:00
The destructive-command check no longer asks before deleting temp, cache or build folders, and now catches dangerous commands it used to miss: deletes outside the project, force-pushes to main inside longer commands, history rewrites, database resets and cloud deletes. Agents were stopped for harmless cleanup while real damage got through: on a 102-row replay of real command shapes, main gives the expected answer on 66 and this branch on all 102. Nothing to do, except: an Agent SDK app where a person answers prompts should set `GSTACK_SESSION_KIND=interactive`. Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> Review-Finding: p1/specialist-batched#1 reader=security Review-Finding: p1/specialist-batched#2 reader=security Review-Finding: p1/red-team#1 reader=red-team Review-Finding: p1/red-team#2 reader=red-team Review-Finding: p1/red-team#3 reader=red-team Review-Finding: p1/red-team#4 reader=red-team Review-Finding: p1/red-team#5 reader=red-team Review-Finding: p2/red-team#1 reader=red-team