docs(afk-sleep-work): warn against runaway log files in last-breath trap

This commit is contained in:
Bluscream committed 2026-10-02 00:40:33 +02:00
1 parent dc666bc56b
commit 87a456cd31
1 file changed
+6 -4
+6 -4
View File
@@ -246,8 +246,9 @@ unfinished work leaves the environment in a broken, unusable state:
locks (`.git/index.lock`), or held database transactions.
- **Uncommitted state:** Unfinished rebases, stashes, or uncommitted modifications that confuse
subsequent runs or the user.
- **Zombie processes:** Orphaned background build daemons, open sockets, or runaway test loops
consuming host memory.
- **Zombie processes & runaway logs:** Orphaned background build daemons, file watchers, or detached
processes spewing infinite debug output into unrotated log files, silently exhausting disk space
while the agent is frozen or waiting for quota.
### The Controlled Landing protocol
@@ -257,8 +258,9 @@ guaranteed to finish and verify within the remaining budget):
1. **Stop scope expansion:** Refuse new goals, refactors, or dependency upgrades.
2. **Finish or roll back atomic units:** Complete the immediate atomic file edit or roll it back
cleanly (`git checkout -- <file>`) so the repository remains in a compiling, testable state.
3. **Terminate ephemeral processes:** Kill all background test runners, scratch servers, and
temporary debuggers.
3. **Terminate ephemeral processes & log streams:** Kill all background test runners, scratch
servers, watcher daemons, temporary debuggers, and detached tasks redirecting stdout/stderr
to unrotated files.
4. **Run verification gates:** Confirm `git status` is clean or staged cleanly, and the build passes.
5. **Commit atomic progress:** Commit completed, verified units with conventional commit messages so
progress is never lost if the session terminates abruptly.