alex 4ef630b266 L2: record the pgrep -f tap141i0 hazard - it kills the guest, not just tcpdump ... QEMU's command line contains ifname=tap141i0, so pgrep -f on the tap name matches the VM alongside the capture. Stopping the tcpdump that way SIGTERM'd VM141. Nothing was lost (all artefacts were already off the guest and it restarted with a clean volume) but it is a plug-pull on an exclusively-held guest. Use pgrep -x tcpdump.		2026-09-08 18:31:00 -04:00
..
control-flow	L1: CDiff crosses at frame 50, and the AI client seed is fresh in every process	2026-09-08 18:23:19 -04:00
objects	board: lane L5 - reference pair non-deterministic; interest literals verified with a failing control; verified column held at 0 on principle	2026-09-08 17:55:47 -04:00
subsystems	L2: record the pgrep -f tap141i0 hazard - it kills the guest, not just tcpdump	2026-09-08 18:31:00 -04:00
.keep.md	init commit	2026-09-07 12:31:56 -04:00
00-strategy.md	strategy: phase 2 decisions (two repos, c++ shim, accrual order)	2026-09-07 17:10:21 -04:00
01-fingerprint.md	map: RTTI class inventory (1924 types, engine=Mars); reseed board with real targets	2026-09-07 14:48:43 -04:00
_template.md	scaffold RE campaign: board, backlog, findings template, verify tree	2026-09-07 14:40:44 -04:00