# Paths a drive run must not MODIFY. They exist in every tree — that is the
# difference from ops/FORBIDDEN_PATHS, which lists paths that must never exist
# at all and whose presence proves a stale sandbox.
#
# Conflating the two broke every run for half an hour: the harness files were
# added to FORBIDDEN_PATHS, the sync-time stale check saw them present in a
# perfectly good tree, and refused the sandbox with SYNC_FAIL_STALE_TREE. A
# guard that fires on healthy input is worse than no guard.
#
# Why these: autodrive delivered a PR reverting ops/deliver-run.sh, because the
# run predated a fix there. Unattended, a loop can silently undo the guards
# that decide whether its own output ships — including the guard that would
# have caught it.
ops/deliver-run.sh
ops/launch-gate.sh
ops/autodrive.sh
ops/gen-drive-cloud.py
ops/FORBIDDEN_PATHS
ops/IMMUTABLE_PATHS

# Ground truth and the findings log. A drive run launched from an older base
# will show later edits to these as deletions: run 7be717cb's PR removed 30
# lines from ops/BACKLOG.md that way. Assess legitimately writes ops/NEXT.md —
# that stays writable — but the record of what we have learned, and the file an
# assessor reads as truth, are not a run's to rewrite.
ops/BACKLOG.md
ops/STATE.md
ops/AUTODRIVE_BRIEF.md
