Skip to content

docs: the fs report prints, and a reader had no way to learn it stops there #363

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
AminChirazi merged 1 commit into from
Aug 1, 2026
Merged

docs: the fs report prints, and a reader had no way to learn it stops there #363

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions docs/agent-testing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -936,6 +936,15 @@ dropped, since the trap already proved the syscall happened. Only a syscall
whose *destructiveness* could not be adjudicated - an `openat2` whose
`open_how` was unreadable - is a fault.

**It prints, and it is not recorded.** There is no `fs` lane in the trace,
by decision rather than by omission: the report goes to stderr and nothing
survives the run. A lane was designed and declined, because a trace is a
COMMITTED artifact and these paths are absolute - `/home/alice/exports/
acme-corp-2025.csv` would be baked into a file that is reviewed and diffed
Comment on lines +941 to +943
forever. That is the same argument that keeps `execve` out of the trap set
for its argv. So this answers "what did that run destroy", never "what has
this flow destroyed since March".

**Punts, and they are real.** These are ATTEMPTS, not outcomes: the reply
goes out before the kernel runs the call, so an `rmdir` of a directory that
was not there reads exactly like one that removed a tree. `open(path,
Expand Down
Loading